You missed, that I am migrating not only my packages, but my whole virtual
machine from paravirtualized Xen to paravirt. driver KVM.
This mkinitrd magic is only required for disk driver change (xenblk_front to
virtio_blk).
So it's something different, like your upgrade of CentOS.
SAL
On Wed, Jan 21, 2009 at 01:47:34PM -0500, Dustin Henning wrote:
It is probably worth noting that if someone were to run a kernel
update with a package manager after getting this working (using information
from later posts in this thread), they would need to do a manual mkinitrd.
At least that was my experience some time ago when switching from hda to sda
in CentOS, future kernel-xen versions installed via yum tried to boot to hda
and failed. However, I think I actually recompiled originally, though, as
opposed to adding the new drivers to initrd, so I could be wrong.
Dustin
-----Original Message-----
From: fedora-xen-bounces(a)redhat.com [mailto:fedora-xen-bounces@redhat.com]
On Behalf Of Mark McLoughlin
Sent: Wednesday, January 21, 2009 08:49
To: Jan ONDREJ (SAL)
Cc: Fedora Xen
Subject: Switching from IDE to virtio_blk [qas Re: [Fedora-xen] Goodbye Xen
on RH/Fedora?]
(This is all getting offtopic for fedora-xen, we should really move to
fedora-virt)
On Wed, 2009-01-21 at 14:28 +0100, Jan ONDREJ (SAL) wrote:
> virtio_net works well, but I have trouble to boot from virtio_blk.
>
> I can add second disk as virto block device, but I can't boot from
> first disk.
When switching from IDE to virtio, you need to first build a new initrd
in the guest with e.g.:
$> mkinitrd --with virtio_pci --with virtio_blk -f
/boot/initrd-$(kernelversion) $(kernelversion)
You only need to do this once. After that, if a new kernel is installed
while you're booted off a virtio disk, then mkinitrd will include the
modules automatically.
Cheers,
Mark.
--
Fedora-xen mailing list
Fedora-xen(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen