Am 30.05.2015 um 18:20 schrieb Steven Chamberlain: > Christoph Egger wrote: >> I have a kfreebsd that boots via virtio. And I'm pretty sute it was >> created with virtio disks. I'll check once home again. > I already found out the following today: > > grub-probe doesn't know about /dev/vtbd* disks, so it can't install > boot blocks to a new virtio disk without a patch (I'll upload this to > jessie-kfreebsd-p-u soon). > > If the boot blocks are already there, GRUB2 can boot such a disk, and > kfreebsd-10 supports it too. (kfreebsd-9 didn't IIRC) > > It is possible to migrate from if=ide to if=virtio by altering > /etc/fstab (/dev/ada -> /dev/vtbd), and the root device in > /boot/grub/grub.cfg, before making that change. If you forget > to make those changes in advance, it is still possible (but somewhat > awkward) to rescue it and make those changes via VNC. > > Likewise one can migrate e1000 to virtio-net by changing > /etc/network/interfaces (em0 -> vtnet0). > > I think we ought to do this anyway for the buildds and porterboxes? > Furthermore it may avoid the stability issue (if that was related > to the emulated IDE disk or e1000 NIC). > > Regards, Hi, I can confirm that I installed a Jessie kFreeBSD with virtio block and network drivers and it worked as far as I recall. Possible that it took another code path than the one you found. I absolutely agree it seems like a very good idea to migrate the buildds and porterboxes to the virtio interfaces, they should provide a much better performance. Best regards, Jan Henke
Attachment:
signature.asc
Description: OpenPGP digital signature