Re: [Xen-users] Cannot start PV guests

[Andreas Sommer <AndiDog@xxxxxx>]

Fajar A. Nugraha wrote:

extra = "video=xenfb xencons=tty1"
vfb = ['type=vnc,vncdisplay=10']
    

Try this :
- remove (or mark) those two lines
- setup domU's /etc/inittab to spawn login prompt on hvc0

In my last testing, 2.6.30 somehow won't work (similar simptom as
yours) if I enable Xen frame buffer. If I disable it (comment out vfb
line) it works fine on Xen serial console, so perhaps it the same
case.


  

I have successfully tested that domain (Debian lenny installed with
debootstrap) on another machine that runs the 2.6.18.8-xen kernel which
ships with Xen. But on this notebook, only Xen-unstable with 2.6.30-rc6
works, and I can't start PV domains.
    

If you know that 2.6.18 kernel works, why not use that for domU
kernel? dom0 and domU kernel does not have to be the same version. It
doesn't even have to be the same OS.
  

I tried the following kernels (and removed the framebuffer configuration), with no luck:

Output for 2.6.18.8 and 2.6.27.5 (both are from the xenbits.xensource.com GIT repo; output is the same):

...
[  300.030530] RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
[  300.031631] Xen virtual console successfully installed as tty1
[  300.031653] Event-channel device installed.
[  300.037578] blktap_device_init: blktap device major 254
[  300.037583] blktap_ring_init: blktap ring major: 253
[  300.057235] netfront: Initialising virtual ethernet driver.
[  300.057804] PNP: No PS/2 controller found. Probing ports directly.
[  300.058654] i8042.c: No controller found.
[  300.058688] mice: PS/2 mouse device common for all mice
[  300.058733] TCP cubic registered
[  300.058738] NET: Registered protocol family 1
[  300.058743] NET: Registered protocol family 17
[  300.058747] Using IPI No-Shortcut mode
[  300.058785] PCI IO multiplexer device installed.
[  305.154455] XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s...
[  599.991814] XENBUS: Timeout connecting to device: device/vbd/2049 (local state 3, remote state 1)
[  599.991820] XENBUS: Device not ready: device/vbd/2049
[  599.991823] XENBUS: Device with no driver: device/console/0
[  599.991828] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[  599.991890] Freeing unused kernel memory: 148k freed
Loading, please wait...
[  599.992852]  
[  599.992857]   ***************************************************************
[  599.992860]   ***************************************************************
[  599.992864]   ** WARNING: Currently emulating unsupported memory accesses  **
[  599.992867]   **          in /lib/tls glibc libraries. The emulation is    **
[  599.992871]   **          slow. To ensure full performance you should      **
[  599.992874]   **          install a 'xen-friendly' (nosegneg) version of   **
[  599.992880]   **          the library, or disable tls support by executing **
[  599.992884]   **          the following as root:                           **
[  599.992887]   **          mv /lib/tls /lib/tls.disabled                    **
[  599.992892]   ** Offending process: init (pid=179)                         **
[  599.992896]   ***************************************************************
[  599.992899]   ***************************************************************
[  599.992902]  
[  599.992905] Continuing...
[  604.953911]
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... FATAL: Error inserting fan (/lib/modules/2.6.18.8/kernel/drivers/acpi/fan.ko): No such device
FATAL: Error inserting thermal (/lib/modules/2.6.18.8/kernel/drivers/acpi/thermal.ko): No such device
done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... [  605.203803] device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@xxxxxxxxxx
done.
Begin: Waiting for root file system ... done.
Gave up waiting for root device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/sda1 does not exist. Dropping to a shell!


BusyBox v1.10.2 (Debian 1:1.10.2-2) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs)


Output for 2.6.31-rc8 (mainline):

Using config file "./config.cfg".
Started domain c08d06e6-cb72-48ab-88a9-24360beff248 (id=5)

Then the CPU goes up to 100% and dom0 hardly reacts to my user input...



Output for 2.6.30-rc6-tip (from jeremy repository, but without dom0 support):

...
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... [   10.691178] device-mapper: uevent: version 1.0.3
[   10.692853] device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: dm-devel@xxxxxxxxxx
done.
Begin: Waiting for root file system ...

Then it waits forever for the root file system. Note that it's in my configuration (root = "/dev/sda1 ro").



So I'm pretty much stuck, no matter which kernel version :(...

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