Re: upgrade to new xen domU on old xen dom0?

[Josip Rodin <joy@entuzijast.net>]

On Sat, Mar 27, 2010 at 12:02:01PM +0000, Ian Campbell wrote:
> xen-blkfront is a module in the pvops based 2.6.32-x-xen-amd64 where as
> it was statically linked in the non-pvops 2.6.26-x-xen-and64 images.
> This already happened in Lenny for 32 bit guests (sort of) since the
> -686-bigmem kernel (which supports Xen) also uses modules for the
> drivers. I think the change is generally a step in the right direction.
> 
> Perhaps running mkinitramfs within the 2.6.26 environment causes the
> 2.6.32 initrd to not contain the correct module? (since it can't detect
> the requirement for the module because the current kernel has it
> statically linked?)
> 
> This should be fixable with some configuration in the guest (e.g. add
> the modules to /etc/initramfs-tools/modules).

I ran the default install of the image package on the guest running .18,
and then copied the image and initrd over to the parent.
I extracted that initrd image now and I see

lib/modules/2.6.32-4-xen-amd64/kernel/drivers/block/xen-blkfront.ko

in it. Are you saying it could have gotten missed by the initrd init scripts
even though it's there? Couldn't we fix that automatism?

I diffed the trees and noticed that kernel/drivers/net/xen-netfront.ko
is missing from the initrd, but that's probably non-fatal.

-- 
     2. That which causes joy or happiness.