[Bug 241774] FreeBSD 11.3 & 12.0 has broken SCSI & Networking on KVM/QEMU Q35 with OVMF

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241774

--- Comment #48 from John Hartley <drum at graphica.com.au> ---
(In reply to Dobri Dobrev from comment #47)

Hi Dobri,

by way of testing I am doing:

1. Build 12.0-RELEASE with "dev netmap" commented out of GENERIC kernel to get
network access on any of em, vmx or re . You have to keep the kernel with
GENERIC id as otherwise update in step 2 will fail. If you are on 12.0 then I
assume you must have SATA disk as Virto and SCSI will not work.

2. Use "freebsd-update" (freebsd-update -r 9.1-RELEASE upgrade) to do upgrade
from 12.0-RELEASE to 12.1-RELEASE. This will require two reboots via to
"free-update" steps (both /usr/sbin/freebsd-update install).

3. Build 12.1-RELEASE with "dev netmap" commented out of GENERIC kernel and
then do final "freebsd-update" (/usr/sbin/freebsd-update install).

4. Do your Ports or Package updates using postmaster or other tools in usual
way.

You should now have working 12.1 and can apply VirtIO patch (again via kernel
rebuild) if you want to change from SATA to VirtIO based disk.

At this point you should be able to start to use "freebsd-update" to and other
utilities to get binary security updates.

In fullness of time bugs / patches for fix of VirtIO and netmap should flow
through as either binary updates via "freebsd-update" or be part of new release
(12.2).

Right now I am testing process and have got to step 4 (it is slow as each
kernel rebuild takes some time).

Once I have done upgrade test from 12.0 -> 12.1 I will then try some approach
but starting from 11.2 and go to 12.1.

Once on 12.1 I can test VirtIO fix without need to worry about trying to
backport it 11.x .

Both VirtIO and netmap are "performance optimisations". So the extent of need
is driven by throughput requirements of your server. A while back I did upgrade
of quite a large number of FreeBSD VMs (from 8.x, 9.x & 10.x to 11.x) and at
the time I was forced to change disk to SATA as SCSI (and VirtIO) was broken
already at that stage.

The final breaking of networking was what prompted me to raise this bug report,
as I can live with SATA but I can't not have networking.

So I believe you can get out of the "bind" without needing any of patches in
the first instance.

Cheers,

John Hartley.

-- 
You are receiving this mail because:
You are the assignee for the bug.