[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Fedora-xen] RE: Urgent Help Required: FC10 as DomU on FC8 as Dom0



On Wed, Dec 17, 2008 at 09:45:52PM +0000, MOHAMMAD MATEEN ASLAM wrote:
> 
> Hi Pasi,
> 
> Thanks for helping. Yes, apparently, the problem looks in Ramdisk. I have created Ramdisk with following command but it is unable to boot FC10:-
> 
> mkinitrd -f --builtin=xenner --preload=xenblk --builtin=ehci-hcd --builtin=ohci-hcd --builtin=uhci-hcd --builtin=ahci
> --builtin=ata_piix /boot/initrd-2.6.27.7-134.fc10.i686.PAE-domU.img 2.6.27.7-134.fc10.i686.PAE
> if i dont mention these modules  "--builtin=xenner --builtin=ehci-hcd --builtin=ohci-hcd --builtin=uhci-hcd --builtin=ahci --builtin=ata_piix"  i got following errors.
> No module xenblk found for kernel 2.6.27.7-134.fc10.i686, aborting.
> No module ehci-hcd found for kernel 2.6.27.7-134.fc10.i686, aborting.
> No module ohci-hcd found for kernel 2.6.27.7-134.fc10.i686, aborting.
> .....
> 

xenner is something you use on a KVM host to emulate Xen.. I think you
shouldn't need/use xenner with the real Xen. And especially not in domU,
xenner is for KVM "dom0".

> I have also try to use Fedora 10 Ramdisk instead of re-creating but VM halt few steps earlier giving these errors:-
> 
> ...................................
> TCP cubic registered
> Initializing XFRM netlink socket
> NET: Registered protocol family 17
> Using IPI No-Shortcut mode
> registered taskstats version 1
> XENBUS: Device with no driver: device/vbd/2049
> XENBUS: Device with no driver: device/vbd/2050
> XENBUS: Device with no driver: device/vbd/2051

This means xen block/disk device (xvd) driver was not loaded.

> XENBUS: Device with no driver: device/vif/0

This means xen network driver was not loaded.

Does your kernel contain those modules? or are they built-in in the pv_ops
kernels? 

> XENBUS: Device with no driver: device/console/0
>   Magic number: 1:252:3141
> Freeing unused kernel memory: 424k freed
> Write protecting the kernel text: 2788k
> Write protecting the kernel read-only data: 1184k
> Mounting proc filesystem
> Mounting sysfs filesystem
> Creating /dev
> Creating initial device nodes
> Loading /lib/kbd/keymaps/i386/qwerty/us.map
> ------------------------------------------------------------
> 
> 
> I have live updated my Old DomU (FC8)  -> to New DomU (FC10).  Plz let me know if there is a batter way for Ramdisk.
> 

So.. just to get it correctly:

1. You installed Fedora 8 domU 
2. You updated Fedora 8 domU to Fedora 10 (on the fly) with yum
3. You create initrd image for the F10 kernel using the mkinitrd command above

That should work.. assuming you get the initrd correct. 

You could also try installing a fresh F10 domU (with virt-install or
virt-manager) and see if that works.. 

-- Pasi


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]