First, unless something has changed in 3.3, Xen does not currently support SCSI devices in domUs. Maybe that has changed - I'm still on 3.2, so I'm not aware of all of the changes. Second, you need to make sure that the device in your domU config file match the devices you're using in fstab. In the domU config, you'll see something like:
disk=[ 'file:/xenstore/vmdevel/Teaming/disk0,xvda,w', ]
The xvda tells Xen that, in the domU, the disk device should show up as xvda, so entries in /etc/fstab will be /dev/xvda1, /dev/xvda2, etc. If you use hda in the domU config file, then your /etc/fstab will need to use /dev/hda1, /dev/hda2, etc. I've never tried sda in the domU config, so I don't know if that works or not. All of this is if you're using a PV domU - and with PV domUs, it doesn't really matter what you call the device in the config file or the domU, it's going to use the Xen block device driver in the domU to access it - you can call it whatever you like.
If you're using HVM domUs, you can only use IDE, so the devices in both your domU config file and your guest need to be hda, hdb, hdc, and/or hdd, and you'll need to load IDE drivers - no SCSI support in HVM, at least as far as I know (again, could be wrong about that).
>>> Holm Kapschitzki <holm@xxxxxxxxxx> 2008/11/25 05:23 >>>
i built xen 3.3 from sources without initrd. Everything works fine, but
i had to use with=ide creating the domu and in domu fstab i had to use
hda instead of sda. If i use sda i get the following error:
VFS: Cannot open root device "sda2" or unknown-block(0,0) xen kernel
Its cause the kernel modules sd_mod an scsi_mod aren't build as modules?
I build the drivers directly into kernel.
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.