restructure results

1 files changed, 0 insertions, 34 deletions

diff --git a/results/classifier/108/device/1318 b/results/classifier/108/device/1318
deleted file mode 100644
index 5d23da08..00000000
--- a/results/classifier/108/device/1318
+++ /dev/null
@@ -1,34 +0,0 @@
-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