xenconsole: Could not read tty from store: No such file or directory

[zechao wang]

Hello everyone:

When i starting a linux domU, i get the error message: "xenconsole: Could not read tty from store: No such file or directory"

#xm create -c /etc/xen/fc6.cfg
Using config file ...
.......
xenconsole: Could not read tty from store: No such file or directory
-----------------
#xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 251 1 r----- 18.6
fc6 1 256 1 -b---- 0.2
------------------
#xm console 1
xenconsole: Could not read tty from store: No such file or directory

The "xenconsoled" process is running.
The directory "/var/run/xenstored/" is existent.

I searched, but get very little useful information!
Could someone give me some advice ? Thank you very much !




---------------------------------
Mp3·è¿ñËÑ-ОèÈÈžèžßËÙÏÂ

[Marcel Schroers]

Hi Zechao,

well I've had a similiar problem, maybe this will help you
to solve the problem:

Look for the following line in the file /etc/inittab of
you domU (try to mount the domU image in dom0 to edit the inittab
file of the vm):

co:2345:respawn:/sbin/mingetty console

If the line is missing simply add it to the inittab. Below
you find an example how (a part of) my inittab looks like.

-----
# Run gettys in standard runlevels
#
#line added to get a login prompt:
#(dont forget to comment out the following line)
#
co:2345:respawn:/sbin/mingetty console
#co:2345:respawn:/sbin/agetty xvc0 9600 vt100-nav

#1:2345:respawn:/sbin/mingetty tty1
#2:2345:respawn:/sbin/mingetty tty2
#3:2345:respawn:/sbin/mingetty tty3
#4:2345:respawn:/sbin/mingetty tty4
#5:2345:respawn:/sbin/mingetty tty5
#6:2345:respawn:/sbin/mingetty tty6
-------------



I hope this will solve your problem.


cheers,
marcel



Am 22.06.2007 um 05:03 schrieb zechao wang:

> Hello everyone:
>
> When i starting a linux domU, i get the error message: "xenconsole:
> Could not read tty from store: No such file or directory"
>
> #xm create -c /etc/xen/fc6.cfg
> Using config file ...
> .......
> xenconsole: Could not read tty from store: No such file or directory
> -----------------
> #xm list
> Name ID Mem VCPUs State Time(s)
> Domain-0 0 251 1 r----- 18.6
> fc6 1 256 1 -
> b---- 0.2
> ------------------
> #xm console 1
> xenconsole: Could not read tty from store: No such file or directory
>
> The "xenconsoled" process is running.
> The directory "/var/run/xenstored/" is existent.
>
> I searched, but get very little useful information!
> Could someone give me some advice ? Thank you very much !
>
>
>
> Mp3疯狂搜-新歌热歌高速下
> _______________________________________________
> Xen-users mailing list
> Xen-***@lists.xensource.com
> http://lists.xensource.com/xen-users

[Stephan Seitz]

Hi,

as this is currently on topic, does someone know how to get a tty
from a solaris 11 hvm domU?
The only information i found for solaris was for bare metal, where
it says 'if the keyboard is disconnect a serial console will be
available'.
Any suggestions?

Thanks in advance!

Stephan


Marcel Schroers schrieb:
> Hi Zechao,
>
> well I've had a similiar problem, maybe this will help you
> to solve the problem:
>
> Look for the following line in the file /etc/inittab of
> you domU (try to mount the domU image in dom0 to edit the inittab
> file of the vm):
>
> co:2345:respawn:/sbin/mingetty console
>

[Todd Deshane]

Hi,

On Feb 7, 2008 1:58 AM, Hamid Majidy <***@pcsourcenet.com> wrote:
>
>
>
>
> Hello Xen user list. This is to request installation help for a Xen 3.1
> guest domain. Xen installation source was CentOS 5.1 DVD. Dom0 and a guest
> (clientdom) have been installed, but clientdom cannot be connected to.
> Issuing command "xm create -c clientdom" generates message lines:
>
> Using config file "./clientdom".
>
> Started domain clientdom
>
> xenconsole: Could not read tty from store: No such file or directory
>
> "xen top" shows clientdom (as well as Domain-0) started, but "xm console
> clientdom" produces the same error, "xenconsole: Could not read tty from
> store: No such file or directory."
>
>

HVM guests as far as I know don't yet support consoles. You should use
either sdl=1 or vnc=1.

If you use vnc you should make sure that xen-config.sxp has the vnc
options enabled and configured to your liking. You may also need to
manually start the vncviewer to see the guest console. The default
setting when enabled let's you do vncviewer localhost.

Regards,
Todd

>
> Here's my clientdom file:
>
> name = "clientdom"
>
> uuid = "6bf7a6a0-d5c6-463e-a395-6d689a1819c5"
>
> maxmem = 256
>
> memory = 256
>
> vcpus = 1
>
> builder = "hvm"
>
> kernel = "/usr/lib/xen/boot/hvmloader"
>
> boot = "d"
>
> pae = 1
>
> acpi = 1
>
> apic = 1
>
> on_poweroff = "destroy"
>
> on_reboot = "restart"
>
> on_crash = "restart"
>
> device_model = "/usr/lib/xen/bin/qemu-dm"
>
> sdl = 0
>
> vnc = 0
>
> vncunused = 0
>
> vncdisplay = "-5900"
>
> disk = [
> "phy:/dev/VolGroup00/client,hda,w","file:/tmp/Centos5.1.iso,hdb:cdrom,r" ]
>
> #vif = [ "mac=00:16:3e:57:66:7d,bridge=xenbr0,type=ioemu" ]
>
> vif = [ "mac=00:16:3e:57:66:7d,bridge=xenbr0" ]
>
> serial = "pty"
>
>
>
> Several instances of the symptom have been encountered before, due to
> incorrect locations for hvmloader and qemu-dm, which seem to be in the
> correct locations in this case (/usr/lib/xen/boot & /usr/lib/xen/bin
> respectively).
>
>
>
> Has anyone else run into this and resolved it? Any advice greatly
> appreciated.
>
>
>
> Regards,
>
> Hamid.
> _______________________________________________
> Xen-users mailing list
> Xen-***@lists.xensource.com
> http://lists.xensource.com/xen-users
>

[Todd Deshane]

On Feb 7, 2008 11:47 AM, Todd Deshane <***@gmail.com> wrote:
> Hi,
>
> On Feb 7, 2008 1:58 AM, Hamid Majidy <***@pcsourcenet.com> wrote:
> >
> >
> >
> >
> > Hello Xen user list. This is to request installation help for a Xen 3.1
> > guest domain. Xen installation source was CentOS 5.1 DVD. Dom0 and a guest
> > (clientdom) have been installed, but clientdom cannot be connected to.
> > Issuing command "xm create -c clientdom" generates message lines:
> >
> > Using config file "./clientdom".
> >
> > Started domain clientdom
> >
> > xenconsole: Could not read tty from store: No such file or directory
> >
> > "xen top" shows clientdom (as well as Domain-0) started, but "xm console
> > clientdom" produces the same error, "xenconsole: Could not read tty from
> > store: No such file or directory."
> >
> >
>
> HVM guests as far as I know don't yet support consoles. You should use
> either sdl=1 or vnc=1.
>
> If you use vnc you should make sure that xen-config.sxp has the vnc
> options enabled and configured to your liking. You may also need to
> manually start the vncviewer to see the guest console. The default
> setting when enabled let's you do vncviewer localhost.
>

Also, don't pass the -c on the command line, since you can't get an
initial (text) console with the HVM guest.


> Regards,
> Todd
>
>
> >
> > Here's my clientdom file:
> >
> > name = "clientdom"
> >
> > uuid = "6bf7a6a0-d5c6-463e-a395-6d689a1819c5"
> >
> > maxmem = 256
> >
> > memory = 256
> >
> > vcpus = 1
> >
> > builder = "hvm"
> >
> > kernel = "/usr/lib/xen/boot/hvmloader"
> >
> > boot = "d"
> >
> > pae = 1
> >
> > acpi = 1
> >
> > apic = 1
> >
> > on_poweroff = "destroy"
> >
> > on_reboot = "restart"
> >
> > on_crash = "restart"
> >
> > device_model = "/usr/lib/xen/bin/qemu-dm"
> >
> > sdl = 0
> >
> > vnc = 0
> >
> > vncunused = 0
> >
> > vncdisplay = "-5900"
> >
> > disk = [
> > "phy:/dev/VolGroup00/client,hda,w","file:/tmp/Centos5.1.iso,hdb:cdrom,r" ]
> >
> > #vif = [ "mac=00:16:3e:57:66:7d,bridge=xenbr0,type=ioemu" ]
> >
> > vif = [ "mac=00:16:3e:57:66:7d,bridge=xenbr0" ]
> >
> > serial = "pty"
> >
> >
> >
> > Several instances of the symptom have been encountered before, due to
> > incorrect locations for hvmloader and qemu-dm, which seem to be in the
> > correct locations in this case (/usr/lib/xen/boot & /usr/lib/xen/bin
> > respectively).
> >
> >
> >
> > Has anyone else run into this and resolved it? Any advice greatly
> > appreciated.
> >
> >
> >
> > Regards,
> >
> > Hamid.
> > _______________________________________________
> > Xen-users mailing list
> > Xen-***@lists.xensource.com
> > http://lists.xensource.com/xen-users
> >
>

[Sadique Puthen]

Todd Deshane wrote:
> On Feb 7, 2008 11:47 AM, Todd Deshane <***@gmail.com> wrote:
>
>> Hi,
>>
>> On Feb 7, 2008 1:58 AM, Hamid Majidy <***@pcsourcenet.com> wrote:
>>
>>>
>>>
>>> Hello Xen user list. This is to request installation help for a Xen 3.1
>>> guest domain. Xen installation source was CentOS 5.1 DVD. Dom0 and a guest
>>> (clientdom) have been installed, but clientdom cannot be connected to.
>>> Issuing command "xm create -c clientdom" generates message lines:
>>>
>>> Using config file "./clientdom".
>>>
>>> Started domain clientdom
>>>
>>> xenconsole: Could not read tty from store: No such file or directory
>>>
>>> "xen top" shows clientdom (as well as Domain-0) started, but "xm console
>>> clientdom" produces the same error, "xenconsole: Could not read tty from
>>> store: No such file or directory."
>>>
>>>
>>>
>> HVM guests as far as I know don't yet support consoles. You should use
>> either sdl=1 or vnc=1.
>>
>> If you use vnc you should make sure that xen-config.sxp has the vnc
>> options enabled and configured to your liking. You may also need to
>> manually start the vncviewer to see the guest console. The default
>> setting when enabled let's you do vncviewer localhost.
>>
>>
>
> Also, don't pass the -c on the command line, since you can't get an
> initial (text) console with the HVM guest.
>

This is not true. If you are running a Linux/Unix guest as HVM, you can
get the initial boot messages and text console if you pass -c to the "xm
create", but only after you configured your kernel to pass boot messages
to serial console. Start up of a linux hvm guest on my system looks as
below.

[***@dhcp6-7 ~]# xm create rhel4_hvm -c
Using config file "/etc/xen/rhel4_hvm".
Started domain rhel4_hvm
Bootdata ok (command line is ro root=/dev/VolGroup00/LogVol00 console=ttyS0)
Linux version 2.6.9-68.11.EL (***@hs20-bc1-7.build.redhat.com)
(gcc version 3.4.6 20060404 (Red Hat 3.4.6-9)) #1 Thu Feb 7 16:31:37 EST
2008
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001f3fac00 (usable)
BIOS-e820: 000000001f3fac00 - 000000001f400000 (reserved)
DMI 2.4 present.
ACPI: PM-Timer IO Port: 0x1f48
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 15:6 APIC version 16
Setting APIC routing to flat
ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-47
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 low level)
ACPI: INT_SRC_OVR (bus 0 bus_irq 7 global_irq 7 low level)
ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 low level)
ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 low level)
ACPI: HPET id: 0x8086a201 base: 0xfed00000
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 20000000 (gap: 1f400000:e0c00000)
Checking aperture...
Built 1 zonelists
Kernel command line: ro root=/dev/VolGroup00/LogVol00 console=ttyS0
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 65536 bytes)
time.c: Using 93.521442 MHz HPET timer.
time.c: Detected 2992.891 MHz processor.
time.c: Using HPET/TSC based timekeeping.
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Memory: 497176k/511976k available (2452k kernel code, 14036k reserved,
1340k data, 180k init)
Calibrating delay using timer specific routine.. 6022.76 BogoMIPS
(lpj=3011382)
Security Scaffold v1.0.0 initialized
SELinux: Initializing.
selinux_register_security: Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 256 (order: 0, 4096 bytes)
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 2048K
CPU: Intel(R) Xeon(TM) CPU 3.00GHz stepping 04
Using IO APIC NMI watchdog
activating NMI Watchdog ... done.
testing NMI watchdog ... CPU#0: NMI appears to be stuck (0)!
Using local APIC timer interrupts.
Detected 6.250 MHz APIC timer.
checking if image is initramfs... it is
NET: Registered protocol family 16
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20040816
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
ACPI: PCI Interrupt Link [LNKA] (IRQs *5 7 10 11)
ACPI: PCI Interrupt Link [LNKB] (IRQs 5<7>Losing some ticks... checking
if CPU frequency changed.
*7 10 11)
ACPI: PCI Interrupt Link [LNKC] (IRQs 5 7 *10 11)
ACPI: PCI Interrupt Link [LNKD] (IRQs 5 7 10 *11)
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
GSI 16 sharing vector 0xA9 and IRQ 16
ACPI: PCI Interrupt 0000:00:01.2[A] -> GSI 20 (level, low) -> IRQ 169
GSI 17 sharing vector 0xB1 and IRQ 17
ACPI: PCI Interrupt 0000:00:01.3[D] -> GSI 23 (level, low) -> IRQ 177
GSI 18 sharing vector 0xB9 and IRQ 18
ACPI: PCI Interrupt 0000:00:03.0[A] -> GSI 28 (level, low) -> IRQ 185
GSI 19 sharing vector 0xC1 and IRQ 19
ACPI: PCI Interrupt 0000:00:04.0[A] -> GSI 32 (level, low) -> IRQ 193
PCI-DMA: Disabling IOMMU.
IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $
audit: initializing netlink socket (disabled)
audit(1204543653.927:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Initializing Cryptographic API
ksign: Installing public key data
Loading keyring
- Added public key 4148DC44653573
- User ID: Red Hat, Inc. (Kernel Module GPG key)
Limiting direct PCI/PCI transfers.
PCI: PIIX3: Enabling Passive Release on 0000:00:01.0
Activating ISA DMA hang workarounds.
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
ACPI: Processor [PR00] (supports C1)
Real Time Clock Driver v1.12
Linux agpgart interface v0.100 (c) Dave Jones
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 68 ports, IRQ sharing enabled
�ttyS0 at I/O 0x3f8 (irq = 4) is a 16450
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX3: IDE controller at PCI slot 0000:00:01.1
PIIX3: chipset revision 0
PIIX3: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:pio
hda: QEMU HARDDISK, ATA DISK drive
hdb: QEMU HARDDISK, ATA DISK drive
Using cfq io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: max request size: 1024KiB
hda: 10240000 sectors (5242 MB) w/256KiB Cache, CHS=10158/255/63, (U)DMA
hda: hda1 hda2
hdb: max request size: 1024KiB
hdb: 19531250 sectors (10000 MB) w/256KiB Cache, CHS=16383/255/63, (U)DMA
hdb: hdb1
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard on isa0060/serio0
input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 7, 917504 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
ACPI wakeup devices:

ACPI: (supports S5)
Freeing unused kernel memory: 180k freed
Red Hat nash version 4.2.1.13 starting
Mounted /proc filesystem
Mounting sysfs
Creating /dev
Starting udev
Loading dm-mod.ko module
device-mapper: 4.5.5-ioctl (2006-12-01) initialised: dm-***@redhat.com
Loading jbd.ko module
Loading ext3.ko module
Loading dm-mirror.ko module
Loading dm-zero.ko module
Loading dm-snapshot.ko module
Making device-mapper control node
Scanning logical volumes
Reading all physical volumes. This may take a while...
Found volume group "VolGroup00" using metadata type lvm2
Activating logical volumes
2 logical volume(s) in volume group "VolGroup00" now active
Creating root device
Mounting root filesystem
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Switching to new root
SELinux: Disabled at runtime.
INIT: version 2.85 booting
Setting default font (latarcyrheb-sun16): [ OK ]

Welcome to Red Hat Enterprise Linux AS
Press 'I' to enter interactive startup.
Setting clock (localtime): Mon Mar 3 11:27:44 IST 2008 [ OK ]
Starting udev: [ OK ]
............
.............................

--Sadique
>
>
>> Regards,
>> Todd
>>
>>
>>
>>> Here's my clientdom file:
>>>
>>> name = "clientdom"
>>>
>>> uuid = "6bf7a6a0-d5c6-463e-a395-6d689a1819c5"
>>>
>>> maxmem = 256
>>>
>>> memory = 256
>>>
>>> vcpus = 1
>>>
>>> builder = "hvm"
>>>
>>> kernel = "/usr/lib/xen/boot/hvmloader"
>>>
>>> boot = "d"
>>>
>>> pae = 1
>>>
>>> acpi = 1
>>>
>>> apic = 1
>>>
>>> on_poweroff = "destroy"
>>>
>>> on_reboot = "restart"
>>>
>>> on_crash = "restart"
>>>
>>> device_model = "/usr/lib/xen/bin/qemu-dm"
>>>
>>> sdl = 0
>>>
>>> vnc = 0
>>>
>>> vncunused = 0
>>>
>>> vncdisplay = "-5900"
>>>
>>> disk = [
>>> "phy:/dev/VolGroup00/client,hda,w","file:/tmp/Centos5.1.iso,hdb:cdrom,r" ]
>>>
>>> #vif = [ "mac=00:16:3e:57:66:7d,bridge=xenbr0,type=ioemu" ]
>>>
>>> vif = [ "mac=00:16:3e:57:66:7d,bridge=xenbr0" ]
>>>
>>> serial = "pty"
>>>
>>>
>>>
>>> Several instances of the symptom have been encountered before, due to
>>> incorrect locations for hvmloader and qemu-dm, which seem to be in the
>>> correct locations in this case (/usr/lib/xen/boot & /usr/lib/xen/bin
>>> respectively).
>>>
>>>
>>>
>>> Has anyone else run into this and resolved it? Any advice greatly
>>> appreciated.
>>>
>>>
>>>
>>> Regards,
>>>
>>> Hamid.
>>> _______________________________________________
>>> Xen-users mailing list
>>> Xen-***@lists.xensource.com
>>> http://lists.xensource.com/xen-users
>>>
>>>
>
> _______________________________________________
> Xen-users mailing list
> Xen-***@lists.xensource.com
> http://lists.xensource.com/xen-users
>
>

[Rudi Ahlers]

Sadique Puthen wrote:
> Todd Deshane wrote:
>> On Feb 7, 2008 11:47 AM, Todd Deshane <***@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> On Feb 7, 2008 1:58 AM, Hamid Majidy <***@pcsourcenet.com> wrote:
>>>
>>>>
>>>>
>>>> Hello Xen user list. This is to request installation help for a Xen
>>>> 3.1
>>>> guest domain. Xen installation source was CentOS 5.1 DVD. Dom0 and
>>>> a guest
>>>> (clientdom) have been installed, but clientdom cannot be connected to.
>>>> Issuing command "xm create -c clientdom" generates message lines:
>>>>
>>>> Using config file "./clientdom".
>>>>
>>>> Started domain clientdom
>>>>
>>>> xenconsole: Could not read tty from store: No such file or directory
>>>>
>>>> "xen top" shows clientdom (as well as Domain-0) started, but "xm
>>>> console
>>>> clientdom" produces the same error, "xenconsole: Could not read tty
>>>> from
>>>> store: No such file or directory."
>>>>
>>>>
>>>>
>>> HVM guests as far as I know don't yet support consoles. You should use
>>> either sdl=1 or vnc=1.
>>>
>>> If you use vnc you should make sure that xen-config.sxp has the vnc
>>> options enabled and configured to your liking. You may also need to
>>> manually start the vncviewer to see the guest console. The default
>>> setting when enabled let's you do vncviewer localhost.
>>>
>>>
>>
>> Also, don't pass the -c on the command line, since you can't get an
>> initial (text) console with the HVM guest.
>>
>
> This is not true. If you are running a Linux/Unix guest as HVM, you
> can get the initial boot messages and text console if you pass -c to
> the "xm create", but only after you configured your kernel to pass
> boot messages to serial console. Start up of a linux hvm guest on my
> system looks as below.
>

< --snip -->

Ok, so how does one fix this problem? I'm having the exact same problem
(xenconsole: Could not read tty from store: No such file or
directory) when trying to install CentOS 5.1 i386 or Fedora Core 7 i386
on CentOS 5.1 x64

--

Kind Regards
Rudi Ahlers
CEO, SoftDux

Web: http://www.SoftDux.com
Check out my technical blog, http://blog.softdux.com for Linux or other technical stuff, or visit http://www.WebHostingTalk.co.za for Web Hosting stugg

[Rudi Ahlers]

Sadique Puthen wrote:
> Todd Deshane wrote:
>> On Feb 7, 2008 11:47 AM, Todd Deshane <***@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> On Feb 7, 2008 1:58 AM, Hamid Majidy <***@pcsourcenet.com> wrote:
>>>
>>>>
>>>>
>>>> Hello Xen user list. This is to request installation help for a Xen
>>>> 3.1
>>>> guest domain. Xen installation source was CentOS 5.1 DVD. Dom0 and
>>>> a guest
>>>> (clientdom) have been installed, but clientdom cannot be connected to.
>>>> Issuing command "xm create -c clientdom" generates message lines:
>>>>
>>>> Using config file "./clientdom".
>>>>
>>>> Started domain clientdom
>>>>
>>>> xenconsole: Could not read tty from store: No such file or directory
>>>>
>>>> "xen top" shows clientdom (as well as Domain-0) started, but "xm
>>>> console
>>>> clientdom" produces the same error, "xenconsole: Could not read tty
>>>> from
>>>> store: No such file or directory."
>>>>
>>>>
>>>>
>>> HVM guests as far as I know don't yet support consoles. You should use
>>> either sdl=1 or vnc=1.
>>>
>>> If you use vnc you should make sure that xen-config.sxp has the vnc
>>> options enabled and configured to your liking. You may also need to
>>> manually start the vncviewer to see the guest console. The default
>>> setting when enabled let's you do vncviewer localhost.
>>>
>>>
>>
>> Also, don't pass the -c on the command line, since you can't get an
>> initial (text) console with the HVM guest.
>>
>
> This is not true. If you are running a Linux/Unix guest as HVM, you
> can get the initial boot messages and text console if you pass -c to
> the "xm create", but only after you configured your kernel to pass
> boot messages to serial console. Start up of a linux hvm guest on my
> system looks as below.
>
> [***@dhcp6-7 ~]# xm create rhel4_hvm -c
> Using config file "/etc/xen/rhel4_hvm".
> Started domain rhel4_hvm
> Bootdata ok (command line is ro root=/dev/VolGroup00/LogVol00
> console=ttyS0)
> Linux version 2.6.9-68.11.EL (***@hs20-bc1-7.build.redhat.com)
> (gcc version 3.4.6 20060404 (Red Hat 3.4.6-9)) #1 Thu Feb 7 16:31:37
> EST 2008
> BIOS-provided physical RAM map:
> BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
> BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
> BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
> BIOS-e820: 0000000000100000 - 000000001f3fac00 (usable)
> BIOS-e820: 000000001f3fac00 - 000000001f400000 (reserved)
> DMI 2.4 present.
> ACPI: PM-Timer IO Port: 0x1f48
> ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
> Processor #0 15:6 APIC version 16
> Setting APIC routing to flat
> ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
> IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-47
> ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
> ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 low level)
> ACPI: INT_SRC_OVR (bus 0 bus_irq 7 global_irq 7 low level)
> ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 low level)
> ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 low level)
> ACPI: HPET id: 0x8086a201 base: 0xfed00000
> Using ACPI (MADT) for SMP configuration information
> Allocating PCI resources starting at 20000000 (gap: 1f400000:e0c00000)
> Checking aperture...
> Built 1 zonelists
> Kernel command line: ro root=/dev/VolGroup00/LogVol00 console=ttyS0
> Initializing CPU#0
> PID hash table entries: 2048 (order: 11, 65536 bytes)
> time.c: Using 93.521442 MHz HPET timer.
> time.c: Detected 2992.891 MHz processor.
> time.c: Using HPET/TSC based timekeeping.
> Console: colour VGA+ 80x25
> Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
> Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
> Memory: 497176k/511976k available (2452k kernel code, 14036k reserved,
> 1340k data, 180k init)
> Calibrating delay using timer specific routine.. 6022.76 BogoMIPS
> (lpj=3011382)
> Security Scaffold v1.0.0 initialized
> SELinux: Initializing.
> selinux_register_security: Registering secondary module capability
> Capability LSM initialized as secondary
> Mount-cache hash table entries: 256 (order: 0, 4096 bytes)
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 2048K
> CPU: Intel(R) Xeon(TM) CPU 3.00GHz stepping 04
> Using IO APIC NMI watchdog
> activating NMI Watchdog ... done.
> testing NMI watchdog ... CPU#0: NMI appears to be stuck (0)!
> Using local APIC timer interrupts.
> Detected 6.250 MHz APIC timer.
> checking if image is initramfs... it is
> NET: Registered protocol family 16
> PCI: Using configuration type 1
> mtrr: v2.0 (20020519)
> ACPI: Subsystem revision 20040816
> ACPI: Interpreter enabled
> ACPI: Using IOAPIC for interrupt routing
> ACPI: PCI Root Bridge [PCI0] (00:00)
> PCI: Probing PCI hardware (bus 00)
> ACPI: PCI Interrupt Link [LNKA] (IRQs *5 7 10 11)
> ACPI: PCI Interrupt Link [LNKB] (IRQs 5<7>Losing some ticks...
> checking if CPU frequency changed.
> *7 10 11)
> ACPI: PCI Interrupt Link [LNKC] (IRQs 5 7 *10 11)
> ACPI: PCI Interrupt Link [LNKD] (IRQs 5 7 10 *11)
> usbcore: registered new driver usbfs
> usbcore: registered new driver hub
> PCI: Using ACPI for IRQ routing
> GSI 16 sharing vector 0xA9 and IRQ 16
> ACPI: PCI Interrupt 0000:00:01.2[A] -> GSI 20 (level, low) -> IRQ 169
> GSI 17 sharing vector 0xB1 and IRQ 17
> ACPI: PCI Interrupt 0000:00:01.3[D] -> GSI 23 (level, low) -> IRQ 177
> GSI 18 sharing vector 0xB9 and IRQ 18
> ACPI: PCI Interrupt 0000:00:03.0[A] -> GSI 28 (level, low) -> IRQ 185
> GSI 19 sharing vector 0xC1 and IRQ 19
> ACPI: PCI Interrupt 0000:00:04.0[A] -> GSI 32 (level, low) -> IRQ 193
> PCI-DMA: Disabling IOMMU.
> IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $
> audit: initializing netlink socket (disabled)
> audit(1204543653.927:1): initialized
> Total HugeTLB memory allocated, 0
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
> Initializing Cryptographic API
> ksign: Installing public key data
> Loading keyring
> - Added public key 4148DC44653573
> - User ID: Red Hat, Inc. (Kernel Module GPG key)
> Limiting direct PCI/PCI transfers.
> PCI: PIIX3: Enabling Passive Release on 0000:00:01.0
> Activating ISA DMA hang workarounds.
> pci_hotplug: PCI Hot Plug PCI Core version: 0.5
> ACPI: Processor [PR00] (supports C1)
> Real Time Clock Driver v1.12
> Linux agpgart interface v0.100 (c) Dave Jones
> serio: i8042 AUX port at 0x60,0x64 irq 12
> serio: i8042 KBD port at 0x60,0x64 irq 1
> Serial: 8250/16550 driver $Revision: 1.90 $ 68 ports, IRQ sharing enabled
> �ttyS0 at I/O 0x3f8 (irq = 4) is a 16450
> RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 33MHz system bus speed for PIO modes; override with
> idebus=xx
> PIIX3: IDE controller at PCI slot 0000:00:01.1
> PIIX3: chipset revision 0
> PIIX3: not 100% native mode: will probe irqs later
> ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:pio, hdb:pio
> ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:pio
> hda: QEMU HARDDISK, ATA DISK drive
> hdb: QEMU HARDDISK, ATA DISK drive
> Using cfq io scheduler
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> hda: max request size: 1024KiB
> hda: 10240000 sectors (5242 MB) w/256KiB Cache, CHS=10158/255/63, (U)DMA
> hda: hda1 hda2
> hdb: max request size: 1024KiB
> hdb: 19531250 sectors (10000 MB) w/256KiB Cache, CHS=16383/255/63, (U)DMA
> hdb: hdb1
> ide-floppy driver 0.99.newide
> usbcore: registered new driver hiddev
> usbcore: registered new driver usbhid
> drivers/usb/input/hid-core.c: v2.0:USB HID core driver
> mice: PS/2 mouse device common for all mice
> input: AT Translated Set 2 keyboard on isa0060/serio0
> input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1
> md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
> NET: Registered protocol family 2
> IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
> TCP established hash table entries: 16384 (order: 5, 131072 bytes)
> TCP bind hash table entries: 16384 (order: 7, 917504 bytes)
> TCP: Hash tables configured (established 16384 bind 16384)
> Initializing IPsec netlink socket
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> ACPI wakeup devices:
>
> ACPI: (supports S5)
> Freeing unused kernel memory: 180k freed
> Red Hat nash version 4.2.1.13 starting
> Mounted /proc filesystem
> Mounting sysfs
> Creating /dev
> Starting udev
> Loading dm-mod.ko module
> device-mapper: 4.5.5-ioctl (2006-12-01) initialised: dm-***@redhat.com
> Loading jbd.ko module
> Loading ext3.ko module
> Loading dm-mirror.ko module
> Loading dm-zero.ko module
> Loading dm-snapshot.ko module
> Making device-mapper control node
> Scanning logical volumes
> Reading all physical volumes. This may take a while...
> Found volume group "VolGroup00" using metadata type lvm2
> Activating logical volumes
> 2 logical volume(s) in volume group "VolGroup00" now active
> Creating root device
> Mounting root filesystem
> kjournald starting. Commit interval 5 seconds
> EXT3-fs: mounted filesystem with ordered data mode.
> Switching to new root
> SELinux: Disabled at runtime.
> INIT: version 2.85 booting
> Setting default font (latarcyrheb-sun16): [ OK ]
>
> Welcome to Red Hat Enterprise Linux AS
> Press 'I' to enter interactive startup.
> Setting clock (localtime): Mon Mar 3 11:27:44 IST 2008 [ OK ]
> Starting udev: [ OK ]
> ............
> .............................
>
> --Sadique
I'm sitting with this exact same problem. My Linux HVM guests doesn't
output any console info, and instead I get an error: xenconsole: Could
not read tty from store: No such file or directory

[***@pc-00059 ~]# xm console cPanel

xenconsole: Could not read tty from store: No such file or directory


So, how do I get my Linux HVM domU guest's to work on the console?

--

Kind Regards
Rudi Ahlers
CEO, SoftDux

Web: http://www.SoftDux.com
Check out my technical blog, http://blog.softdux.com for Linux or other technical stuff, or visit http://www.WebHostingTalk.co.za for Web Hosting stuff

[Sadique Puthen]

Todd Deshane wrote:
> Hi,
>
> On Feb 7, 2008 1:58 AM, Hamid Majidy <***@pcsourcenet.com> wrote:
>
>>
>>
>> Hello Xen user list. This is to request installation help for a Xen 3.1
>> guest domain. Xen installation source was CentOS 5.1 DVD. Dom0 and a guest
>> (clientdom) have been installed, but clientdom cannot be connected to.
>> Issuing command "xm create -c clientdom" generates message lines:
>>
>> Using config file "./clientdom".
>>
>> Started domain clientdom
>>
>> xenconsole: Could not read tty from store: No such file or directory
>>
>> "xen top" shows clientdom (as well as Domain-0) started, but "xm console
>> clientdom" produces the same error, "xenconsole: Could not read tty from
>> store: No such file or directory."
>>
>>
>>
>
> HVM guests as far as I know don't yet support consoles.

This may be true for windows, but Linux hvm guests really supports
consoles through serial consoles.

For fully virt (Linux): ---

Edit guest configuration file and add "serial = pty"

Then edit guest grub.conf file and add console=ttyS0 to kernel line and
add "co:2345:respawn:/sbin/agetty ttyS0 9600 vt100-nav" to your
/etc/inittab.

--Sadique
> You should use
> either sdl=1 or vnc=1.
>
> If you use vnc you should make sure that xen-config.sxp has the vnc
> options enabled and configured to your liking. You may also need to
> manually start the vncviewer to see the guest console. The default
> setting when enabled let's you do vncviewer localhost.
>
> Regards,
> Todd
>
>
>> Here's my clientdom file:
>>
>> name = "clientdom"
>>
>> uuid = "6bf7a6a0-d5c6-463e-a395-6d689a1819c5"
>>
>> maxmem = 256
>>
>> memory = 256
>>
>> vcpus = 1
>>
>> builder = "hvm"
>>
>> kernel = "/usr/lib/xen/boot/hvmloader"
>>
>> boot = "d"
>>
>> pae = 1
>>
>> acpi = 1
>>
>> apic = 1
>>
>> on_poweroff = "destroy"
>>
>> on_reboot = "restart"
>>
>> on_crash = "restart"
>>
>> device_model = "/usr/lib/xen/bin/qemu-dm"
>>
>> sdl = 0
>>
>> vnc = 0
>>
>> vncunused = 0
>>
>> vncdisplay = "-5900"
>>
>> disk = [
>> "phy:/dev/VolGroup00/client,hda,w","file:/tmp/Centos5.1.iso,hdb:cdrom,r" ]
>>
>> #vif = [ "mac=00:16:3e:57:66:7d,bridge=xenbr0,type=ioemu" ]
>>
>> vif = [ "mac=00:16:3e:57:66:7d,bridge=xenbr0" ]
>>
>> serial = "pty"
>>
>>
>>
>> Several instances of the symptom have been encountered before, due to
>> incorrect locations for hvmloader and qemu-dm, which seem to be in the
>> correct locations in this case (/usr/lib/xen/boot & /usr/lib/xen/bin
>> respectively).
>>
>>
>>
>> Has anyone else run into this and resolved it? Any advice greatly
>> appreciated.
>>
>>
>>
>> Regards,
>>
>> Hamid.
>> _______________________________________________
>> Xen-users mailing list
>> Xen-***@lists.xensource.com
>> http://lists.xensource.com/xen-users
>>
>>
>
> _______________________________________________
> Xen-users mailing list
> Xen-***@lists.xensource.com
> http://lists.xensource.com/xen-users
>
>

[Hamid Majidy]

Thank you, Sadique, Todd & Tait for your helpful suggestions. Unfortunately
I am still having the same issue, despite all of your suggestions.



Here's a summary of changes:

1. added console=ttyS0 to kernel line of /boot/grub/grub.conf (Sadique)

2. added "co:2345:respawn:/sbin/agetty ttyS0 9600 vt100-nav" to /etc/inittab
(Sadique)

3. rebooted server (common sense)

4. installed LibVNCServer-0.9.1 (Todd)

5. enabled vnc params in guest VM config file (Todd, Tait)



Also changed disk configuration, as the physical disk subsystem is SAS, so I
though it might have an issue since the system has no /dev/hd* drivers
present.



Now I have in /etc/xen/clientdom:

name = "clientdom"

uuid = "6bf7a6a0-d5c6-463e-a395-6d689a1819c5"

maxmem = 256

memory = 256

vcpus = 1

builder = "hvm"

kernel = "/usr/lib/xen/boot/hvmloader"

boot = "d"

pae = 1

acpi = 1

apic = 1

on_poweroff = "destroy"

on_reboot = "restart"

on_crash = "restart"

[***@auntie xen]# cat /etc/xen/clientdom

name = "clientdom"

uuid = "6bf7a6a0-d5c6-463e-a395-6d689a1819c5"

maxmem = 256

memory = 256

vcpus = 1

builder = "hvm"

kernel = "/usr/lib/xen/boot/hvmloader"

boot = "d"

pae = 1

acpi = 1

apic = 1

on_poweroff = "destroy"

on_reboot = "restart"

on_crash = "restart"

device_model = "/usr/lib/xen/bin/qemu-dm"

sdl = 0

vnc = 1

vncviewer = 1

vncdisplay = "5900"

disk = [
"phy:/dev/VolGroup00/client,ioemu:sda,w","file:/tmp/Centos5.1.iso,sdb:cdrom,
r" ]

vif = [ "mac=00:16:3e:57:66:7d,bridge=xenbr0" ]

serial = "pty"



But I still get "xenconsole: Could not read tty from store: No such file or
directory" upon "xm console clientdom".



When I start guest with "xm create clientdom", I get:

xm create clientdom

Using config file "./clientdom".

VNC= 3

Started domain clientdom



But when I try to connect to it with "vncviewer 192.168.122.1:5900" I get:

VNC Viewer Free Edition 4.1.2 for X - built Mar 14 2007 22:51:02

Copyright (C) 2002-2005 RealVNC Ltd.

See http://www.realvnc.com for information on VNC.

vncviewer: unable to open display ""



Any ideas? All feedback greatly appreciated.



Thanks,

Hamid.



-----Original Message-----
From: xen-users-***@lists.xensource.com
[mailto:xen-users-***@lists.xensource.com] On Behalf Of Sadique Puthen
Sent: Thursday, February 07, 2008 9:57 AM
To: ***@gmail.com
Cc: Hamid Majidy; xen-***@lists.xensource.com
Subject: Re: [Xen-users] xenconsole: Could not read tty from store: No
suchfile or directory



Todd Deshane wrote:

> Hi,

>

> On Feb 7, 2008 1:58 AM, Hamid Majidy <***@pcsourcenet.com> wrote:

>

>>

>>

>> Hello Xen user list. This is to request installation help for a Xen 3.1

>> guest domain. Xen installation source was CentOS 5.1 DVD. Dom0 and a
guest

>> (clientdom) have been installed, but clientdom cannot be connected to.

>> Issuing command "xm create -c clientdom" generates message lines:

>>

>> Using config file "./clientdom".

>>

>> Started domain clientdom

>>

>> xenconsole: Could not read tty from store: No such file or directory

>>

>> "xen top" shows clientdom (as well as Domain-0) started, but "xm console

>> clientdom" produces the same error, "xenconsole: Could not read tty from

>> store: No such file or directory."

>>

>>

>>

>

> HVM guests as far as I know don't yet support consoles.



This may be true for windows, but Linux hvm guests really supports

consoles through serial consoles.



For fully virt (Linux): ---



Edit guest configuration file and add "serial = pty"



Then edit guest grub.conf file and add console=ttyS0 to kernel line and

add "co:2345:respawn:/sbin/agetty ttyS0 9600 vt100-nav" to your

/etc/inittab.



--Sadique

> You should use

> either sdl=1 or vnc=1.

>

> If you use vnc you should make sure that xen-config.sxp has the vnc

> options enabled and configured to your liking. You may also need to

> manually start the vncviewer to see the guest console. The default

> setting when enabled let's you do vncviewer localhost.

>

> Regards,

> Todd

>

>

>> Here's my clientdom file:

>>

>> name = "clientdom"

>>

>> uuid = "6bf7a6a0-d5c6-463e-a395-6d689a1819c5"

>>

>> maxmem = 256

>>

>> memory = 256

>>

>> vcpus = 1

>>

>> builder = "hvm"

>>

>> kernel = "/usr/lib/xen/boot/hvmloader"

>>

>> boot = "d"

>>

>> pae = 1

>>

>> acpi = 1

>>

>> apic = 1

>>

>> on_poweroff = "destroy"

>>

>> on_reboot = "restart"

>>

>> on_crash = "restart"

>>

>> device_model = "/usr/lib/xen/bin/qemu-dm"

>>

>> sdl = 0

>>

>> vnc = 0

>>

>> vncunused = 0

>>

>> vncdisplay = "-5900"

>>

>> disk = [

>> "phy:/dev/VolGroup00/client,hda,w","file:/tmp/Centos5.1.iso,hdb:cdrom,r"
]

>>

>> #vif = [ "mac=00:16:3e:57:66:7d,bridge=xenbr0,type=ioemu" ]

>>

>> vif = [ "mac=00:16:3e:57:66:7d,bridge=xenbr0" ]

>>

>> serial = "pty"

>>

>>

>>

>> Several instances of the symptom have been encountered before, due to

>> incorrect locations for hvmloader and qemu-dm, which seem to be in the

>> correct locations in this case (/usr/lib/xen/boot & /usr/lib/xen/bin

>> respectively).

>>

>>

>>

>> Has anyone else run into this and resolved it? Any advice greatly

>> appreciated.

>>

>>

>>

>> Regards,

>>

>> Hamid.

>> _______________________________________________

>> Xen-users mailing list

>> Xen-***@lists.xensource.com

>> http://lists.xensource.com/xen-users

>>

>>

>

> _______________________________________________

> Xen-users mailing list

> Xen-***@lists.xensource.com

> http://lists.xensource.com/xen-users

>

>





_______________________________________________

Xen-users mailing list

Xen-***@lists.xensource.com

http://lists.xensource.com/xen-users

[jim burns]

On Thursday 07 February 2008 05:19:26 pm Hamid Majidy wrote:
> When I start guest with "xm create clientdom", I get:
> xm create clientdom
> Using config file "./clientdom".
> VNC= 3
> Started domain clientdom
>  
> But when I try to connect to it with "vncviewer 192.168.122.1:5900" I get:
> VNC Viewer Free Edition 4.1.2 for X - built Mar 14 2007 22:51:02
> Copyright (C) 2002-2005 RealVNC Ltd.
> See http://www.realvnc.com for information on VNC.
> vncviewer: unable to open display ""
>  

vnc=3 could mean it's presenting a session on 5903, not 5900.
Put 'vncconsole=1' in your config to automatically spawn a vnc session. After
the guest is up, do a '/bin/ps a -HA' on dom0, for a threaded process listing
with command line args. The line under the one with 'qemu-dm' should be
something like 'vncviewer :5903'.

[Hamid Majidy]

Thanks, Jim, for your input. I think I know what the problem is. I have not
installed XWindows which VNC depends on. Guest OSs will have server roles
and I avoid installing XWindows and the like on servers.

Sdl, apparently, also requires X.

So the question becomes, is there a text mode way to connect to domU guests
in Xen?

Thanks,
Hamid.

-----Original Message-----
From: xen-users-***@lists.xensource.com
[mailto:xen-users-***@lists.xensource.com] On Behalf Of jim burns
Sent: Thursday, February 07, 2008 4:51 PM
To: xen-***@lists.xensource.com
Subject: Re: [Xen-users] xenconsole: Could not read tty from store:
Nosuchfile or directory

On Thursday 07 February 2008 05:19:26 pm Hamid Majidy wrote:
> When I start guest with "xm create clientdom", I get:
> xm create clientdom
> Using config file "./clientdom".
> VNC= 3
> Started domain clientdom
>  
> But when I try to connect to it with "vncviewer 192.168.122.1:5900" I get:
> VNC Viewer Free Edition 4.1.2 for X - built Mar 14 2007 22:51:02
> Copyright (C) 2002-2005 RealVNC Ltd.
> See http://www.realvnc.com for information on VNC.
> vncviewer: unable to open display ""
>  

vnc=3 could mean it's presenting a session on 5903, not 5900.
Put 'vncconsole=1' in your config to automatically spawn a vnc session.
After
the guest is up, do a '/bin/ps a -HA' on dom0, for a threaded process
listing
with command line args. The line under the one with 'qemu-dm' should be
something like 'vncviewer :5903'.

[jim burns]

On Friday 08 February 2008 01:06:02 am Hamid Majidy wrote:
> So the question becomes, is there a text mode way to connect to domU guests
> in Xen?

client-machine> ssh guest-ip

[jim burns]

On Friday 08 February 2008 01:06:02 am Hamid Majidy wrote:
> Thanks, Jim, for your input. I think I know what the problem is. I have not
> installed XWindows which VNC depends on. Guest OSs will have server roles
> and I avoid installing XWindows and the like on servers.
>
> Sdl, apparently, also requires X.
>
> So the question becomes, is there a text mode way to connect to domU guests
> in Xen?

Also, you don't need X on dom0 so much as you might find it useful on the
client machine you connect from. My 'ssh' example then becomes 'ssh -X
domu-ip' for running individual X programs. You can even install a vnc server
on the domu, and connect to it over your ssh session.

Or, if you change/add 'vnclisten="0.0.0.0"' to your domu's config, then from a
client machine, you can do 'vncviewer dom0-ip:n'. That's dom0, not domu, and
n is the port number that qemu-dm is presenting it's vnc session on.