Xen users - Apr 2006 - Can''t use 2.6.16-xen as dom0 kernel

Hello,

 I compiled a 2.6.16-xen kernel from xen-unstable but I cannot use it as
a dom0 kernel. Here is the error:

---------------------
...
TCP reno registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot open root device "sda1" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0) (XEN) Domain 0 crashed: rebooting machine in 5
seconds. (XEN) Domain 0 crashed: rebooting machine in 5 seconds.
 (XEN) Domain 0 crashed: rebooting machine in 5 seconds.
 (XEN) Domain 0 crashed: rebooting machine in 5 seconds.

-----------------------

I used the default configuration file for 2.6.16-xen except I change the
ext3 support. The /dev/sda1 is an ext3 file system so I compiled the
support for this file system directly in the xenlinux kernel not as a
module. My grub menu entry is:


  title Xen-3.0-unstable  / XenLinux 2.6 (X86_64)
  root (hd0,0)
  kernel /boot/xen-3.gz dom0_mem=1048576 com1=9600,8n1 
  module /boot/vmlinuz-2.6-xen root=/dev/sda1 console=ttyS0


I compiled Xen with `make KERNELS=*2.6* world` so I obtained all
xenlinux kernels. I tried to boot dom0 with the 2.6.16-xen0 and it
worked (I just replaced /boot/vmlinuz-2.6-xen by
/boot/vmlinuz-2.6-xen0 in grub). I also tried to start a domU with
kernel 2.6.16-xen and it worked. So to make a summary:

- 2.6.16-xen doesn''t boot as dom0
- 2.6.16-xen0 boots
- 2.6.16-xen boots as domU

I search for ''vmlinuz-2.6-xen'' in the mailing list but I
didn''t find any
matching document (and it''s the same in the bug list).

So if you have any hints...
Thanks for your help,

Best regards,
Guillaume

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

>  I compiled a 2.6.16-xen kernel from xen-unstable but I cannot use it as
> a dom0 kernel. Here is the error:
> 
> ---------------------
> ...
> TCP reno registered
> Initializing IPsec netlink socket
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> md: Autodetecting RAID arrays.
> md: autorun ...
> md: ... autorun DONE.
> VFS: Cannot open root device "sda1" or unknown-block(0,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0,0) (XEN) Domain 0 crashed: rebooting machine in 5
> seconds. (XEN) Domain 0 crashed: rebooting machine in 5 seconds.
>  (XEN) Domain 0 crashed: rebooting machine in 5 seconds.
>  (XEN) Domain 0 crashed: rebooting machine in 5 seconds.

The -xen kernel is built with almost all drivers configured as 
modules; hence you''ll need an initrd including the driver[s] for
your scsi or ide controller so you can mount the root filesystem.

Alternatively just build a -xen0 kernel [which includes almost all
drivers compiled in]. 


cheers,

S.


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

On Wed, 05 Apr 2006 14:32:47 +0100
Steven Hand <Steven.Hand@cl.cam.ac.uk> wrote:
> 
> >  I compiled a 2.6.16-xen kernel from xen-unstable but I cannot use
> > it as
> > a dom0 kernel. Here is the error:
> > 
> > ---------------------
> > ...
> > TCP reno registered
> > Initializing IPsec netlink socket
> > NET: Registered protocol family 1
> > NET: Registered protocol family 17
> > md: Autodetecting RAID arrays.
> > md: autorun ...
> > md: ... autorun DONE.
> > VFS: Cannot open root device "sda1" or unknown-block(0,0)
> > Please append a correct "root=" boot option
> > Kernel panic - not syncing: VFS: Unable to mount root fs on
> > unknown-block(0,0) (XEN) Domain 0 crashed: rebooting machine in 5
> > seconds. (XEN) Domain 0 crashed: rebooting machine in 5 seconds.
> >  (XEN) Domain 0 crashed: rebooting machine in 5 seconds.
> >  (XEN) Domain 0 crashed: rebooting machine in 5 seconds.
> 
> 
> The -xen kernel is built with almost all drivers configured as 
> modules; hence you''ll need an initrd including the driver[s] for
> your scsi or ide controller so you can mount the root filesystem.
Thank you steve for the very quick answer. I compiled the scsi driver as
a module and everything is fine now. So the -xen kernel is working on
Debian 3.1 stable system.

Cheers,
Guillaume

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