On Mon, 4 Dec 2006, Thiago Morais wrote:
Hello All.
Now, I got this error:
Linux version 2.6.18-1.2849.fc6xen (brewbuilder@hs20-bc2-4.build.redhat.com)
This is booting a xenU right? not the dom0?
Red Hat nash version 5.1.19 starting Mounting proc filesystem Mounting sysfs filesystem Creating /dev Creating initial device nodes Setting up hotplug. Creating block device nodes. Loading uhci-hcd.ko module USB Universal Host Controller Interface driver v3.0 Loading ohci-hcd.ko module Loading ehci-hcd.ko module Loading jbd.ko module Loading ext3.ko module Loading scsi_mod.ko module SCSI subsystem initialized Loading sd_mod.ko module Loading scsi_transport_spi.ko module Loading mptbase.ko module Fusion MPT base driver 3.04.01 Copyright (c) 1999-2005 LSI Logic Corporation Loading mptscsih.ko module Loading mptspi.ko module Fusion MPT SPI Host driver 3.04.01 Creating root device. Mounting root filesystem. mount: could not find filesystem '/dev/root'
Your xenu kernel did not load the xenblk or xennet modules via initrd.
This is probably because you are booting a rootfs and not a disk image, and you are using the initrd from the kernel-xen image installed on the host (dom0), which got a re-tailored initrd image to suit its own requirements, which exclude those xen virtual drivers (since its dom0 not xenu).
Easiest fix is to unpack the initrd, add the two xen modules from /lib/modules/ add the insmod call in the "init" script of the initrd, and repack the initrd image.
The real fix is for redhat to always include xennet and xenblk drivers in the initrd for any kernel-xen initrd, even if it seems that the initrd is installed on the dom0. Really, the space saved in the kernel or in the initrd is not worth having to re-image the initrd for every new kernel-xen you people package up. The package kernel-xen is meant for dom and xenu, so please add the xennet and xenblk drivers in the initrd.
Paul