blob: 6bc10b8f647058761ce969c3b2f0486c840f785b (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
|
device: 0.849
network: 0.748
virtual: 0.582
socket: 0.561
graphic: 0.514
vnc: 0.466
PID: 0.425
hypervisor: 0.420
performance: 0.411
architecture: 0.411
i386: 0.394
boot: 0.384
TCG: 0.370
register: 0.364
risc-v: 0.346
files: 0.328
x86: 0.319
arm: 0.309
VMM: 0.309
mistranslation: 0.307
ppc: 0.298
kernel: 0.280
semantic: 0.258
peripherals: 0.248
permissions: 0.241
KVM: 0.193
debug: 0.091
user-level: 0.073
assembly: 0.028
virtio-net ignores the absence of the VIRTIO_NET_F_CTRL_VQ feature bit
When negotiating virtio-net feature bits, the device ignores the absence of the VIRTIO_NET_F_CTRL_VQ bit in driver feature bits and provides three virtqueues, including the control virtqueue, even though the driver is expecting only the receive and transmit virtqueues. Looking into the source code, it appears it always assumes the presence of the control virtqueue, violating thus the VIRTIO version 1.0 specification.
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/151
|