Mr. Stach,
Good catch! With your help, I feel my luck is improving, if slowly... I've updated accordingly, and now am getting a brand new file system issue:
Waiting for driver initialization.
Scanning and configuring dmraid supported devices
Creating root device.
Mounting root filesystem.
mount: could not find filesystem '/dev/root'
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!
Here is the contents of /tmp/fstab:
[root@vvmm03-XEN xen]# cat /tmp/fstab-domU
/dev/vg00/c5root00 / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
devpts /dev/pts devpts gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
/dev/vg00/swap00 swap swap defaults 0 0
I'm not sure why it's looking for /dev/root..
Thanks again,
Christopher Hunt
On Mon, Nov 9, 2009 at 11:32 AM, Christopher G. Stach II
<cgs@ldsys.net> wrote:
> Found volume group "vg00" using metadata type lvm2 ## this is the VG
> on the KVM host
> Volume group "virt01vg00" not found ## this is the VG on the XEN host
mkinitrd is getting this from your dom0's /etc/fstab.
sed 's/virt01vg00/vg00/g' /etc/fstab > /tmp/fstab-domU
mkinitrd -f --fstab=/tmp/fstab-domU --with=xenblk --with=xennet --preload=xenblk --preload=xennet /boot/initrd-2.6.18-164.6.1.el5xen-domU.img 2.6.18-164.6.1.el5xen
Better luck this time. :)
--