blob: 5d23da08e7f5f7bcf9aa726d48fdfb1ccdbf74f9 (
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
|
device: 0.945
graphic: 0.910
network: 0.865
PID: 0.801
performance: 0.796
socket: 0.766
permissions: 0.700
semantic: 0.655
vnc: 0.647
debug: 0.575
KVM: 0.409
boot: 0.403
files: 0.341
other: 0.184
vsock device fails with "qemu-system-x86_64: vhost_set_features failed: Operation not supported (95)" when queue_reset=true
Description of problem:
Immediately after guest vsock driver initialize, qemu prints error messages. I'm not able to connect to the guest with vsock:
```
[ 0.654463] Run /init as init process
[ 0.679778] NET: Registered PF_VSOCK protocol family
qemu-system-x86_64: vhost_set_features failed: Operation not supported (95)
qemu-system-x86_64: Error starting vhost: 95
ssh-keygen: generating new host keys: RSA DSA ECDSA ED25519
#
```
Steps to reproduce:
1. Clone `git://passt.top/passt`
2. In `passt/test`, run `make mbuto.img`
3. Run `qemu-system-x86_64 -enable-kvm -m 2048 -kernel KERNEL -initrd mbuto.img -nographic -serial stdio -nodefaults -append "console=ttyS0" -device vhost-vsock-pci,guest-cid=31415,queue_reset=true` replacing KERNEL with the host kernel image.
Additional information:
- Problem goes away if `queue_reset=false`, which means it goes away with default options prior to `69e1c14aa222` ("virtio: core: vq reset feature negotation support")
- Occurs both with and without KVM
|