3 files changed, 117 insertions, 0 deletions
diff --git a/results/classifier/108/other/1315 b/results/classifier/108/other/1315
new file mode 100644
index 000000000..48ca4f3a7
--- /dev/null
+++ b/results/classifier/108/other/1315
@@ -0,0 +1,16 @@
+device: 0.874
+network: 0.863
+performance: 0.598
+debug: 0.512
+graphic: 0.438
+semantic: 0.254
+PID: 0.180
+permissions: 0.162
+boot: 0.115
+socket: 0.091
+vnc: 0.085
+KVM: 0.066
+other: 0.041
+files: 0.014
+
+Assertion failure in vmxnet3_activate_device
diff --git a/results/classifier/108/other/1315257 b/results/classifier/108/other/1315257
new file mode 100644
index 000000000..804af2009
--- /dev/null
+++ b/results/classifier/108/other/1315257
@@ -0,0 +1,70 @@
+graphic: 0.818
+permissions: 0.815
+performance: 0.814
+debug: 0.768
+semantic: 0.734
+PID: 0.728
+device: 0.725
+KVM: 0.718
+other: 0.714
+socket: 0.678
+boot: 0.666
+files: 0.588
+network: 0.556
+vnc: 0.502
+
+QEMU get black screen when adjust resolution in full screen mode. 
+
+Description:
+QEMU cause X11 error when adjust resolution in full screen mode or start QEMU with "-full-screen".
+
+Additional info:
+* host OS infomation
+    Archlinux 64bit
+* gest OS infomation
+    Windows XP SP3 32bit
+* Archlinux package version(s)
+qemu 1.7.1-1
+cinnamon 2.2.3-3
+sdl 1.2.15-5
+xf86-video-ati 1:7.3.0-1
+xf86-video-fbdev 0.4.4-2
+xf86-video-modesetting 0.8.1-2
+xf86-video-vesa 2.3.2-4
+xorg-server 1.15.1-1
+
+* error output in Xterm
+X Error of failed request:  BadValue (integer parameter out of range for operation)
+  Major opcode of failed request:  153 (XFree86-VidModeExtension)
+  Minor opcode of failed request:  10 (XF86VidModeSwitchToMode)
+  Value in failed request:  0x2c2
+  Serial number of failed request:  412
+  Current serial number in output stream:  414
+
+* Xorg log output
+    *with the command "grep EE /var/log/Xorg.0.log"
+        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
+[  7726.317] Initializing built-in extension MIT-SCREEN-SAVER
+    *with the command "grep WW /var/log/Xorg.0.log"
+        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
+[  7726.314] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/misc/".
+[  7726.314] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
+[  7726.314] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
+[  7726.316] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
+[  7726.334] (WW) Falling back to old probe method for modesetting
+[  7726.334] (WW) Falling back to old probe method for fbdev
+[  7726.335] (WW) Falling back to old probe method for vesa
+
+Steps to reproduce:
+1.Start QEMU with the command:
+    qemu-system-i386 -enable-kvm -machine type=pc,accel=kvm -rtc base=localtime -nodefaults -no-quit -usbdevice tablet -cpu host -smp 2 -m 1G -vga std -soundhw ac97 -net nic,model=virtio -net bridge,br=virbr0 -drive if=virtio,index=0,media=disk,format=raw,cache=none,file=/home/user/VM/WinXP.img
+2.Press ctl + alt + f to full screen.
+3.Adjust resolution in guest OS.
+or
+1.Make sure the guest OS resolution is not the same as host OS.
+2.Start QEMU with parameter "-full-screen".
+
+Looking through old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?
+
+[Expired for QEMU because there has been no activity for 60 days.]
+
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.]
+