1 files changed, 92 insertions, 0 deletions
diff --git a/results/classifier/118/none/1860742 b/results/classifier/118/none/1860742
new file mode 100644
index 000000000..d6c3bc18f
--- /dev/null
+++ b/results/classifier/118/none/1860742
@@ -0,0 +1,92 @@
+architecture: 0.758
+kernel: 0.727
+boot: 0.589
+device: 0.575
+x86: 0.564
+permissions: 0.536
+ppc: 0.521
+PID: 0.476
+socket: 0.468
+user-level: 0.412
+graphic: 0.374
+assembly: 0.366
+hypervisor: 0.340
+semantic: 0.336
+performance: 0.335
+files: 0.327
+VMM: 0.325
+peripherals: 0.301
+i386: 0.301
+vnc: 0.292
+virtual: 0.279
+arm: 0.257
+mistranslation: 0.252
+risc-v: 0.247
+debug: 0.234
+network: 0.213
+register: 0.189
+TCG: 0.170
+KVM: 0.137
+
+xv6 Bootloop
+
+Qemu Version: 4.2.0
+
+Launch command: 
+qemu-system-x86_64 -nographic -drive file=fs.img,index=1,media=disk,format=raw -drive file=xv6.img,index=0,media=disk,format=raw -smp 2 -m 512
+
+How to reproduce? 
+1.)  Use/install latest release of qemu (4.2.0 at time of writing)
+
+2.)  Download, build, and run xv6 (a simple os designed for learning operating systems fundamentals)
+
+cd /tmp
+git clone https://github.com/mit-pdos/xv6-public.git
+cd xv6-public
+make qemu-nox
+
+3.)  Qemu should now bootloop (seem to try to boot but then just repeat). This is what it looks like below before it repeats:
+
+SeaBIOS (version ?-20191223_100556-anatol)
+
+iPXE (http://ipxe.org) 00:03.0 CA00 PCI2.10 PnP PMM+1FF92A50+1FEF2A50 CA00
+                                                                               
+Booting from Hard Disk..
+
+
+
+Host: Arch Linux - Kernel version: 5.4.13
+Guest: xv6 (https://github.com/mit-pdos/xv6-public)
+
+Suspicion:
+
+When I was using qemu 2.11.1 inside docker, the xv6 os booted with no problem. I am thinking that something changed between Qemu 2.11.1 and Qemu 4.2.0 which is now causing boot problems.
+
+Also in my ubuntu 19.10 system.
+
+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.
+
+
+Still seems to be an issue for me.
+
+Qemu Version 5.2.0
+Arch Linux 5.11.16-arch1-1
+
+
+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/192
+
+