[Xen-users] Re: Exporting Dom0 disks to DomU as SCSI disks does not work

[John S Little <JSLittl@xxxxxxxxxxxxx>]

Hello..
 
> Hello allz,
> 
> I'm using Xen 3.0.1 on an x86_64 and tried to export 2 logical volumes
> from Dom0 to DomU as sda1 and sdb1, but DomU can't mount it.
> If I change it to hda1/hdb1, it works very well. Does someone have an
> idea what I could be missing?
> 
> Here's my DomU Xen Startup file:
> 
> --- snip ---
> 
> kernel = "/etc/xen/kernel/linux-2.6.12.6-xenU"
> memory = 512
> cpus = ""         # leave to Xen to pick
> name = "test1"
> disk = [ 'phy:xen-volumes/test1-swap,sda1,w',
> 'phy:xen-volumes/test1,sdb1,w' ]
> vif = [ 'bridge=xenbr0' ]
> root = "/dev/sdb1 ro"
> 
> --- snap ---
> 
> 
> Here are the kernel messages shown when trying to start my DomU:
> 
> --- snip ---
> 
> Using config file "/etc/xen/test1".
> Started domain test1
> Linux version 2.6.12.6-xenU (root@sarge64) (gcc-Version 3.3.5 (Debian
> 1:3.3.5-13)) #2 SMP Fri Feb 10 17:02:40 CET 2006
> kernel direct mapping tables upto 20800000 @ 4ac000-5b2000
> Built 1 zonelists
> Kernel command line:  root=/dev/sdb1 ro
> Initializing CPU#0
> PID hash table entries: 4096 (order: 12, 131072 bytes)
> Xen reported: 2992.692 MHz processor.
> Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
> Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
> Software IO TLB disabled
> Memory: 509184k/532480k available (1564k kernel code, 22552k reserved,
> 587k data, 136k init)
> Mount-cache hash table entries: 256
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 2048K
> CPU: Physical Processor ID: 0
> Brought up 1 CPUs
> Grant table initialized
> NET: Registered protocol family 16
> xen_mem: Initialising balloon driver.
> SCSI subsystem initialized
> PCI: System does not support PCI
> PCI: System does not support PCI
> IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
> Initializing Cryptographic API
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> Xen virtual console successfully installed as tty1
> Event-channel device installed.
> netfront: Initialising virtual ethernet driver.
> NET: Registered protocol family 2
> Registering block device major 8
> register_blkdev: cannot get major 8 for sd
> xen_blk: can't get major 8 with name sd
> Registering block device major 8
> register_blkdev: cannot get major 8 for sd
> xen_blk: can't get major 8 with name sd
> IP: routing cache hash table of 2048 buckets, 32Kbytes
> TCP established hash table entries: 131072 (order: 9, 2097152 bytes)
> TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
> TCP: Hash tables configured (established 131072 bind 65536)
> VFS: Cannot open root device "sdb1" 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)
> 
> --- snap --- 

Are you using an initrd for your domU?  The syntax for this varies by 
distribution.  For SuSE it is mkinitrd -k <xen kernel name> -i 
<name-your-initrd-here> -m "<put in your modules here>". 

In your domU config make an entry like: 
ramdisk = "/boot/initrd-xen" where initrd-xen is your initrd or a softlink 
to it.

> My DomU kernel has SCSI and SCSI disk support compiled in, so this
> should not be the problem.
> 
> 
> Cheers,
> 
> --
> Christian Hertel

hth
Regards,

John 


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