On Wed, Jan 31, 2007 at 06:54:34AM -0800, master@xxxxxxxxxxxxxxx wrote: > I would agree it's broken as I've also been unable to get guests to work > "out of the box". I've found the problem to be a missing kernel module in > the initrd, required for disk access (xenblk.ko). If I build an initrd > with xenblk.ko included, guests boot fine. > > I just make an initrd this command: > > mkinitrd --with=xenblk.ko /boot/your_image_name.img your_kernelname > > Just use the kernel name from uname -a > > mkinitrd --with=xenblk.ko /boot/initrd_test.img 2.6.19-prepcifs_fix Thanks, but my problem is that the 'init' inside the initrd is runing lvm commands, probably because it was built on a host that has LVM, and I need to remove these lvm commands from the init inside the initrd. How do I do that? Your above solution would have solved my problem yesterday when I ran into this, but now I have reimaged the server using LVM, and I am facing yet another problem. thanks. -- Fedora-xen mailing list Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen
