add 18th iteration of classifier

1 files changed, 117 insertions, 0 deletions

diff --git a/results/classifier/118/none/1888818 b/results/classifier/118/none/1888818
new file mode 100644
index 000000000..a742ea2eb
--- /dev/null
+++ b/results/classifier/118/none/1888818
@@ -0,0 +1,117 @@
+mistranslation: 0.570
+hypervisor: 0.516
+semantic: 0.508
+VMM: 0.444
+permissions: 0.440
+virtual: 0.435
+debug: 0.434
+ppc: 0.421
+TCG: 0.420
+performance: 0.416
+KVM: 0.415
+graphic: 0.403
+risc-v: 0.396
+user-level: 0.394
+register: 0.375
+arm: 0.372
+device: 0.361
+architecture: 0.356
+kernel: 0.345
+assembly: 0.343
+network: 0.339
+PID: 0.321
+peripherals: 0.316
+socket: 0.315
+i386: 0.314
+files: 0.310
+boot: 0.309
+vnc: 0.295
+x86: 0.261
+
+Multi-queue vhost-user fails to reconnect with qemu version >=4.2
+
+Test Environment:
+DPDK version: DPDK v20.08
+Other software versions: qemu4.2, qemu5.0.
+OS: Linux 4.15.0-20-generic
+Compiler: gcc (Ubuntu 7.3.0-16ubuntu3) 8.4.0
+Hardware platform: Purley.
+Test Setup
+Steps to reproduce
+List the steps to reproduce the issue.
+
+Test flow
+=========
+1. Launch vhost-user testpmd as port0 with 2 queues:
+
+./x86_64-native-linuxapp-gcc/app/testpmd -l 2-4 -n 4 \
+    --file-prefix=vhost --vdev 'net_vhost0,iface=vhost-net,queues=2,client=1' -- -i --txd=1024 --rxd=1024 --txq=2 --rxq=2
+testpmd>start
+
+3. Launch qemu with virtio-net:
+
+ taskset -c 13 \
+    qemu-system-x86_64 -name us-vhost-vm1 \
+       -cpu host -enable-kvm -m 2048 -object memory-backend-file,id=mem,size=2048M,mem-path=/mnt/huge,share=on \
+       -numa node,memdev=mem \
+       -mem-prealloc -monitor unix:/tmp/vm2_monitor.sock,server,nowait -netdev user,id=yinan,hostfwd=tcp:127.0.0.1:6005-:22 -device e1000,netdev=yinan \
+       -smp cores=1,sockets=1 -drive file=/home/osimg/ubuntu16.img  \
+       -chardev socket,id=char0,path=./vhost-net,server \
+       -netdev type=vhost-user,id=mynet1,chardev=char0,vhostforce,queues=2 \
+       -device virtio-net-pci,mac=52:54:00:00:00:01,netdev=mynet1,mrg_rxbuf=on,csum=on,gso=on,host_tso4=on,guest_tso4=on,mq=on,vectors=15 \
+       -vnc :10 -daemonize
+
+6. Quit testpmd and restart vhost-user :
+
+testpmd>quit
+./x86_64-native-linuxapp-gcc/app/testpmd -l 2-4 -n 4 \
+    --file-prefix=vhost --vdev 'net_vhost0,iface=vhost-net,queues=2,client=1' -- -i --txd=1024 --rxd=1024 --txq=2 --rxq=2
+
+
+Expected Result:
+After the vhost-user is killed then re-launched, the virtio-net can connect back to vhost-user again.
+
+Actual Result:
+Vhost-user relaunch failed with continous log printed"VHOST_CONFIG: Processing VHOST_USER_SET_FEATURES failed.
+
+Analysis:
+This is a regression bug, bad commit: c6beefd674f
+When vhost-user quits, QEMU doesnot save acked features for each virtio-net after vhost-user quits. When vhost-user reconnects to QEMU, QEMU sends two different features(one is the true acked feature while the another is 0x40000000) to vhost-user successively which causing vhost-user exits abnormally.
+
+The QEMU project is currently moving its bug tracking to another system.
+For this we need to know which bugs are still valid and which could be
+closed already. Thus we are setting the bug state to "Incomplete" now.
+
+If the bug has already been fixed in the latest upstream version of QEMU,
+then please close this ticket as "Fix released".
+
+If it is not fixed yet and you think that this bug report here is still
+valid, then you have two options:
+
+1) If you already have an account on gitlab.com, please open a new ticket
+for this problem in our new tracker here:
+
+    https://gitlab.com/qemu-project/qemu/-/issues
+
+and then close this ticket here on Launchpad (or let it expire auto-
+matically after 60 days). Please mention the URL of this bug ticket on
+Launchpad in the new ticket on GitLab.
+
+2) If you don't have an account on gitlab.com and don't intend to get
+one, but still would like to keep this ticket opened, then please switch
+the state back to "New" within the next 60 days (otherwise it will get
+closed as "Expired"). We will then eventually migrate the ticket auto-
+matically to the new system (but you won't be the reporter of the bug
+in the new system and thus won't get notified on changes anymore).
+
+Thank you and sorry for the inconvenience.
+
+
+
+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/277
+
+