From 3e4c5a6261770bced301b5e74233e7866166ea5b Mon Sep 17 00:00:00 2001 From: Christian Krinitsin Date: Sun, 1 Jun 2025 21:35:14 +0200 Subject: clean up repository --- .../target_missing/host_missing/accel_missing/1032 | 16 ---------------- 1 file changed, 16 deletions(-) delete mode 100644 gitlab/issues_text/target_missing/host_missing/accel_missing/1032 (limited to 'gitlab/issues_text/target_missing/host_missing/accel_missing/1032') diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1032 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1032 deleted file mode 100644 index 039b57fd4..000000000 --- a/gitlab/issues_text/target_missing/host_missing/accel_missing/1032 +++ /dev/null @@ -1,16 +0,0 @@ -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 /WinDev2204Eval-disk001.vdi/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=/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 /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: -# -- cgit 1.4.1