[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] xenconsole: Could not read tty from store: No such file or directory



Todd Deshane wrote:
On Feb 7, 2008 11:47 AM, Todd Deshane <deshantm@xxxxxxxxx> wrote:
Hi,

On Feb 7, 2008 1:58 AM, Hamid Majidy <hamid@xxxxxxxxxxxxxxx> 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.

[root@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 (brewbuilder@xxxxxxxxxxxxxxxxxxxxxxxxxxx) (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-devel@xxxxxxxxxx
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-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.