1 files changed, 31 insertions, 0 deletions
diff --git a/results/classifier/108/other/1315747 b/results/classifier/108/other/1315747
new file mode 100644
index 000000000..1af487064
--- /dev/null
+++ b/results/classifier/108/other/1315747
@@ -0,0 +1,31 @@
+device: 0.618
+graphic: 0.587
+performance: 0.587
+boot: 0.490
+semantic: 0.483
+permissions: 0.400
+network: 0.378
+files: 0.367
+other: 0.329
+socket: 0.260
+PID: 0.186
+vnc: 0.180
+debug: 0.130
+KVM: 0.014
+
+Qemu on Windows
+
+I have a problem with the latest snapshot from http://qemu.weilnetz.de/.  Where should I raise it?  Here?  It's not clear to me that I should do it since that's probably an unsupported build, whereas there is no support forum or e-mail address on that website.
+
+THanks.
+
+Please describe the problem, maybe I can help you then. Yes, qemu.weilnetz.de contains experimental software which might contain bugs - see the comments on that site. If I get a qualified problem report, I usually try to fix it.
+
+I have found the following symptoms with any combination of image and guest operating system, including Linux and freebsd, with qemu-system-x86_64 and qemu-system-sparc, so I'm pretty sure it's a systematic problem.  The images all boot fine on a Linux host.
+
+What's happening is that the guest operating system bootloader finds the operating system and starts to boot, but it fails as soon as it tries to read /etc/init with messages implying it can't read the root filesystem.  This is strange because the booter has read it.  I wonder if the difference is that the booter uses polled I/O whereas the operating systems use DMA and interrupts?  What ever the reason is I'm baffled on how to proceed.
+
+The host operating system is Windows 8.
+
+[Expired for QEMU because there has been no activity for 60 days.]
+