[Fedora-xen] DomU problem with tap:aio and xvdN.

Sadique Puthen xenguy at gmail.com
Tue Jan 16 05:35:29 UTC 2007


Gary W. Smith wrote:
> Hello, 
>
> In a nutshell, I can't get DomU's to work with xvdN and tap:aio under
> FC6.2869.  I have also tried to get them to work with XenSource 3.0.4.
>
> I've been asking this in the xen-users group but I haven't had any
> positive response.  I have the following DomU's that I'm testing with:
> FC4/5/6, CentOS4.  In general, they all seem to have the same problems.
>
> The problem is that when I reference the FC6 Xen boot kernel in the
> kernel config line for the DomU it kernel panics.  I have copied
> /lib/modules/* (FC6 and XenSource) to the DomU as well for testing.  If
> I do sdN and file it all works fine, but only for XenSource kernel.
>
> At the Dom0 level we are booting to FC.2869 and only referencing the
> XenSource 3.0.4 images at the DomU config file level.
>
> Am I missing something fundamental?  I have also ran into this problem
> with the jailtime.org images as well.  
>
> FC6 kernel:
> (kernel         = '/boot/vmlinuz-2.6.18-1.2869.fc6xen')
>
> XENBUS: Device with no driver: device/vbd/51713
> XENBUS: Device with no driver: device/vbd/51714
> XENBUS: Device with no driver: device/vif/0
> md: Autodetecting RAID arrays.
> md: autorun ...
> md: ... autorun DONE.
> VFS: Cannot open root device "xvda1" 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)
>
> XenSource 3.0.4 kernel:
> (kernel         = '/xen/xen-3.0.4/boot/vmlinuz-2.6-xen')
>
> md: Autodetecting RAID arrays.
> md: autorun ...
> md: ... autorun DONE.
> WARNING: g.e. still in use!
> WARNING: leaking g.e. and page still in use!
> end_request: I/O error, dev xvda1, sector 2
> EXT2-fs: unable to read superblock
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(202,1)
>
>
> Overall config file:
>
> name           = 'fedora4'
> memory         = '256'
> disk           = [ 'file:/xen-build/fedora4/xen-D0.img,xvda1,w' ,
> 'file:/xen-build/fedora4/xen-swap.img,xvda2,w' ]
> #disk           = [
> 'tap:aio:/xen-build/fedora4/xen-D0.img,xvda1,w','tap:aio:/xen-build/fedo
> ra4/xen-swap.img,xvda2,w' ]
> root           = '/dev/xvda1 ro'
> vif            = [ 'mac=00:16:e6:CD:49:5B' ]
> kernel         = '/xen/xen-3.0.4/boot/vmlinuz-2.6-xen'
>   
Why don't use bootloader = "/usr/bin/pygrub" and load a modified kernel 
from domU itself?
> #kernel         = '/boot/vmlinuz-2.6.18-1.2869.fc6xen'
> on_reboot      = 'restart'
> on_crash       = 'restart'
> extras         = 'console=xvc0'
>
>
>
> --
> Fedora-xen mailing list
> Fedora-xen at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen
>
>   




More information about the Fedora-xen mailing list