add new classifier result

1 files changed, 32 insertions, 0 deletions

diff --git a/results/classifier/105/device/1318 b/results/classifier/105/device/1318
new file mode 100644
index 00000000..9918e5ca
--- /dev/null
+++ b/results/classifier/105/device/1318
@@ -0,0 +1,32 @@
+device: 0.945
+instruction: 0.926
+graphic: 0.910
+network: 0.865
+socket: 0.766
+semantic: 0.655
+vnc: 0.647
+assembly: 0.569
+KVM: 0.409
+boot: 0.403
+mistranslation: 0.287
+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