Since your actually forming the raid on dom-0 and not inside of the
guest, there is absolutely no need to load md and associated modules in
the guest at all. The guest will just see the volume group you are
exporting as a regular sata drive the same size as the vg being
exported.
I''m guessing the second drive is for swap?
Hope this helps
Best,
-Tim
On Mon, 2006-10-23 at 16:36 +1000, Brian Austin wrote:> Hi,
>
> I have a probably simple problem..
>
> Having installed xen 3 on a debian etch linux box, I get the following
> error trying to launch a domu.
> the computer has 4x sata HDD, I am trying to install my domu on a raid
pack.
> I have the domo on a software raid 1
> legion:/etc/xen# mount
> /dev/md0 on / type ext3 (rw,errors=remount-ro)
> proc on /proc type proc (rw,noexec,nosuid,nodev)
> /sys on /sys type sysfs (rw,noexec,nosuid,nodev)
> udev on /dev type tmpfs (rw,mode=0755)
> devshm on /dev/shm type tmpfs (rw)
> devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
> /dev/md1 on /var type ext3 (rw)
>
> why does the domu get caught up in that rad config?
>
> initrd-tools: 0.1.84.1
> mount: unknown filesystem type ''devfs''
> md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
> md: bitmap version 4.39
> md: raid1 personality registered for level 1
> SCSI subsystem initialized
> register_blkdev: cannot get major 8 for sd
> md: md0 stopped.
> mdadm: no recogniseable superblock on /dev/sda1
> mdadm: /dev/sda1 has wrong uuid.
> mdadm: cannot open device /dev/sdb1: No such device or address
> mdadm: /dev/sdb1 has wrong uuid.
> mdadm: cannot open device /dev/sdc1: No such device or address
> mdadm: /dev/sdc1 has wrong uuid.
> mdadm: no devices found for /dev/md0
> umount: devfs: not mounted
> mount: unknown filesystem type ''devfs''
> kjournald starting. Commit interval 5 seconds
> EXT3 FS on sda1, internal journal
> EXT3-fs: recovery complete.
> EXT3-fs: mounted filesystem with ordered data mode.
> umount: devfs: not mounted
> pivot_root: No such file or directory
> /sbin/init: 432: cannot open dev/console: No such file
> Kernel panic - not syncing: Attempted to kill init!
>
>
> my config file looks like (below)....
> vif commented out deliberately
> bbvm/bblv is my logical volume
>
> legion:/etc/xen# ls /dev/bbvm/bblv -als
> 0 lrwxrwxrwx 1 root root 21 2006-10-23 16:15 /dev/bbvm/bblv ->
> /dev/mapper/bbvm-bblv
>
> config file
>
> kernel = "/boot/vmlinuz-2.6.16-2-xen-686"
> ramdisk = "/boot/initrd.img-2.6.16-2-xen-686"
> memory = 640
> name = "bambamVM"
> #vif = [''mac=5A:12:34:56:78:9A, bridge=xenbr0'']
>
> disk = [''phy:bbvm/bblv,sda1,w''
> ,''phy:sdd5,sda4,w''
> ]
> root = "/dev/sda1 rw"
>
>
> thanks in advance
>
> Brian
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
