On Mon, Sep 28, 2009 at 08:32:12AM +1000, Devraj Mukherjee wrote: > >> > >> Is this happening because the version of the kernel on the Dom0 is way > >> too old for guests to boot? I am just a bit hesitant in rebooting my > >> server for the new kernel to take effect unless I am sure :) > >> > > > > No, that shouldn't be the reason. > > > > The layer between dom0 and guests is Xen hypervisor, not the kernel. > > Although Redhat ships the hypervisor in the same rpm as the kernel :) > > > > That's what I thought as well. I did however find the following post > while searching for answers > http://lists.centos.org/pipermail/centos/2008-January/049757.html > > That outlines something similar to what I am experiencing and > indicates a reboot of the Dom0 fixed it. I am guessing this is because > of Kernel + Driver loading issues. > > > The output looks like the initrd image is broken; it doesn't set up the root > > device.. does it load the xenblk driver? Does it detect the xvd* disks? > > > > Is xenblk supposed to be loaded on Dom0? > No, in the guest kernel. > > and this is my boot log for the DomU > initrd execution starts here.. > Write protecting the kernel read-only data: 478k > Red Hat nash version 5.1.19.6 starting > Mounting proc filesystem > Mounting sysfs filesystem > Creating /dev > Creating initial device nodes > Setting up hotplug. > Creating block device nodes. > Loading ehci-hcd.ko module > Loading ohci-hcd.ko module > Loading uhci-hcd.ko module > USB Universal Host Controller Interface driver v3.0 > Loading jbd.ko module > Loading ext3.ko module > Loading xenblk.ko module > Ok, so it hangs at loading xenblk? No further output? -- Pasi