Well that was more helpful than I could reasonable hope for but alas, the error didn't change much: <br><div style="margin-left: 40px; font-family: courier new,monospace;">device-mapper: dm-raid45: initialized v0.2594l<br>
Waiting for driver initialization.<br>Scanning and configuring dmraid supported devices<br>Scanning logical volumes<br> Reading all physical volumes. This may take a while...<br> Found volume group "vg00" using metadata type lvm2 ## this is the VG on the KVM host<br>
Activating logical volumes<br> Volume group "virt01vg00" not found ## this is the VG on the XEN host<br>Creating root device.<br>Mounting root filesystem.<br>kjournald starting. Commit interval 5 seconds<br>EXT3-fs: mounted filesystem with ordered data mode.<br>
Setting up other filesystems.<br>Setting up new root fs<br>setuproot: moving /dev failed: No such file or directory<br>no fstab.sys, mounting internal defaults<br>setuproot: error mounting /proc: No such file or directory<br>
setuproot: error mounting /sys: No such file or directory<br>Switching to new root and running init.<br>unmounting old /dev<br>unmounting old /proc<br>unmounting old /sys<br>ERROR opening /dev/console: No such file or directory<br>
Trying to use fd 0 instead.<br>WARNING: can't access (null)<br>exec of init ((null)) failed!!!: Bad address<br>Kernel panic - not syncing: Attempted to kill init!<br></div><br><br>I wonder if i need to mount the block device and edit fstab? <br>
<br>Christopher Hunt<br><br><div class="gmail_quote">On Mon, Nov 9, 2009 at 11:09 AM, Christopher G. Stach II <span dir="ltr"><<a href="mailto:cgs@ldsys.net">cgs@ldsys.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">----- "Christopher Hunt" <<a href="mailto:dharmachris@gmail.com">dharmachris@gmail.com</a>> wrote:<br>
<br>
</div><div class="im">> This brings me back to suspecting the problem is in the different file<br>
> structures. I'm still trying to wrap my head around the other replies<br>
> in this thread.<br>
<br>
</div>mkinitrd in dom0 with xenblk and xennet and use that new initrd for the guests. After you get the guests up and running, install kernel-xen in each one and switch to using pygrub. The following should handle the first part, but no warranties implied. :)<br>
<br>
mkinitrd --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<br>
<br>
for i in /etc/xen/guest[0-9]*; do<br>
cp ${i} ${i}.bak<br>
sed -i '/^ramdisk/cramdisk = "/boot/initrd-2.6.18-164.6.1.el5xen-domU.img"' ${i}<br>
done<br>
<font color="#888888"><br>
--<br>
</font><div><div></div><div class="h5">Christopher G. Stach II<br>
<br>
<br>
_______________________________________________<br>
CentOS-virt mailing list<br>
<a href="mailto:CentOS-virt@centos.org">CentOS-virt@centos.org</a><br>
<a href="http://lists.centos.org/mailman/listinfo/centos-virt" target="_blank">http://lists.centos.org/mailman/listinfo/centos-virt</a><br>
</div></div></blockquote></div><br>