ugh.... after doing inglorious battle, I return.  It's definitely situation (1).  The error messages haven't changed.  Inside the init file, should the paths references be from the point of view of Dom0?

lvm vgchange -ay --ignorelockingfailure  vg00
resume /dev/vg00/swap00
echo Creating root device.
mkrootdev -t ext3 -o defaults,ro /dev/mapper/vg00-root
echo Mounting root filesystem.
mount /sysroot
echo Setting up other filesystems.
setuproot
echo Switching to new root and running init.
switchroot

Also, should the xen host config file (/etc/xen/guest02) root parameter point to the dom0 root or the block device for the domU?

root = "/dev/mapper/virt01vg00-c5root00 ro"  ##dom0's root file system

Thanks very much,
Christopher Hunt


On Mon, Nov 9, 2009 at 12:54 PM, Christopher G. Stach II <cgs@ldsys.net> wrote:

----- "Christopher G. Stach II" <cgs@ldsys.net> wrote:

> 1. mkinitrd --with=xenblk --with=xennet --preload=xenblk
> --preload=xennet <img> <version>
> (yes, that's the original one without the fstab)
> 2. gunzip -c /boot/initrd-blah.img > /root/blah
> 3. mkdir /mnt/blah
> 4. mount -o loop /root/blah /mnt/blah
> 5. vi /mnt/blah/init
> <change occurrences of dom0 VG to guest VG>
> <change dom0 root device name to guest root device name>
> 6. umount /mnt/blah
> 7. gzip -c /root/blah > /boot/initrd-blah.img

If you followed these directions, you're probably scratching your head. I screwed up. The initrd is actually a cpio archive, so:

1. mkinitrd --with=xenblk --with=xennet --preload=xenblk --preload=xennet <img> <version>
(yes, that's the original one without the fstab)
2. mkdir /root/initrd-blah
3. cd /root/initrd-blah
4. gunzip -c /boot/initrd-blah.img | cpio -idmv
5. vi /root/initrd-blah/init
6. find . -print | cpio -o | gzip -c > /boot/initrd-blah.img

--
Christopher G. Stach II


_______________________________________________
CentOS-virt mailing list
CentOS-virt@centos.org
http://lists.centos.org/mailman/listinfo/centos-virt