Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 19 Jan 2020 08:58:37 +0000
From:      bugzilla-noreply@freebsd.org
To:        virtualization@FreeBSD.org
Subject:   [Bug 236922] Virtio fails as QEMU-KVM guest with Q35 chipset on Ubuntu 18.04.2 LTS
Message-ID:  <bug-236922-27103-b0kkKtAzNz@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-236922-27103@https.bugs.freebsd.org/bugzilla/>
References:  <bug-236922-27103@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236922

--- Comment #50 from John Hartley <drum@graphica.com.au> ---
(In reply to Tommy P from comment #43)

Hi Tomny P,

Teting: Q35, OVMF, VirtIO Storage, em / vmx / re with netmap networking

I believe I have not got repeatable way to get VirtIO (minus networking) and
other general networking going on 12.1 .

I outlined process here:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236922#c49

Which in summary:

1. Use new VirtIO update provide by your patch
2. Disable VirtIO network from dev/virtio and modules/virtio
3. Apply netmap updates, but extend scope of condition compilation in
sys/dev/netmap/if_ptnet.c to as per this snippet:

<<snip>>
...
#include <dev/netmap/netmap_mem2.h>

#ifdef WITH_PTNETMAP
#include <dev/virtio/network/virtio_net.h>

#ifndef INET
#error "INET not defined, cannot support offloadings"
#endif
...
<<end snip>>

4. Remove vtnet driver from sys/amd64/conf/GENERIC & virtio network from
sys/conf/files

5. Ensure you have right QEMU Q35 machine version.

There is a caveat. This build works on with Q35 v 3.1 not 4.0.

From: virsh dumpxml

<<snip>>
...
<type arch=3D'x86_64' machine=3D'pc-q35-3.1'>hvm</type>
...
<<end snip>>

So VirtIO is seeing some difference in behaviour. So that for:
- Q35-3.1 you get VirtIO Storage
- Q35-4.0 you do not get VirtIO Storage

Matts has also been seeing variation in netmap networking cross QEMU 3.1 and
QEMU 4.1, so this machine variation across release is likely related:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D241774#c69

Likely as per MattS case this is new bug and explains why people are getting
different testing results.

Cheers,

John Hartley.

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-236922-27103-b0kkKtAzNz>