1 files changed, 46 insertions, 0 deletions
diff --git a/results/classifier/118/performance/1032 b/results/classifier/118/performance/1032
new file mode 100644
index 00000000..82d947ee
--- /dev/null
+++ b/results/classifier/118/performance/1032
@@ -0,0 +1,46 @@
+performance: 0.978
+peripherals: 0.929
+architecture: 0.893
+device: 0.876
+virtual: 0.867
+graphic: 0.863
+x86: 0.854
+user-level: 0.813
+hypervisor: 0.793
+files: 0.744
+network: 0.736
+socket: 0.729
+assembly: 0.726
+boot: 0.717
+mistranslation: 0.700
+PID: 0.695
+permissions: 0.674
+TCG: 0.671
+kernel: 0.655
+VMM: 0.614
+risc-v: 0.613
+register: 0.554
+semantic: 0.541
+debug: 0.506
+arm: 0.499
+KVM: 0.498
+vnc: 0.497
+ppc: 0.383
+i386: 0.311
+
+Slow random performance of virtio-blk
+Steps to reproduce:
+1. Download Virtualbox Windows 11 image from https://developer.microsoft.com/en-us/windows/downloads/virtual-machines/
+2. Download virtio-win-iso: `wget https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.215-2/virtio-win-0.1.215.iso`
+3. Extract WinDev*.zip `unzip WinDev2204Eval.VirtualBox.zip`and import the extracted Ova in VirtualBox (import WinDev with the option "conversion to vdi" clicked)
+4. `qemu-img convert -f vdi -O raw <YourVirtualBoxVMFolder>/WinDev2204Eval-disk001.vdi<YourQemuImgFolder>/WinDev2204Eval-disk001.img`
+5. Start Windows 11 in Qemu: 
+``` 
+qemu-system-x86_64 -enable-kvm -cpu host -device virtio-blk-pci,scsi=off,drive=WinDevDrive,id=virtio-disk0,bootindex=0  -drive file=<YourQemuImgFolder>/WinDev2204Eval-disk001.img,if=none,id=WinDevDrive,format=raw -net nic -net user,hostname=windowsvm -m 8G -monitor stdio -name "Windows" -usbdevice tablet -device virtio-serial -chardev spicevmc,id=vdagent,name=vdagent -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 -cdrom <YourDownloadFolder>/virtio-win-0.1.215.iso
+```
+6. Win 11 won't boot and will go into recovery mode (even the safeboot trick doesn't work here), please follow that [answer](https://superuser.com/questions/1057959/windows-10-in-kvm-change-boot-disk-to-virtio#answer-1200899) to load the viostor driver over recovery cmd
+7. Reboot the VM and it should start
+2. Install CrystalDiskMark 
+3. Execute CrystalDiskMark Benchmark
+Additional information:
+#