[Xen-users] domU xenified kernel, 2.6.29.6, no console?

["Fajar A. Nugraha" <fajar@xxxxxxxxx>]

Hi,

I'm testing 2.6.29.6 (with suse patches) xen kernel, with a minimal
busybox-based initrd. After some kernel config tweaking (including
disabling DMI scanning, thanks to
http://lists.xensource.com/archives/html/xen-users/2009-04/msg00128.html)
it finally works. Well, almost:P

Here's a snippet of boot log:

#====
Console: colour dummy device 80x25
console [tty0] enabled
console [xvc-1] enabled
...
Xen virtual console successfully installed as xvc0
...
XENBUS: Device with no driver: device/console/0
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Freeing unused kernel memory: 200k freed
Write protecting the kernel read-only data: 3416k
#====

... and that;s it. The output stops there. The same initrd with
similar config works fine with 2.6.30 pv_ops kernel.

#====
Console: colour dummy device 80x25
console [tty0] enabled
console [hvc0] enabled
...
XENBUS: Device with no driver: device/console/0
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Freeing unused kernel memory: 332k freed
Write protecting the kernel read-only data: 3116k
udhcpc (v1.14.3) started
Sending discover...
Sending select for 192.168.122.89...
Lease of 192.168.122.89 obtained, lease time 3600
Resetting default routes
adding dns 192.168.122.1

Please press Enter to activate this console.
#====

Lines after "udhcpc" is from busybox.
Any ideas what I'm missing? Some mandatory kernel config perhaps?

-- 
Fajar

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