----- "Christopher Hunt" dharmachris@gmail.com wrote:
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. :)
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
for i in /etc/xen/guest[0-9]*; do cp ${i} ${i}.bak sed -i '/^ramdisk/cramdisk = "/boot/initrd-2.6.18-164.6.1.el5xen-domU.img"' ${i} done
Well that was more helpful than I could reasonable hope for but alas, the error didn't change much: device-mapper: dm-raid45: initialized v0.2594l Waiting for driver initialization. Scanning and configuring dmraid supported devices Scanning logical volumes Reading all physical volumes. This may take a while... Found volume group "vg00" using metadata type lvm2 ## this is the VG on the KVM host Activating logical volumes Volume group "virt01vg00" not found ## this is the VG on the XEN host Creating root device. Mounting root filesystem. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. 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 ERROR opening /dev/console: No such file or directory Trying to use fd 0 instead. WARNING: can't access (null) exec of init ((null)) failed!!!: Bad address Kernel panic - not syncing: Attempted to kill init!
I wonder if i need to mount the block device and edit fstab?
Christopher Hunt
On Mon, Nov 9, 2009 at 11:09 AM, Christopher G. Stach II cgs@ldsys.netwrote:
-
Christopher G. Stach II -
Christopher Hunt