1 files changed, 63 insertions, 0 deletions
diff --git a/results/classifier/118/x86/1838465 b/results/classifier/118/x86/1838465
new file mode 100644
index 000000000..b40c96cd7
--- /dev/null
+++ b/results/classifier/118/x86/1838465
@@ -0,0 +1,63 @@
+x86: 0.912
+kernel: 0.871
+device: 0.779
+architecture: 0.726
+boot: 0.718
+performance: 0.691
+graphic: 0.598
+user-level: 0.598
+TCG: 0.555
+ppc: 0.553
+virtual: 0.544
+PID: 0.509
+hypervisor: 0.478
+network: 0.474
+socket: 0.471
+files: 0.469
+mistranslation: 0.456
+permissions: 0.455
+register: 0.423
+peripherals: 0.408
+debug: 0.407
+vnc: 0.405
+arm: 0.342
+semantic: 0.321
+assembly: 0.297
+i386: 0.257
+risc-v: 0.242
+VMM: 0.234
+KVM: 0.184
+
+qemu-system-x86_64 kernel panic 30% of the time starting up VM
+
+I have created a Fedora Core 5 x86_64 VM image. When I run the image using QEMU on Windows the VM hangs while loading the kernel about 30% of the time. I am trying to use this VM with a CI software, looking at the history the build failed 27 out of 79 attempts. QEMU 3.0.0 is installed on the CI machine. I have tried using the exact same image using QEMU on Linux (Ubuntu) and found the image boot successful every time (40+ attempts). The VM image is fairly old it was created using QEMU 0.11.1.
+
+I have tried multiple versions on QEMU on windows; 0.11.1, 2.12.1, and 3.0.0 all of them fail randomly. I can reproduce the issue on several different Windows 10 computers.
+
+The command I am using to start the VM is “qemu-system-x86_64.exe -cpu qemu64 -smp cores=2 -device e1000,netdev=net0 -boot menu=off -m 1G -drive `"file=C:\qimages\Fedora-Core-5-x64.qcow2,index=0,media=disk`" -snapshot -netdev user,id=net0,hostfwd=tcp::10022-:22”
+
+I can provide the qcow image but it is somewhat large coming it at 4.15GB so I’m not sure what would be the best way to transfer it.
+
+
+
+Is this using TCG (i.e. emulation) rather than Hyper V virtualisation?
+
+There are problems reliable booting the VM using TCG, HAXM, and Hyper-V. TCG fails the least often. Attached is a pic of the error using HAXM, a lot of "BUG: soft lockup detect on CPU#x!". 
+
+I tried to add logging but nothing ever shows up in the log file. I tried adding "-d cpu,guest_errors -D E:\log.txt" to the command but the log file is always empty.
+
+The QEMU project is currently considering to move 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 older bugs to
+"Incomplete" now.
+
+If you still think this bug report here is valid, then please switch
+the state back to "New" within the next 60 days, otherwise this report
+will be marked as "Expired". Or please mark it as "Fix Released" if
+the problem has been solved with a newer version of QEMU already.
+
+Thank you and sorry for the inconvenience.
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+