On Wed, Jan 21, 2009 at 3:45 PM, Richard W.M. Jones <rjones@xxxxxxxxxx> wrote:
Well what I did was that I created a special initramfs, with virtio-net and virtio-blk drivers, as well as all of their dependencies (virtio-pci, virti-baloon and possibly one more), edited the init script going inside the initrd image so that it triggers the virtio drivers, then booted up on that ROOT filesystem using the kernel command line.Yes I have to agree with Emre here - I don't think it's as simple asOn Wed, Jan 21, 2009 at 03:06:43PM +0100, Emre Erenoglu wrote:
> On Wed, Jan 21, 2009 at 2:48 PM, Mark McLoughlin <markmc@xxxxxxxxxx> wrote:
>
> > (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.
>
>
> You will also need to specify /dev/vdX on the kernel root= line and make
> sure your init script inside your initrd triggers the virtio drivers at boot
> so that the /dev/vdX are created.
just rebuilding mkinitrd. I got that far but gave up later on.
on system side, it's better to edit fstab but root is anyway mounted.
You may need to boot to shell at your initrd to see what's going on, or probe by hand to see the devices are created etc.
You also need to use the correct guest configuration file so that virtio-type devices are created instead of emulated ones.
--
Emre
-- Fedora-xen mailing list Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen
