add deepseek and gemma results

author: Christian Krinitsin <mail@krinitsin.com> 2025-07-03 07:27:52 +0000
committer: Christian Krinitsin <mail@krinitsin.com> 2025-07-03 07:27:52 +0000
commit: d0c85e36e4de67af628d54e9ab577cc3fad7796a (patch)
tree: f8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/deepseek-2-tmp/output/graphic
parent: 7f4364274750eb8cb39a3e7493132fca1c01232e (diff)
download: emulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz
emulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip
321 files changed, 0 insertions, 5677 deletions
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1001 b/results/classifier/deepseek-2-tmp/output/graphic/1001
deleted file mode 100644
index 7dcd022a..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1001
+++ /dev/null
@@ -1,2 +0,0 @@
-
-query the current cursor position with QMP
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1017793 b/results/classifier/deepseek-2-tmp/output/graphic/1017793
deleted file mode 100644
index 7a8496ea..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1017793
+++ /dev/null
@@ -1,6 +0,0 @@
-
-S3 Trio64V+ support
-
-Is it possible to add S3 Trio emulation to QEMU at all? Since 0.12.3 the Cirrus Logic seems no longer working properly (bad font render/corrupted video). Also, S3 is a widely supported device on many OSes and architectures, which will give more compatibility for QEMU.
-
-Thanks!
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1020 b/results/classifier/deepseek-2-tmp/output/graphic/1020
deleted file mode 100644
index 2f17ce59..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1020
+++ /dev/null
@@ -1,17 +0,0 @@
-
-Display mode 0x6 doubles lines
-Description of problem:
-When developing https://github.com/korneliuszo/ne2000xt I've occured problem with double lines in mode 0x06 of VGA display, problem doesn't exist in mode 0x05
-Steps to reproduce:
-1. Call int 0x10, to setup video mode
-2. put data into video ram  (./cga.py -i 192.168.1.102 -I ~/a.png)
-3. bad display
-Additional information:
-Bad display:
-![a](/uploads/a6d13b7f5f45000c46371b0bdf526d2a/a.png)
-
-Same data, but in mode 0x05
-![b](/uploads/585d4dfe35b4ee028374100c10929f68/b.png)
-
-Same script as in bad display but run under 86Box
-![20220510-172456-004004](/uploads/bf42813fbcbb6a73e736d0635c6425c5/20220510-172456-004004.png)
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1021649 b/results/classifier/deepseek-2-tmp/output/graphic/1021649
deleted file mode 100644
index da402cc8..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1021649
+++ /dev/null
@@ -1,10 +0,0 @@
-
-qemu 1.1.0 waits for a keypress at boot
-
-qemu 1.1.0 waits for a keypress at boot.  Please don't ever do this.
-
-Try the attached test script.  When run it will initially print nothing, until you hit a key on the keyboard.
-
-Removing -nographic fixes the problem.
-
-Using virtio-scsi instead of virtio-blk fixes the problem.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1022023 b/results/classifier/deepseek-2-tmp/output/graphic/1022023
deleted file mode 100644
index 5e0e46e5..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1022023
+++ /dev/null
@@ -1,7 +0,0 @@
-
-vga/std lacks few wide screen modes.
-
-hi,
-i have noticed that qemu-1.0.1 doesn't support few widescreen modes on -vga std, e.g. 1680x1050, 1600x1000, 1440x900.
-i have a few laptops with kvm and i would like to work with qemu windows guest native full wide screen mode.
-could you please add these modes?
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1036 b/results/classifier/deepseek-2-tmp/output/graphic/1036
deleted file mode 100644
index be15bc6f..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1036
+++ /dev/null
@@ -1,16 +0,0 @@
-
-QEMU immediately exits when combining a GL-enabled SDL display with SPICE
-Description of problem:
-Running QEMU with the given command line results in QEMU immediately exiting with this line being printed, and no other output:
-
-```
-qemu-system-x86_64: Display spice is incompatible with the GL context
-```
-
-I am unsure whether this is a supported mode of setting up QEMU, but QEMU 6.2.0 ran just fine with it (or, to be more precise, it wasn't an issue until ac32b2fff127843355b4f7e7ac9f93dd4a395adf).
-
-The issue does not happen with `-display sdl,gl=off`, as GL is presumably not involved at all in that case.
-Steps to reproduce:
-1. Run `./qemu-system-x86_64 -display sdl,gl=on -spice port=5930`.
-Additional information:
-This issue has been reproduced on other distributions, including Ubuntu 20.04 and Ubuntu 22.04.
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1037606 b/results/classifier/deepseek-2-tmp/output/graphic/1037606
deleted file mode 100644
index d7a75499..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1037606
+++ /dev/null
@@ -1,6 +0,0 @@
-
-vmwgfx does not work with kvm vmware vga
-
-vmwgfx driver fails to initialize inside kvm.
-
-tried: kvm -m 2048 -vga vmware -cdrom RebeccaBlackLinux.iso (Ubuntu based, any Ubuntu live CD would do)
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/104 b/results/classifier/deepseek-2-tmp/output/graphic/104
deleted file mode 100644
index c5c31cdf..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/104
+++ /dev/null
@@ -1,2 +0,0 @@
-
-Cursor jumps on shape change with vmware vga
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1054558 b/results/classifier/deepseek-2-tmp/output/graphic/1054558
deleted file mode 100644
index f3ee8d9f..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1054558
+++ /dev/null
@@ -1,7 +0,0 @@
-
-1366x768 resolution missing
-
-I use ArchLinux with QEMU 1.2.0.
-I found that 1366x768 resolution is missing, even if I use -vga std or -vga vmware.
-I think that it is necessary to patch it into the source.
-Also, why not add a command-line option to specify custom resolutions without patching the source? (I know that VirtualBox has a hidden option to add any resolution.)
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/108 b/results/classifier/deepseek-2-tmp/output/graphic/108
deleted file mode 100644
index 724c9025..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/108
+++ /dev/null
@@ -1,2 +0,0 @@
-
-Windows ME falsely detects qemu's videocards as Number Nine Imagine 128
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1087974 b/results/classifier/deepseek-2-tmp/output/graphic/1087974
deleted file mode 100644
index 3331111b..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1087974
+++ /dev/null
@@ -1,5 +0,0 @@
-
-[regression] vnc tight png produces garbled output
-
-VNC Tight PNG compression did work fine two or three month ago but don't anymore. Now when Tight PNG is used parts of the desktop are shown but they are scrambled together.
-I have always tested this feature against QEMU git with noVNC by only allowing Tight PNG compression.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1108 b/results/classifier/deepseek-2-tmp/output/graphic/1108
deleted file mode 100644
index 540c488a..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1108
+++ /dev/null
@@ -1,2 +0,0 @@
-
-D-Bus display does fails to build if libgdm is not detected
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1119861 b/results/classifier/deepseek-2-tmp/output/graphic/1119861
deleted file mode 100644
index 79aae87c..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1119861
+++ /dev/null
@@ -1,20 +0,0 @@
-
-Poor console performance in Windows 7
-
-As part of its conformance test suite, Wine tests the behavior of the Windows console API. Part of this test involves opening a test console and scrolling things around. The test probably does not need to perform that many scroll operations to achieve its goal. However as is it illustrates a significant performance issue in QEmu. Unfortunately it does so by timing out (the tests must run in less than 2 minutes). Here are the run times on a few configurations:
-
- 10s - QEmu 1.4 + Q9450@2.6GHz + Windows XP + QXL + QXL driver
-  8s - QEmu 1.12 + Opteron 6128 + Windows XP + QXL + QXL driver
-127s - QEmu 1.12 + Opteron 6128 + Windows 7 + cirrus + vga driver
-127s - QEmu 1.12 + Opteron 6128 + Windows 7 + QXL + QXL driver
-147s - QEmu 1.12 + Opteron 6128 + Windows 7 + vmvga + vga driver
-145s - QEmu 1.12 + Opteron 6128 + Windows 7 + vmvga + vmware driver (xpdm, no better with all graphics effects disabled)
-
- 10s - Metal + Atom N270 + Windows XP + GMA 950 + Intel driver
-  6s - Metal + i5-3317U + Windows 8 + HD4000 + Intel driver
-  3s - VMware + Q9450@2.6GHz + Windows XP + vmvga + vmware driver
- 65s - VMware + Q9450@2.6GHz + Windows 7 + vmvga + vmware driver
-
-So when running on the bare metal all versions of Windows are about as fast. However in QEmu Windows 7 is almost 16 times slower than Windows XP! VMware is impacted too but it's still maintains a good lead in performance.
-
-Disabling all graphics effects did not help so it's not clear that the fault lies with Windows 7's compositing desktop window manager. Maybe it has to do with the lack of a proper wddm driver?
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1135567 b/results/classifier/deepseek-2-tmp/output/graphic/1135567
deleted file mode 100644
index baccd786..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1135567
+++ /dev/null
@@ -1,24 +0,0 @@
-
-QXL crashes a Windows 7 guest if host goes into screensaver
-
-Note: if further information is required, I'll be glad to supply it.
-
-I am using on the host
-- HP z800 with 72GB RAM and 2x x5680
-- Gentoo 64-bit host (3.7.9 kernel, FGLRX RADEON driver 13.1)
-- LIBVIRT 1.0.2 with QEMU(-KVM) 1.4.0
-
-The guest:
-- Windows 7 32-bit
-- 2GB allocated
-- 2 CPU
-- using virtio for everything (disk,net,memballoon)
-- Display = SPICE with spice channel
-- Video driver is qxl (ram says 64MB)
-- Spice-guest-tools 0.52 installed
-
-When I use QXL and  have the guest open in Virt-Manager/Virt-Viewer and let the host go into screensaver mode, the Win7 crashes hard.
-
-When I change video to VGA, it survives the screen saver,  no problem at all ,smooth sailing.
-
-regards
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1157368 b/results/classifier/deepseek-2-tmp/output/graphic/1157368
deleted file mode 100644
index afbaaefa..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1157368
+++ /dev/null
@@ -1,8 +0,0 @@
-
-Desktop background messed up when running Raring in a QEMU-based virtual machine
-
-Screenshot attached.
-
-Problem occurs only when choosing the default cirrus graphics card. The other graphics cards do not show this problem but are very unstable.
-
-The screenshot is of the whole desktop with a Virtual Machine Manager window containing the desktop of the VM. You see that its actual background is messed up and also the background images which you can choose when right-clicking the background and choosing "Change Desktop Background".
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1172 b/results/classifier/deepseek-2-tmp/output/graphic/1172
deleted file mode 100644
index a0634e8d..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1172
+++ /dev/null
@@ -1,60 +0,0 @@
-
-Make pixman an optional dependency
-Additional information:
-Only these files use pixman functions (excluding tests, of course):
-```
-meson.build
-contrib/vhost-user-gpu/vhost-user-gpu.c
-contrib/vhost-user-gpu/meson.build
-chardev/meson.build
-include/ui/spice-display.h
-include/ui/sdl2.h
-include/ui/gtk.h
-include/ui/qemu-pixman.h
-include/ui/console.h
-include/hw/display/xlnx_dp.h
-include/hw/virtio/virtio-gpu.h
-include/hw/virtio/virtio-gpu-pixman.h
-hw/display/vga.c
-hw/display/ramfb.c
-hw/display/vhost-user-gpu.c
-hw/display/virtio-gpu-gl.c
-hw/display/virtio-gpu-udmabuf.c
-hw/display/xenfb.c
-hw/display/ati_2d.c
-hw/display/meson.build
-hw/display/vmware_vga.c
-hw/display/qxl-render.c
-hw/display/xlnx_dp.c
-hw/display/bochs-display.c
-hw/display/sm501.c
-hw/display/virtio-gpu.c
-hw/vfio/display.c
-hw/s390x/meson.build
-ui/cocoa.m
-ui/console-gl.c
-ui/vnc.c
-ui/qemu-pixman.c
-ui/gtk.c
-ui/console.c
-ui/trace-events
-ui/meson.build
-ui/dbus-listener.c
-ui/vnc-enc-tight.c
-ui/vnc.h
-ui/spice-display.c
-ui/dbus-display1.xml
-ui/sdl2-2d.c
-```
-
-This code in `meson.build` always require **pixman** for building system emulators:
-```meson
-pixman = not_found
-if have_system or have_tools
-  pixman = dependency('pixman-1', required: have_system, version:'>=0.21.8',
-                      method: 'pkg-config', kwargs: static_kwargs)
-endif
-```
-https://gitlab.com/qemu-project/qemu/-/blob/master/meson.build#L520
-
-Most of the code could work without it.
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1186935 b/results/classifier/deepseek-2-tmp/output/graphic/1186935
deleted file mode 100644
index 6dfa4457..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1186935
+++ /dev/null
@@ -1,15 +0,0 @@
-
-[1.5] QEMU monitor gets overlapped by GTK menu bar
-
-The QEMU minitor gets partially hidden by the menu bar which was introduced in QEMU version 1.5.0.
-
-Steps to reproduce:
-
- 1. Run `qemu-system-x86_64`
- 2. Press Ctrl + Alt + 2 (or use the menu bar)
- 3. Observe that the monitor output is partially shown, without the "compat_monitor0 console" and "QEMU 1.5.0 monitor - type 'help' for more information" lines.
-
-Attached is a screenshot of `qemu-system-x86_64` and `qemu-system-x86_64 -display sdl`.
-
-Version: 1.5.0
-Distribution: Arch Linux 64-bit
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1187319 b/results/classifier/deepseek-2-tmp/output/graphic/1187319
deleted file mode 100644
index 52d390e9..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1187319
+++ /dev/null
@@ -1,9 +0,0 @@
-
-Ctrl-Alt-- and Ctrl-Alt-+ have no effect in SDL
-
-The manual page mentions Ctrl-Alt-- for shrinking a window and Ctrl-Alt-+ for enlarging it. Pressing these keys do not seem to have any effect.
-
-I tried -/= with and without holding shift and the numpad. By the way, the numpad plus and min do not have any effect in GTK either.
-
-Keyboard layout: US int with AltGr dead keys
-version: 1.5.0
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1193555 b/results/classifier/deepseek-2-tmp/output/graphic/1193555
deleted file mode 100644
index eaeb2199..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1193555
+++ /dev/null
@@ -1,12 +0,0 @@
-
-Add scale options to window menu
-
-This is a workaround against bug #504368, which makes QEMU window text blurry if resized. This is a common and annoying problem:
-
-http://butnottoohard.blogspot.com/2010/01/qemukvm-windows-7-blurry-text.html
-http://unix.stackexchange.com/questions/60564/how-can-i-restore-default-window-size-in-kvm-qemu
-
-
-The ability to resize window is a feature - it allows to adjust viewport of QEMU to the convenient working area. But there should be an option to restore the size of the window or scale it like 1:2, 2:1 etc. I don't know about if that should be exposed to QEMU monitor as some "window <command>" set , but it would be extremely convenient to provide at least Ctrl+Alt+U functionality through window level menu.
-
-Ubuntu 13.04, QEMU 1.4.0
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1193564 b/results/classifier/deepseek-2-tmp/output/graphic/1193564
deleted file mode 100644
index 2416f3ea..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1193564
+++ /dev/null
@@ -1,4 +0,0 @@
-
-monitor: rename `screendump` command to `screenshot`
-
-`screendump` is hard to memorize for occasional users. It is easier to remember `screenshot` name.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1201 b/results/classifier/deepseek-2-tmp/output/graphic/1201
deleted file mode 100644
index 1c2888c6..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1201
+++ /dev/null
@@ -1,11 +0,0 @@
-
-Qemu with Windows 10
-Description of problem:
-I see a colored screen with flashing cursor and cannot complete Windows installation.
-Steps to reproduce:
-1. Install `qemu-w64-setup-20220831.exe` on Windows 10 Pro for Workstations 21H2.
-2. `cd C:\Program Files\qemu`
-3. `qemu-img.exe create -f raw win.img 25600M`
-4. `qemu-system-i386w.exe -boot c -m 4096 -hda win.img -cdrom "C:\Users\me\Downloads\Win10_21H2_English_x64.iso"`
-Additional information:
-![xCeQH](/uploads/90a39994e020ffb174583fd3bafa520b/xCeQH.png)
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1209 b/results/classifier/deepseek-2-tmp/output/graphic/1209
deleted file mode 100644
index d3f71065..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1209
+++ /dev/null
@@ -1,6 +0,0 @@
-
-Optionally do not clear the screen when starting a VM
-Additional information:
-```
-QEMU emulator version 6.2.0 (qemu-6.2.0-14.fc36)
-```
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1211 b/results/classifier/deepseek-2-tmp/output/graphic/1211
deleted file mode 100644
index fcfd38f5..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1211
+++ /dev/null
@@ -1,8 +0,0 @@
-
-Bad fonts in "cirrus" VGA card.
-Description of problem:
-Similar to #988. Fixed by set "no_bitblt" and "sw_cursor" in XF86Config file.
-Steps to reproduce:
-Similar to #988.
-Additional information:
-
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1216368 b/results/classifier/deepseek-2-tmp/output/graphic/1216368
deleted file mode 100644
index e91a4c10..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1216368
+++ /dev/null
@@ -1,18 +0,0 @@
-
-unsupported screen resolution crashes sdl-qemu
-
-if the (windows) guest sets a screen resolution that the SDL backend does not support,
-qemu does an exit(1).
-with this fix, the the resolution is still wrong (only part of the desktop is displayed),
-but qemu keeps running and the guest can auto-revert the video mode:
-
-ui/sdl.c:do_sdl_resize()
-    SDL_Surface * tmp_screen;
-    tmp_screen = SDL_SetVideoMode(width, height, bpp, flags);
-    if (!tmp_screen) {
-//      fprintf(stderr, "Could not open SDL display (%dx%dx%d): %s\n", width, 
-//              height, bpp, SDL_GetError());
-//      exit(1);
-    } else {
-        real_screen = tmp_screen;
-    }
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1239008 b/results/classifier/deepseek-2-tmp/output/graphic/1239008
deleted file mode 100644
index c372a178..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1239008
+++ /dev/null
@@ -1,21 +0,0 @@
-
-qemu fails to scroll screen on ^Vidmem output
-
-Pascal uses ^Vidmem for B800 console output. The terminal does not oblige the Pascal OS code to scroll the output. Virtualbox emulation works, so this must be a qemu bug. Using QEMU in KVM mode as Ubuntu LTS.
-
-Source line to trip bug(in theory pushes VideoMem up one line):
-
-procedure Scroll;
-//this is whats causing crashes. FIXME:Virtualbox not affected.QEMU BUG?
-begin
-  if scrolldisabled then exit;
-      if (CursorPosY >= 24) then begin  //in case called before end of screen
-    blank:= $20 or (TextAttr shl 8);
-    Move((VidMem+(2*80))^,VidMem^,24*(2*80));
-    // Empty last line
-    FillWord((VidMem+(24*2*80))^,80,Blank);
-    CursorPosX:=1;
-    CursorPosY:=23;
-    update_cursor;
-  end;
-end;
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1243639 b/results/classifier/deepseek-2-tmp/output/graphic/1243639
deleted file mode 100644
index 4586431f..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1243639
+++ /dev/null
@@ -1,63 +0,0 @@
-
-qemu-1.5.3   segment fault  with  -vga qxl
-
-execute " qemu-system-x86_64    -enable-kvm -machine accel=kvm:tcg -m 1G  -drive file=/dev/sda  --full-screen -spice addr=127.0.0.1,port=5900,disable-ticketing -vga qxl "  on shell will  get  segment fault  after  a few seconds   if  I  don't connect to it with  spicec client  immediately.
-
-IF  excute  "spicec -h 127.0.0.1 -p 5900 "  immediately !!!!    after the  qemu-system-x86_64  execution, then  no segment fault happens  and  it runs well.
-
-=====================
-
-GDB output:
-
-root@kali-john:~# gdb /usr/local/bin/qemu-system-x86_64
-GNU gdb (GDB) 7.4.1-debian
-(gdb) run -enable-kvm -machine accel=kvm:tcg -m 1G  -drive file=/dev/sda  --full-screen -spice addr=127.0.0.1,port=5900,disable-ticketing -vga qxl
-
-[Thread debugging using libthread_db enabled]
-Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
-[New Thread 0x7ffff3737700 (LWP 14797)]
-[New Thread 0x7ffff2d54700 (LWP 14798)]
-[New Thread 0x7ffff0fff700 (LWP 14799)]
-
-Program received signal SIGSEGV, Segmentation fault.
-0x00007ffff683ad70 in pixman_image_get_data () from /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
-(gdb) bt
-#0  0x00007ffff683ad70 in pixman_image_get_data () from /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
-#1  0x000055555581060a in surface_data (s=0x5555566183a0) at /zh-download/QEMU/qemu-1.5.3/include/ui/console.h:235
-#2  0x0000555555818616 in vga_draw_graphic (s=0x55555662c778, full_update=1) at /zh-download/QEMU/qemu-1.5.3/hw/display/vga.c:1788
-#3  0x0000555555818c6a in vga_update_display (opaque=0x55555662c778) at /zh-download/QEMU/qemu-1.5.3/hw/display/vga.c:1917
-#4  0x000055555580eb15 in qxl_hw_update (opaque=0x55555662bd70) at /zh-download/QEMU/qemu-1.5.3/hw/display/qxl.c:1766
-#5  0x00005555557bd6bc in graphic_hw_update (con=0x555556618d00) at ui/console.c:254
-#6  0x00005555557c8426 in qemu_spice_display_refresh (ssd=0x55555662c418) at ui/spice-display.c:417
-#7  0x000055555580eff0 in display_refresh (dcl=0x55555662c420) at /zh-download/QEMU/qemu-1.5.3/hw/display/qxl.c:1886
-#8  0x00005555557c0cb1 in dpy_refresh (s=0x555556618370) at ui/console.c:1436
-#9  0x00005555557bd3af in gui_update (opaque=0x555556618370) at ui/console.c:192
-#10 0x0000555555797f20 in qemu_run_timers (clock=0x5555565b5a30) at qemu-timer.c:394
-#11 0x0000555555798183 in qemu_run_all_timers () at qemu-timer.c:453
-#12 0x0000555555760bb7 in main_loop_wait (nonblocking=0) at main-loop.c:470
-#13 0x00005555557cd19c in main_loop () at vl.c:2029
-#14 0x00005555557d43f2 in main (argc=13, argv=0x7fffffffe2b8, envp=0x7fffffffe328) at vl.c:4419
-(gdb) 
-
-
-======================
-
-http://www.spice-space.org/download/releases/spice-0.12.4.tar.bz2
-http://www.spice-space.org/download/releases/spice-protocol-0.12.6.tar.bz2
-spice  compiling 
-      ./configure --enable-smartcard=no   && make
-
-qemu-1.5.3
-compiling 
-    ./configure \
---disable-strip  --enable-debug \
---target-list=x86_64-softmmu,x86_64-linux-user  \
---disable-sdl  --audio-drv-list=alsa --disable-vnc --disable-xen --disable-libiscsi  \
-	--disable-seccomp --disable-glusterfs --disable-libssh2 --disable-smartcard-nss  \
-	--disable-usb-redir --disable-brlapi --disable-curl  --disable-bsd-user 		    \
-  \
---enable-kvm --enable-spice --enable-system --enable-guest-agent --enable-vhost-net 
-
-
-root@kali-john:~# qemu-system-x86_64 -version
-QEMU emulator version 1.5.3, Copyright (c) 2003-2008 Fabrice Bellard
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1249 b/results/classifier/deepseek-2-tmp/output/graphic/1249
deleted file mode 100644
index a368437f..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1249
+++ /dev/null
@@ -1,2 +0,0 @@
-
-qemu-edid Division By Zero -- by misuse of the option "-d"
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1274170 b/results/classifier/deepseek-2-tmp/output/graphic/1274170
deleted file mode 100644
index 928039cc..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1274170
+++ /dev/null
@@ -1,4 +0,0 @@
-
-qemu window hides in the background on osx
-
-When launching qemu on OSX (10.8.5), the window comes up in the background.  A bit of googling shows that the addition of [NSApp activateIgnoringOtherApps:YES]; before the [NSApp run]; in main fixes this.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1276 b/results/classifier/deepseek-2-tmp/output/graphic/1276
deleted file mode 100644
index 125044f1..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1276
+++ /dev/null
@@ -1,16 +0,0 @@
-
-[SDL] Fractional scaling is blurry
-Description of problem:
-The display looks blurry
-Steps to reproduce:
-1. Use a Wayland compositor (eg. Sway) with scale set to `1.25`
-2. Launch an Ubuntu guest with the SDL display
-3. Notice blurryness
-Additional information:
-https://github.com/libsdl-org/SDL/issues/6438
-
-Blurry display https://user-images.githubusercontent.com/67585967/197484538-fde750aa-8982-4ac2-9d83-3861f6411a31.png
-
-Display with 1.00 scale https://user-images.githubusercontent.com/67585967/197484417-afd1d1c5-5ea1-46ce-82c5-fa8d9b2df459.png
-
-It was suggested in the SDL issue (https://github.com/libsdl-org/SDL/issues/6438#issuecomment-1289513402) that it's caused by the `SDL_WINDOW_ALLOW_HIGHDPI` not being set. However, after setting that flag, the display is sharp again but it's not scaled properly (boxed) https://github.com/libsdl-org/SDL/issues/6438#issuecomment-1291663284, no idea what other changes need to be made.
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1285 b/results/classifier/deepseek-2-tmp/output/graphic/1285
deleted file mode 100644
index 92783a11..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1285
+++ /dev/null
@@ -1,21 +0,0 @@
-
-Can't use spice-app on macOS because GIO can't find handler for spice+unix scheme
-Description of problem:
-```
-qemu-system-aarch64: info: Launching display with URI: spice+unix:///tmp/.U96NU1/spice.sock
-qemu-system-aarch64: warning: GLib-GIO: No default handler found for url scheme 'spice+unix'.
-qemu-system-aarch64: warning: GLib-GIO: No default handler found for url scheme 'spice+unix'.
-qemu-system-aarch64: Failed to launch spice+unix:///tmp/.U96NU1/spice.sock URI: Operation not supported
-qemu-system-aarch64: You need a capable Spice client, such as virt-viewer 8.0
-```
-
-```
-$ virt-viewer --version
-virt-viewer version 11.0
-```
-Steps to reproduce:
-1. Have virt-viewer in $PATH
-2. Run command above
-3. Observe error above
-Additional information:
-
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1290558 b/results/classifier/deepseek-2-tmp/output/graphic/1290558
deleted file mode 100644
index 281b2e87..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1290558
+++ /dev/null
@@ -1,14 +0,0 @@
-
-color issue (ppc as guest)
-
-Hi, 
-
-on my qemu 1.6.1 -- installed via fink on host Mac OS X 10.8 -- guest PowerPc with Mac OS X 10.4 from original install disk, boots fine but I observe a color issue exactly as described here: 
-http://virtuallyfun.superglobalmegacorp.com/?p=3197
-http://virtuallyfun.superglobalmegacorp.com/?p=3189
-
-Has the problem been reported and/or fixed already? Is any workaround known or has one been suggested? 
-I apologize for a "fuzzy" problem description, but I am not an expert user. You may get in touch with me directly at <email address hidden>
-
-Thanks,
-Joe.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1294898 b/results/classifier/deepseek-2-tmp/output/graphic/1294898
deleted file mode 100644
index f64f223b..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1294898
+++ /dev/null
@@ -1,79 +0,0 @@
-
-gtk: menubar visible in fullscreen mode with gtk3
-
-Using the gtk UI, compiled with gtk3, the menu bar is fully visible in full screen mode. On gtk2 it's hidden. The set_size_request call isn't abided on gtk3 it seems.
-
-Simple fix is:
-
-diff --git a/ui/gtk.c b/ui/gtk.c
-index 66e886f..7b3bd3d 100644
---- a/ui/gtk.c
-+++ b/ui/gtk.c
-@@ -805,7 +805,7 @@ static void gd_menu_full_screen(GtkMenuItem *item, void *opaque)
- 
-     if (!s->full_screen) {
-         gtk_notebook_set_show_tabs(GTK_NOTEBOOK(s->notebook), FALSE);
--        gtk_widget_set_size_request(s->menu_bar, 0, 0);
-+        gtk_widget_hide(s->menu_bar);
-         gtk_widget_set_size_request(s->drawing_area, -1, -1);
-         gtk_window_fullscreen(GTK_WINDOW(s->window));
-         if (gd_on_vga(s)) {
-@@ -815,7 +815,7 @@ static void gd_menu_full_screen(GtkMenuItem *item, void *opaque)
-     } else {
-         gtk_window_unfullscreen(GTK_WINDOW(s->window));
-         gd_menu_show_tabs(GTK_MENU_ITEM(s->show_tabs_item), s);
--        gtk_widget_set_size_request(s->menu_bar, -1, -1);
-+        gtk_widget_show(s->menu_bar);
-         gtk_widget_set_size_request(s->drawing_area,
-                                     surface_width(s->ds),
-                                     surface_height(s->ds));
-
-
-The problem with that is that hiding the menu bar means all its associated accelerators are no longer usable, so there's way to exit fullscreen mode. That's kind of a problem :)
-
-We can install the accelerators on the window, but make sure the menu item still shows the accelerator short cut. Example with the fullscreen accelerator:
-
-diff --git a/ui/gtk.c b/ui/gtk.c
-index 66e886f..fbce2b0 100644
---- a/ui/gtk.c
-+++ b/ui/gtk.c
-@@ -799,7 +799,7 @@ static void gd_menu_show_tabs(GtkMenuItem *item, void *opaque)
-     }
- }
- 
--static void gd_menu_full_screen(GtkMenuItem *item, void *opaque)
-+static void gd_do_full_screen(void *opaque)
- {
-     GtkDisplayState *s = opaque;
- 
-@@ -828,6 +828,11 @@ static void gd_menu_full_screen(GtkMenuItem *item, void *opaque)
-     gd_update_cursor(s, FALSE);
- }
- 
-+static void gd_menu_full_screen(GtkMenuItem *item, void *opaque)
-+{
-+    gd_do_full_screen(opaque);
-+}
-+
- static void gd_menu_zoom_in(GtkMenuItem *item, void *opaque)
- {
-     GtkDisplayState *s = opaque;
-@@ -1304,10 +1309,11 @@ static GtkWidget *gd_create_menu_view(GtkDisplayState *s, GtkAccelGroup *accel_g
-     gtk_menu_set_accel_group(GTK_MENU(view_menu), accel_group);
- 
-     s->full_screen_item = gtk_menu_item_new_with_mnemonic(_("_Fullscreen"));
--    gtk_menu_item_set_accel_path(GTK_MENU_ITEM(s->full_screen_item),
--                                 "<QEMU>/View/Full Screen");
--    gtk_accel_map_add_entry("<QEMU>/View/Full Screen", GDK_KEY_f,
--                            HOTKEY_MODIFIERS);
-+    gtk_accel_group_connect(accel_group, GDK_KEY_f, HOTKEY_MODIFIERS, 0,
-+         g_cclosure_new_swap(G_CALLBACK(gd_do_full_screen), s, NULL));
-+    gtk_accel_label_set_accel(
-+        GTK_ACCEL_LABEL(gtk_bin_get_child(GTK_BIN(s->full_screen_item))),
-+        GDK_KEY_f, HOTKEY_MODIFIERS);
-     gtk_menu_shell_append(GTK_MENU_SHELL(view_menu), s->full_screen_item);
- 
-     separator = gtk_separator_menu_item_new();
-
-
-However gtk_accel_label_set_accel, which shows the accel key sequence in the menu, is gtk 3.8+ :/ So older versions wouldn't have any visual indication of the shortcuts. Maybe that's not a problem, SDL didn't have any indication of shortcuts either.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1308 b/results/classifier/deepseek-2-tmp/output/graphic/1308
deleted file mode 100644
index 7ac8c857..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1308
+++ /dev/null
@@ -1,2 +0,0 @@
-
-Qemu headless build process is stopped, complaining about a missing pixman.h
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1309034 b/results/classifier/deepseek-2-tmp/output/graphic/1309034
deleted file mode 100644
index 139361ea..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1309034
+++ /dev/null
@@ -1,29 +0,0 @@
-
-A way not to grab keyboards or mice
-
-I set up the window manager to move windows with Alt-Btn1, and to
-iconify windows with Shift-Btn1. But since qemu grabs keyboards and
-mice, I can't move or iconify the qemu window.
-
-I tried not to grab anything, by inserting return, just beginnig of
-ui/sdl.c:sdl_grab_start() as follows:
-
-static void sdl_grab_start(void)
-{
-    return;
-    /*
-
-It is comfortable. I'm glad if you make a way not to grab.
-Environment variables, options, etc are welcome.
-
-Current command line is:
-QEMU_AUDIO_DRV=pa /usr/local/bin/qemu-system-x86_64 -enable-kvm -hda /dosc/win8_x64.img -soundhw hda -boot c -m 2G -cpu Nehalem,+sep -usb -usbdevice tablet -display sdl -rtc base=localtime
-
-qemu version is:
-luna:linux % qemu-system-x86_64 --version
-QEMU emulator version 1.7.93, Copyright (c) 2003-2008 Fabrice Bellard
-luna:linux % 
-
-Host: slackware64 14.1
-Host Environment: xfce4 / sawfish
-Guest: Windows 8.1 x64
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1314293 b/results/classifier/deepseek-2-tmp/output/graphic/1314293
deleted file mode 100644
index 00b74f8a..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1314293
+++ /dev/null
@@ -1,8 +0,0 @@
-
-screendump with qxl + spice shows stale data
-
-The monitor 'screendump' command returns stale data for VMs using qxl + spice. If you perform multiple screendumps, screendump #N will show roughly the display from the time screendump #N-1 was taken. This affects 'virsh screenshot' and libvirt screenshot APIs by association.
-
-Gerd explains that new monitor commands/infrastructure is likely required to handle this correctly:
-
-https://lists.gnu.org/archive/html/qemu-devel/2014-04/msg03840.html
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1315257 b/results/classifier/deepseek-2-tmp/output/graphic/1315257
deleted file mode 100644
index 3bc6f658..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1315257
+++ /dev/null
@@ -1,51 +0,0 @@
-
-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".
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1326533 b/results/classifier/deepseek-2-tmp/output/graphic/1326533
deleted file mode 100644
index 2369b574..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1326533
+++ /dev/null
@@ -1,20 +0,0 @@
-
-SDL2 UI sends a NULL to sdl_grab_start if fullscreen, which crashes
-
-in ui/sdl2.c:
-
-    if (full_screen) {
-        gui_fullscreen = 1;
-        sdl_grab_start(0);
-    }
-
-Is sent, but no null checks are made in sdl_grab_start (its assumed to be an allocated pointer). So a crash happens if you start qemu -full-screen.
-
-It should at lease send the first [0] of the newly allocated sdl2_console through.
-
-Quickly looking around should look something like:
-
-    if (full_screen) {
-        gui_fullscreen = 1;
-        sdl_grab_start(&sdl2_console[0]);
-    }
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1329 b/results/classifier/deepseek-2-tmp/output/graphic/1329
deleted file mode 100644
index d835525c..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1329
+++ /dev/null
@@ -1,13 +0,0 @@
-
-Screen doesn't update until mouse pointer moves over it
-Description of problem:
-When changing the color scheme in CDE, the screen should change 
-color everywhere at once, but doesn't do so. It only updates 
-in the area where the mouse moves. And there it does so over 
-the whole width of the screen .
-Steps to reproduce:
-1. Change color scheme in CDE
-2. Move around mouse pointer
-Additional information:
-Screen capture of the problem
-https://youtu.be/qZJzACIxSuk
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1335 b/results/classifier/deepseek-2-tmp/output/graphic/1335
deleted file mode 100644
index 95f8e3e1..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1335
+++ /dev/null
@@ -1,2 +0,0 @@
-
-hot to dump bitmap to disk
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1336801 b/results/classifier/deepseek-2-tmp/output/graphic/1336801
deleted file mode 100644
index 85cc0610..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1336801
+++ /dev/null
@@ -1,13 +0,0 @@
-
-12.04 guest hangs on a 14.04 host  server with cirrus graphics
-
-A new 12.04.4 server guest installation hangs on a 14.04 server host machine.
-
-I did the following:
-
-Created a new Virtual Machine with the Ubuntu 12.04 template using virt-manager
-Ran through the installation without a hitch to install a LAMP+SSH server. All standard options apart from that.
-On reboot the 12.04 guest started but then hung after doing fsck step.
-Trying different options (change disk driver, etc) made it progress a couple more steps but still hung.
-
-The thing that fixed it in the end was to switch to a VGA display driver, away from the default.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1338591 b/results/classifier/deepseek-2-tmp/output/graphic/1338591
deleted file mode 100644
index 57ad5e4f..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1338591
+++ /dev/null
@@ -1,20 +0,0 @@
-
-Cursor jumps on shape change with vmware vga
-
-I launch QEMU with the following command line:
-
-qemu-system-i386 /home/ruslan/iso/Windoze/qemuxp.img -m 512 -display sdl -vga vmware -enable-kvm
-
-The guest OS is Windows XP. To reproduce the problem, do this:
-
-0. Make sure guest is WinXP (don't know if it's really necessary), use vmware VGA
-1. Set mouse cursor theme to default black&white theme, i.e. that without any translucency etc.
-2. Open a text editor, e.g. built-in notepad
-3. Move the cursor inside text entry widget
-4. See the cursor jumping away. You basically can't enter the cursor there.
-
-This also reproduces with MS Word 2003 even with oxy-white cursor theme (i.e. that with translucency) — seems Word uses its plain black&transparent cursor for I-beam cursor.
-
-This doesn't happen with other VGAs, i.e. cirrus and std.
-
-I used qemu git master to test this. qemu-system-i386 --version reports version 2.0.90, git describe says v2.1.0-rc0-1-g9d9de25. This also happened in earlier QEMU versions, like 1.5.x and older.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1352130 b/results/classifier/deepseek-2-tmp/output/graphic/1352130
deleted file mode 100644
index 47957be1..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1352130
+++ /dev/null
@@ -1,31 +0,0 @@
-
-Feature Request: Add OpenGL/3D acceleration support
-
-Hello,
-I would like to request that support for OpenGL and 3D acceleration be added to QEMU. I am sure it has been discussed before, but at the dawn of a new century there are a number of possible solutions and I haven't seen anything implemented into upstream.
-
-Options -
-
-1. VMGL
-http://www.cs.toronto.edu/~andreslc/xen-gl/
-
-2. Qemu-patch
-http://web.archive.org/web/20110721175015/http://qemu-forum.ipi.fi/viewtopic.php?t=2984
-
-3. Wine
-http://www.winehq.com
-
-3.a. WineD3D links: (Direct3D-on-OpenGL wrapper)
-http://www.virtualbox.org/ticket/3639
-http://www.nongnu.org/wined3d/
-
-4. DirectX OpenGL Wrapper
-http://sourceforge.net/projects/dxglwrap
-
-5. Transgaming SwiftShader
-This technology allows software rendering of many DirectX effects.
-
-6. VMware chose Gallium3D: (12.12.2009)
-http://vmware-svga.svn.sourceforge.net/viewvc/vmware-svga/trunk/doc/gpu-wiov.pdf?revision=1
-
-Thank you.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1357226 b/results/classifier/deepseek-2-tmp/output/graphic/1357226
deleted file mode 100644
index 79bf5302..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1357226
+++ /dev/null
@@ -1,12 +0,0 @@
-
-qemu: uncaught target signal 11 (Segmentation fault) - core dumped
-
-steps to reproduce:
-pbuilder-dist utopic armhf create
-pbuilder-dist utopic armhf login
-apt-get install imagemagick
-convert foo.xpm foo.png
-qemu: uncaught target signal 11 (Segmentation fault) - core dumped
-Segmentation fault
-
-(doesn't matter if images are actually there or not)
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1361618 b/results/classifier/deepseek-2-tmp/output/graphic/1361618
deleted file mode 100644
index bf90c3c3..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1361618
+++ /dev/null
@@ -1,13 +0,0 @@
-
-sparc cg3 1152x900 display abnormal
-
-when I use -vga cg3 -g 1152x900 with qemu-system-sparc, the display is abnormal
-I had try qemu-2.1.0 on win2003 with openBIOS or OBP
-    qemu-system-sparc.exe -vga cg3 -g 1152x900
-or
-    qemu-system-sparc.exe -vga cg3 -g 1152x900 -bios ss5.bin
-
-I also try qemu-2.0.2 on debian 6.0.1a i686 on VirtualBox host win2003
-with same command, in vnc view, the display is same as on win2003.
-
-If I don't use -g 1152x900 parameter, everything is OK, sunOS 4.1.4 work well.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1368791 b/results/classifier/deepseek-2-tmp/output/graphic/1368791
deleted file mode 100644
index 1f001a6c..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1368791
+++ /dev/null
@@ -1,13 +0,0 @@
-
-qemu build fails on Ubuntu 10.04 LTS since recent pixman changes
-
-Since commit 0dfa7e30126364c434a48cb37a1a41119e536c2a, the qemu git mainline no longer builds on Ubuntu 10.04 LTS.  The build fails with:
-
-  CC    ui/input.o
-ui/qemu-pixman.c: In function 'qemu_pixelformat_from_pixman':
-ui/qemu-pixman.c:42: error: 'PIXMAN_TYPE_RGBA' undeclared (first use in this function)
-ui/qemu-pixman.c:42: error: (Each undeclared identifier is reported only once
-ui/qemu-pixman.c:42: error: for each function it appears in.)
-make: *** [ui/qemu-pixman.o] Error 1
-
-Andreas Gustafsson, <email address hidden>
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1374905 b/results/classifier/deepseek-2-tmp/output/graphic/1374905
deleted file mode 100644
index a492dbb2..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1374905
+++ /dev/null
@@ -1,28 +0,0 @@
-
-Pixelation issue in 16-bit color VGA graphics
-
-What happened:
-I ran the 9front installation ISO (here: http://r-36.net/9front/9front-3853.02ebd469f43a.iso.bz2) in QEMU, with a blank qcow2, using `qemu-system-i386 -hda 9front.qcow2.img -cdrom 9front-3853.02ebd469f43a.iso -boot d -vga std -m 1G`. During the console boot, I accept the default display settings (1024x768x16, VESA, PS2 mouse), and 9front proceeds to the GUI boot. However, every pixel is blurred, making text illegible and the GUI unusable.
-
-What I expected:
-Normal pixel rendering / normal display.
-
-Step by step instructions:
-0. Install QEMU 2.1.2 (I use Homebrew's bottle, `brew install qemu`)
-1. Download 9front ISO (9front-3853.02ebd469f43a.iso.bz2)
-2. Create new QEMU image: `qemu-img create -f qcow2 9front.qcow2.img 20G`.
-3. Boot 9front ISO: `qemu-system-i386 -hda 9front.qcow2.img -cdrom 9front-3853.02ebd469f43a.iso -boot d -vga std -m 1G`
-4. It displays a console boot screen; accept default args (local, glenda, 1024x768x16, vesa, ps2, etc...)
-5. GUI is drawn.
-6. Pixel are blurred and unreadable
-
-Details:
-This bug does not occur when 32 bit color is used, using the 1024x768x32. This bug does not occur when QEMU is built with SDL (in Homebrew, `brew install qemu --with-sdl`), although the console portion of 9front's boot runs significantly slower.
-
-System:
-OS X 10.9.5 x86-64
-Macbook Retina Late 2012
-Intel i7 Ivy Bridge dual core.
-
-Build:
-Homebrew's QEMU 2.1.2 bottle, which is build without GTK, SDL, or VDE.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1379688 b/results/classifier/deepseek-2-tmp/output/graphic/1379688
deleted file mode 100644
index 97708624..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1379688
+++ /dev/null
@@ -1,6 +0,0 @@
-
-qemu's monitor and parallel create huge window
-
-I have qemu 2.1. When I try to switch to monitor or parallel0, I get window which is 30 *thousand* pixels in height. It is only gray with no content. This did not happen with previous versions of qemu.
-
-Kwin crashes because it cannot handle such a huge window.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1392468 b/results/classifier/deepseek-2-tmp/output/graphic/1392468
deleted file mode 100644
index 33f87b60..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1392468
+++ /dev/null
@@ -1,6 +0,0 @@
-
-qemu uses a bitmap icon
-
-qemu currently uses the icon in pc-bios/qemu-icon.bmp, which, obviously, is a bitmap file. It is loaded such that white pixels will be transparent. This can cause nasty artifacts in the display.
-
-Unless there is a specific reason to use bitmaps, I'd suggest moving to, e.g., a PNG file with a proper alpha channel.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1399957 b/results/classifier/deepseek-2-tmp/output/graphic/1399957
deleted file mode 100644
index 9dc807ab..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1399957
+++ /dev/null
@@ -1,13 +0,0 @@
-
-Strange colors on PowerMac Machine OsX
-
-Strange colors on PowerMac Machine OsX
-if it used VmWare or Std i have strange color palette as result.
-I had benn made a grab of screen here 
-
-http://i1249.photobucket.com/albums/hh511/tlosm/qyellow_zps1d2dfc18.jpg
-
-My Machine is a PowerMac G5 Quad with Nvidia 7800Gtx 512mb
-
-thankyou
-Luigi
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1405176 b/results/classifier/deepseek-2-tmp/output/graphic/1405176
deleted file mode 100644
index 6fa60035..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1405176
+++ /dev/null
@@ -1,6 +0,0 @@
-
-ctrl+alt+2 not work on gtk display
-
-I download 2.2.0 release  on http://wiki.qemu.org/Download
-the monitor console does not appear in gtk display but works for sdl and vnc.
-my gtk is 3.12.2
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1412098 b/results/classifier/deepseek-2-tmp/output/graphic/1412098
deleted file mode 100644
index 05ddc9b4..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1412098
+++ /dev/null
@@ -1,15 +0,0 @@
-
-qemu crashes when ctrl-alt-u is pressed
-
-Qemu version: 2.2.0 release, compiled from source
-Host OS: Windows 7 Ultimate x64
-Guest OS: not applicable, crash occurs even without OS and occurs with all OSs
-Executable: qemu-system-i386.exe or qemu-system-i386w.exe
-
-To reproduce:
-Start qemu-system-i386 or qemu-system-i386w without any options. Press CTRL-ALT-U, which is supposed to rescale the window. Instead, qemu just crashes.
-
-Compilation:
-Qemu 2.2.0 release compiled from sources under MinGW on the host.
-Configure options used:
-'../qemu-2.2.0/configure' '--python=C:/Python27/python' '--prefix=/mingw/build/qemu-2.2.0-bin' '--target-list=i386-softmmu'
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1416246 b/results/classifier/deepseek-2-tmp/output/graphic/1416246
deleted file mode 100644
index f78b0d89..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1416246
+++ /dev/null
@@ -1,51 +0,0 @@
-
-create guest fail when compile qemu with parameter "--disable-gtk"
-
-Environment:
-------------
-Host OS (ia32/ia32e/IA64):ia32e
-Guest OS (ia32/ia32e/IA64):ia32e
-Guest OS Type (Linux/Windows):Linux
-kvm.git Commit:8fff5e374a2f6047d1bb52288af7da119bc75765
-qemu.kvm Commit:16017c48547960539fcadb1f91d252124f442482
-Host Kernel Version:3.19.0-rc3
-Hardware:Ivytown_EP, Haswell_EP
-
-
-Bug detailed description:
---------------------------
-compile the qemu with disable gtk, the create guest , the guest create fail
-
-note:
-1.qemu.git: 699eae17b841e6784dc3864bf357e26bff1e9dfe
-when compile the qemu with enable gtk or disable gtk, the guest create pass
-
-2. this should be a qemu bug
-kvm.git   +  qemu.git   = result
-8fff5e37  +  16017c48   = bad
-8fff5e37  +  699eae17   = good
-
-Reproduce steps:
-----------------
-1. git clone git://vt-sync/qemu.git qemu.git
-2. cd qemu.git
-3. ./configure --target-list=x86_64-softmmu --disable-sdl --disable-gtk
-4. make -j16
-5. ./x86_64-softmmu/qemu-system-x86_64 -enable-kvm -m 4G -smp 2 -net none /root/rhel6u5.qcow
-
-Current result:
-----------------
-create gust fail when compile qemu with disable gtk
-
-Expected result:
-----------------
-create guest pass when compile qemu with disable or enable gtk
-
-Basic root-causing log:
-----------------------
-[root@vt-ivt2 qemu.git]# ./x86_64-softmmu/qemu-system-x86_64 -enable-kvm -m 4G -smp 2 -net none /root/rhel6u5-1.qcow 
-qemu-system-x86_64: Invalid parameter 'to'
-Segmentation fault (core dumped)
-
-some dmesg message:
-qemu-system-x86[96364]: segfault at 24 ip 00007fe6d9636a69 sp 00007fffc03cf970 error 4 in qemu-system-x86_64[7fe6d9330000+4ba000]
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1425597 b/results/classifier/deepseek-2-tmp/output/graphic/1425597
deleted file mode 100644
index e084138a..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1425597
+++ /dev/null
@@ -1,15 +0,0 @@
-
-moving window + changing screen resolution = bug
-
-Steps to reproduce:
-1. Run qemu (sdl)
-2. Start moving the window
-3. At that moment the virtualized OS should change its screen resolution (for example, when switching from initial qemu screen to grub)
-
-What I see:
-Window size doesn't change, but internal screen resolution changes, so, image scale stops to be 1:1, now I see virtualized OS in wrong scale.
-
-What I expected to see:
-Window size changes so, that it keeps synchronized with internal resolution (as usual)
-
-This bug preserves at lastest git version at the moment, i. e. 3d30395f7fb3315e4ecf0de4e48790e1326bbd47
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1431 b/results/classifier/deepseek-2-tmp/output/graphic/1431
deleted file mode 100644
index 5af17d65..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1431
+++ /dev/null
@@ -1,51 +0,0 @@
-
-qemu spice support opengl
-Steps to reproduce:
-I wan to use spice support opengl, but my qemu seems not support,what can i do to support opengl for spice?
-
-qemu configure:
-```
-./configure --target-list=x86_64-softmmu --enable-kvm --enable-debug --enable-spice --enable-numa --enable-libusb --enable-curl --enable-usb-redir --enable-libiscsi  --enable-virglrenderer --enable-opengl  --enable-gtk --prefix="/usr"
-```
-
-xml:
-```xml
-<domain type='kvm'>
-    <name>test</name>
-    <memory>1048576</memory>
-    <currentMemory>1048576</currentMemory>
-    <vcpu>1</vcpu>
-    <os>
-      <type arch='x86_64' machine='pc'>hvm</type>
-    </os>
-   <cpu mode='custom' match='exact' check='full'>
-    <topology sockets='1' dies='1' cores='1' threads='1'/>
-  </cpu>
-   <features>
-     <acpi/>
-     <apic/>
-     <pae/>
-   </features>
-   <clock offset='localtime'/>
-   <on_poweroff>destroy</on_poweroff>
-   <on_reboot>restart</on_reboot>
-   <on_crash>destroy</on_crash>
-   <devices>
-     <emulator>/usr/bin/qemu-system-x86_64</emulator>
-     <disk type='file' device='disk'>
-      <driver name='qemu' type='qcow2'/>
-       <source file='/root/kk.img'/>
-       <target dev='hda' bus='ide'/>
-     </disk>
-    <input type='mouse' bus='ps2'/>
-    <graphics type='spice'>
-      <listen type='none'/>
-      <gl enable='yes' rendernode='/dev/dri/renderD128'/>
-    </graphics>
-   </devices>
-</domain>
-```
-
-error report:
-
-![image](/uploads/74ecd52966d71bbbd2921f4c292002a9/image.png)
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1439800 b/results/classifier/deepseek-2-tmp/output/graphic/1439800
deleted file mode 100644
index d86f17fe..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1439800
+++ /dev/null
@@ -1,9 +0,0 @@
-
-GTK fullscreen mode start stretched but fixes after leaving and returning full screen mode
-
-I'm running QEMU 2.2.91 compiled directly from git and starting QEMU with the -full-screen option. The guest OS is Windows 8.1 using the VGA driver from QEMU.
-
-The image can be fixed leaving the full-screen mode and returning it back. So it appears that QEMU loses the information with multiple resolution changes of the boot process and fails in the end.
-
-The description can be a little confusing, so I've put a video on Youtube, so it can demonstrate the real issue:
-https://www.youtube.com/watch?v=-lWbWEUOSsk
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1448985 b/results/classifier/deepseek-2-tmp/output/graphic/1448985
deleted file mode 100644
index 78fd72ef..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1448985
+++ /dev/null
@@ -1,25 +0,0 @@
-
-llvmpipe i386 crashes when running on qemu64 cpu
-
-I have installed Ubuntu 14.04.2 amd64 with all updates.
-I have downloaded the Ubuntu 14.0.4.2 i386 iso (ubuntu-14.04.2-desktop-i386.iso, MD5SUM = a8a14f1f92c1ef35dae4966a2ae1a264).
-
-It does not boot to Unity from QEMU-KVM with the all following commands:
-* sudo kvm -m 1536 -cdrom ubuntu-14.04.2-desktop-i386.iso
-* sudo kvm -m 1536 -cdrom ubuntu-14.04.2-desktop-i386.iso -vga std
-* sudo kvm -m 1536 -cdrom ubuntu-14.04.2-desktop-i386.iso -vga vmware
-
-ProblemType: Bug
-DistroRelease: Ubuntu 14.04
-Package: qemu-kvm 2.0.0+dfsg-2ubuntu1.10
-ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
-Uname: Linux 3.13.0-49-generic x86_64
-NonfreeKernelModules: nvidia
-ApportVersion: 2.14.1-0ubuntu3.10
-Architecture: amd64
-CurrentDesktop: Unity
-Date: Mon Apr 27 14:11:31 2015
-InstallationDate: Installed on 2015-01-04 (112 days ago)
-InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
-SourcePackage: qemu
-UpgradeStatus: No upgrade log present (probably fresh install)
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1452742 b/results/classifier/deepseek-2-tmp/output/graphic/1452742
deleted file mode 100644
index 7e46c520..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1452742
+++ /dev/null
@@ -1,10 +0,0 @@
-
-the option for vdagent communication needed for qxl scren resizing is not documented
-
-Hello,
-
-I tried running a guest with vdagent which is supposed to resize the guest screen to match client window size.
-
-However, a special serial port needs to be created for the vdagent to communicate with the client.
-
-This patch adds a short note to the vga qxl option.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1453608 b/results/classifier/deepseek-2-tmp/output/graphic/1453608
deleted file mode 100644
index 196e6852..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1453608
+++ /dev/null
@@ -1,6 +0,0 @@
-
-explain what pcsys_monitor in manpage
-
-The specification of vnc passwords seems to have changed. `man qemu-system-x86_64` mentions `set_password` to be used in `pcsys_monitor`. Both are are not further mentioned in the man page and misteriously inexisting in both the web and the source root (as far as `grep -r -I 'pcsys_monitor' .` is concerned). That's too vage to be usable.
-
-experienced with 2.3.0
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1455 b/results/classifier/deepseek-2-tmp/output/graphic/1455
deleted file mode 100644
index 84d80a4e..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1455
+++ /dev/null
@@ -1,4 +0,0 @@
-
-copy-paste not working
-Description of problem:
-copy-paste not working under Sway (wayland - wlroots) when I use `-display gtk`. This was broken recently. I have `spice-vdagent` as well as `spice-vdagentd` running properly in the guest, still copy-paste not working.
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1455254 b/results/classifier/deepseek-2-tmp/output/graphic/1455254
deleted file mode 100644
index 22a00e49..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1455254
+++ /dev/null
@@ -1,59 +0,0 @@
-
-Segmentation fault. __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:69
-
-compiled qemu at commit 1eeace9c237a729d11c7acd7c0338ab4562af637
-
-with ./configure --enable-debug --enable-vnc --target-list=x86_64-softmmu
-
-
-
-gdb --args ./qemu-system-x86_64 -nographic -parallel none -serial none -nodefconfig -nodefaults -machine accel=kvm -enable-kvm -m 1024M -vga qxl -k de -cpu qemu64 -smp cpus=1,cores=1,threads=1,sockets=1 -net nic,model=rtl8139,macaddr=xxx -net tap -drive file=freebsd.img,media=disk,if=ide -vnc :18
-GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
-Copyright (C) 2014 Free Software Foundation, Inc.
-License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
-This is free software: you are free to change and redistribute it.
-There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
-and "show warranty" for details.
-This GDB was configured as "x86_64-linux-gnu".
-Type "show configuration" for configuration details.
-For bug reporting instructions, please see:
-<http://www.gnu.org/software/gdb/bugs/>.
-Find the GDB manual and other documentation resources online at:
-<http://www.gnu.org/software/gdb/documentation/>.
-For help, type "help".
-Type "apropos word" to search for commands related to "word"...
-Reading symbols from ./qemu-system-x86_64...done.
-(gdb) run
-Starting program: /root/qemu/x86_64-softmmu/qemu-system-x86_64 -nographic -parallel none -serial none -nodefconfig -nodefaults -machine accel=kvm -enable-kvm -m 1024M -vga qxl -k de -cpu qemu64 -smp cpus=1,cores=1,threads=1,sockets=1 -net nic,model=rtl8139,macaddr=xxx-net tap -drive file=freebsd.img,media=disk,if=ide -vnc :18
-[Thread debugging using libthread_db enabled]
-Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
-[New Thread 0x7ffff44a0700 (LWP 25946)]
-ifconfig up for tap2
-add bride for tap2
-[New Thread 0x7ffff3c9f700 (LWP 25957)]
-[New Thread 0x7ffff2e99700 (LWP 25958)]
-[New Thread 0x7ffff0dd4700 (LWP 25959)]
-[New Thread 0x7fff9bfff700 (LWP 25961)]
-
-Program received signal SIGSEGV, Segmentation fault.
-__memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:69
-69	../sysdeps/x86_64/multiarch/memcmp-sse4.S: No such file or directory.
-(gdb) backtrace
-#0  __memcmp_sse4_1 () at ../sysdeps/x86_64/multiarch/memcmp-sse4.S:69
-#1  0x00005555558be7a3 in qemu_spice_create_update (ssd=0x555557240140) at ui/spice-display.c:222
-#2  0x00005555558bf610 in qemu_spice_display_refresh (ssd=0x555557240140) at ui/spice-display.c:495
-#3  0x00005555557d106e in display_refresh (dcl=0x555557240148) at hw/display/qxl.c:1857
-#4  0x00005555558b763d in dpy_refresh (s=0x5555573a0e80) at ui/console.c:1493
-#5  0x00005555558b3e5a in gui_update (opaque=0x5555573a0e80) at ui/console.c:197
-#6  0x00005555558e9651 in timerlist_run_timers (timer_list=0x5555562cbab0) at qemu-timer.c:502
-#7  0x00005555558e9699 in qemu_clock_run_timers (type=QEMU_CLOCK_REALTIME) at qemu-timer.c:513
-#8  0x00005555558e9983 in qemu_clock_run_all_timers () at qemu-timer.c:621
-#9  0x00005555558e830b in main_loop_wait (nonblocking=0) at main-loop.c:500
-#10 0x0000555555729903 in main_loop () at vl.c:1799
-#11 0x00005555557311c7 in main (argc=29, argv=0x7fffffffe9e8, envp=0x7fffffffead8) at vl.c:4385
-
-
-Linux is 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-3 (2015-04-23) x86_64 GNU/Linux
-
-
-the segfault occurs after I log into the gnome session. virtualized os is FreeBSD
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1459626 b/results/classifier/deepseek-2-tmp/output/graphic/1459626
deleted file mode 100644
index ed710fd0..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1459626
+++ /dev/null
@@ -1,14 +0,0 @@
-
-emacs (gtk3) core dumped with -vga qxl
-
-Emacs (gtk3) exited with bus error and core dumped with -vga qxl. If I use the builtin modesetting xorg driver, emacs could survive for a short while sometimes. If I use xf86-video-qxl (git r587.8babd05), it dies right away with the same error. It seems to corrupt xorg at some point as well, because sometimes I cannot exit i3 properly and gnome-terminal can go crazy afterwards (all letters become empty retangles).
-
-It doesn't seem to happen with other -vga driver.
-
-Error message is attached. Can also provide the core dumped but it's of 47M.
-
-I started the vm as root (sudo) with the following command: qemu-system-x86_64 -enable-kvm -m 4G -virtfs local,mount_tag=qemu,security_model=passthrough,path=/mnt/qemu/ -kernel /mnt/qemu/boot/vmlinuz-linux -initrd /mnt/qemu/boot/initramfs-linux-fallback.img -append 'rw root=qemu fstype=9p' -usbdevice tablet -vga qxl -spice port=12345,disable-ticketing
-
-/mnt/qemu is a btrfs snapshot of the subvolume used as the host root
-
-Arch Linux, qemu 2.3.0, xorg-server 1.17.1, linux 4.0.4, gtk 3.16.3, glib 2.44.1
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1479717 b/results/classifier/deepseek-2-tmp/output/graphic/1479717
deleted file mode 100644
index f4c563d9..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1479717
+++ /dev/null
@@ -1,6 +0,0 @@
-
-Auto resize VM doesn't work with windows 10 guest
-
-I,m using a Ubuntu 15.04 host and a windows 10 guest (both 64 bit) on a intel i7 proc. My ubuntu system is up-to-date and I'm using QEMU emulator version 2.2.0. I use virt-manager 1.0.1 and SPICE guest tools 0.100 are installed on the guest. 
-
-With the exactly same setup and a windows 7 guest I can set "Auto resize VM with window" and it perfectly works. After installing SPICE in windows 10 I can still select this box, but it doesn't work any longer.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1484925 b/results/classifier/deepseek-2-tmp/output/graphic/1484925
deleted file mode 100644
index 80cbd436..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1484925
+++ /dev/null
@@ -1,25 +0,0 @@
-
-Segfault with custom vnc client
-
-Hey,
-
-I'm using Citrix XenServer 6.5. I worte a script that uses noVNC to connect to the rfb console via xapi. When I use GRML and try to boot it, the QEMU process segfaults and kills my VM. This happens when the screen resizes and the kernel is loading:
-
-recvfrom(3, "\3\1\0\0\0\0\2\200\1\220\3\0\2\200\0\0\0P\1\220", 4096, 0, NULL, NULL) = 20
---- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0xb28000} ---
-
-I can see in the child process the following message, right before the parent Segfaults:
-read(4, "cirrus: blanking the screen line_offset=0 height=480\n", 53) = 53
-
-This issue only happens, when I have my custom php/novnc-client connected. I also tried the nodejs/novnc package from xen-orchestra - same result. Using the stock client from Citrix XenCenter it works just fine. So I think it is related to noVNC. I hope this is just a bug and not exploitable to force a VM to crash or execute code. 
-
-XenServer launches the qemu with the following command line:
-
-qemu-dm-25 --syslog -d 25 -m 2048 -boot dc -serial pty -vcpus 1 -videoram 4 -vncunused -k en-us -vnc 127.0.0.1:1 -usb -usbdevice tablet -net nic,vlan=0,macaddr=8a:43:e2:b1:57:df,model=rtl8139 -net tap,vlan=0,bridge=xenbr0,ifname=tap25.0 -acpi -monitor pty
-
-XenServer 6.5 is using the following version:
-# /usr/lib64/xen/bin/qemu-dm -help
-QEMU PC emulator version 0.10.2, Copyright (c) 2003-2008 Fabrice Bellard
-
-Greetings
-Uli Stärk
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1488212 b/results/classifier/deepseek-2-tmp/output/graphic/1488212
deleted file mode 100644
index bc4bd4df..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1488212
+++ /dev/null
@@ -1,12 +0,0 @@
-
-16bit appcrash on W2K8 32bit and Vista 32bit guests
-
-16 bit appcrash on 32bit windows 2008 and Vista guest. Used git bisect and determined the problem has occurred since vgabios update included in commit 6eefccc0bb9c34051b1e21880fc3a1c1c8686edd in qemu.git. Using a vgabios before this commit works.
-
-To reproduce boot a Vista or Windows 2008 guest and start a command window. In the command window type command.com . Notice ntvdm appcrash.
-
-
-qemu-system-x86_64 -name eccovm9 -M pc-i440fx-2.1 -cpu SandyBridge -enable-kvm -m 4096 -smp 4,sockets=4,cores=1,threads=1 -usb -drive file=/home/libvirt/images/eccovm9.img,if=none,id=drive-virtio-disk0,format=raw,cache=directsync -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0 -device usb-tablet,id=input0 -vnc 127.0.0.1:0 -vga cirrus
-
-qemu-system-x86_64 -version
-QEMU emulator version 2.4.50, Copyright (c) 2003-2008 Fabrice Bellard
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1500935 b/results/classifier/deepseek-2-tmp/output/graphic/1500935
deleted file mode 100644
index fd09fbb7..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1500935
+++ /dev/null
@@ -1,13 +0,0 @@
-
-Qemu / KVM always wants to be on top
-
-Whenever I pass with the mouse over the KVM (qemu) window, it automatically raises on top, obscuring other windows on the same desktop, which is rather intrusive...
-No other application does this.
-
-> dpkg -l qemu-kvm
-Desired=Unknown/Install/Remove/Purge/Hold
-| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
-|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
-||/ Name           Version      Architecture Description
-+++-==============-============-============-=================================
-ii  qemu-kvm       2.0.0+dfsg-2 amd64        QEMU Full virtualization
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1505062 b/results/classifier/deepseek-2-tmp/output/graphic/1505062
deleted file mode 100644
index 2dc1bca5..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1505062
+++ /dev/null
@@ -1,22 +0,0 @@
-
-Regression: QEMU 2.4 on Linux 4.2 fails to init display with SMM enabled
-
-QEMU version: 2.4, also tested b37686f (2015-10-09 12:18:13 +0100) not working. Requires KVM and SDL, possibly others.
-Kernel version: 4.1 working, 4.2 not working.
-Architecture: x86_64
-Target: x86_64, also tested i386 not working.
-
-Step 0: Install versions listed above.
-Step 1: Run "qemu-system-$TARGET -enable-kvm"
-Step 2: Run "qemu-system-$TARGET -enable-kvm -nodefaults -vga std -machine pc-i440fx-2.3"
-Step 3: Run "qemu-system-$TARGET -enable-kvm -nodefaults -vga std -machine pc-i440fx-2.4"
-Step 4: Run "qemu-system-$TARGET -enable-kvm -nodefaults -vga std -machine pc-i440fx-2.3,smm=on"
-Step 5: Run "qemu-system-$TARGET -enable-kvm -nodefaults -vga std -machine pc-i440fx-2.4,smm=off"
-Step 6: Run "qemu-system-$TARGET -enable-kvm -nodefaults -vga std -machine pc-q35-2.3"
-Step 7: Run "qemu-system-$TARGET -enable-kvm -nodefaults -vga std -machine pc-q35-2.4"
-Step 8: Run "qemu-system-$TARGET -enable-kvm -nodefaults -vga std -machine pc-q35-2.3,smm=on"
-Step 9: Run "qemu-system-$TARGET -enable-kvm -nodefaults -vga std -machine pc-q35-2.4,smm=off"
-
-Expected behavior: All 8 invocations result in an rectangular SDL window showing a framebuffer showing failure to locate a boot device.
-
-Actual behavior: Invocations corresponding to steps 2, 4, 5, 6, 8, and 9 (i.e. those using 2.4 and *not* smm=off) behave as expected, however those in steps 1, 3, and 7 result in a square black SDL window with no text. Note that step 1 is more or less the "default configuration" for QEMU with KVM.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1529764 b/results/classifier/deepseek-2-tmp/output/graphic/1529764
deleted file mode 100644
index 56722414..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1529764
+++ /dev/null
@@ -1,10 +0,0 @@
-
-No video output with the official Windows XP VMWare VGA driver
-
-Steps to reproduce:
-
-1) Set -vga to vmware
-2) Install Windows XP SP3
-3) Install VGA drivers from http://packages.vmware.com/tools/releases/latest/windows/x86/VMware-tools-windows-10.0.5-3227872.iso
-
-Result: completely black screen (even after F8 -> use VGA mode).
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1530 b/results/classifier/deepseek-2-tmp/output/graphic/1530
deleted file mode 100644
index e0a1b598..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1530
+++ /dev/null
@@ -1,12 +0,0 @@
-
-Problem with sdl,gl=on windows 10
-Description of problem:
-sdl window opens with black screen, freezes, then crashes
-Steps to reproduce:
-1. run the command
-Additional information:
-- Works fine with just `sdl`, running `gtk,gl=on` outputs `opengl is not supported by the display`
-- tried with both `-vga virtio` and `vga std`, same result
-- tried with SVM turned on and off (AMD cpu, ryzen 2600x), same result
-- built the project `./configure --enable-gtk --enable-sdl --enable-opengl, saw the `OK` for all 3
-- have opengl ver 4.6
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1530386 b/results/classifier/deepseek-2-tmp/output/graphic/1530386
deleted file mode 100644
index 7eed137a..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1530386
+++ /dev/null
@@ -1,9 +0,0 @@
-
-command.com on win95 throws video mode out
-
-on a presumed-good copy of Windows 95 obtained from http://forum.xda-developers.com/showthread.php?t=1960870, the operating system boots successfully and shows up fine, but as soon as I double-click the MS-DOS icon, the window, while remaining the same size, goes to a different resolution and only shows a small portion of what it did, with strange colors and artifacts. tried first with the Debian 2.5 package, then with latest cvs sources, then with the 2.5.0 release, all the same problem.
-
-jcomeau@aspire:/usr/src/qemu-2.5.0/build$ cd /tmp/win95/SDL/
-jcomeau@aspire:/tmp/win95/SDL$ /usr/src/qemu-2.5.0/build/i386-softmmu/qemu-system-i386 c.img 
-jcomeau@aspire:/tmp/win95/SDL$ /usr/src/qemu-2.5.0/build/i386-softmmu/qemu-system-i386 --version
-QEMU emulator version 2.5.0, Copyright (c) 2003-2008 Fabrice Bellard
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1534683 b/results/classifier/deepseek-2-tmp/output/graphic/1534683
deleted file mode 100644
index b7e0d2df..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1534683
+++ /dev/null
@@ -1,13 +0,0 @@
-
-no mouse cursor / qxl / windows seven guest 
-
-Hello, 
-When i'm using qxl graphic card with qemu 2.4.1 , and sdl2 client ( display ) , in a windows seven guest vm , there's no mouse cursor.
-I'm using last qxl driver.
-
-With windows8.1 , there is no problem, mouse cursor is present.
-
-I need this to use two monitor with a windows guest, 
-
-any suggestions are welcome, 
-Regards,
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1538 b/results/classifier/deepseek-2-tmp/output/graphic/1538
deleted file mode 100644
index 8c5bf420..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1538
+++ /dev/null
@@ -1,2 +0,0 @@
-
-igd.c gives up IGD legacy mode if no option ROM found
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1546680 b/results/classifier/deepseek-2-tmp/output/graphic/1546680
deleted file mode 100644
index 1ab21d4a..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1546680
+++ /dev/null
@@ -1,6 +0,0 @@
-
-Incorrect display colors when running big endian guest on POWER8 little endian host
-
-When running a big endian CentOS guest on a little endian host system the display shows severe color issues, probably due to endianness not being properly detected / switched in the emulated display hardware.  Little endian guests show no display issues on the same host hardware and software.
-
-See attachment for an example of the problem.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1547012 b/results/classifier/deepseek-2-tmp/output/graphic/1547012
deleted file mode 100644
index d405d79c..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1547012
+++ /dev/null
@@ -1,34 +0,0 @@
-
-qemu instances crashes with certain spice clients
-
-It's possible to make qemu instances crash when using certain browsers connected as spice-clients.
-
-my environment:
-
-- OpenStack Kilo installed from ubuntu-cloud archive (qemu-system-x86 2.2+dfsg-5expubuntu9.6~cloud0)
-- Using spice for web-console access
-
-How to reproduce:
-
-1. Start a VM on openstack
-2. access the OpenStack dashboard using iceweasel 43.0.4 
-3. Open the spice-console
-4. Leave the console open for few minutes
-5. The VM will crash on the hypervisor
-
-The content of qemu log-files for this particular VM:
-
-2016-02-18 07:25:23.655+0000: starting up
-LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=spice /usr/bin/qemu-system-x86_64 -name instance-0000188f -S -machine pc-i440fx-utopic,accel=kvm,usb=off -cpu SandyBridge,+erms,+smep,+fsgsbase,+pdpe1gb,+rdrand,+f16c,+osxsave,+dca,+pcid,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme -m 4096 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid cb04ff25-056f-4f82-a2e8-1fbb762bc29e -smbios type=1,manufacturer=OpenStack Foundation,product=OpenStack Nova,version=2015.1.2,serial=00000000-0000-0000-0000-0cc47a45f5e8,uuid=cb04ff25-056f-4f82-a2e8-1fbb762bc29e -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-0000188f.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive file=rbd:libvirt/cb04ff25-056f-4f82-a2e8-1fbb762bc29e_disk:id=cinder:key=AQBYmdBUCDq7IBAA/7tLevRjdF3Bo7522xkFqA==:auth_supported=cephx\;none:mon_host=xxx.xxx.xxx.xxx\:6789\;xxx.xxx.xxx.xxx\:6789\;xxx.xxx.xxx.xxx\:6789\;xxx.xxx.xxx.xxx\:6789\;xxx.xxx.xxx.xxx\:6789,if=none,id=drive-virtio-disk0,format=raw,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=55,id=hostnet0,vhost=on,vhostfd=58 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:a4:74:3b,bus=pci.0,addr=0x3 -chardev file,id=charserial0,path=/var/lib/nova/instances/cb04ff25-056f-4f82-a2e8-1fbb762bc29e/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1 -chardev pty,id=charchannel0 -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -spice port=5929,addr=172.24.1.30,disable-ticketing,seamless-migration=on -k fr-ch -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vgamem_mb=16,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -msg timestamp=on
-char device redirected to /dev/pts/64 (label charserial1)
-char device redirected to /dev/pts/65 (label charchannel0)
-main_channel_link: add main channel client
-main_channel_handle_parsed: net test: latency 44.136000 ms, bitrate 157538461538 bps (150240.384615 Mbps)
-inputs_connect: inputs channel client create
-red_dispatcher_set_cursor_peer:
-((null):18188): SpiceWorker-CRITICAL **: red_worker.c:1629:common_alloc_recv_buf: unexpected message size 214862 (max is 1024)
-2016-02-18 07:30:47.008+0000: shutting down
-
-It's funny because this error only occurs with certain browser versions, in my case with Iceweasel 43.0.4 and 44. 0 but it works well with Chrome 48.0.256482 and Firefox 44.0.2.
-
-Marking this a potential security issue as it could maybe lead to a denial-of-service if a user sends crafted packets.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1548170 b/results/classifier/deepseek-2-tmp/output/graphic/1548170
deleted file mode 100644
index b90aac66..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1548170
+++ /dev/null
@@ -1,18 +0,0 @@
-
-qemu-kvm-spice spice server locks up when large user image is set
-
-QEMU emulator version 2.0.0 (Debian 2.0.0+dfsg-2ubuntu1.22), Copyright (c) 2003-2008 Fabrice Bellard
-
-I have QEMU kvm spice installed, running a Windows 10 1511, freshly installed this morning, using VirtIO root volume, Ethernet, and QXL graphics through Spice. It successfully installed the latest updates, and installed Visual Studio 2010 Professional plus Service Pack 1 and updates.
-
-Upon attempting to configure the following PNG as my account's user picture in the Settings control panel applet:
-
-https://static.kode54.net/pwywcomm_christopher_8bpp.png
-
-It added successfully, but then I noticed that Windows does not support alpha blended user pictures, and it blended it against white, so I quickly replaced it with the following:
-
-https://static.kode54.net/pwywcomm_christopher_blended.png
-
-Upon assigning that, with the other one still in the previous image buttons, Spice locked up completely. The VM was still running, as evidenced by a successful Remote Desktop session.
-
-Do I need to replace my entire Qemu setup with a Git or hand built official version to verify that this isn't Ubuntu's fault?
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1553999 b/results/classifier/deepseek-2-tmp/output/graphic/1553999
deleted file mode 100644
index f45287ee..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1553999
+++ /dev/null
@@ -1,11 +0,0 @@
-
-OpenGL support is disabled
-
-$ qemu-system-x86_64 -enable-kvm -display sdl,gl=on -vga qxl
-SDL1 display code has no opengl support.
-Please recompile qemu with SDL2, using
-./configure --enable-sdl --with-sdlabi=2.0
-qemu-system-x86_64: OpenGL support is disabled
-
-
-Can you please recompile qemu with support for opengl. The -display mode allows for opengl support.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1555076 b/results/classifier/deepseek-2-tmp/output/graphic/1555076
deleted file mode 100644
index ca3a1a60..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1555076
+++ /dev/null
@@ -1,34 +0,0 @@
-
-Qemu 2.5 dont start with sdl,gl=on or gtk,gl=on
-
-with this config line 
- qemu-system-i386 -m 2047 -hda /dev/sda3 -display sdl,gl=on -sdl -vga virtio -cdrom xenial-desktop-i386.iso 
-
-
-i have this exit
-
-ERROR:ui/console-gl.c:95:surface_gl_create_texture: code should not be reached
-
-same is i use this:
-
-qemu-system-i386 -m 2047 -hda /dev/sda3 -display gtk,gl=on -sdl -vga virtio -cdrom xenial-desktop-i386.iso 
-ERROR:ui/console-gl.c:95:surface_gl_create_texture: code should not be reached
-
-
-My Os i Debian Jessie  on P5020 PPC64 4GB ram GPU RadeonHD .
-Configure gave me gl ok, sdl ok , Virtio and Virgl OK .
-
-My Mesa are the 11.3 dev ... the same issue was found on oldest and stable release of mesa .
-
-OpenGL vendor string: X.Org
-OpenGL renderer string: Gallium 0.4 on AMD TURKS (DRM 2.43.0)
-OpenGL version string: 2.1 Mesa 11.3.0-devel (git-3146014)
-OpenGL shading language version string: 1.30
-
-
-OpenGL ES profile version string: OpenGL ES 2.0 Mesa 11.3.0-devel (git-3146014)
-OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16
-
-
-Thanks 
-Luigi
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1556044 b/results/classifier/deepseek-2-tmp/output/graphic/1556044
deleted file mode 100644
index 1f734e89..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1556044
+++ /dev/null
@@ -1,9 +0,0 @@
-
-Redox GUI hangs with 100% CPU on ARM
-
-Booting into Redox OS cli on ARM with qemu-system-i386 works fine. However, starting the Redox GUI (orbital) brings up the graphical interface and then starts using 100% CPU. I'd guess it's related to mouse detection and handling.
-
-The OS image is fully usable on x86.
-
-
-https://www.dropbox.com/s/u6v2k9wzcuiycfo/redox-disk.img.xz?dl=0
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1556372 b/results/classifier/deepseek-2-tmp/output/graphic/1556372
deleted file mode 100644
index be67f982..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1556372
+++ /dev/null
@@ -1,11 +0,0 @@
-
-Superfluous popup on Cocoa to verify quit, cannot be disabled.
-
-This patch severely reduces the quality of life for developers using QEMU in a rapid Edit-Compile-Test cycle.
-Any method of quitting QEMU via the UI triggers this dialogue, whose default option is "cancel" -- necessitating the use of the mouse to click "Confirm".
-
-This dialogue cannot be disabled by any flag, and is highly annoying. Recommend a flag to disable this confirmation, or in fact disable it by default and enable it with a flag.
-
-Patch in question:
-
-https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg05031.html
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1568356 b/results/classifier/deepseek-2-tmp/output/graphic/1568356
deleted file mode 100644
index fc3db1ac..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1568356
+++ /dev/null
@@ -1,13 +0,0 @@
-
-ERROR:ui/sdl2-2d.c:120:sdl2_2d_switch:
-
-when display sdl is selected  in display switch resolution qemu exit with a core dump with this message
-
-
-ERROR:ui/sdl2-2d.c:120:sdl2_2d_switch: code should not be reached
-
-My Machine is a Cyrus+ PowerPc P5020 4gb ram Radeon 6570 2Gb
-
-This issue affected PowerMac G5 quad too .
-
-My distro is Mate 16.04
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1577937 b/results/classifier/deepseek-2-tmp/output/graphic/1577937
deleted file mode 100644
index 6f8ec2ea..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1577937
+++ /dev/null
@@ -1,24 +0,0 @@
-
-netbeans not working with std graphic driver
-
-Qemu Version:
-QEMU emulator version 2.5.1, Copyright (c) 2003-2008 Fabrice Bellard
-
-Launching VM with:
-sudo qemu-system-x86_64 -enable-kvm -m 1024M ~/guest.vm -usb -vga std
-
-Guest:
-Kali Linux 2016.1
-Kernel:
-4.4.0-kali1-amd64
-Affected Arch:
-64bit & 32bit
-
-Netbeans failing to start after netbeans splash comes up. No netbeans window is being drawn.
-Problem can be reproduced.
-It IS working with -vga qxl, so maybe there's a bug in std emulation.
-
-output from netbeans log (more in attachement):
-
-SEVERE [global]
-java.lang.RuntimeException: failed to load system cursor: DnD.Cursor.CopyDrop : cannot load system cursor: CopyDrop.32x32
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1581796 b/results/classifier/deepseek-2-tmp/output/graphic/1581796
deleted file mode 100644
index 074559a5..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1581796
+++ /dev/null
@@ -1,14 +0,0 @@
-
-console-gl.c:96:surface_gl_create_texture:code should not be reached
-
-Facing this if i enable gtk,gl option same is with sd2 gl options.
-
-PowerPc P5020 4gb ram Ubuntu Mate 16:04 
-
-tested on 
-RadeonSi 7750HD 2gb ddr3
-r600 6570 2gb ddr3
-
-
-Thanks
-Luigi
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1581936 b/results/classifier/deepseek-2-tmp/output/graphic/1581936
deleted file mode 100644
index aa46017a..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1581936
+++ /dev/null
@@ -1,67 +0,0 @@
-
-Frozen Windows 7 VMs with VGA CVE-2016-3712 fix (2.6.0 and 2.5.1.1)
-
-Hi,
-
-As already posted on the QEMU devel list [1] I stumbled upon a problem with QEMU in version 2.5.1.1 and 2.6.0.
-
-the VM shows Windows loading
-files for the installation, then the "Starting Windows" screen appears
-here it hangs and never continues.
-
-Changing the "-vga" option to cirrus solves this, the installation can
-proceed and finish. When changing back to std (or also qxl, vmware) the
-installed VM also hangs on the "Starting Windows" screen while qemu
-showing a little but no excessive load.
-
-This phenomena appears also with QEMU 2.6.0 but not with 2.6.0-rc4, a
-git bisect shows fd3c136b3e1482cd0ec7285d6bc2a3e6a62c38d7 (vga: make
-sure vga register setup for vbe stays intact (CVE-2016-3712)) as the
-culprit for this regression, as its a fix for a DoS its not an option to
-just revert it, I guess.
-
-The bisect log is:
-
-git bisect start
-# bad: [bfc766d38e1fae5767d43845c15c79ac8fa6d6af] Update version for v2.6.0 release
-git bisect bad bfc766d38e1fae5767d43845c15c79ac8fa6d6af
-# good: [975eb6a547f809608ccb08c221552f666611af25] Update version for v2.6.0-rc4 release
-git bisect good 975eb6a547f809608ccb08c221552f666611af25
-# good: [2068192dcccd8a80dddfcc8df6164cf9c26e0fc4] vga: update vga register setup on vbe changes
-git bisect good 2068192dcccd8a80dddfcc8df6164cf9c26e0fc4
-# bad: [53db932604dfa7bb9241d132e0173894cf54261c] Merge remote-tracking branch 'remotes/kraxel/tags/pull-vga-20160509-1' into staging
-git bisect bad 53db932604dfa7bb9241d132e0173894cf54261c
-# bad: [fd3c136b3e1482cd0ec7285d6bc2a3e6a62c38d7] vga: make sure vga register setup for vbe stays intact (CVE-2016-3712).
-git bisect bad fd3c136b3e1482cd0ec7285d6bc2a3e6a62c38d7
-# first bad commit: [fd3c136b3e1482cd0ec7285d6bc2a3e6a62c38d7] vga: make sure vga register setup for vbe stays intact (CVE-2016-3712).
-
-
-I could reproduce that with QEMU 2.5.1 and QEMU 2.6 on a Debian derivate
-(Promox VE) with 4.4 Kernel and also with QEMU 2.6 on an Arch Linux
-System with a 4.5 Kernel, so it should not be host distro depended. Both
-machines have Intel x86_64 processors.
-The problem should be reproducible with said Versions or a build from
-git including the above mentioned commit (fd3c136) by starting a VM with
-an Windows 7 ISO, e.g.:
-
-Freezing installation (as vga defaults to std I marked it as optional):
-./x86_64-softmmu/qemu-system-x86_64 -boot d -cdrom win7.iso -m 1024 [-vga (std|qxl|vmware)]
-
-Working installation:
-./x86_64-softmmu/qemu-system-x86_64 -boot d -cdrom win7.iso -m 1024 -vga cirrus
-
-If someone has already an installed Windows 7 VM this behaviour should be
-also observable when trying to start it with the new versions of QEMU.
-
-Noteworthy may be that Windows 10 is working, I do not had time to get
-other Windows versions and test them, I'll do that as soon as possible.
-Various Linux system also seems do work fine, at least I did not ran
-into an issue there yet.
-
-I also tried testing with SeaBIOS and OVMF as firmware, as initially I
-had no idea what broke, both lead to the same result - without the 
-CVE-2016-3712 fix they both work, with not.
-Further, KVM enabled and disabled does not make any difference.
-
-
-[1] http://lists.nongnu.org/archive/html/qemu-devel/2016-05/msg02416.html
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1585008 b/results/classifier/deepseek-2-tmp/output/graphic/1585008
deleted file mode 100644
index 8e5da80e..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1585008
+++ /dev/null
@@ -1,16 +0,0 @@
-
-Windows 7 guests hang on bootup when qxl video is used
-
-I installed libvirt-bin and virt-manager on Ubuntu 16.04.  I created a new VM for Windows 7, basically with default settings, which includes qxl video..  The Windows boot process hangs with the "Starting Windows" animation.  CPU and disk I/O drop to zero, and it continues animating.... forever and ever...  It never finishes booting.  But it doesn't fully "hang" either: the animation continues to animate.
-
-As a workaround, I set the video mode to "Cirrus" and then Windows boots but it is slow and limited.  And also apparently to be avoided:
-
-https://www.kraxel.org/blog/2014/10/qemu-using-cirrus-considered-harmful/
-
-I can confirm it's only when qxl is enabled, because if I switch from Cirrus back to qxl, it hangs again - and going back to Cirrus again "fixes" the problem.
-
-This issue is also reported elsewhere:
-
-http://serverfault.com/questions/776406/windows-7-setup-hangs-at-starting-windows-using-proxmox-4-2
-
-https://forum.proxmox.com/threads/win7-setup-hangs-in-proxmox-ve-4-2.27388/
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1588473 b/results/classifier/deepseek-2-tmp/output/graphic/1588473
deleted file mode 100644
index 345ae81d..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1588473
+++ /dev/null
@@ -1,20 +0,0 @@
-
-Qemu Mate 16.10 and Gtk dont build 
-
-when i try to build last qemu 2.6 on 16.10 of ubuntu mate i have this.
-note on 16.04 was building without problem
-  
-LINK  i386-softmmu/qemu-system-i386
-../ui/gtk.o: In function `gd_get_pointer':
-/home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_display_get_default_seat'
-/home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_seat_get_pointer'
-../ui/gtk.o: In function `gd_grab_update':
-/home/amigaone/src/qemu/ui/gtk.c:1339: undefined reference to `gdk_display_get_default_seat'
-/home/amigaone/src/qemu/ui/gtk.c:1353: undefined reference to `gdk_seat_grab'
-/home/amigaone/src/qemu/ui/gtk.c:1356: undefined reference to `gdk_seat_ungrab'
-../ui/gtk.o: In function `gd_get_pointer':
-/home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_display_get_default_seat'
-/home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_seat_get_pointer'
-/home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_display_get_default_seat'
-/home/amigaone/src/qemu/ui/gtk.c:486: undefined reference to `gdk_seat_get_pointer'
-collect2: error: ld returned 1 exit status
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1590322 b/results/classifier/deepseek-2-tmp/output/graphic/1590322
deleted file mode 100644
index 0aedd624..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1590322
+++ /dev/null
@@ -1,11 +0,0 @@
-
-mouse_button 0 takes back to initial position
-
-i wrote a python script to perform some drag function in the Qemu simulator.
-mouse_move x , y
-mouse_button 1
-mouse_move new_x,new_y
-mouse_move 0
-
-
-The mouse_move 0 doesn't release the mouse in the position new_x,new_y instead it takes  it back to the point x,y and then releases the mouse
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1591628 b/results/classifier/deepseek-2-tmp/output/graphic/1591628
deleted file mode 100644
index 5cd503ea..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1591628
+++ /dev/null
@@ -1,45 +0,0 @@
-
-2.6.0 hangs linux vm using vfio for pci passthrough of graphics card
-
-Not a duplicate of my old bug 1488363
-
-qemu version 2.5.1 works fine
-qemu version 2.6.0 fails
-
-seabios 1.9.2-1
-
-using kernel 4.5.5 with grsecurity
-
-I built using the arch packaging tools, but commented out all the patch code, so it should be vanilla.
-
-The problem is just that I start a Linux vm using either my radeon R7 260x or radeon HD 6770, and with qemu 2.6.0, it looks normal until after the grub menu, and then the screen looks broken (with mostly black, and some pixely junk spread horizontally in a few places on the screen... first we thought maybe the monitor died). I'm not sure if it's before or only at the moment where the screen resolution changes (I could check that or record it on request). Also, the VM is not pingable and does not respond to "system_powerdown" on qemu monitor.
-
-However, the same setup works fine with windows 8. And it works fine without graphics cards passed through. A usb controller passed through works fine too.
-
-
-And then I ran a bisect...
-
-        2d82f8a3cdb276bc3cb92d6f01bf8f66bf328d62 is the first bad commit
-        commit 2d82f8a3cdb276bc3cb92d6f01bf8f66bf328d62
-        Author: Alex Williamson <email address hidden>
-        Date:   Thu Mar 10 09:39:08 2016 -0700
-
-            vfio/pci: Convert all MemoryRegion to dynamic alloc and consistent functions
-            
-            Match common vfio code with setup, exit, and finalize functions for
-            BAR, quirk, and VGA management.  VGA is also changed to dynamic
-            allocation to match the other MemoryRegions.
-            
-            Signed-off-by: Alex Williamson <email address hidden>
-
-        :040000 040000 0acfd49b6ecae780b6f52a34080ecec6b3ec3672 e0cfdadede08f553463c0b23931eda81107f41b8 M      hw
-        
-then confirm it by reverting that commit
-        git checkout v2.6.0
-        git revert 2d82f8a3cdb276bc3cb92d6f01bf8f66bf328d62
-        git mergetool -t kdiff3
-            "select all from C", save
-            not sure if this is the right way to do this...but it compiles and works (bug fixed)
-        git commit -m "revert 2d82f8a3cdb276bc3cb92d6f01bf8f66bf328d62 resolve conflicts"
-
-And that 2.6.0 build with that one patch reverted works fine.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1591724 b/results/classifier/deepseek-2-tmp/output/graphic/1591724
deleted file mode 100644
index 9b83bc8f..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1591724
+++ /dev/null
@@ -1,21 +0,0 @@
-
-Windows 7 installation DVD can't boot in qemu 2.6.0/OVMF
-
-With Qemu 2.5.50 (compiled from git some time ago) I can boot Windows 7 x64 installation DVD as follows:
-~/code/qemu-v2/bin/slic-v2/native/x86_64-softmmu/qemu-system-x86_64 \
-    -machine type=pc,accel=kvm \
-    -enable-kvm \
-    -cpu host \
-    -m 2048 \
-    -vga cirrus \
-    -boot d \
-    -drive if=pflash,file=/vms/ovmf_x64_firstrun.bin,format=raw \
-    -cdrom /vms/win7_sp1.iso \
-    -monitor stdio
-
-This bug suggests different vga options https://bugs.launchpad.net/qemu/+bug/1581936. Here's the behaviours I'm getting with 2.6.0:
-
-std - "Starting Windows" with wavering flag hangs indefinitely
-cirrus - at "Starting Windows" wasps of light freeze before assembling into a flag
-qxl - "Starting Windows" with wavering flag hangs indefinitely
-virtio - "Starting Windows" with wavering flag hangs indefinitely
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1592315 b/results/classifier/deepseek-2-tmp/output/graphic/1592315
deleted file mode 100644
index 96cab627..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1592315
+++ /dev/null
@@ -1,62 +0,0 @@
-
-Windows 10 continuous screen refresh if resize guest to match window size is selected with QXL
-
-When VDA-Agent starts up, I get a continuous flicker of the screen. This is almost like a screen refresh, where I am not even able to really click on things and/or open menus.
-
-Running Windows 10, x64
-
-app-emulation/spice-0.13.1-r2::gentoo
-net-misc/spice-gtk-0.31::gentoo
-app-emulation/spice-protocol-0.12.11::gentoo
-app-emulation/qemu--2.6.0::gentoo
-nvidia-drivers-367.18
-xorg-server-1.18.3
-
-Kernel string: 
-
-Linux wks-ros 4.4.11 #6 SMP PREEMPT Mon May 30 00:01:35 MDT 2016 x86_64 Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz GenuineIntel GNU/Linux
-
-Launch string:
-
-SPICE_PORT=5924
-DRIVERS_IMG=media/virtio-win-0.1.118.iso
-SYSTEM_DISK=system.disk
-BIOS_ROM="OVMF.fd"
-DVDROM_DRIVE="/dev/sr0"
-VM_NAME="Windows 10 x64 VM"
-
-/usr/bin/qemu-system-x86_64 \
-	-machine accel=kvm \
-	-acpitable file="acpi_slic.bin" \
-	-bios "${BIOS_ROM}" \
-	-no-shutdown \
-	-cpu qemu64,+ssse3,+sse4.1,+sse4.2 \
-	-smp cpus=2,sockets=2,cores=1,threads=1 \
-	-m 16G \
-    -realtime mlock=off \
-    -drive file="${SYSTEM_DISK}",if=virtio \
-    -spice port=${SPICE_PORT},addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on \
-    -chardev spicevmc,id=charchannel0,name=vdagent \
-    -device virtio-serial-pci -chardev spicevmc,id=vdagent,debug=0,name=vdagent \
-    -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 \
-    -device qxl-vga,id=video0 \
-    -device virtio-balloon-pci,id=balloon0 \
-    -rtc base=localtime,driftfix=slew \
-    -name "${VM_NAME}" & exec spicy --title "${VM_NAME}" 127.0.0.1 -p ${SPICE_PORT}
-
-
-
-Some additional interesting things I've observed:
-
-* If the QXL driver is not installed, then the flicker doesn't happen
-* As soon as i enable the VDA Agent, the annoying flicker / screen refresh begins
-* When I disable the VDA Agent, same thing happens.
-
-- I tried Windows-Guest-Tools-0.100 and version 0.0103-r1
-
-- And an assortment of QXL drivers, (WDM, proper for Windows 10).
-
-
-As a workaround, I can set "Scale display" to On, and "Resize Guest to Match" to off (using Spicy-gtk). This stops the flicker.
-
-- Another strange thing is that I my XQL driver in Windows shows 8GB of Video mem. I am not sure how/why this is, as I have not seen this before.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1592351 b/results/classifier/deepseek-2-tmp/output/graphic/1592351
deleted file mode 100644
index 6145b840..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1592351
+++ /dev/null
@@ -1,23 +0,0 @@
-
-mouse pointer offset with gtk,gl=on
-
-When I turn gl=on for -display gtk, some Y offset is added to the mouse pointer coordinates. That is, when I click on an icon, an icon _above_ the one I clicked triggers.
-
-Using xev, it seems to be offset of 10-12 pixels.
-
-It happens with all ps/2 mouse, -usbdevice mouse and -usbdevice tablet. 
-
-Without gl=on, the pointer is precise.
-
-I have these qemu versions:
-qemu-2.6.0-470.2.x86_64
-qemu-ipxe-1.0.0-470.2.noarch
-qemu-ksm-2.6.0-470.2.x86_64
-qemu-kvm-2.6.0-470.2.x86_64
-qemu-ovmf-x86_64-2015+git1462940744.321151f-2.1.noarch
-qemu-ppc-2.6.0-470.2.x86_64
-qemu-seabios-1.9.1-470.2.noarch
-qemu-sgabios-8-470.2.noarch
-qemu-tools-2.6.0-470.2.x86_64
-qemu-vgabios-1.9.1-470.2.noarch
-qemu-x86-2.6.0-470.2.x86_64
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1600112 b/results/classifier/deepseek-2-tmp/output/graphic/1600112
deleted file mode 100644
index 2462c4f7..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1600112
+++ /dev/null
@@ -1,8 +0,0 @@
-
-Qemu GTK interface showing question marks instead of correct strings
-
-Qemu version: 2.6.0
-
-When running Qemu system emulation (configured with GTK interface), all interface strings shows up as question marks instead of the correct translated strings. Tested on locale zh_CN.UTF-8.
-
-I have attached a screenshot below for better understanding.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1606708 b/results/classifier/deepseek-2-tmp/output/graphic/1606708
deleted file mode 100644
index b5b26d3e..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1606708
+++ /dev/null
@@ -1,22 +0,0 @@
-
-QEMU crashes when switching consoles using SDL
-
-I've trying to use QEMU with SDL, and I noticed that it doesn't behave well, specially when switching from VGA to any console. Resuming, switching is erratic when using SDL, and its effects go from creating a new window, doing nothing, showing a window that disappears inmediately or even crash.
-
-Tested with:
-Arch Linux with all packages updated (2016/7/26)
-TWM as window manager
-QEMU (both stable 2.6.0-1 and latest git commit f49ee63)
-Command: qemu-system-x86_64 -display sdl
-
-sdl2 version 2.0.4-2
-
-How to reproduce:
-1. Open QEMU with the given command
-2. Try to switch console (Ctrl-Alt-2 for example)
-
-Expected behaviour:
-As in GTK, the window should now show the desired console
-
-Actual behaviour:
-Here I have to say I can't explain it very well. Almost always it just creates a new window that shows the desired console, but it is closed inmediatley. If not, it opens a new window that keeps open, and it sometimes is responsive, but further attempts to switch consoles end causing a crash, and QEMU has to be SIGKILLed
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1606899 b/results/classifier/deepseek-2-tmp/output/graphic/1606899
deleted file mode 100644
index 193b1615..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1606899
+++ /dev/null
@@ -1,12 +0,0 @@
-
-virtio-vga does not let guest poweroff properly
-
-I have a VM running rawhide (Fedora development) and I can't poweroff the machine when I enable virtio-vga. Reboot works correctly. Using QXL works also. The machine arrive to print the "Powering off" message (from Linux kernel) but then hangs.
-
-The command line is
-
-/usr/bin/qemu-system-x86_64 -machine accel=kvm -name rawhide -machine pc-i440fx-2.3,accel=kvm,usb=off -cpu Haswell-noTSX -m 2048 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 64216421-aec4-4ce4-aa52-aed9e4e31a1c -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/rawhide.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x6.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x6 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x6.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x6.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 -drive file=/home/rawhide.qcow2,if=none,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive if=none,id=drive-ide0-0-0,readonly=on -device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev user,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:fc:11:43,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/rawhide.org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel1,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=com.redhat.spice.0 -device usb-tablet,id=input0 -spice ipv4,addr=0.0.0.0,port=5900,disable-ticketing,image-compression=lz,seamless-migration=on,streaming-video=filter -device virtio-vga,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on
-
-I though was due to Virgl but disabling it does not change.
-
-I'm using Qemu 2.6.0 from Fedora 24.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1607 b/results/classifier/deepseek-2-tmp/output/graphic/1607
deleted file mode 100644
index 505ec88c..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1607
+++ /dev/null
@@ -1,2 +0,0 @@
-
-QEMU calls glXMakeCurrent which is current in another thread when running VM with SDL
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1610 b/results/classifier/deepseek-2-tmp/output/graphic/1610
deleted file mode 100644
index 03e063ac..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1610
+++ /dev/null
@@ -1,2 +0,0 @@
-
-support of directX in windows guest
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1611 b/results/classifier/deepseek-2-tmp/output/graphic/1611
deleted file mode 100644
index 48e692fc..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1611
+++ /dev/null
@@ -1,2 +0,0 @@
-
-How to test rutabaga_gfx/gfxstream patches
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1614521 b/results/classifier/deepseek-2-tmp/output/graphic/1614521
deleted file mode 100644
index 75c78f06..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1614521
+++ /dev/null
@@ -1,4 +0,0 @@
-
--display accepts "none[a-z,0-9]*" instead of 'none'
-
-When using the '-display' option the parameter 'none' is not the only string that causes the behaviour of 'none'. I can use '-display noneMICKEYMOUSE' and still have the none behaviour.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1615079 b/results/classifier/deepseek-2-tmp/output/graphic/1615079
deleted file mode 100644
index b4fc17ae..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1615079
+++ /dev/null
@@ -1,4 +0,0 @@
-
-GTK+ UI virtual consoles scrolling broken
-
-"In the virtual consoles, you can use Ctrl-Up, Ctrl-Down, Ctrl-PageUp and Ctrl-PageDown to move in the back log."
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1615212 b/results/classifier/deepseek-2-tmp/output/graphic/1615212
deleted file mode 100644
index a5c52980..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1615212
+++ /dev/null
@@ -1,4 +0,0 @@
-
-SDL UI switching to monitor half-broken and scrolling broken
-
-ctrl+alt+2 must be pressed 2 or more times for the monitor console window to appear with -sdl, the window flashes and disappears also before finally staying open
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1617385 b/results/classifier/deepseek-2-tmp/output/graphic/1617385
deleted file mode 100644
index 32f3ff65..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1617385
+++ /dev/null
@@ -1,14 +0,0 @@
-
-No snapshot possible with virtio-gpu activated
-
-I'm using "Qemu" and "Virtual Machine Manager" on Debian-8-Stretch - both newest versions out of the Debian-testing-repository (state 26.08.2016).
-
-If I try to save a virtual machine, it fails and I'll get the following error:
-
-libvirtError: internal error: unable to execute QEMU command 'migrate': State blocked by non-migratable device '0000:00:02.0/virtio-gpu'
-
-This only happens, if I chose "Virtio" as graphics-driver (no matter if I use "Spice" or "Vnc" as Server by the way). If I switch to any other driver (Cirrus, Qxl, Vga, VMvga...) there is no problem to take a snapshot and save the virtual machine.
-
-Unfortunately "virtio-gpu" (together with "Spice-Server") is the only driver that provides proper working/running my virtual machines on my PC.
-
-feuerkogel1
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1618122 b/results/classifier/deepseek-2-tmp/output/graphic/1618122
deleted file mode 100644
index f95b0d8f..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1618122
+++ /dev/null
@@ -1,46 +0,0 @@
-
-qemu-monitor screendump very slow
-
-qemu-monitor screendump often using 10-20% cpu usage of one core to take a small capture.
-
-Most of the CPU usage seems to come from libpixman. There were many reports of libpixman becoming 8 times slower in newer releases.
-
-https://github.com/qemu/qemu/blob/0c56c6ab68902281094c7aac6305e2321c34c187/ui/console.c#L285
-
-
-Simple Valgrind Ir report.
-
---------------------------------------------------------------------------------
-            Ir 
---------------------------------------------------------------------------------
-56,592,286,124  PROGRAM TOTALS
-
---------------------------------------------------------------------------------
-            Ir  file:function
---------------------------------------------------------------------------------
-40,288,379,712  ???:0x000000000000caa0 [/usr/lib64/libpixman-1.so.0.34.0]
- 3,585,795,168  ???:0x000000000006df20 [/usr/lib64/libpixman-1.so.0.34.0]
- 1,763,982,432  ???:0x0000000000052360 [/usr/lib64/libpixman-1.so.0.34.0]
- 1,517,832,033  ???:__memcpy_sse2_unaligned [/usr/lib64/libc-2.23.so]
-   993,997,885  ???:__GI_mempcpy [/usr/lib64/libc-2.23.so]
-   484,059,456  ???:0x0000000000050430 [/usr/lib64/libpixman-1.so.0.34.0]
-   460,109,168  ???:pixman_image_composite32 [/usr/lib64/libpixman-1.so.0.34.0]
-
-I tried taking a look on how to fix this, but it seems pixmap is deeply enrooted inside the monitor.  I wanted to try to simply take whats on the display and memcpy it into .ppm format manually creating the file header, but I cant figure out where the raw display buffer/image starts.
-
-For example this is DisplaySurface:
-
-struct DisplaySurface {
-    pixman_format_code_t format;
-    pixman_image_t *image;
-    uint8_t flags;
-#ifdef CONFIG_OPENGL
-    GLenum glformat;
-    GLenum gltype;
-    GLuint texture;
-#endif
-};
-
-Which as you can see already has the pixman_image_t. Maybe I should just work with that pixman_image_t?
-
-The most effective solution IMO seems to just memcpy from the display into a premade header for a .ppm or .bmp file assuming 24 or 32 bpp. No need for libpixman.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1619438 b/results/classifier/deepseek-2-tmp/output/graphic/1619438
deleted file mode 100644
index f2845be8..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1619438
+++ /dev/null
@@ -1,4 +0,0 @@
-
-GTK+ UI, delete key deletes to the left in the monitor
-
-it must delete characters to the right, otherwise it is like having two backspaces
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1620660 b/results/classifier/deepseek-2-tmp/output/graphic/1620660
deleted file mode 100644
index f62b52f7..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1620660
+++ /dev/null
@@ -1,8 +0,0 @@
-
-man page is missing suboptions for "-display"
-
-Some of the display options have suboptions, for example:
-
-> -display gtk[,grab_on_hover=on|off][,gl=on|off]
-
-None of these suboptions are currently documented in qemu-options.hx (checked git@f04ec5a)
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1622 b/results/classifier/deepseek-2-tmp/output/graphic/1622
deleted file mode 100644
index 7ead2375..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1622
+++ /dev/null
@@ -1,2 +0,0 @@
-
-PNG screendump has R/B channels swapped
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1635339 b/results/classifier/deepseek-2-tmp/output/graphic/1635339
deleted file mode 100644
index 81912fbc..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1635339
+++ /dev/null
@@ -1,12 +0,0 @@
-
-qxl_pre_save assertion failure on vm "save"
-
-When I try and save my Windows 10 VM, I see an assertion failure, and the machine is shut down.
-
-I see the following in the log:
-
-main_channel_handle_parsed: agent start
-qemu-system-x86_64: /build/qemu-Zwynhi/qemu-2.5+dfsg/hw/display/qxl.c:2101: qxl_pre_save: Assertion `d->last_release_offset < d->vga.vram_size' failed.
-2016-10-20 11:52:42.713+0000: shutting down
-
-Please let me know what other information would be relevant!
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1637511 b/results/classifier/deepseek-2-tmp/output/graphic/1637511
deleted file mode 100644
index 072f5f92..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1637511
+++ /dev/null
@@ -1,22 +0,0 @@
-
-Armitage crashes KVM guest with Kali2016.2 for QXL video
-
-I recently got a strange bug which seems to be related to qemu-kvm and QXL. I came here via the hints of the KVM web-site for KVM/qemu bug tracking. But, I am not sure whether this is the right bug-tracker at all. Please advise me if I placed the report wrongly. 
-
-I installed Kali2016.2 as a KVM guest on a Opensuse Leap 42.1 host (fully updated). The KVM guest machine was configured to use a spice display and QXL video. Everything OK with the installation with the exception of one major application with a Java interface - Armitage. 
-
-Armitage is correctly configured and starts (with some minor Java errors) and opens its interface (msf console, target window  etc.) Trying to open the 2 specific menu points "Hosts" or "Attack" in the menu bar leads to something very strange: The screen flickers, then the whole login session is stopped and a standard login window opens. This happens independently of the setting for the type of Armitage target window (graphical or table like)  
-
-Why do I report this bug here? 
-Because it happens with the QXL graphical video interface ONLY - not with video=vga or vmvga ! Neither does the bug occur when Armitage is started in a ssh (-X) session from the host. 
-
-So, it is closely related to qemu-kvm AND QXL and the Java interaction with both. 
-
-I really wonder what in the world can make 2 specific menu points of a Java application crash a KVM guest and restart a login shell in Kali only when QXL is used?  
-
-qemu-kvm version : 2.3.1
-Kernel version of OS LEAP 42.1: Linux 4.1.31-30-default           
-
-I have described the bug also to the Kali people - see https://bugs.kali.org/view.php?id=3698
-
-Please inform me what further data are required - if this is relevant in this bug-tracker at all.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1642011 b/results/classifier/deepseek-2-tmp/output/graphic/1642011
deleted file mode 100644
index c36c1138..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1642011
+++ /dev/null
@@ -1,16 +0,0 @@
-
-Mouse wheel events not forwarded to guest using GTK display
-
-Using QEMU 2.7.0 with KVM enabled, when I launch the guest without options (using the default of gtk), the mouse wheel events are not propagated to the guest.
-
-When I start qemu using -display sdk, mouse wheel events are properly forwarded.
-
-I can determine that the guest is not receiving mouse wheel events by doing cat /dev/input/by-id/usb-QEMU_QEMU_USB_Mouse_42-event-mouse. When I scroll the wheel, no output is printed to the screen.
-
-The guest is ChromiumOS.
-
-The command line is:
-
-qemu-system-x86_64 -enable-kvm -m 2G -smp 4 -vga cirrus -usbdevice mouse -pidfile /tmp/kvm.pid -chardev pipe,id=control_pipe,path=/tmp/kvm.pipe -serial file:/tmp/kvm.serial -mon chardev=control_pipe -net nic,model=virtio -net user,hostfwd=tcp:127.0.0.1:9222-:22 -drive file=chromiumos/src/build/images/amd64-generic/latest/chromiumos_qemu_image.bin,index=0,media=disk,cache=unsafe
-
-(Most of that invocation sets up Linux fifos for various and nefarious purposes and can be profitably ignored).
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1644 b/results/classifier/deepseek-2-tmp/output/graphic/1644
deleted file mode 100644
index e9cbd907..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1644
+++ /dev/null
@@ -1,15 +0,0 @@
-
-qemu 8.0.0 console-gl.c:105: surface_gl_update_texture: Assertion `gls' failed.
-Description of problem:
-run ubuntu20.04 in virtualBox, and run qemu in this ubuntu.
-1. qemu report error at qemu start.
-2. qemu-system-x86_64 can't run myOS with 'virtio-gpu-pci -display sdl,gl=on',
-3. qemu report error: qemu-system-x86_64: ../ui/console-gl.c:105: surface_gl_update_texture: Assertion `gls' failed. Aborted
-Steps to reproduce:
-1. run ubuntu20.04 in virtualBox
-2. qemu config enabled sdl, virglrenderer, opengl, gtk
-3. ./qemu-system-x86_64  -machine q35 -cpu Nehalem -m 1024 -smp 8 -kernel myOS -device virtio-gpu-pci -display sdl,gl=on
-4. qemu report error: qemu-system-x86_64: ../ui/console-gl.c:105: surface_gl_update_texture: Assertion `gls' failed. Aborted
-Additional information:
-qemu-system-x86_64: ../ui/console-gl.c:105: surface_gl_update_texture: Assertion `gls' failed.
-Aborted
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1649040 b/results/classifier/deepseek-2-tmp/output/graphic/1649040
deleted file mode 100644
index 857f851c..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1649040
+++ /dev/null
@@ -1,65 +0,0 @@
-
-Ubuntu 16.04.1 Grub Splash Doesn't Appear
-
-My Specs:
-
-Slackware 14.2 x86_64 > Host
-QEMU 2.7.0 
-
-Ubuntu 16.04.1 > Guest
-
-Start options for Ubuntu:
-
-qemu-system-x86_64 -drive format=raw,file=ubuntu.img \
--cpu host \
---enable-kvm \
--smp 2 \
--m 4096 \
--vga vmware \
--soundhw ac97 \
--usbdevice tablet \
--rtc base=localtime \
--usbdevice host:0781:5575
-
-
-
-I've started Ubuntu around 6-8 times, and I have only see the Grub Boot Splash appear twice, so pretty much without fail it typically boots past the grub splash and automatically boots...
-
-
-These are the /etc/default/grub settings; (I only changed these options GRUB_TIMEOUT=15 and GRUB_GFXMODE=1440x900)
-
-
-# If you change this file, run 'update-grub' afterwards to update
-# /boot/grub/grub.cfg.
-# For full documentation of the options in this file, see:
-#   info -f grub -n 'Simple configuration'
-
-GRUB_DEFAULT=0
-GRUB_HIDDEN_TIMEOUT=0
-GRUB_HIDDEN_TIMEOUT_QUIET=true
-GRUB_TIMEOUT=15
-GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
-GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
-GRUB_CMDLINE_LINUX=""
-
-# Uncomment to enable BadRAM filtering, modify to suit your needs
-# This works with Linux (no patch required) and with any kernel that obtains
-# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
-#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
-
-# Uncomment to disable graphical terminal (grub-pc only)
-#GRUB_TERMINAL=console
-
-# The resolution used on graphical terminal
-# note that you can use only modes which your graphic card supports via VBE
-# you can see them in real GRUB with the command `vbeinfo'
-GRUB_GFXMODE=1440x900
-
-# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
-#GRUB_DISABLE_LINUX_UUID=true
-
-# Uncomment to disable generation of recovery mode menu entries
-#GRUB_DISABLE_RECOVERY="true"
-
-# Uncomment to get a beep at grub start
-#GRUB_INIT_TUNE="480 440 1"
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1649042 b/results/classifier/deepseek-2-tmp/output/graphic/1649042
deleted file mode 100644
index f0870abb..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1649042
+++ /dev/null
@@ -1,36 +0,0 @@
-
-Ubuntu 16.04.1 LightDM Resolution Not Correct
-
-My Specs:
-
-Slackware 14.2 x86_64 > Host
-Nvidia GPU GTX660M
-nvidia-driver-352.63
-QEMU 2.7.0
-
-Ubuntu 16.04.1 x86_64 > Guest
-Unity
-Xorg nouveau - 1:1.0.12-1build2
-
-These are the startup options for Ubuntu:
-
-qemu-system-x86_64 -drive format=raw,file=ubuntu.img \
--cpu host \
---enable-kvm \
--smp 2 \
--m 4096 \
--vga vmware \
--soundhw ac97 \
--usbdevice tablet \
--rtc base=localtime \
--usbdevice host:0781:5575
-
-Unity desktop resolution set for 1440x900.
-
-I noticed when I come to the login screen to enter my password the LightDM resolution fills my entire desktop.
-
-I searched online and found this solution;
-
-cp ~/.config/monitor.xml /var/lib/lightdm/.config
-
-For now I'm assuming this step should not be needed and the resolution should be correctly detected and set?
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1656710 b/results/classifier/deepseek-2-tmp/output/graphic/1656710
deleted file mode 100644
index d79f3539..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1656710
+++ /dev/null
@@ -1,12 +0,0 @@
-
-Please support Ctrl-Alt-= to zoom in
-
-With the GTK3 interface, qemu-system supports pressing Ctrl-Alt-plus
-to zoom in and Ctrl-Alt-minus to zoom out.  However, unlike many
-programs that support similar zoom hotkeys, qemu-system actually
-requires using '+', making the hotkey Ctrl-Alt-Shift-= .  Most programs
-with similar zoom hotkeys allow Ctrl-Alt-= as a synonym.
-
-Please consider accepting Ctrl-Alt-= as an additional zoom-in hotkey.
-
-(Observed in QEMU 2.8)
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1656711 b/results/classifier/deepseek-2-tmp/output/graphic/1656711
deleted file mode 100644
index e943ce9f..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1656711
+++ /dev/null
@@ -1,16 +0,0 @@
-
-GTK3 interface doesn't zoom-to-fit by default
-
-The SDL interface automatically scales the video output to
-match the window size.  The GTK3 interface has an off-by-default option
-"Zoom To Fit" for that.  As far as I can tell, no command-line option
-exists to turn that option on.  That makes it harder to quickly zoom a
-freshly launched VM; instead of just hitting a maximize-window hotkey, I
-also have to navigate through the menu to select "Zoom To Fit".
-
-Given that VMs typically start out running in a much lower-resolution
-video mode than the host (and VMs not running a full graphical
-environment often stay that way), this seriously impacts the usability
-of qemu-system.
-
-(Observed in QEMU 2.8)
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1658634 b/results/classifier/deepseek-2-tmp/output/graphic/1658634
deleted file mode 100644
index 64ec6db8..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1658634
+++ /dev/null
@@ -1,8 +0,0 @@
-
-Can't get correct display with latest QEMU and OVMF BIOS
-
-I tried to install a Ubuntu 16.04.1 Desktop 64bits with latest QEMU and OVMF UEFI BIOS, however I can't get correct display output with default vga configuration (-vga std). However, qemu works with a couple of different configurations:
-1. "-vga cirrus" + "-bios OVMF.fd": works
-2. "-vga std" + non-UEFI bios: works
-
-The same error with QEMU 2.8.0 release. Everything works well on 2.7.0/1.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/167 b/results/classifier/deepseek-2-tmp/output/graphic/167
deleted file mode 100644
index c68f590b..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/167
+++ /dev/null
@@ -1,2 +0,0 @@
-
-qemu 4.0 doesnt support glsl 3.0 but yes older versions, that have no sense IMO
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1670509 b/results/classifier/deepseek-2-tmp/output/graphic/1670509
deleted file mode 100644
index d9e809fb..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1670509
+++ /dev/null
@@ -1,8 +0,0 @@
-
-sgabios outputs incorrect video modes
-
-When run with a bootstrap loader that uses int 0x10 with 0x1301 in %ax, incorrect video modes are output to the serial port.  I believe the VGA image will be correct.  This might also affect the returned values for some interrupts.
-
-This is caused because the set_cursor_position routine fails to save and restore %bx.
-
-I'm working on a fix for this.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1674925 b/results/classifier/deepseek-2-tmp/output/graphic/1674925
deleted file mode 100644
index 537c6d09..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1674925
+++ /dev/null
@@ -1,22 +0,0 @@
-
-Qemu PPC64 kvm no display if  --device virtio-gpu-pci is selected
-
-Hi,
-i did many tests on qemu 2.8 on my BE machines and i found an issue that i think was need to be reported
-
-Test Machines BE 970MP 
-
-if i setup qemu with
-
-qemu-system-ppc64 -M 1024 --display sdl(or gtk),gl=on --device virtio-gpu-pci,virgl --enable-kvm and so and so
-
-result is doubled window one is vga other is virtio-gpu-pci without any start of the VM . pratically i dont have any output of openbios and on the virtual serial output
-
-the same issue i found is if i select:
-qemu-system-ppc64 -M 1024 --display gtk(or sdl) --device virtio-gpu-pci --enable-kvm and so and so
-
-
-i had been try to change all the -M types of all kind of pseries without any positive result.
-
-Ciao 
-Luigi
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1679126 b/results/classifier/deepseek-2-tmp/output/graphic/1679126
deleted file mode 100644
index 6bacb2ed..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1679126
+++ /dev/null
@@ -1,39 +0,0 @@
-
-null pointer access on migration resume of systemrescuecd boot menu with qxl-vga
-
-With qemu-2.8.0 up to 2.9.0-rc2 and git master (6954cdc), when resuming from a migration state file created from a VM suspended while showing the System Rescue CD 4.9.2 boot menu and using the QXL VGA device, I get a null point access in pixman_image_get_data called from qemu_spice_create_update (spice-display.c:215).  When I added assert(ssd->mirror != NULL) above that line, assert failed.  I don't get the crash when using standard VGA or cirrus-vga.  I am using gcc-4.9.3 on Gentoo x86_64 with Intel i7-4700HQ CPU and kernel: 4.9.15-gentoo.
-
-Here is the valgrind trace from the git version:
-==2634== Thread 1:
-==2634== Invalid read of size 4
-==3516==    at 0x65F3050: pixman_image_get_data (in /usr/lib64/libpixman-1.so.0.34.0)
-==3516==    by 0x6F0CEB: qemu_spice_create_update (spice-display.c:215)
-==3516==    by 0x6F1CC7: qemu_spice_display_refresh (spice-display.c:502)
-==3516==    by 0x58CF77: display_refresh (qxl.c:1948)
-==3516==    by 0x6E8084: do_safe_dpy_refresh (console.c:1591)
-==3516==    by 0x6E80D5: dpy_refresh (console.c:1604)
-==3516==    by 0x6E4508: gui_update (console.c:201)
-==3516==    by 0x81898E: timerlist_run_timers (qemu-timer.c:536)
-==3516==    by 0x8189D6: qemu_clock_run_timers (qemu-timer.c:547)
-==3516==    by 0x818D98: qemu_clock_run_all_timers (qemu-timer.c:662)
-==3516==    by 0x81952A: main_loop_wait (main-loop.c:514)
-==3516==    by 0x4ADD29: main_loop (vl.c:1898)
-
-Minimal steps to reproduce:
-
-Compile (debug compile flags are just so valgrind works, the crash occurs with non-debug compile flags as well):
-CFLAGS="-g -O0" CXXFLAGS="-g -O0" ./configure --target-list=i386-softmmu,x86_64-softmmu
-./configure
-make
-
-Start VM and leave it on the System Rescue CD graphical boot menu:
-x86_64-softmmu/qemu-system-x86_64 -nodefaults -machine pc -drive file=systemrescuecd-x86-4.9.2.iso,if=none,id=cdrom-cd,readonly=on -device ide-cd,bus=ide.0,drive=cdrom-cd,bootindex=1 -device qxl-vga -monitor unix:monitor.sock,server,nowait -display gtk
-
-Suspend VM and save state:
-socat - unix:monitor.sock
-  stop
-  migrate "exec:cat > vm.state"
-  quit
-
-Attempt to resume VM (but this crashes):
-x86_64-softmmu/qemu-system-x86_64 -nodefaults -machine pc -drive file=systemrescuecd-x86-4.9.2.iso,if=none,id=cdrom-cd,readonly=on -device ide-cd,bus=ide.0,drive=cdrom-cd,bootindex=1 -device qxl-vga -monitor unix:monitor.sock,server,nowait -display gtk -incoming exec:"cat vm.state"
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1703795 b/results/classifier/deepseek-2-tmp/output/graphic/1703795
deleted file mode 100644
index 3b385128..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1703795
+++ /dev/null
@@ -1,6 +0,0 @@
-
-Unable to release mouse in SDL2 mode
-
-Starting with commit 8f4ea9cd0b770dbe496d9d24f0ef8813fdbfe0d0 "sdl: prefer sdl2 over sdl1", I can no longer release mouse pointer grab unless I use --with-sdlabi=1.2 configure option.
-
-This easily reproduces in e.g. guest Kubuntu, when I let it start Xorg and then click into the QEMU window. After this the mouse is trapped and no matter how I combine Ctrl+Alt and motion of the cursor, the pointer never goes out from the window. When at the border, QEMU window switches from "Press Ctrl+Alt to exit grab" to "QEMU", i.e. it thinks that it has released the grab. But it hasn't really, so I have to go to VT1 and do "pkill qemu" from there to get my pointer back.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1708215 b/results/classifier/deepseek-2-tmp/output/graphic/1708215
deleted file mode 100644
index 3e0d0460..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1708215
+++ /dev/null
@@ -1,26 +0,0 @@
-
-Windows 10 clipboard bug
-
-Hello,
-
-I am using qemu on arch:
-    pacman -Q libvirt qemu linux virt-manager
-libvirt 3.5.0-1
-qemu 2.9.0-2
-linux 4.12.3-1
-virt-manager 1.4.1-2
-
-I have a windows 10 Guest, with all updates and the following packages installed in the guest:
-- QEMU guest agent 7.3.2
-- SPICE Guest Tools 0.132
-
-When I start the VM, I can copy/paste from the host to the guest. However, after I use COPY inside the VM, copy/paste is not working any more from host to guest. However, I can still copy/paste from guest to host.
-
-To summarize:
-- copy/paste from guest to host works always
-- copy/paste from host to guest works only if copy was not previously used in guest.
-
-If this bug needs to be reported using another portal or if I can provide any further information, please contact me.
-
-Best Regards,
-gxgung
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1718719 b/results/classifier/deepseek-2-tmp/output/graphic/1718719
deleted file mode 100644
index 6bee704a..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1718719
+++ /dev/null
@@ -1,12 +0,0 @@
-
-qemu can't capture keys properly under wayland
-
-This appears to be different than the previous similar bugs; patches do look to be applied to use libinput in the wayland case. Still:
-
-unknown keycodes `(unnamed)', please report to <email address hidden>
-
-I am using qemu-system-x86                       1:2.10+dfsg-0ubuntu1
-
-Many key inputs work correctly, but at boot the system will not properly catch the arrow keys, the above error shows up immediately after hitting Esc (for instance) to get to the boot menu. Booting from CD onto a daily Ubuntu desktop image, I can't navigate the splash menu.
-
-The same works correctly through virt-manager (which uses spice AFAICT, but wayland tends to crash when running virt-manager), and things work if I switch my session to Xorg rather than wayland.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1723731 b/results/classifier/deepseek-2-tmp/output/graphic/1723731
deleted file mode 100644
index 35db7797..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1723731
+++ /dev/null
@@ -1,22 +0,0 @@
-
-Qemu turns to black screen while starting to copy installation files of Windows 7
-
-Distribution: Arch Linux, Kernel: linux-4.13.5, Qemu: 2.10.1, OVMF: git (built 06.10.17).
-Steps to reproduce: create Qemu VM with such config:
-
-QEMU_VM_NAME=$(basename $(dirname "$0")) #Qemu virtual machine name (taken from working directory)
-QEMU_WORKING_DIR="$(dirname "$0")" #Qemu current working directory
-DIF=12 #set 2-digit number here
-QEMU_MONITOR_PORT=370${DIF} #Qemu monitor port
-QEMU_SERIAL_PORT=371${DIF} #Qemu serial port
-QEMU_PARALLEL_PORT=372${DIF} #Qemu parallel port
-
-
-qemu-system-x86_64 -daemonize -display gtk -boot menu=on -monitor telnet:127.0.0.1:${QEMU_MONITOR_PORT},server,nowait -serial telnet:127.0.0.1:${QEMU_SERIAL_PORT},server,nowait -uuid fafafafa-1234-bcbc-5678-11112222ff${DIF} -name ${QEMU_VM_NAME},process=QEMU-${QEMU_VM_NAME} -parallel none -net none -nodefconfig -nodefaults -no-user-config -rtc base=localtime,clock=vm,driftfix=slew -realtime mlock=off -machine type=q35,accel=kvm,usb=off,dump-guest-core=off -smp 2,sockets=1,cores=2,threads=1 -object iothread,id=iothread1 -object iothread,id=iothread2 -cpu Penryn,kvm=off,check,vendor=GenuineIntel,+vmx -m 2G -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,addr=0x1b.0x0 -global qxl-vga.revision=4 -device ich9-intel-hda,addr=0x11.0x0,id=sound0 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device ich9-usb-ehci1,id=ehci1,addr=0x12.0x7 -device ich9-usb-uhci1,id=uhci1,masterbus=ehci1.0,firstport=0,multifunction=on,addr=0x12.0x0 -device ich9-usb-uhci2,id=uhci2,masterbus=ehci1.0,firstport=2,addr=0x12.0x1 -device ich9-usb-uhci3,id=uhci3,masterbus=ehci1.0,firstport=4,addr=0x12.0x2 -device ide-hd,bus=ide.0,drive=drive-sata0-0-0,id=sata0-0-0 -drive file="${QEMU_WORKING_DIR}"/${QEMU_VM_NAME}.qcow2,if=none,media=disk,id=drive-sata0-0-0,format=qcow2 -device ide-cd,bus=ide.1,drive=drive-sata0-0-1,id=sata0-0-1 -drive if=none,media=cdrom,readonly=on,id=drive-sata0-0-1 -device usb-tablet,id=tbl0,bus=ehci1.0,port=2,usb_version=2,serial=1123,display=tbl0
--device usb-kbd,id=kbd0,bus=ehci1.0,port=1,usb_version=1,serial=1122,display=kbd0
-
-After that connect to Qemu console, insert Windows 7 installation media and start installation. You can successfully choose language, keyboard layout and partition your harddrive but after 2-3 seconds after beginning of copying installation files the graphical console screen turns to black and 1 CPU core on the host raises to 100% permanently and nothing happens. But if you installed Windows 7 before - there is no problems with VM. Tested on GTK, SDL types of screen.
-
-Qemu was installed from official repo and also I tried with built by myself version. Other OSes: Windows 8, 8.1, 10, Arch Linux, Debian, FreeBSD installed successfully.
-
-When you try to install Windows 7 in BIOS mode - you can pass all the installations steps, but after first reboot after installing guest agent, qxl and virtio-net drivers - OS freezes on Windows logo.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1730 b/results/classifier/deepseek-2-tmp/output/graphic/1730
deleted file mode 100644
index 4258381f..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1730
+++ /dev/null
@@ -1,17 +0,0 @@
-
-Virtual console in GTK input uses wrong color for dark gray
-Description of problem:
-The virtual console in the GTK window uses black to draw dark gray text. This becomes unintelligible if drawing on black background.
-Steps to reproduce:
-1. Boot any distro to shell prompt with `-serial vc`.
-2. Switch to serial console in QEMU GTK window (Ctrl+Alt+3).
-4. Run `echo -e "\e[1;30mDark Greay\e[m"`.
-5. Output is black on black.
-
-or
-
-1. `qemu-system-x86_64 -bios /usr/share/edk2/x64/OVMF.fd`
-2. Enter EFI internal shell
-3. `cls 0 8`
-4. Run `help cls` and observe correct colors in VGA window.
-5. Switch to serial console and observe black on black colors.
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1730099 b/results/classifier/deepseek-2-tmp/output/graphic/1730099
deleted file mode 100644
index de1b1438..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1730099
+++ /dev/null
@@ -1,10 +0,0 @@
-
-Sometimes, when not touching the SDL window, the guest freezes
-
-I often just run some development guest machine, and leave its SDL window on a workspace I don’t touch, and only interact with it via TCP.
-
-And sometimes, the guest just freezes.
-
-After it gets the focus back, it comes back to life (starts responding via network).
-
-QEMU release version: 2.8.1.1
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1730101 b/results/classifier/deepseek-2-tmp/output/graphic/1730101
deleted file mode 100644
index c87aa9a5..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1730101
+++ /dev/null
@@ -1,6 +0,0 @@
-
-The guest is only starting after its SDL window gets focus
-
-I’m using i3wm and have workspace assigning rules that make QEMU’s SDL window be assigned to a workspace I don’t really switch to.
-
-When I run start a guest machine, its SDL window is moved to that workspace (I never see it); but the machine freezes after displaying that black window. It only starts booting after I switch to the workspace and view the window.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1734474 b/results/classifier/deepseek-2-tmp/output/graphic/1734474
deleted file mode 100644
index 35f304b5..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1734474
+++ /dev/null
@@ -1,5 +0,0 @@
-
-Maemo does not boot on emulated N800
-
-I start QEMU with qemu-system-arm-m 130 -M n800 -kernel zImage.1 -mtdblock maemo.img -append "root=/dev/mtdblock3 rootfstype=jffs2"
-On QEMU 1.2.0 see "NOKIA" logo and then desktop appears, but on 1.5.0 and newer (including latest versions) I see only white screen and no signs of life. Was this caused by regression or any syntax change?
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1736042 b/results/classifier/deepseek-2-tmp/output/graphic/1736042
deleted file mode 100644
index f318f098..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1736042
+++ /dev/null
@@ -1,20 +0,0 @@
-
-qemu-system-x86_64 does not boot image reliably
-
-Booting image as root user with following command works randomly.
-
-./qemu-system-x86_64 -enable-kvm -curses -smp cpus=4 -m 8192 /root/ructfe2917_g.qcow2
-
-Most of the time it ends up on "800x600 Graphic mode"(been stuck there even for 4 hours before killed), but 1 out of ~20 it boots image correctly(and instantly).
-
-This is visible in v2.5.0 build from sources, v2.5.0 from Ubuntu Xenial and v2.1.2 from Debian Jessie.
-
-The image in question was converted from vmdk using:
-
-qemu-img convert -O qcow2 file.vmdk file.qcow2
-
-The image contains Ubuntu with grub.
-
-I can provide debug logs, but will need guidance how to enable them(and what logs are necessary).
-
-As a side note, it seems that booting is more certain after connecting(or mounting) partition using qemu-nbd/mount.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1746394 b/results/classifier/deepseek-2-tmp/output/graphic/1746394
deleted file mode 100644
index 8e5236e9..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1746394
+++ /dev/null
@@ -1,4 +0,0 @@
-
-No provider of glEGLImageTargetTexture2DOES found with NVIDIA proprietary driver
-
-https://github.com/anholt/libepoxy/issues/148
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/175 b/results/classifier/deepseek-2-tmp/output/graphic/175
deleted file mode 100644
index f254b7ce..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/175
+++ /dev/null
@@ -1,2 +0,0 @@
-
-qmp monitor deadlock (with spice events for ex)
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1750899 b/results/classifier/deepseek-2-tmp/output/graphic/1750899
deleted file mode 100644
index 1ca30c3f..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1750899
+++ /dev/null
@@ -1,25 +0,0 @@
-
-Mouse cursor sometimes can't pass the invisible border on the right side of the screen
-
-I'm using qemu 2.11 on Gentoo Linux, with configured GPU passthrough (Radeon RX580) to the guest Windows 10.
-This configuration is alive for last 4 years, this time I changed a lot qemu, linux kernel and windows versions, changed GPU and always all was working as expected. I always used standard PS/2 mouse emulation and that was enough for me.
-
-Now, I bought two new monitors, instead of old one, and setup them as one logical monitor, using technology called Eyefinity - it's a part of standard Radeon software. Now Windows thinks, that I have one monitor with resolution 2160x1920 (I bought Dell monitors with a thin borders and use them in portrait mode).
-
-Windows uses it without any problems, but mouse become crazy - sometimes (~3 times from each 5) I can't move cursor to the right border of the screen, it looks like the invisible vertical border. I spent really huge amount of time to understand, which component is the root of problem and found, that it's really a mouse. I tried all possible variants (standard, tablet, virtio-mouse-pci, virtio-tablet-pci), and found, that in both mouse variants bug is reproducing, and in both tablet variants - cursor stuck near all real borders and corners, so it's not a variant too.
-The only working variant becomes passing real USB port to my VM and insert second mouse to this port. So, now it's working, but I have two mice on my working place, which doesn't seems very useful.
-
-Here is my command line:
-
-QEMU_AUDIO_DRV=pa QEMU_PA_SAMPLES=4096 qemu-system-x86_64 -enable-kvm -M q35 -m 12168 -cpu host,kvm=off -smp 4,sockets=1,cores=4 \
--bios /usr/share/qemu/bios.bin -rtc base=localtime -vga none -device secondary-vga \
--drive id=virtiocd,if=none,format=raw,file=/home/akushsky/virtio-win-0.1.141.iso \
--device driver=ide-cd,bus=ide.1,drive=virtiocd \
--device ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1 \
--device vfio-pci,host=05:00.0,bus=root.1,addr=00.0,multifunction=on,romfile=/opt/kvm/images/Sapphire.RX580.8192.170320_1.bin,x-vga=on \
--device virtio-scsi-pci,id=scsi \
--drive file=/dev/sdb,id=disk,format=raw,if=none,discard=on,cache=none,aio=native,detect-zeroes=unmap -device scsi-hd,drive=disk,id=scsi0 \
--device ich9-intel-hda,bus=pcie.0,addr=1b.0,id=sound0 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 \
--usb -usbdevice host:046d:c52b
-
-All in all, I checked on Windows 7 and Windows 10, and on qemu 2.10 and 2.11 - bug is always reproducible.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1752646 b/results/classifier/deepseek-2-tmp/output/graphic/1752646
deleted file mode 100644
index 1f6e6a60..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1752646
+++ /dev/null
@@ -1,23 +0,0 @@
-
-Freezing VNC screen on some the UEFI framebuffer applications
-
-Hi folks!
-
-I use TianCore (UEFI) formware on the qemu (master version last commit a6e0344).
-When kernel/linux is start, it using UEFI Framebuffer. Then I run UEFI application (which writes directly to the framebuffer) my VNS screen is freezing. Then I restart vnclient I see only one frame.
-
-When I run application, I getting in the file hw/display/vga.c on function 'vga_ioport_write' some commands, it change "s->ar_index" from 0x20 -> 0x10 
-
-In the function vga_update_display:
-1751         if (!(s->ar_index & 0x20)) {
-1752             graphic_mode = GMODE_BLANK;
-1753         } else {
-
-And I got GMODE_BLANK mode. If I patch it:
-1751         if (0) {
-
-my VNC not freezing.
-
-From "Hardware Level VGA and SVGA Video Programming Information Page" I saw, what ar_index is 0x3C0 (Attribute Controller Data Write Register), 0x20(5-bit) is PAS -- Palette Address Source
-
-If there is a output via the UEFI framebuffer, does the difference have a PAS or not? Why do we need to pause the output if the PAS is exposed? Especially when the application outputs via framebuffer.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1755912 b/results/classifier/deepseek-2-tmp/output/graphic/1755912
deleted file mode 100644
index a40c0992..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1755912
+++ /dev/null
@@ -1,69 +0,0 @@
-
-qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
-
-When using qemu-system-x86_64 with the option -vga qxl, it crashes. The easiest way to crash it is by trying to change the guest's resolution. However, the system may randomly crash too, not happening only when changing resolution. Here is the terminal output of one of these random crashes:
-
---------
-
-$ qemu-system-x86_64 -hda /dev/sdb -m 2048 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
-WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
-         Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
-         Specify the 'raw' format explicitly to remove the restrictions.
-
-(process:21313): Spice-WARNING **: 16:01:45.759: display-channel.c:2431:display_channel_validate_surface: canvas address is 0x7f8eb948ab18 for 0 (and is NULL)
-
-
-(process:21313): Spice-WARNING **: 16:01:45.759: display-channel.c:2432:display_channel_validate_surface: failed on 0
-
-(process:21313): Spice-CRITICAL **: 16:01:45.759: display-channel.c:2035:display_channel_update: condition `display_channel_validate_surface(display, surface_id)' failed
-Abortado (imagem do núcleo gravada)
-
---------
-
-I was running QEMU as a normal user which is on the groups kvm and disk. Initially I supposed the problem was because I was running QEMU as root, but as a normal user this happens too.
-
-I have tested with guests with different Ubuntu version: 18.04, 17.10 and 16.04. It is happening with them all.
-
-ProblemType: Crash
-DistroRelease: Ubuntu 18.04
-Package: qemu-system-x86 1:2.11+dfsg-1ubuntu4
-ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
-Uname: Linux 4.15.0-10-generic x86_64
-ApportVersion: 2.20.8-0ubuntu10
-Architecture: amd64
-CurrentDesktop: XFCE
-Date: Wed Mar 14 17:13:52 2018
-ExecutablePath: /usr/bin/qemu-system-x86_64
-InstallationDate: Installed on 2017-06-13 (273 days ago)
-InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
-KvmCmdLine: COMMAND         STAT  EUID  RUID   PID  PPID %CPU COMMAND
-MachineType: LENOVO 80UG
-ProcCmdline: qemu-system-x86_64 -hda /dev/sdb -smp cpus=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
-ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
-Signal: 6
-SourcePackage: qemu
-StacktraceTop:
- () at /usr/lib/x86_64-linux-gnu/libspice-server.so.1
- () at /usr/lib/x86_64-linux-gnu/libspice-server.so.1
- () at /usr/lib/x86_64-linux-gnu/libspice-server.so.1
- () at /usr/lib/x86_64-linux-gnu/libspice-server.so.1
- () at /usr/lib/x86_64-linux-gnu/libspice-server.so.1
-Title: qemu-system-x86_64 crashed with SIGABRT
-UpgradeStatus: Upgraded to bionic on 2017-10-20 (145 days ago)
-UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev plugdev sambashare sudo
-dmi.bios.date: 07/10/2017
-dmi.bios.vendor: LENOVO
-dmi.bios.version: 0XCN43WW
-dmi.board.asset.tag: NO Asset Tag
-dmi.board.name: Toronto 4A2
-dmi.board.vendor: LENOVO
-dmi.board.version: SDK0J40679 WIN
-dmi.chassis.asset.tag: NO Asset Tag
-dmi.chassis.type: 10
-dmi.chassis.vendor: LENOVO
-dmi.chassis.version: Lenovo ideapad 310-14ISK
-dmi.modalias: dmi:bvnLENOVO:bvr0XCN43WW:bd07/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
-dmi.product.family: IDEAPAD
-dmi.product.name: 80UG
-dmi.product.version: Lenovo ideapad 310-14ISK
-dmi.sys.vendor: LENOVO
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1762558 b/results/classifier/deepseek-2-tmp/output/graphic/1762558
deleted file mode 100644
index 58fe33cc..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1762558
+++ /dev/null
@@ -1,29 +0,0 @@
-
-Many crashes with "memslot_get_virt: slot_id 170 too big"-type errors in 2.12.0 rc2
-
-Since qemu 2.12.0 rc2 - qemu-2.12.0-0.6.rc2.fc29 - landed in Fedora Rawhide, just about all of our openQA-automated tests of Rawhide guests which run with qxl / SPICE graphics in the guest have died partway in, always shortly after the test switches from the installer (an X environment) to a console on a tty. qemu is, I think, hanging. There are always some errors like this right around the time of the hang:
-
-[2018-04-09T20:13:42.0736 UTC] [debug] QEMU: id 0, group 0, virt start 0, virt end ffffffffffffffff, generation 0, delta 0
-[2018-04-09T20:13:42.0736 UTC] [debug] QEMU: id 1, group 1, virt start 7f42dbc00000, virt end 7f42dfbfe000, generation 0, delta 7f42dbc00000
-[2018-04-09T20:13:42.0736 UTC] [debug] QEMU: id 2, group 1, virt start 7f42d7a00000, virt end 7f42dba00000, generation 0, delta 7f42d7a00000
-[2018-04-09T20:13:42.0736 UTC] [debug] QEMU: 
-[2018-04-09T20:13:42.0736 UTC] [debug] QEMU: (process:45812): Spice-CRITICAL **: memslot.c:111:memslot_get_virt: slot_id 218 too big, addr=da8e21fbda8e21fb
-
-or occasionally like this:
-
-[2018-04-09T20:13:58.0717 UTC] [debug] QEMU: id 0, group 0, virt start 0, virt end ffffffffffffffff, generation 0, delta 0
-[2018-04-09T20:13:58.0720 UTC] [debug] QEMU: id 1, group 1, virt start 7ff093c00000, virt end 7ff097bfe000, generation 0, delta 7ff093c00000
-[2018-04-09T20:13:58.0720 UTC] [debug] QEMU: id 2, group 1, virt start 7ff08fa00000, virt end 7ff093a00000, generation 0, delta 7ff08fa00000
-[2018-04-09T20:13:58.0720 UTC] [debug] QEMU: 
-[2018-04-09T20:13:58.0720 UTC] [debug] QEMU: (process:25622): Spice-WARNING **: memslot.c:68:memslot_validate_virt: virtual address out of range
-[2018-04-09T20:13:58.0720 UTC] [debug] QEMU:     virt=0x0+0x18 slot_id=0 group_id=1
-[2018-04-09T20:13:58.0721 UTC] [debug] QEMU:     slot=0x0-0x0 delta=0x0
-[2018-04-09T20:13:58.0721 UTC] [debug] QEMU: 
-[2018-04-09T20:13:58.0721 UTC] [debug] QEMU: (process:25622): Spice-WARNING **: display-channel.c:2426:display_channel_validate_surface: invalid surface_id 1048576
-[2018-04-09T20:14:14.0728 UTC] [debug] QEMU: id 0, group 0, virt start 0, virt end ffffffffffffffff, generation 0, delta 0
-[2018-04-09T20:14:14.0728 UTC] [debug] QEMU: id 1, group 1, virt start 7ff093c00000, virt end 7ff097bfe000, generation 0, delta 7ff093c00000
-[2018-04-09T20:14:14.0728 UTC] [debug] QEMU: id 2, group 1, virt start 7ff08fa00000, virt end 7ff093a00000, generation 0, delta 7ff08fa00000
-[2018-04-09T20:14:14.0728 UTC] [debug] QEMU: 
-[2018-04-09T20:14:14.0728 UTC] [debug] QEMU: (process:25622): Spice-CRITICAL **: memslot.c:122:memslot_get_virt: address generation is not valid, group_id 1, slot_id 0, gen 110, slot_gen 0
-
-The same tests running on Fedora 28 guests on the same hosts are not hanging, and the same tests were not hanging right before the qemu package got updated, so this seems very strongly tied to the new qemu.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1766841 b/results/classifier/deepseek-2-tmp/output/graphic/1766841
deleted file mode 100644
index 59cae4f9..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1766841
+++ /dev/null
@@ -1,21 +0,0 @@
-
-QEMU 2.12 Running Problem in Windows 7 Installation
-
-QEMU Version: 2.12 (Binary installer qemu-w64-setup-20180424.exe  from Stefan Weil's website so I am not sure I should report it to Weil by email or by this bug report system.)
-Host System: Windows 7 64bit
-Guest System: 9front 6350 (Codename“CONTENTS, MAINTAINED, STABLE”, Release 2018/02/02)
-
-QEMU Command:
-qemu-system-x86_64 -usb -device usb-mouse -hda plan9.qcow2.img -cdrom 9front-6350.iso -boot d
-
-QEMU warning: 
-(qemu-system-x86_64.exe:8844): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file 'D:\qemu\lib\gdk-pixbuf-2.0\2.10.0\loaders.cache': No such file or directory
-
-This likely means that your installation is broken.
-Try running the command
-  gdk-pixbuf-query-loaders > D:\qemu\lib\gdk-pixbuf-2.0\2.10.0\loaders.cache
-to make things work again for the time being.
-
-(qemu-system-x86_64.exe:8844): Gtk-WARNING **: Could not find the icon 'window-minimize-symbolic-ltr'. The 'hicolor' theme was not found either, perhaps you need to install it.
-You can get a copy from:
-        http://icon-theme.freedesktop.org/releases
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1767176 b/results/classifier/deepseek-2-tmp/output/graphic/1767176
deleted file mode 100644
index 314ca555..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1767176
+++ /dev/null
@@ -1,47 +0,0 @@
-
-GTK build fails with qemu 2.12.0
-
-With the 2.12.0 release of QEMU passing `--enable-gtk` to configure causes the build to fail. I'm running macOS 10.13.5 with Xcode 9.3 FWIW.
-
-I'm building against GTK 2.24.32, which I appreciate is no longer the preferred version here, but I don't think the error is related to that aspect. I'll try and find the time later to attempt a GTK3 build to check that though.
-
-```
-ui/gtk.c:1147:16: error: use of undeclared identifier 'qemu_input_map_osx_to_qcode'; did you mean 'qemu_input_map_usb_to_qcode'?
-        return qemu_input_map_osx_to_qcode;
-               ^~~~~~~~~~~~~~~~~~~~~~~~~~~
-               qemu_input_map_usb_to_qcode
-/private/tmp/qemu-20180426-60786-1av6pq8/qemu-2.12.0/include/ui/input.h:99:22: note: 'qemu_input_map_usb_to_qcode' declared here
-extern const guint16 qemu_input_map_usb_to_qcode[];
-                     ^
-```
-
-I tried poking around locally by applying the following diff, based off of a very brief glance over the code involved, but that simply causes the build to error out in a different way at a later point, so I assume I'm doing something stupid.
-
-
-```
-diff --git a/Makefile b/Makefile
-index d71dd5b..e857c3c 100644
---- a/Makefile
-+++ b/Makefile
-@@ -313,6 +313,7 @@ KEYCODEMAP_FILES = \
- 		 ui/input-keymap-qnum-to-qcode.c \
- 		 ui/input-keymap-usb-to-qcode.c \
- 		 ui/input-keymap-win32-to-qcode.c \
-+		 ui/input-keymap-osx-to-qcode.c \
- 		 ui/input-keymap-x11-to-qcode.c \
- 		 ui/input-keymap-xorgevdev-to-qcode.c \
- 		 ui/input-keymap-xorgkbd-to-qcode.c \
-diff --git a/include/ui/input.h b/include/ui/input.h
-index 16395ab..8183840 100644
---- a/include/ui/input.h
-+++ b/include/ui/input.h
-@@ -101,6 +101,9 @@ extern const guint16 qemu_input_map_usb_to_qcode[];
- extern const guint qemu_input_map_win32_to_qcode_len;
- extern const guint16 qemu_input_map_win32_to_qcode[];
- 
-+extern const guint qemu_input_map_osx_to_qcode_len;
-+extern const guint16 qemu_input_map_osx_to_qcode[];
-+
- extern const guint qemu_input_map_x11_to_qcode_len;
- extern const guint16 qemu_input_map_x11_to_qcode[];
-```
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1775011 b/results/classifier/deepseek-2-tmp/output/graphic/1775011
deleted file mode 100644
index cea5afc0..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1775011
+++ /dev/null
@@ -1,21 +0,0 @@
-
--display gtk,gl=on crashes on Wayland
-
-steps to reproduce:
-
-1. run a Wayland compositor (I use sway, probably the same bug exists for other compositors)
-2. execute qemu -display gtk,gl=on
-
-expected results:
-
-a GTK window is created that shows SeaBIOS failing to boot
-
-actual results:
-
-segmentation fault  qemu-system-x86_64 -display gtk,gl=on
-
-additional information:
-
-qemu version 2.12.0 from Arch Linux
-
-looks like qemu is trying to take the Wayland display from GTK and initialize EGL but telling EGL it's a X11 display, which is not correct. setting GDK_BACKEND=x11 works around the issue.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1776224 b/results/classifier/deepseek-2-tmp/output/graphic/1776224
deleted file mode 100644
index 84f30fac..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1776224
+++ /dev/null
@@ -1,41 +0,0 @@
-
-QEMU's SPICE server not getting leds callback when sending capslock
-
-I'm having troubles using the QEMU's SPICE server for remote views. When
-trying to sync leds from my SPICE client to QEMU, I can see that the
-caps lock keycodes are sent but the server state never gets updated
-(which leads in funny behaviours like caps lock "blinking" in the guest
-if the clients resyncs its state often).
-
-That behaviour doesn't happen at all with the numlock led which does the
-same thing but with different keycodes.
-
-Here is an example of what's happening when the client tries to resync
-with a capslock difference:
-
-> Spice received: 58
-> ps2_put_keycode: 88
->
-> Spice received: 186
-> ps2_put_keycode: 240
-> ps2_put_keycode: 88
-> ps2_queue: 186
-
-And with numlock:
-
-> Spice received: 69
-> ps2_put_keycode: 119
->
-> Spice received: 197
-> ps2_put_keycode: 240
-> ps2_put_keycode: 119
-> ps2_queue: 197
-> ps2_set_ledstate: 0
-> Spice new ledstate: 0
-
-
-This behaviour is consistent across SPICE clients and only appears in a linux TTY (it works fine if I start an X server and on windows). It still happens on QEMU latest commit at the time (0d2fa03dae4fbe185a082f361342b1e30aed4582)
-
-Spice registers a callback for leds via qemu_add_led_event_handler but
-it's never called for capslock. Is that a normal behaviour ? Is there
-any reasons for the capslock led not to be updated ?
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1777672 b/results/classifier/deepseek-2-tmp/output/graphic/1777672
deleted file mode 100644
index 565b77af..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1777672
+++ /dev/null
@@ -1,68 +0,0 @@
-
-QEMU raspi virtual/physical frame buffer not implemented
-
-I fully recognize that the error here could be mine, but the code is pretty simple and straightforward; When emulating a Raspberry PI 3 using aarch64 and allocating a virtual framebuffer larger than the physical frambuffer (for double-buffering purposes), the QEMU window shows the full size of the *virtual* framebuffer rather than the size of the *physical* framebuffer.
-
-You can replicate this with code such as:
-
-
-#define FBWIDTH 1024
-#define FBHEIGHT 768
-
-void lfb_init()
-{
-    uart_puts("Initializing Framebuffer\n");
-    mbox[0] = 35*4;
-    mbox[1] = MBOX_REQUEST;
-
-    mbox[2] = 0x48003;  //set phy wh
-    mbox[3] = 8;
-    mbox[4] = 8;
-    mbox[5] = FBWIDTH;         //FrameBufferInfo.width
-    mbox[6] = FBHEIGHT;          //FrameBufferInfo.height
-
-    mbox[7] = 0x48004;  //set virt wh
-    mbox[8] = 8;
-    mbox[9] = 8;
-    mbox[10] = FBWIDTH;        //FrameBufferInfo.virtual_width
-    mbox[11] = FBHEIGHT * 2;         //FrameBufferInfo.virtual_height
-    
-    mbox[12] = 0x48009; //set virt offset
-    mbox[13] = 8;
-    mbox[14] = 8;
-    mbox[15] = 0;           //FrameBufferInfo.x_offset
-    mbox[16] = 0;           //FrameBufferInfo.y.offset
-    
-    mbox[17] = 0x48005; //set depth
-    mbox[18] = 4;
-    mbox[19] = 4;
-    mbox[20] = 32;          //FrameBufferInfo.depth
-
-    mbox[21] = 0x48006; //set pixel order
-    mbox[22] = 4;
-    mbox[23] = 4;
-    mbox[24] = 1;           //RGB, not BGR preferably
-
-    mbox[25] = 0x40001; //get framebuffer, gets alignment on request
-    mbox[26] = 8;
-    mbox[27] = 8;
-    mbox[28] = 4096;        //FrameBufferInfo.pointer
-    mbox[29] = 0;           //FrameBufferInfo.size
-
-    mbox[30] = 0x40008; //get pitch
-    mbox[31] = 4;
-    mbox[32] = 4;
-    mbox[33] = 0;           //FrameBufferInfo.pitch
-
-    mbox[34] = MBOX_TAG_LAST;
-
-    if(mbox_call(MBOX_CH_PROP) && mbox[20]==32 && mbox[28]!=0) {
-        mbox[28]&=0x3FFFFFFF;
-        fbwidth=mbox[5];
-        fbheight=mbox[6];
-        pitch=mbox[33];
-        lfb=(void*)((unsigned long)mbox[28]);
-    }
-}
-
-I will assume, for the sake of this posting, that the reader understands the mailbox architecture and the appropriate address definitions for them.  The key point is that allocating a virtual buffer twice the height of the physical buffer results in QEMU improperly displaying a double-height window.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1777786 b/results/classifier/deepseek-2-tmp/output/graphic/1777786
deleted file mode 100644
index 873bfd57..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1777786
+++ /dev/null
@@ -1,47 +0,0 @@
-
-virtio-gpu-3d.c: change virtio_gpu_fence_poll timer scale
-
-We use virtio-gpu to accelerate Unigine Heaven Benchmark in VM. But we get only 5 FPS when we use AMD RX460 in our host.
-We found that guest os spent a lot of time in waiting for the return of glMapBufferRange/glUnmapBuffer commad. We suspected the host GPU was waiting for fence. So we finally change the timer of fence_poll. Afer change timer from
- ms to us， Benchmark result raise up to 22 FPS.
-
-From a4003af5c4fe92d55353f42767d0c45de95bb78f Mon Sep 17 00:00:00 2001
-From: chen wei <email address hidden>
-Date: Fri, 8 Jun 2018 17:34:45 +0800
-Subject: [PATCH] virtio-gpu:improve 3d performance greatly
-
-  opengl function need fence support.when CPU execute opengl function, it need wait fence for synchronize GPU.
-so qemu must deal with fence timely as possible. but now the expire time of the timer to deal with fence is 10 ms.
-I think it is too long for opengl. So i will change it to 20 ns.
-  Before change, when i play Unigine_Heaven 3d game with virglrenderer, the fps is 3.  atfer change the fps up to 23.
-
-Signed-off-by: chen wei   <email address hidden>
-Signed-off-by: wang qiang <email address hidden>
----
- hw/display/virtio-gpu-3d.c | 4 ++--
- 1 file changed, 2 insertions(+), 2 deletions(-)
-
-diff --git a/hw/display/virtio-gpu-3d.c b/hw/display/virtio-gpu-3d.c
-index 3558f38..c0a5d21 100644
---- a/hw/display/virtio-gpu-3d.c
-+++ b/hw/display/virtio-gpu-3d.c
-@@ -582,7 +582,7 @@ static void virtio_gpu_fence_poll(void *opaque)
-     virgl_renderer_poll();
-     virtio_gpu_process_cmdq(g);
-     if (!QTAILQ_EMPTY(&g->cmdq) || !QTAILQ_EMPTY(&g->fenceq)) {
--        timer_mod(g->fence_poll, qemu_clock_get_ms(QEMU_CLOCK_VIRTUAL) + 10);
-+        timer_mod(g->fence_poll, qemu_clock_get_us(QEMU_CLOCK_VIRTUAL) + 20);
-     }
- }
- 
-@@ -629,7 +629,7 @@ int virtio_gpu_virgl_init(VirtIOGPU *g)
-         return ret;
-     }
- 
--    g->fence_poll = timer_new_ms(QEMU_CLOCK_VIRTUAL,
-+    g->fence_poll = timer_new_us(QEMU_CLOCK_VIRTUAL,
-                                  virtio_gpu_fence_poll, g);
- 
-     if (virtio_gpu_stats_enabled(g->conf)) {
--- 
-2.7.4
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1778182 b/results/classifier/deepseek-2-tmp/output/graphic/1778182
deleted file mode 100644
index e5dacd0d..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1778182
+++ /dev/null
@@ -1,23 +0,0 @@
-
-qemu-system-aarch64 shows black framebuffer window on minimal bare metal example on SDL but not on VNC
-
-QEMU v2.12.0, Ubuntu 18.04 host.
-
-Build QEMU and the bare metal image exactly as described at: https://raspberrypi.stackexchange.com/revisions/85135/4 with:
-
-Then cd into example 09_framebuffer.
-
-Now if I do:
-
-../../qemu/aarch64-softmmu/qemu-system-aarch64 -M raspi3 -kernel kernel8.img -serial stdio
-
-the SDL window shows up black.
-
-However, if I use VNC:
-
-../../qemu/aarch64-softmmu/qemu-system-aarch64 -M raspi3 -kernel kernel8.img -serial stdio -vnc :1
-vinagre :5901
-
-an image of Homer Simpson appears as expected.
-
-Therefore, I think this must be a QEMU / SDL bug instead of the repository, since we get different behaviors with `-vnc` and with SDL.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1779650 b/results/classifier/deepseek-2-tmp/output/graphic/1779650
deleted file mode 100644
index 924cd840..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1779650
+++ /dev/null
@@ -1,6 +0,0 @@
-
-The display stays black after waking up a domain via SPICE with a QXL card
-
-As the title says, in a jessie VM, waking up a VM via the spice remote view works with a VGA graphic card. With a QXL card though, the domain wakes up but the display stays black (the keyboard is working though).
-
-Qemu: Master, 281bd281222776229d5dbf84d1a5c6d8d9d2a34b
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1780812 b/results/classifier/deepseek-2-tmp/output/graphic/1780812
deleted file mode 100644
index b6e8de9a..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1780812
+++ /dev/null
@@ -1,10 +0,0 @@
-
-Full-Screen Switch Does Nothing When Using SDL
-
-When using SDL switches, e.g.
-
--sdl -full-screen -display sdl
-
-... you'd expect the display to start full-screen, as per the switch description, but it just starts in a window. Pressing the full-screen key combination (Ctrl+Alt+F) enters fullscreen mode as expected.
-
-Tested on QEmu 2.12.0 using qemu-system-x86_64.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1780815 b/results/classifier/deepseek-2-tmp/output/graphic/1780815
deleted file mode 100644
index 74ed1b89..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1780815
+++ /dev/null
@@ -1,8 +0,0 @@
-
-SDL Doesn't Rescale Image on Resolution Change
-
-Whilst in fullscreen mode, if the guest changes resolution for whatever reason, the screen doesn't update the scaling so you end up looking at only part of the screen, e.g. if the guest changes from 640x480 to 1024x768, the image will still be fullscreen, but what you're actually looking at will be the top-left most 640x480 segment of the screen stretched out.
-
-Manually going out of fullscreen mode and then back in fixes the scaling, but you have to do that every time the guest changes resolution.
-
-QEmu 2.12.0 using qemu-system-x86_64 with Arch Linux host.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1781515 b/results/classifier/deepseek-2-tmp/output/graphic/1781515
deleted file mode 100644
index 90c03ed8..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1781515
+++ /dev/null
@@ -1,14 +0,0 @@
-
-Resolution switch leads to the screen/image being corrupted
-
-I am currently using QEMU on a Arch Linux host, the guest OS is also Arch Linux.
-
-The QEMU version is currently 2.12.0-2 packaged by Arch Linux, the command line I'm using to fire an Arch VM is:
-
-$ qemu-system-x86_64 -enable-kvm -hda archlinux.qcow2 -m 4G -smp 4
-
-The problem I'm currently having is, after firing the VM and running startx I want to change the resolution to the native resolution, which is 1366x768 on my ThinkPad T450, however, after changing the resolution the image on the guest gets corrupted and it's impossible to see anything.
-
-At this point I can only turn off the VM. The only workaround I found is to start the VM with -vga virtio.
-
-The problem in this case occurs with -vga std which is the default video driver.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1784 b/results/classifier/deepseek-2-tmp/output/graphic/1784
deleted file mode 100644
index e7861632..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1784
+++ /dev/null
@@ -1,14 +0,0 @@
-
-Mac M1 Max / Debian guest / Luks password / Switching to graphical login manager (lightdm/Gdm) hangs in 75%
-Description of problem:
-In approximately 70% of cases I start QEMU with a Debian guest where the Debian guest was installed with full disk encryption, QEMU 'hangs' (does not respond') after I unlock the encrypted guest and the guest tries to start the graphical login manager (gdm or lightdm).
-
-I need to force quit QEMU, restart it multiple times until the start of the graphical login manager works.
-Steps to reproduce:
-1. Install Debian with (guided) full disk encryption and either the Gnome or the XFCE desktop environment
-2. To be able to unlock the hard disk after the installation finished, the Linux boot parameter 'console=tty1' needs to be added within grub to the Linux command line
-3. Try to restart/reboot QEMU  several times and QEMU will become unresponsive multiple times in this process.
-Additional information:
-I encounter this problem for several months now, with different versions of QEMU, macOS and Debian.
-
-There is one observation, which might help: I installed [DropBear](https://packages.debian.org/buster/dropbear-initramfs) to experiment with remote unlocking of Luks encrypted Linux boxes. It seems, that QEMU does not go into the unresponsive state, when I unlock the hard disk via SSH and not focus the QEMU window until after the graphical login manager started. (Only tried remote unlocking a few times so it is too early to confirm if this works 100% of the time.
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1784900 b/results/classifier/deepseek-2-tmp/output/graphic/1784900
deleted file mode 100644
index f0dae0ff..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1784900
+++ /dev/null
@@ -1,41 +0,0 @@
-
-QEMU (frontend) crashes upon warm reboot with virtio-gpu device and vga=775 on Linux cmdline
-
-With vga=775 on the Linux command line a first boot of the VM running Linux works fine. After a warm reboot it crashes during Linux boot. The VM was used remotely via virt-manager and VNC.
-
-Bisecting the code lead to the following patch that introduced the bug:
-
-commit 1fccd7c5a9a722a9cbf1bc91693f4618034f01ac (HEAD, refs/bisect/bad)
-Author: Gerd Hoffmann <email address hidden>
-Date:   Mon Jul 2 18:24:43 2018 +0200
-
-    virtio-gpu: disable scanout when backing resource is destroyed
-
-    Signed-off-by: Gerd Hoffmann <email address hidden>
-    Reviewed-by: Marc-André Lureau <email address hidden>
-    Message-id: <email address hidden>
-
-diff --git a/hw/display/virtio-gpu.c b/hw/display/virtio-gpu.c
-index 336dc59007..08cd567218 100644
---- a/hw/display/virtio-gpu.c
-+++ b/hw/display/virtio-gpu.c
-@@ -430,6 +430,16 @@ static void virtio_gpu_disable_scanout(VirtIOGPU *g, int scanout_id)
- static void virtio_gpu_resource_destroy(VirtIOGPU *g,
-                                         struct virtio_gpu_simple_resource *res)
- {
-+    int i;
-+
-+    if (res->scanout_bitmask) {
-+        for (i = 0; i < g->conf.max_outputs; i++) {
-+            if (res->scanout_bitmask & (1 << i)) {
-+                virtio_gpu_disable_scanout(g, i);
-+            }
-+        }
-+    }
-+
-     pixman_image_unref(res->image);
-     virtio_gpu_cleanup_mapping(res);
-     QTAILQ_REMOVE(&g->reslist, res, next);
-
-
-Reported backtraces can be found here:  https://paste.fedoraproject.org/paste/OUDEfCk1IY7xiy0I0PDlkw
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1787 b/results/classifier/deepseek-2-tmp/output/graphic/1787
deleted file mode 100644
index 49138d9b..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1787
+++ /dev/null
@@ -1,14 +0,0 @@
-
-Qemu asan test make vm crash when using qxl and spice
-Description of problem:
-When I tested QEMU with asan, the vm crash. The error message is as follows：
-![1](/uploads/a44f3790fe6c375aa8eac3a178da963d/1.jpg)
-Steps to reproduce:
-1.Start the vm with qxl and spice.
-2.Attach the vm with vnc and spice.
-3.Placed for more than three days.
-4.Operation on spice client and possible reproduce this bug.
-Additional information:
-https://github.com/qemu/qemu/blob/44f28df24767cf9dca1ddc9b23157737c4cbb645/ui/cursor.c#L112
-I think the reason for the problem is that the cursor pointer was not set to NULL when qemu call cursor_put. But I don't know what situation will trigger this error.
-This error is difficult to reproduce by natural.
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1787070 b/results/classifier/deepseek-2-tmp/output/graphic/1787070
deleted file mode 100644
index d5a4a06c..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1787070
+++ /dev/null
@@ -1,35 +0,0 @@
-
-Guests using the qxl-vga are freezing
-
-I have noticed that guests using qxl-vga are freezing. They may freeze after a few minutes or after many hours. The freeze consists of the entire system hanging, except the cursor, but the cursor animation stops too. Changing to tty is not possible after this. There are three things noticed in common on the guests when they freeze:
-
--The guest is using the QXL VGA (freezes weren't observed with other VGAs);
--A new workload is starting;
--The mouse cursor is the animated as the one of loading. For example, https://i.imgur.com/raQFteG.png
- 
-The host is Xubuntu 18.04 amd64, QEMU version is 3.0.0-dirty. The guests tested were:
-
--openSUSE Tumbleweed;
--openSUSE Leap 15;
--Xubuntu 18.04 Bionic Beaver;
--CentOS 7.
-
-With openSUSE guests, the install process couldn't even be finished, as the installer would freeze. There were 2 GB of available memory (checked in a tty before the freeze) and netconsole was enabled. Unfortunately, it was impossible to obtain any information from them. This is an image of one openSUSE guest frozen: https://i.imgur.com/ZP0eQKq.png
-
-The command line used was: 
-
-qemu-system-x86_64 -nodefaults -m 3072 -M pc,usb=true -accel kvm -cpu host -smp cores=2,threads=2 -device qemu-xhci -drive id=centusb,if=none,file=leap.qcow2 -device usb-storage,id=centusb,drive=centusb -netdev user,id=n0 -device usb-tablet,id=usbtablet -device e1000,netdev=n0 -device usb-audio,id=usbaudio -device qxl-vga,xres=1366,yres=768 -display gtk -monitor vc -serial vc  -cdrom "openSUSE-Leap-15.0-DVD-x86_64.iso" -boot d
-
-With CentOS guests, the install process fail sometimes, but sometimes it's able to install. However, on the yum update, it would freeze too. In one instance it froze while updating glibc, which made the guest unbootable. https://i.imgur.com/B3WhSDX.png
-
-The command line used was: 
-
-qemu-system-x86_64 -nodefaults -m 2048 -M pc,usb=true -accel kvm -cpu host -smp cores=2,threads=2 -device qemu-xhci -drive id=centusb,if=none,file=centos.qcow2 -device usb-storage,id=centusb,drive=centusb -netdev user,id=n0 -device usb-tablet,id=usbtablet -device e1000,netdev=n0 -device usb-audio,id=usbaudio -device virtio-vga,virgl=true -display gtk -monitor vc -serial vc -cdrom "CentOS-7-livecd-GNOME-x86_64.iso" -bios /usr/share/ovmf/OVMF.fd
-
-With Xubuntu 18.04 guests, the system worked for many hours until the freeze happened. On this case it happened when opening Audacious. Fortunately, the logging services worked for some time, which allowed me to get a relevant message which can be seen at http://termbin.com/nuof . It repeated a few times, but then the logging stopped. https://i.imgur.com/2zckqj5.png shows the guest screen in the moment it froze.
-
-The command line used was:
-
-qemu-system-x86_64 -nodefaults -m 1024 -M pc,usb=true -accel kvm -cpu host -smp cores=2,threads=2 -device qemu-xhci -drive id=centusb,if=none,file=xubmini -device usb-storage,id=centusb,drive=centusb -netdev user,id=n0 -device usb-tablet,id=usbtablet -device e1000,netdev=n0 -device usb-audio,id=usbaudio -device qxl-vga,xres=1366,yres=768 -display gtk -monitor vc -serial vc
-
-I'm sorry for not having more detailed information but, even setting netconsole, openSUSE and CentOS guests were unable to print any information.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1788701 b/results/classifier/deepseek-2-tmp/output/graphic/1788701
deleted file mode 100644
index c30f145d..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1788701
+++ /dev/null
@@ -1,8 +0,0 @@
-
-"Zoom to fit" doesn't work  with -display gtk -vga virtio
-
-qemu version: 2.12.1
-
-When using -display gtk for all -vga options (std,qxl,vmware,cirrus) the option "Zoom To Fit" is unchecked and auto-resizing of the window works well; except for -vga virtio: here "Zoom To Fit" is checked and auto-resizing doesn't work.
-
-Proposal: disable "Zoom To Fit" as default for virtio as well
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1789 b/results/classifier/deepseek-2-tmp/output/graphic/1789
deleted file mode 100644
index dfa36d67..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1789
+++ /dev/null
@@ -1,18 +0,0 @@
-
-First connection to spice hangs after 1 min
-Description of problem:
-After starting a VM the first connection to spice logs this errors:
-
-```
-2023-07-25T16:00:47.497042Z qemu-system-x86_64: warning: Spice: main:0 (0x7f1a3fca5b90): invalid net test stage, ping id 0 test id 0 stage 4
-2023-07-25T16:00:47.497170Z qemu-system-x86_64: warning: Spice: main:0 (0x7f1a3fca5b90): invalid net test stage, ping id 0 test id 0 stage 0
-```
-
-And after 60 seconds the spice viewer is closed with this error:
-```
-2023-07-25T16:01:47.384207Z qemu-system-x86_64: warning: Spice: main:0 (0x7f1a3fca5b90): rcc 0x7f1a1968cb60 has been unresponsive for more than 30000 ms, disconnecting
-```
-Steps to reproduce:
-1. Start vm with spice
-2. Connect to spice
-3. Wait for at least 60 seconds and the viewer will close
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1793297 b/results/classifier/deepseek-2-tmp/output/graphic/1793297
deleted file mode 100644
index e321a723..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1793297
+++ /dev/null
@@ -1,11 +0,0 @@
-
-windows's paint software cross-shadped cursor offset a pixel in guest windows which is generated by qemu-kvm
-
-I have already tested lots of versions of QEMU. Since qemu-2.3.0 -- qemu-3.0.0. I find weird phenomena about windows's paint software cross-shaped cursor offset a pixel since qemu-2.10.0, but it is ok before the version of qemu-2.10.0. Only spice agent and service are running in guest windows since qemu-2.10.0, windows's paint software cross-shaped cursor offset a pixel is the same as the windows's paint software cross-shaped cursor focus point is the same as the true windows machine instead of virtual windows machine.
-What does QEMU change since qemu-2.10.0? It is the changes that result in windows's paint software cross-shaped cursor is not accurate with true windows machine for comparison.  
-The following is the full command line used to launch the QEMU guest:
-# /usr/bin/qemu-system-x86_64 -m 4096 -smp 2 -M pc -name win7-6904 -hda /home/win7_kvmgt.img -bios /usr/bin/bios.bin -enable-kvm -k en-us -vga qxl -display egl-headless -spice disable-ticketing,port=6904,streaming-video=all -machine kernel_irqchip=on,usb=on -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -cpu host -device usb-tablet
-
-BTW, guest windows display card is QXL driver.
-But the following full command line used to launch the QEMU guest is OK. For comparison, I pasted it below (Just add vdagent and spicevmc in the command line to make sure spice service and agent is running in the guest windows):
-# /usr/bin/qemu-system-x86_64 -m 4096 -smp 2 -M pc -name win7-6904 -hda /home/win7_kvmgt.img -bios /usr/bin/bios.bin -enable-kvm -k en-us -vga qxl -display egl-headless -spice disable-ticketing,port=6904,streaming-video=all -machine kernel_irqchip=on,usb=on -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -cpu host -device usb-tablet -device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x5 -chardev spicevmc,name=vdagent,id=vdagent -device virtserialport,nr=1,bus=virtio-serial0.0,chardev=vdagent,name=com.redhat.spice.0
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1793859 b/results/classifier/deepseek-2-tmp/output/graphic/1793859
deleted file mode 100644
index d617c1eb..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1793859
+++ /dev/null
@@ -1,12 +0,0 @@
-
-GTK display and mouse input area scaling fails when using vfio-pci device
-
-Version qemu 3.0.0-1 running on Arch. Found on Windows 8.1 and Windows 10 VM's when using Intel gvt-g device. 
-
-While in fullscreen the GTK display is scaled larger than the x11 screen or virtual machine resolution. Without choosing zoom-to-fit portions of the VM display are not shown on x11 screen regardless of the VM resolution. When zoom-to-fit is done the mouse that's shown on screen and actual input are off sync. The mouse can wander off screen when going left and down.
-
-This message is shown when changing from gxl-vga to vfio-pci in view menu. 
-(qemu-system-x86_64:6472): Gtk-WARNING **: 09:50:06.663: drawing failure for widget 'GtkDrawingArea': NULL pointer
-(qemu-system-x86_64:6472): Gtk-WARNING **: 09:50:06.664: drawing failure for widget 'GtkNotebook': NULL pointer
-(qemu-system-x86_64:6472): Gtk-WARNING **: 09:50:06.664: drawing failure for widget 'GtkBox': NULL pointer
-(qemu-system-x86_64:6472): Gtk-WARNING **: 09:50:06.664: drawing failure for widget 'GtkWindow': NULL pointer
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1795799 b/results/classifier/deepseek-2-tmp/output/graphic/1795799
deleted file mode 100644
index af4047d0..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1795799
+++ /dev/null
@@ -1,31 +0,0 @@
-
-Cirrus video, graphical corruption, bad fonts
-
-The error
-===
-
-I started qemu by
-
-`shell
-$ ./qemu-system-i386 -serial stdio -cdrom /dev/cdrom -vga cirrus
-S1111111111S1111111111S1111111111S1111111111▒*n*n*n*n
-`
-
-with the original suse7.0 cd 1 in the cdrom drive (I think https://archive.org/details/suse-7.0_release_i386 has the image). After some console output (that uses a vga framebuffer which seems to work fine) the suse installer is started. It is displayed mostly correct, but several text passages are completely garbled.
-
-I noticed the same type of corruption when trying to run an old XF86 SVGA Server on a SuSE 6.2 System using the `-vga cirrus` option.
-
-Therefore I think that the cirrus emulation might not work as intended any more.
-
-Qemu version
-===
-
-I used  qemu-w64-setup-20180815.exe provided by https://qemu.weilnetz.de/w64/
-
-./qemu-system-i386 -version
-QEMU emulator version 3.0.0 (v3.0.0-11723-ge2ddcc5879-dirty)
-Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers
-
-Hope you can fix it. 
-
-Best regards!
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1799792 b/results/classifier/deepseek-2-tmp/output/graphic/1799792
deleted file mode 100644
index 246a3137..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1799792
+++ /dev/null
@@ -1,13 +0,0 @@
-
-Broken scaling with gtk,gl=on on a hidpi display
-
-Tested on QEMU 3.0.0 on Arch Linux.
-
-I'm using a hidpi screen, and therefore use those environment variables in order to have GTK+ apps properly scaled:
-
-GDK_SCALE=2
-GDK_DPI_SCALE=0.5
-
-However, QEMU, when launched with "-display gtk,gl=on" option, doesn't scale the window content properly, as seen on the attached screenshot.
-
-Switching to "-display gtk,gl=off" and "-display sdl,gl=on" makes it work fine.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1800156 b/results/classifier/deepseek-2-tmp/output/graphic/1800156
deleted file mode 100644
index 7fad058c..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1800156
+++ /dev/null
@@ -1,6 +0,0 @@
-
-windows 8.1 loose grab/leave window on windowed
-
-Hello, i am new to QEMU and i encounter that annoying issue (windowed) when i move the mouse a bit too much then it leave the window.
-
-Windows 8.1, Latest QEMU (Windows binaries).
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1800401 b/results/classifier/deepseek-2-tmp/output/graphic/1800401
deleted file mode 100644
index 5027c33e..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1800401
+++ /dev/null
@@ -1,30 +0,0 @@
-
-efifb on Linux guest fails to load when using VGA passthrough
-
-The EFI framebuffer fails to load when booting a Gentoo guest using ovmf + vga_passthrough.  I retested using they system rescue CD and saw the same issue, but also noticed that when a second framebuffer loads, nouveaufb in my case, the terminal appears.  I have also verified that the Gentoo min CD is not hanging at boot as I can type 'poweroff' after waiting a few minutes and the system responds by powering off.  I am unable to reproduce with seabios as I have been unable to get vga passthrough to work with that BIOS.
-
-Steps to Reproduce:
-    1. Install qemu and ovmf
-    2. Download systemrescuecd-x86-5.3.1.iso
-    3. Run qemu using one of the configurations below
-    4. Select first boot option in GRUB menu
-    5. Wait 30 seconds
-    6. Press enter # System rescue is prompting for the keymap between steps 5 and 6
-    7. Wait 2 minutes
-    8. Observe fb console
-    9. Note lack of output until very late in boot process
-   10. Check dmesg
-   11. Note efifb failed to load (invalid address)
-   12. Note nouveaufb started late in boot process 
-
-Expected Results:
-   The EFI FB to load and display output to monitor.  This is the behavior I see when booting the host system via UEFI.
-
-Actual Results:
-   The EFI FB fails to load and display output.  System fails to display any output until nouveaufb loads.  When booting using the Gentoo minCD, this makes the system largely unusable.
-
-Additional information:
-
-Tested using Gentoo's app-emulation/qemu-3.0.0 version.  Bug report: https://bugs.gentoo.org/669880
-
-I also tested qemu at git commit 179f9ac887973c818b2578bd79fa3ed2522657d4.  Configuration log for the build will be attached.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1802915 b/results/classifier/deepseek-2-tmp/output/graphic/1802915
deleted file mode 100644
index 1dc9b833..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1802915
+++ /dev/null
@@ -1,8 +0,0 @@
-
-GTK display refresh rate is throttled
-
-Guest OS running with GL enabled GTK display shows a reduced refresh rate, e.g. moving cursor around with iGVT-g DMA Buf.
-
-It seems that a default refresh interval GUI_REFRESH_INTERVAL_DEFAULT (30ms) is defined in include/ui/console.h, throttling the display refresh rate at 33Hz.
-
-To correct this throttle issue, a shorter interval should be applied to display change listener or the default value should be used.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1805697 b/results/classifier/deepseek-2-tmp/output/graphic/1805697
deleted file mode 100644
index ff6aced3..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1805697
+++ /dev/null
@@ -1,16 +0,0 @@
-
-egl-headless crashes
-
-egl-headless crashes when it is trying change the resolution. After XFCE login, for example.
-
-I tryed it on 2.12, 3.0 and 3.1.0-rc2 versions.
-
-# qemu-system-x86_64 -enable-kvm -enable-kvm -M q35 -smp 8 -vga virtio -spice port=59011,addr=0.0.0.0,disable-ticketing -hda image.qcow2 -m 4G -display egl-headless -chardev spicevmc,name=vdagent,id=vdagent
-
-main_channel_link: add main channel client
-main_channel_client_handle_pong: net test: latency 6.942000 ms, bitrate 8497925311 bps (8104.253112 Mbps)
-inputs_connect: inputs channel client create
-red_qxl_set_cursor_peer:
-gl_version 31 - compat profile
-qemu-system-x86_64: ui/egl-headless.c:128: egl_scanout_flush: Assertion `surface_width(edpy->ds) == edpy->guest_fb.width' failed.
-Aborted (core dumped)
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1810105 b/results/classifier/deepseek-2-tmp/output/graphic/1810105
deleted file mode 100644
index 1f5f8703..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1810105
+++ /dev/null
@@ -1,24 +0,0 @@
-
-Hint showing volume never disappears, blocking buttons to minimize, maximize and close
-
-When hovering the mouse over the volume indicator or changing its volume using the mouse wheel it shows the current volume set as a hint. For example:
-
-Volume 100%
-
-The problem is that the hint never disappears, not even clicking on it. On some occasions the hint can cover the minimize, maximize and close buttons, causing significant problems on using the desktop environment, as these three buttons won't be usable anymore with the hint over it.
-
-Where the hint appears it's no longer possible to interact with the screen.
-
-ProblemType: Bug
-DistroRelease: Ubuntu 18.04
-Package: xfce4-pulseaudio-plugin 0.4.1-0ubuntu1
-ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
-Uname: Linux 4.15.0-43-generic x86_64
-ApportVersion: 2.20.9-0ubuntu7.5
-Architecture: amd64
-CurrentDesktop: XFCE
-Date: Sun Dec 30 17:09:23 2018
-InstallationDate: Installed on 2018-12-30 (0 days ago)
-InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20181230)
-SourcePackage: xfce4-pulseaudio-plugin
-UpgradeStatus: No upgrade log present (probably fresh install)
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1815889 b/results/classifier/deepseek-2-tmp/output/graphic/1815889
deleted file mode 100644
index c237da61..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1815889
+++ /dev/null
@@ -1,42 +0,0 @@
-
-qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()
-
-Unable to launch Default Fedora 29 images in gnome-boxes
-
-ProblemType: Crash
-DistroRelease: Ubuntu 19.04
-Package: qemu-system-x86 1:3.1+dfsg-2ubuntu1
-ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
-Uname: Linux 4.19.0-12-generic x86_64
-ApportVersion: 2.20.10-0ubuntu20
-Architecture: amd64
-Date: Thu Feb 14 11:00:45 2019
-ExecutablePath: /usr/bin/qemu-system-x86_64
-KvmCmdLine: COMMAND         STAT  EUID  RUID   PID  PPID %CPU COMMAND
-MachineType: Dell Inc. Precision T3610
-ProcEnviron: PATH=(custom, user)
-ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic root=UUID=939b509b-d627-4642-a655-979b44972d17 ro splash quiet vt.handoff=1
-Signal: 31
-SourcePackage: qemu
-StacktraceTop:
- __pthread_setaffinity_new (th=<optimized out>, cpusetsize=128, cpuset=0x7f5771fbf680) at ../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34
- () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
- () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
- start_thread (arg=<optimized out>) at pthread_create.c:486
- clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
-Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()
-UpgradeStatus: Upgraded to disco on 2018-11-14 (91 days ago)
-UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
-dmi.bios.date: 11/14/2018
-dmi.bios.vendor: Dell Inc.
-dmi.bios.version: A18
-dmi.board.name: 09M8Y8
-dmi.board.vendor: Dell Inc.
-dmi.board.version: A01
-dmi.chassis.type: 7
-dmi.chassis.vendor: Dell Inc.
-dmi.modalias: dmi:bvnDellInc.:bvrA18:bd11/14/2018:svnDellInc.:pnPrecisionT3610:pvr00:rvnDellInc.:rn09M8Y8:rvrA01:cvnDellInc.:ct7:cvr:
-dmi.product.name: Precision T3610
-dmi.product.sku: 05D2
-dmi.product.version: 00
-dmi.sys.vendor: Dell Inc.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1819908 b/results/classifier/deepseek-2-tmp/output/graphic/1819908
deleted file mode 100644
index cc2b52ef..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1819908
+++ /dev/null
@@ -1,14 +0,0 @@
-
-slight screen corruption when maximizing window
-
-Host: Ubuntu disco
-qemu-kvm: 1:3.1+dfsg-2ubuntu2
-libvirt: 5.0.0-1ubuntu2
-
-
-Guest: ubuntu bionic
-guest is using cirrus video, with the extra modules kernel package installed and the cirrus kernel module loaded
-
-A non-maximized terminal window works just fine. As an example, I run "lsmod". It fills the screen, which then scrolls a bit.
-
-The moment I maximize that window, though, the rendering breaks. I can see the commands I type, but not their output. See attached video.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1827005 b/results/classifier/deepseek-2-tmp/output/graphic/1827005
deleted file mode 100644
index accd3a2a..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1827005
+++ /dev/null
@@ -1,14 +0,0 @@
-
-hvf: ubuntu iso boot menu issue
-
-With hvf acceleration on macOS, ubuntu server installation ISO boot language menu shows fractured images.
-
-To reproduce the issue:
-./x86_64-softmmu/qemu-system-x86_64 -m 800 -accel hvf -cdrom ~/ubuntu-16.04.4-server-amd64.iso
-
-Control:
-./x86_64-softmmu/qemu-system-x86_64 -m 800 -accel tcg -cdrom ~/ubuntu-16.04.4-server-amd64.iso
-
-Host: macOS Mojave 10.14.3
-Guest: Ubuntu Server 16.04.4 ISO
-QEMU: version 3.1.94 (v4.0.0-rc4)
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1827772 b/results/classifier/deepseek-2-tmp/output/graphic/1827772
deleted file mode 100644
index bf5723bd..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1827772
+++ /dev/null
@@ -1,16 +0,0 @@
-
-[RFC] dma buf: support sprite plane
-
-QEMU does not support sprite/overlay in DMA-buf mode for Intel gvt vGPUs. Some use cases relies on sprite plane support, e.g. hw accelerated video playback in Windows 10 guest.
-
-To support this feature, functions in both kernel and QEMU should be implemented:
-
-- query support for plane info in kernel: 
-  in vgpu_get_plane_info() of drm/i915/gvt/dmabuf.c, calls to intel_vgpu_decode_sprite_plane() shall be made;
-
-- struct to hold VFIODMABuf object in QEMU:
-  in struct VFIODisplay of include/hw/vfio/vfio-common.h;
-- copying of data in QEMU:
-  in vfio_display_get_dmabuf() of hw/vfio/display.c;
-- drawing of sprite plane in QEMU:
-  in vfio_display_dmabuf_update() of hw/vfio/display.c;
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1829 b/results/classifier/deepseek-2-tmp/output/graphic/1829
deleted file mode 100644
index c4ad59f2..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1829
+++ /dev/null
@@ -1,89 +0,0 @@
-
-DoS via assert failure by guest user
-Description of problem:
-As root in guest VM user can execute special script, which crashes the whole VM with error
-
-```plaintext
-hw/display/qxl.c:1594 inside of function void qxl_set_mode(PCIQXLDevice *, unsigned int, int): Assertion `qxl_add_memslot(d, 0, devmem, QXL_SYNC) == 0` failed
-```
-Steps to reproduce:
-1. This bug can be reproduced with:
-
-   ```bash
-   cat << EOF | ./build/qemu-system-x86_64 -vga qxl -m 2048 -nodefaults -qtest stdio
-   outl 0xcf8 0x8000101c
-   outl 0xcfc 0xc000
-   outl 0xcf8 0x80001001
-   outl 0xcfc 0x01000000
-   outl 0xc006 0x00
-   EOF
-   ```
-2. Also, we can execute this python3 script inside guest VM as root (to invoke VM use command: **_qemu-system-x86_64 -vga qxl -hda debian.img -m 2048 -nodefaults_**):
-
-   ```python
-   import os
-   f = os.open("/dev/port", os.O_RDWR|os.O_NDELAY)
-   l = os.lseek(f, 0xcf8, 0)
-   os.write(f, b'\x80\x00\x10\x1c')
-   l = os.lseek(f, 0xcfc, 0)
-   os.write(f, b'\xc0\x00')
-   l = os.lseek(f, 0xcf8, 0)
-   os.write(f, b'\x80\x00\x10\x01')
-   l = os.lseek(f, 0xcfc, 0)
-   os.write(f, b'\x01\x00\x00\x00')
-   l = os.lseek(f, 0xc006, 0)
-   os.write(f, b'\x00')
-   ```
-
-   This script causes VM to crash.
-
-   [PoC_qxl-vga_crash.mkv](/uploads/7ee262c20dca69aa9417812f6a93a532/PoC_qxl-vga_crash.mkv)
-Additional information:
-This issue was found by fuzzing. Here is an auto-generated C source code for a test case that will reproduce the bug.
-
-```plaintext
-/*
- * Autogenerated Fuzzer Test Case
- *
- * Copyright (c) 2023 Artem Nasonov <anasonov@astralinux.ru>
- *
- * This work is licensed under the terms of the GNU GPL, version 2 or later.
- * See the COPYING file in the top-level directory.
- */
-
-#include "qemu/osdep.h"
-
-#include "libqtest.h"
-
-/*
- * cat << EOF | qemu-system-x86_64 -vga qxl -hda \
- * ~/Downloads/virtualdebian.img -m 2048 -nodefaults -qtest stdio
- * outl 0xcf8 0x8000101c
- * outl 0xcfc 0xc000
- * outl 0xcf8 0x80001001
- * outl 0xcfc 0x01000000
- * outl 0xc006 0x00
- * EOF
-*/
-static void test_qxl_set_mode(void)
-{
-QTestState *s = qtest_init("-vga qxl -m 2048 -nodefaults");
-qtest_outl(s, 0xcf8, 0x8000101c);
-qtest_outl(s, 0xcfc, 0xc000);
-qtest_outl(s, 0xcf8, 0x80001001);
-qtest_outl(s, 0xcfc, 0x01000000);
-qtest_outl(s, 0xc006, 0x00);
-qtest_quit(s);
-}int main(int argc, char **argv)
-{
-    const char *arch = qtest_get_arch();
-
-    g_test_init(&argc, &argv, NULL);
-
-   if (strcmp(arch, "x86_64") == 0) {
-        qtest_add_func("fuzz/test_qxl_set_mode",test_qxl_set_mode);
-   }
-
-   return g_test_run();
-}
-```
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1829945 b/results/classifier/deepseek-2-tmp/output/graphic/1829945
deleted file mode 100644
index 1c5a20a3..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1829945
+++ /dev/null
@@ -1,11 +0,0 @@
-
-SDL support missing from qemu-1:3.1+dfsg-2ubuntu3.1
-
-qemu support is missing from qemu-1:3.1+dfsg-2ubuntu3.1 on Disco. This is dispite qemu --help saying its available. SDL support is needed to use Packer(https://www.packer.io/) in graphical mode.
-
-# qemu-system-x86_64 -cpu host -smp 2,sockets=2,cores=1,threads=1 -machine type=pc,accel=kvm -display sdl -cdrom ubuntu.iso
-qemu-system-x86_64: Display 'sdl' is not available.
-
-# qemu-system-x86_64 --help | grep sdl
--display sdl[,frame=on|off][,alt_grab=on|off][,ctrl_grab=on|off]
--sdl            shorthand for -display sdl
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1829964 b/results/classifier/deepseek-2-tmp/output/graphic/1829964
deleted file mode 100644
index ea73f60f..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1829964
+++ /dev/null
@@ -1,34 +0,0 @@
-
-HOST VRAM Leak when performs android-x86 window rotation with Virt-GPU
-
-I will report something strange thing about host VRAM leakage after anroid-x86 window rotation when it runs with virt-gpu(+ virgl-renderer)
-
-Please watching below video link.
-
-https://www.youtube.com/watch?v=mJIbGZLWF1s&feature=youtu.be
-
-(orginal video file : https://drive.google.com/file/d/1lkdTx_8yTbSVjKXlnxnnk96fWe-w6Mxb/view?usp=sharing)
-
-I don't sure what is the problem...
-
-Here are my tested history
---------------------------------------------------------------------------------------------------
-Install android-x86 on I7 desktop PCs with intel UHD GPU  - No leak.
-Install android-x86 on I7 desktop PCs with NVIDIA GTX GPU series - No leak.
-Install android-x86 on guest machine emulated skylake cpu with QEMU(+virt-gpu, virgl-renderer) - Leak
-(HOST CPU - I5, INTEL UHD GPU)
-Install android-x86 on guest machine emulated skylake cpu with QEMU(+virt-gpu, virgl-renderer) - Leak
-(HOST CPU - I7, NVIDIA GTX GPU)
-
-COMMON:
-In case of NVIDIA GPU : check vram using nvidia-smi
-In case of intel UHD GPU : check shared-vram using free cmd
-
-We checked guest android-x86 system down when vram is full after performing many rotation
--------------------------------------------------------------------------------------------
-
-Is it virt-gpu driver's problem?
-
-I hope someone can help me...
-
-Thanks in advance!!
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1833101 b/results/classifier/deepseek-2-tmp/output/graphic/1833101
deleted file mode 100644
index 87505270..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1833101
+++ /dev/null
@@ -1,42 +0,0 @@
-
-vexpress-a9 (but not -a15) creates two pl111 LCDs due to duplicate sysbus_create_simple("pl111", ...) calls
-
-Hi,
-
-Just a small report that (12ec8bd is current master)
-
-https://github.com/qemu/qemu/blob/12ec8bd/hw/arm/vexpress.c#L652:
-
-  ...
-  vexpress_common_init() {
-    ...
-    sysbus_create_simple("pl111", map[VE_CLCD], pic[14]);
-    ...
-  ...
-
-and
-
-https://github.com/qemu/qemu/blob/12ec8bd/hw/arm/vexpress.c#L304:
-
-  ...
-  a9_daughterboard_init() {
-    ...
-    sysbus_create_simple("pl111", 0x10020000, pic[44]);
-    ...
-  ...
-
-result in two LCD panels when using vexpress-a9.
-
-vexpress-a15 does not appear to be affected (my -a9 kernel does not work with it, but I see only one pl111 created).
-
-Understandably (but still annoyingly), -nodefaults has no effect.
-
-This bug is most evident when using SDL (so I can use ",frame=off"), which dumps two top-level windows onto the screen. GTK hides this because, coincidentally, the pl111 that ends up being used is the one that is selected (possibly the one created last?), relegating this to an obscure glitch only noticeable if you scrutinize the menu.
-
-This is a bugreport as opposed to a pull request as I have no idea which call to remove - and complete ignorance of the potential housekeeping and consideration that may be warranted first.
-
-FWIW, a simple testcase can be made with the vmlinuz from https://people.debian.org/~aurel32/qemu/armhf/ and
-
-qemu-system-arm -M vexpress-a9 -kernel vmlinuz-3.2.0-4-vexpress -nodefaults -sdl
-
-Thanks!
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1835729 b/results/classifier/deepseek-2-tmp/output/graphic/1835729
deleted file mode 100644
index 1d4c0499..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1835729
+++ /dev/null
@@ -1,10 +0,0 @@
-
-GTK display does not support host scale factor
-
-In the GNOME desktop environment, for HiDPI displays there is support to upscale everything.
-
-This can be set in "System Settings -> Displays -> Scale".
-
-I believe this affects GDK in the same way as setting the "GDK_SCALE" environment variable does.
-
-When launching `qemu-system-x86_64 ... -display gtk`, this scale factor seems to get lost; the result is that the host window is upscaled and doubled in size, while the guest appears only in the bottom left corner of the UI.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1835732 b/results/classifier/deepseek-2-tmp/output/graphic/1835732
deleted file mode 100644
index 03bbba16..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1835732
+++ /dev/null
@@ -1,12 +0,0 @@
-
-GTK display zoom in, zooms infinitely
-
-The zoom in feature in the "View" menu of the gtk frontend (launch qemu with -display gtk), seems to be very broken.
-
-If I hit the zoom in feature, it first zooms in.
-
-Then, it zooms in again.
-
-Every subsequent second that passes, it zooms in again, until it eventually eats up too much host resources and freezes the host desktop.
-
-I have seen this with 3.1.0 (Debian 1:3.1+dfsg-8~deb10u1), and also with a locally built 4.0, My colleague also confirms having seen the issue with 3.1.0 (Debian 1:3.1+dfsg-8).
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1835793 b/results/classifier/deepseek-2-tmp/output/graphic/1835793
deleted file mode 100644
index 626e6e46..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1835793
+++ /dev/null
@@ -1,12 +0,0 @@
-
-Running an edk2 based bios
-
-This is not necessarily a bug, however I wasn't sure were to get help.
-
-I am currently working on using QEMU  to run a BIOS my company has developed. In order to see if the software was working correctly, I was able to successfully run the edk2 bios using the following command:
-
-qemu-system-x86_64.exe -bios "C:\Users\matthew.intriago\Desktop\ovmf.fd" -net none
-
-However, when running the same command using  our personalized bios, QEMU launches stating that “guest has not initialized display”. Theoretically, QEMU should be able to run the bios since it is edk2 based, the only difference between the two is that our bios has more features. 
-
-If anyone has any insight on what the issue might be I would greatly appreciate any help.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1837218 b/results/classifier/deepseek-2-tmp/output/graphic/1837218
deleted file mode 100644
index 63348878..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1837218
+++ /dev/null
@@ -1,21 +0,0 @@
-
-qemu segfaults after spice update with bochs-display
-
-Description:
-
-qemu segfaults after latest spice update with bochs-display. Downgrading spice solves the issue. Switching to qxl-vga and/or virtio-gpu also works even with new spice.
-
-Additional info:
-* package version(s)
-
-spice 0.14.2-1
-qemu-headless 4.0.0-3
-
-* config and/or log files etc.
-
-pf@defiant:~ » /mnt/vms/02-archlinux/start.sh
-/mnt/vms/02-archlinux/start.sh: line 41: 13501 Segmentation fault (core dumped) qemu-system-x86_64 -name "${NAME}" -display none -spice ipv4,addr=127.0.0.1,port=270${ID},disable-ticketing,disable-copy-paste,disable-agent-file-xfer,agent-mouse=off -serial mon:telnet:127.0.0.1:280${ID},server,nowait,nodelay -gdb tcp::260${ID} -nodefaults -machine q35,accel=kvm -cpu max -smp cores=${CPU},threads=1,sockets=1 -m ${MEM} -drive if=pflash,format=raw,readonly,file="${BIOS}" -drive if=pflash,format=raw,file="${VARS}" -device virtio-rng -device bochs-display -device virtio-keyboard -netdev bridge,id=bridge.0,br=vm0 -device virtio-net,mac=${_MAC}:01,netdev=bridge.0,mq=on,vectors=${_VECTORS} -fsdev local,id="${NAME}",path="${SHARED}",security_model=mapped,writeout=immediate -device virtio-9p-pci,fsdev="${NAME}",mount_tag="shared" -device virtio-scsi,id=scsi,num_queues=${CPU},vectors=${_VECTORS} -device scsi-hd,drive=hd1 -drive if=none,media=disk,id=hd1,file="${DISK1}",format=raw,cache=directsync,discard=unmap,detect-zeroes=unmap -device scsi-hd,drive=hd2 -drive if=none,media=disk,id=hd2,file="${DISK2}",format=raw,cache=directsync,discard=unmap,detect-zeroes=unmap -device scsi-cd,drive=cd1 -drive if=none,media=cdrom,id=cd1,file="${CDROM1}",format=raw,cache=directsync
-
-Steps to reproduce:
-
-Update spice, launch a VM like the above and observe a segfault.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1843151 b/results/classifier/deepseek-2-tmp/output/graphic/1843151
deleted file mode 100644
index 42630364..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1843151
+++ /dev/null
@@ -1,14 +0,0 @@
-
-Regression: QEMU 4.1.0 qxl and KMS resoluiton only 4x10
-
-Host is Arch Linux.  linux 5.2.13, qemu 4.1.0.
-
-Guest is Arch Linux Sept 2019 ISO.  linux 5.2.11.
-
-Have replicated this both on a system using amdgpu and one using integrated ASPEED graphics.
-
-Downgrading from 4.1.0 to 4.0.0 works as usual, see: https://www.youtube.com/watch?v=NyMdcYwOCvY
-
-Going back to 4.1.0 reproduces, see: https://www.youtube.com/watch?v=H3nGG2Mk6i0
-
-4.1.0 displays fine until KMS kicks in.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1844053 b/results/classifier/deepseek-2-tmp/output/graphic/1844053
deleted file mode 100644
index 276e9e19..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1844053
+++ /dev/null
@@ -1,62 +0,0 @@
-
-task blocked for more than X seconds - events drm_fb_helper_dirty_work
-
-I've had bunches of these errors on 9 different boots, between 2019-08-21 and now, with Arch host and guest, from linux 5.1.16 to 5.2.14 on host and guest, with QEMU 4.0.0 and 4.1.0.  spice 0.14.2, spice-gtk 0.37, spice-protocol 0.14.0, virt-viewer 8.0.
-
-I've been fighting with some other issues related to a 5.2 btrfs regression, a QEMU qxl regression (see bug 1843151) which I ran into when trying to temporarily abandon virtio-vga, and I haven't paid enough attention to what impact it has on the system when these occur.  In journalctl, I can see I often rebooted minutes after they occurred, but sometimes much later.  That must mean whenever I saw it happen that I rebooted the VM, or potentially it impacted functionality of the system.
-
-Please let me know if and how I can get more information for you if needed.
-
-I've replicated this on both a system with integrated ASPEED video, and on an AMD Vega 64 running amdgpu.
-
-As an example, I have one boot which reported at 122 seconds, 245, 368, 491, 614, 737, 860, 983, 1105, 1228, then I rebooted.
-
-I have another that reported 122/245/368/491/614/737, went away for 10 minutes, then started reporting again 122/245/368/491, and went away.  Then, I rebooted about 20 hours later.
-
-Host system has no graphical impact when this happens, and logs nothing in its journalctl.
-
-==========
-
-INFO: task kworker/0:1:15 blocked for more than 122 seconds.
-      Not tainted 5.2.14-1 #1
-"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
-kworker/0:1     D    0    15      2 0x800004000
-Workqueue: events drm_fb_helper_dirty_work [drm_kms_helper]
-Call Trace:
- ? __schedule+0x27f/0x6d0
- schedule+0x3d/0xc0
- virtio_gpu_queue_fenced_ctrl_buffer+0xa1/0x130 [virtio_gpu]
- ? wait_woken+0x80/0x80
- virtio_gpu_surface_dirty+0x2a5/0x300 [virtio_gpu]
- drm_fb_helper_dirty_work+0x156/0x160 [drm_kms_helper]
- process_one_work+0x19a/0x3b0
- worker_tread+0x50/0x3a0
- kthread+0xfd/0x130
- ? process_one_work+0x3b0/0x3b0
- ? kthread_park+0x80/0x80
- ret_from_fork+0x35/0x40
-
-==========
-
-/usr/bin/qemu-system-x86_64 \
-   -name vm,process=qemu:vm \
-   -no-user-config \
-   -nodefaults \
-   -nographic \
-   -uuid <uuid> \
-   -pidfile <pidfile> \
-   -machine q35,accel=kvm,vmport=off,dump-guest-core=off \
-   -cpu SandyBridge-IBRS \
-   -smp cpus=4,cores=2,threads=1,sockets=2 \
-   -m 4G \
-   -drive if=pflash,format=raw,readonly,file=/usr/share/ovmf/x64/OVMF_CODE.fd \
-   -drive if=pflash,format=raw,file=/var/qemu/efivars/vm.fd \
-   -monitor telnet:localhost:8000,server,nowait,nodelay \
-   -spice unix,addr=/tmp/spice.vm.sock,disable-ticketing \
-   -device ioh3420,id=pcie.1,bus=pcie.0,slot=0 \
-   -device virtio-vga,bus=pcie.1,addr=0 \
-   -usbdevice tablet \
-   -netdev bridge,id=network0,br=br0 \
-   -device virtio-net-pci,netdev=network0,mac=F4:F6:34:F6:34:2d,bus=pcie.0,addr=3 \
-   -device virtio-scsi-pci,id=scsi1 \
-   -drive driver=raw,node-name=hd0,file=/dev/lvm/vm,if=none,discard=unmap,cache=none,aio=threads
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1847906 b/results/classifier/deepseek-2-tmp/output/graphic/1847906
deleted file mode 100644
index ddbd4ee1..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1847906
+++ /dev/null
@@ -1,9 +0,0 @@
-
-Cocoa display hangs on macOS 10.15 (Catalina)
-
-I have downloaded the latest stable source tarball 4.1.0 and compiled it (i386-softmmu target).
-
-After opening a black window, QEMU hangs (spinning beach ball).
-When building with `--disable-cocoa --enable-sdl`, display seems to work fine.
-
-The same happened when I tried to build QEMU through HomeBrew and MacPorts.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1854204 b/results/classifier/deepseek-2-tmp/output/graphic/1854204
deleted file mode 100644
index 65a91beb..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1854204
+++ /dev/null
@@ -1,7 +0,0 @@
-
-Menu is not clickable on OSX Catalina
-
-1) Run `qemu-system-x86_64`
-2) Try to click on the main menu
-
-Menu is not clickable until another window is activated and QEMU window is activated again
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1856399 b/results/classifier/deepseek-2-tmp/output/graphic/1856399
deleted file mode 100644
index 8e40c477..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1856399
+++ /dev/null
@@ -1,20 +0,0 @@
-
-Intel GVT-g works in X11, segfaults in wayland
-
-Hello,
-
-I am using an uptodate Arch Linux 64bit with qemu version 4.2.0, but the problem was also present in older versions. The problem occurs with Linux 5.4 and 4.19.
-The problem also occurs with Debian as guest. I am running sway.
-If I provide -vga std, then qemu works fine until I use the qemu window to switch to the vfio-pci device. There are no problems under X11/xwayland at all.
-
-
-Commandline:
-qemu-system-x86_64
-    -enable-kvm
-    -cpu host
-    -smp 2
-    -m 8192
-    -display gtk,gl=on
-    -device vfio-pci,sysfsdev=/sys/devices/pci0000:00/0000:00:02.0/[ID]/,x-igd-opregion=on,display=on
-    -cdrom archlinux-2019.11.01-x86_64.iso
-    -vga none
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1859254 b/results/classifier/deepseek-2-tmp/output/graphic/1859254
deleted file mode 100644
index 4d36bf61..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1859254
+++ /dev/null
@@ -1,32 +0,0 @@
-
-host window size does not change when guest video screen size changes while moving host window
-
-When QEMU is emulating a legacy text mode, then switches to a VESA mode, if you happen to be moving the host window while the switch is made, the host window never changes size.  The emulated size does, but the host window doesn't.
-
-For example, at Legacy boot up, the screen mode is mode 03 at 80x25.  Then when the GUEST OS changes the screen to a VESA mode, say 1024x768x16, normally the host window will change to that size to accommodate the new emulated screen size.
-
-However, if you happen to be moving the host window at the time of the screen mode change, the host window doesn't change in size to accommodate the new screen size.  
-
-I am using:
-  QEMU for Windows, version 4.1.0-11789
-  Host: Windows 10 (latest updates)
-  Emulating: Intel x64, Legacy BIOS
-Command line:
-"c:\program files\qemu\qemu-system-x86_64.exe" -m 256 -drive file=C:\fysos64.img,format=raw,if=ide,media=disk,index=0 -parallel file:para.txt -boot c -d guest_errors -vga std -smp cpus=4 -rtc base=localtime,clock=host,driftfix=slew -net none -monitor stdio
-
-I tried different -vga settings:
-   -vga std
-   -vga cirrus
-   -vga vmware
-Each did the same thing.
-
-[ Side note (possible error in documentation):
-[  at: https://qemu.weilnetz.de/doc/qemu-doc.html#SVGA-graphic-modes-support
-[  end of 2.16.2.1
-[  (option -std-vga)
-[    possibly should be
-[  (option -vga std)
-
-If you need an image to test with, I have been using www.fysnet.net/temp/fysos64.zip (2meg zipped/10meg raw).  It starts in Legacy BIOS/Hardware mode 3, then switches to VESA 1024x768x16 within a few seconds, so be ready to move the HOST window when the mode changes.
-
-I do not have a Linux box to test with, so unknown if this is only an issue with the Windows version or not.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1859723 b/results/classifier/deepseek-2-tmp/output/graphic/1859723
deleted file mode 100644
index a79707cb..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1859723
+++ /dev/null
@@ -1,8 +0,0 @@
-
-Qemu ungrabs before cursor reaches border
-
-This was first reported https://bugzilla.redhat.com/show_bug.cgi?id=1285378
-
-video: https://peertube.co.uk/videos/watch/fedaa432-79ef-4d30-bd0e-26c806e48db0
-
-version: QEMU emulator version 4.2.0
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1862 b/results/classifier/deepseek-2-tmp/output/graphic/1862
deleted file mode 100644
index 182014d0..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1862
+++ /dev/null
@@ -1,19 +0,0 @@
-
-SVGA/VESA strange colors (NetWare 6.x)
-Description of problem:
-The text mode part of the installation is correct but whenever the X server is starting, the display seems to be in 16 colors although GUI settings shows "SVGA/256 colors" (NetWare setup reports a "SVGA Plug & Play" display, VESA 2.0 compliance expected). Color depth issue with VESA? Telling NetWare to use explicitly the Cirrus Logic driver for a CL GD 5446 bring the display back to normal and colors are displayed as they should.
-Steps to reproduce:
-1. Grab a NetWare 6.0 installation ISO on some abandonware site (no need of a license key, unlicensed = 2 users max.)
-2. Execute the command line above
-3. Complete the text-mode part (defaults choices are fine)
-Additional information:
-NetWare 6.0 + Qemu => Same issue. SVGA PnP with wrong colors.
-NetWare 6.5 + Qemu => Same issue. SVGA PnP with wrong colors.
-NetWare 6.0 + PCem/86Box => does not exhibit the issue. Colors are normal.
-
-Using SeaBIOS 1.16.
-
-Screenshots:
-
-![NW60_SVGA_16_colors](/uploads/d72838ee709f97043c0f295b8e2d222c/NW60_SVGA_16_colors.png)
-![NW60_SVGA_Normal_colors](/uploads/6a0b36b2a2348f69ffd24206b1a54780/NW60_SVGA_Normal_colors.png)
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1864814 b/results/classifier/deepseek-2-tmp/output/graphic/1864814
deleted file mode 100644
index 98f7b152..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1864814
+++ /dev/null
@@ -1,15 +0,0 @@
-
-Improve UX for macOS when launching from a fullscreen app
-
-System/setup:
-* MacBook Pro, macOS (any version from the last 2 years), external monitor.
-* IDE on the laptop, emulator is used on the external monitor.
-
-Currently, when starting the emulator from e.g. Android Studio or IntelliJ IDEA, which is set to fullscreen mode on the laptop, which is like it's own virtual desktop (Space) in macOS, what happens is this:
-
-1. The virtual desktop (Space) on the laptop screen is switched because of #2. The reason is that only one window can be shown in Fullscreen this way.
-2. The qemu splashscreen is shown for a few seconds, then it disappears. This is the reason for the virtual desktop switch. This splashscreen seems actually unnecessary to me, it has no value and it causes problems.
-3. The actual emulator is shown, in my case on the external monitor (correctly). I guess if the splashscreen would not be shown, the virtual desktop switch would not happen, because the emulator would happen on the correct screen directly.
-
-So maybe the splashscreen and the emulator window should be the same window, so that the OS can remember it's position being the same as the emulator?
-Or maybe the splash could be disabled (by default? otherwise an update to IDEs would be necessary for the improved behavior?)
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1864984 b/results/classifier/deepseek-2-tmp/output/graphic/1864984
deleted file mode 100644
index 8d0b874a..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1864984
+++ /dev/null
@@ -1,10 +0,0 @@
-
-"nr_entries is too big" when using virgl
-
-I have a bootable image where GNOME Shell fails because it hits a limit in virtio-gpu.
-
-In `hw/display/virtio-gpu.c`, there is a limit for `nr_entries` at 16384. There is no explanation for that limit. But there does not seem to be any limit on the kernel side.
-
-Raising this limit with a patch to 262144 solves the issue.
-
-Could there be an explanation why this limit is needed? And why this value? Or could this limit be just removed?
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1865248 b/results/classifier/deepseek-2-tmp/output/graphic/1865248
deleted file mode 100644
index d293be5b..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1865248
+++ /dev/null
@@ -1,12 +0,0 @@
-
-bundle QEMU installer with a QEMU GUI (graphical user interface) such as Virt Manager
-
-For a better out of the box user experience on the Windows platform it would be nice if a QEMU GUI would be by installed by the same QEMU installer. Currently it is required to first install QEMU and then install a QEMU GUI.
-
-I don't know all QEMU GUIs but looks like Virt Manager is a decent QEMU GUI and still maintained.
-
-Virt Manager is also available for Windows.
-
-https://serverfault.com/questions/340949/is-there-a-way-to-run-virt-manager-on-windows
-
-However as per these instructions it is difficult (many steps) for laymen to install Virt Manager on Windows (cygwin...).
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1873339 b/results/classifier/deepseek-2-tmp/output/graphic/1873339
deleted file mode 100644
index 99f68282..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1873339
+++ /dev/null
@@ -1,8 +0,0 @@
-
-Qemu DOS Quake - 640x480 and above resolutions - Unable to load VESA palette in dos prompt and game crashing are not working 
-
-I have problem make Quake Demo working with 640x480+, with 320x200 working fine.
-I tried 3 virtual videocards settings: -vga cirrus 640x480 is not available, probably emulated GPU has not enough VRAM or some Vesa2 utility is needed. For -vga std and -vga vmware // 640x480 is available in game menu, but when i tried to set it, im getting: Unable to load VESA palette in dos prompt and game crashing.
-With vmware svgaII other Q2DOS 640x480 and 1024x768 its working fine, so it not working only with some games.
-
-  Qemu 4.2, its same on Linux and Windows.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1873341 b/results/classifier/deepseek-2-tmp/output/graphic/1873341
deleted file mode 100644
index 668ad037..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1873341
+++ /dev/null
@@ -1,12 +0,0 @@
-
-Qemu Win98 VM with KVM videocard passthrough DOS mode video is not working for most of games..
-
-Hello,
-im using Win98 machine with KVM videocards passthrough which is working fine, but when i try Windows 98 - Dosbox mode, there is something work with all videocards which i tried PCI-E/PCI - Nvidia, 3Dfx, Matrox.
-
- Often is framerate is very slow, as slideshow:
-Doom 2, Blood, even for Fdisk start - i can see how its slowly rendering individual lines, or its not working at all - freeze / black screen only - Warcraft 2 demo (vesa 640x480). 
-
- There is something wrong with it.
-
- Qemu 2.11 + 4.2, Linux Mint 19.3. Gigabyte Z170 MB.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1876 b/results/classifier/deepseek-2-tmp/output/graphic/1876
deleted file mode 100644
index 1d9223e9..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1876
+++ /dev/null
@@ -1,2 +0,0 @@
-
-Host wayland gtk problem
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1880539 b/results/classifier/deepseek-2-tmp/output/graphic/1880539
deleted file mode 100644
index 25e19774..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1880539
+++ /dev/null
@@ -1,26 +0,0 @@
-
-I/O write make QXL abort in qxl_set_mode()
-
-libFuzzer found:
-
-qxl-0: guest bug: qxl_add_memslot: guest_start > guest_end 0xffffffffffffffff > 0x3ffffff
-qemu-fuzz-i386: hw/display/qxl.c:1611: void qxl_set_mode(PCIQXLDevice *, unsigned int, int): Assertion `qxl_add_memslot(d, 0, devmem, QXL_SYNC) == 0' failed.
-==8134== ERROR: libFuzzer: deadly signal
-    #0 0x55fddfcfb3f0 in __sanitizer_print_stack_trace (qemu-fuzz-i386+0xcb13f0)
-    #1 0x55fddfc0a3e1 in fuzzer::PrintStackTrace() (qemu-fuzz-i386+0xbc03e1)
-    #2 0x55fddfbeac6f in fuzzer::Fuzzer::CrashCallback() (qemu-fuzz-i386+0xba0c6f)
-    #3 0x55fddfbeacc3 in fuzzer::Fuzzer::StaticCrashSignalCallback() (qemu-fuzz-i386+0xba0cc3)
-    #4 0x7fd640644c6f  (/lib64/libpthread.so.0+0x12c6f)
-    #5 0x7fd640483e34 in __GI_raise (/lib64/libc.so.6+0x37e34)
-    #6 0x7fd64046e894 in __GI_abort (/lib64/libc.so.6+0x22894)
-    #7 0x7fd64046e768 in __assert_fail_base.cold (/lib64/libc.so.6+0x22768)
-    #8 0x7fd64047c565 in __GI___assert_fail (/lib64/libc.so.6+0x30565)
-    #9 0x55fde08afd8b in qxl_set_mode (qemu-fuzz-i386+0x1865d8b)
-    #10 0x55fde08b9602 in ioport_write (qemu-fuzz-i386+0x186f602)
-    #11 0x55fddff170a7 in memory_region_write_accessor (qemu-fuzz-i386+0xecd0a7)
-    #12 0x55fddff16c13 in access_with_adjusted_size (qemu-fuzz-i386+0xeccc13)
-    #13 0x55fddff157b4 in memory_region_dispatch_write (qemu-fuzz-i386+0xecb7b4)
-
-Can be reproduce doing "writeb 0x06 0x23" on QXL I/O (PCI BAR #3).
-
-Command line: 'qemu-system-i386 -display none -M pc -vga qxl'
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1882784 b/results/classifier/deepseek-2-tmp/output/graphic/1882784
deleted file mode 100644
index 544e2427..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1882784
+++ /dev/null
@@ -1,32 +0,0 @@
-
-Legacy IGD passthrough in QEMU 5 disabled
-
-Bug with tag v5.0.0, or commit fdd76fecdde1ad444ff4deb7f1c4f7e4a1ef97d6
-
-As of QEMU 5 Legacy IGD PT is no longer working.
-
-Host is a Xeon E3-1226 v3 and my method to test is to run the following:
-
-./qemu-system-x86_64 \
-  -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pci.0,addr=0x1f' \
-  -device 'vfio-pci,host=00:02.0,addr=02.0' \
-  -L '/usr/share/kvm' \
-  -nographic \
-  -vga none \
-  -nodefaults
-
-in the hope of seeing a "IGD device 0000:00:02.0 cannot support legacy mode due to existing devices at address 1f.0" error.
-
-The culprit appears to be this commit:
-
-https://github.com/qemu/qemu/commit/29d62771c81d8fd244a67c14a1d968c268d3fb19
-
-Specifically the following block in pci-quirks.c:
-
-#ifdef CONFIG_VFIO_IGD
-    vfio_probe_igd_bar4_quirk(vdev, nr);
-#endif
-
-as the kconfig variable CONFIG_VFIO_IGD doesn't appear to be available outside of makefiles as described here: https://qemu.weilnetz.de/doc/devel/kconfig.html. I can confirm that the igd code is being pulled in as removing this check, as would defining the variable I presume, makes Legacy IGD PT work again (ie I see the expected "existing devices" error).
-
-I first spotted this in Proxmox, but have confirmed the bug by building QEMU sources.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1882851 b/results/classifier/deepseek-2-tmp/output/graphic/1882851
deleted file mode 100644
index 705a4db9..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1882851
+++ /dev/null
@@ -1,21 +0,0 @@
-
-QEMU video freezes with "Guest disabled display" (virtio driver)
-
-I am using Arch Linux as my Guest and Host OS, after starting qemu with the following command:
-
-  $ qemu-system-x86_64 -enable-kvm -hda arch-zoom.qcow2 -m 4G -vga virtio
-
-and waiting for a screen blank, I get this message:
-
-  Guest disabled display
-
-And nothing happens after that, I can move the mouse or hit any key, and the message is still there.
-
-I can still reboot the VM but that's not optimal.
-
-I can reproduce this with the latest QEMU release (5.0.0) or git master, 
-I also tried this with older releases (4.0.0, 3.0.0) and the issue is still there.
-
-I can't reproduce this with other video drivers (std, qxl).
-
-With std/qxl the screen will blank a bit and then continue as normal.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1884302 b/results/classifier/deepseek-2-tmp/output/graphic/1884302
deleted file mode 100644
index 95e95e53..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1884302
+++ /dev/null
@@ -1,19 +0,0 @@
-
-disable automatic mouse grabbing
-
-I'm using QEMU 5.0.0 on a Gentoo Linux host system. Guest is an Arch Linux system.
-
-I'd like to disable automatic mouse grabbing when the QEMU window is focused.
-I would prefer for QEMU to grab the mouse only after a click.
-
-I use the i3 window manager on my host system.
-Suppose I'm in workspace 1, while the QEMU window is in workspace 2.
-In order to switch to workspace 2, I need to press the "Win+2" key combination ("Win" is the Windows key).
-The problem is that the character "2" (from "Win+2") will get transferred to the guest system.
-For example, if I have a text editor opened under the guest system, the character "2" will be pasted inside the document I'm working on, which is pretty annoying.
-
-I would like instead to press the "Win+2" key combination and then explicitely click on the QEMU window with the mouse before grabbing it.
-
-Command line:
-
-qemu-system-x86_64 -drive file=/home/fturco/qemu/arch.img,media=disk,index=0,if=virtio,format=raw,cache=none -cpu host -m 2G -k it -enable-kvm -net nic,model=virtio -net user -vga virtio -display sdl -usb -rtc base=utc -soundhw ac97 -monitor stdio -no-quit
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1884507 b/results/classifier/deepseek-2-tmp/output/graphic/1884507
deleted file mode 100644
index 20acca68..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1884507
+++ /dev/null
@@ -1,7 +0,0 @@
-
-'none' machine should use 'none' display option
-
-As the 'none' machine doesn't have any peripheral (except CPU cores)
-it is pointless to start a display. 
-
-'-M none' should imply '-display none'.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1884990 b/results/classifier/deepseek-2-tmp/output/graphic/1884990
deleted file mode 100644
index a2db3eb6..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1884990
+++ /dev/null
@@ -1,7 +0,0 @@
-
-Cirrus graphics results in monochrome colour depth at 640x480 resolution
-
-Recently we upgraded to a distribution that bundled QEMU 4.2.0.  We were previously running on QEMU 3.0.0.  When booting Windows 10 VMs on x86_64, users experienced slow, monochrome graphics and the resolution was restricted to 640x480.  Reverting to the prior vgabios-cirrus.bin from the prior source tarball remediated the issue.
-
-An example QEMU command line is below, if needed:
-/bin/qemu-system-x86_64 -vnc 0.0.0.0:100 -device cirrus-vga,id=video0,bus=pci.0,addr=0x2  -machine pc-i440fx-4.2,accel=kvm,usb=off,dump-guest-core=off -cpu qemu64 -m 2048 -overcommit mem-lock=off -smp 1,sockets=1,cores=1,threads=1 -no-user-config -nodefaults -hda test.raw &
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1888492 b/results/classifier/deepseek-2-tmp/output/graphic/1888492
deleted file mode 100644
index 0546489a..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1888492
+++ /dev/null
@@ -1,56 +0,0 @@
-
-After installing Ubuntu, restart and pop up the CMD command prompt
-
-QEMU release version： V5.1.0
-time：2020年7月22日10:34:40
-Operation: 安装完Ubuntu后重新启动，并弹出CMD命令提示符
-Question:
-Command used：qemu-system-x86_64.exe -name test -m 4096 -machine accel=hax -cdrom .\workspace\ubuntu\ubuntu-20.04-desktop-amd64.iso .\workspace\img\ubuntu.img
-HAX is working and emulator runs in fast virt mode.
-*** BUG ***
-In pixman_region32_init_rect: Invalid rectangle passed
-Set a breakpoint on '_pixman_log_error' to debug
-
-*** BUG ***
-In pixman_region32_init_rect: Invalid rectangle passed
-Set a breakpoint on '_pixman_log_error' to debug
-
-*** BUG ***
-In pixman_region32_init_rect: Invalid rectangle passed
-Set a breakpoint on '_pixman_log_error' to debug
-
-*** BUG ***
-In pixman_region32_init_rect: Invalid rectangle passed
-Set a breakpoint on '_pixman_log_error' to debug
-
-*** BUG ***
-In pixman_region32_init_rect: Invalid rectangle passed
-Set a breakpoint on '_pixman_log_error' to debug
-
-*** BUG ***
-In pixman_region32_init_rect: Invalid rectangle passed
-Set a breakpoint on '_pixman_log_error' to debug
-
-*** BUG ***
-In pixman_region32_init_rect: Invalid rectangle passed
-Set a breakpoint on '_pixman_log_error' to debug
-
-*** BUG ***
-In pixman_region32_init_rect: Invalid rectangle passed
-Set a breakpoint on '_pixman_log_error' to debug
-
-*** BUG ***
-In pixman_region32_init_rect: Invalid rectangle passed
-Set a breakpoint on '_pixman_log_error' to debug
-
-*** BUG ***
-In pixman_region32_init_rect: Invalid rectangle passed
-Set a breakpoint on '_pixman_log_error' to debug
-
-
-(qemu:660): Gtk-WARNING **: Negative content width -7 (allocation 1, extents 4x4) while allocating gadget (node headerbar, owner GtkHeaderBar)
-
-(qemu:660): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -102 and height 16
-
-(qemu:660): Gtk-WARNING **: Negative content width -23 (allocation 1, extents 12x12) while allocating gadget (node label, owner GtkLabel)
-qemu-system-x86_64.exe: Gtk: gtk_distribute_natural_allocation: assertion 'extra_space >= 0' failed
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1888964 b/results/classifier/deepseek-2-tmp/output/graphic/1888964
deleted file mode 100644
index 9ce17f20..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1888964
+++ /dev/null
@@ -1,41 +0,0 @@
-
-Segfault using GTK display with dmabuf (iGVT-g) on Wayland
-
-When using...
- a) Intel virtualized graphics (iGVT-g) with dmabuf output
- b) QEMU's GTK display with GL output enabled (-display gtk,gl=on)
- c) A Wayland compositor (Sway in my case)
-a segfault occurs at some point on boot (I guess as soon as the guest starts using the virtual graphics card?)
-
-The origin is the function dpy_gl_scanout_dmabuf in ui/console.c, where it calls
-    con->gl->ops->dpy_gl_scanout_dmabuf(con->gl, dmabuf);
-However, the ops field (struct DisplayChangeListenerOps) does not have dpy_gl_scanout_dmabuf set because it is set to dcl_gl_area_ops which does not have dpy_gl_scanout_dmabuf set.
-Only dcl_egl_ops has dpy_gl_scanout_dmabuf set.
-Currently, the GTK display uses EGL on X11 displays, but GtkGLArea on Wayland. This can be observed in early_gtk_display_init() in ui/gtk.c, where it says (simplified code):
-
-if (opts->has_gl && opts->gl != DISPLAYGL_MODE_OFF) {
-        if (GDK_IS_WAYLAND_DISPLAY(gdk_display_get_default())) {
-            gtk_use_gl_area = true;
-            gtk_gl_area_init();
-        } else {
-            DisplayGLMode mode = opts->has_gl ? opts->gl : DISPLAYGL_MODE_ON;
-            gtk_egl_init(mode);
-        }
-}
-
-To reproduce the findings above, add this assertion to dpy_gl_scanout_dmabuf:
-    assert(con->gl->ops->dpy_gl_scanout_dmabuf);
-This will make the segfault turn into an assertion failure.
-
-A workaround is to force QEMU to use GDK's X11 backend (using GDK_BACKEND=x11).
-
-Note: This might be a duplicate of 1775011, however the information provided in that bug report is not sufficient to make the assertion.
-
-QEMU version: b0ce3f021e0157e9a5ab836cb162c48caac132e1 (from Git master branch)
-OS: Arch Linux, Kernel Version 5.17.0-1
-
-Relevant flags of the QEMU invocation:
-qemu-system-x86_64 \
-  -vga none \
-  -device vfio-pci-nohotplug,sysfsdev="$GVT_DEV",romfile="${ROMFILE}",display=on,x-igd-opregion=on,ramfb=on \
-  -display gtk,gl=on
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1890208 b/results/classifier/deepseek-2-tmp/output/graphic/1890208
deleted file mode 100644
index 1ec9c5f7..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1890208
+++ /dev/null
@@ -1,12 +0,0 @@
-
-Mouse pointer disappears when it is over console window
-
-The host mouse pointer disappears when it is over a console window.
-
-I am emulating quite simple hardware: just text console and no mouse. I don't expect the mouse to have any effect on the emulated computers, but I need to know where the mouse pointer is. That is  important because I need to use the mouse to switch between applications and to switch between virtual machines (QEMU grabs Alt+Tab events). Also, it is quite tricky to work with multiple screens when we don't know where the mouse pointer is.
-
-I am using:
-* Virtual Machine Manager 2.2.1
-* QEMU 4.2.0
-* Fedora 32
-* KDE Plasma 5.18.5
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1890310 b/results/classifier/deepseek-2-tmp/output/graphic/1890310
deleted file mode 100644
index 2c14a70e..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1890310
+++ /dev/null
@@ -1,48 +0,0 @@
-
-Segfault in artist.c:block_move
-
-Hello,
-Reproducer:
-
-cat << EOF | ./hppa-softmmu/qemu-system-hppa -m 64 -display none \
--qtest stdio -accel qtest
-writeq 0xf8100802 0xff5c651ffffb7c5c
-writeq 0xf8100afb 0x25e000000000000
-EOF
-
-AddressSanitizer:DEADLYSIGNAL
-=================================================================
-==12686==ERROR: AddressSanitizer: SEGV on unknown address 0x7f001a540000 (pc 0x55af3a373078 bp 0x7ffc23001a00 sp 0x7ffc23001670 T0)
-==12686==The signal is caused by a READ memory access.
-    #0 0x55af3a373078 in block_move /hw/display/artist.c:525:13
-    #1 0x55af3a365fbc in artist_reg_write /hw/display/artist.c:964:9
-    #2 0x55af39a577a3 in memory_region_write_accessor /softmmu/memory.c:483:5
-    #3 0x55af39a56adc in access_with_adjusted_size /softmmu/memory.c:539:18
-    #4 0x55af39a54873 in memory_region_dispatch_write /softmmu/memory.c:1466:16
-    #5 0x55af39102056 in flatview_write_continue /exec.c:3176:23
-    #6 0x55af390ea866 in flatview_write /exec.c:3216:14
-    #7 0x55af390ea387 in address_space_write /exec.c:3308:18
-    #8 0x55af39afe604 in qtest_process_command /softmmu/qtest.c:452:13
-    #9 0x55af39af5c08 in qtest_process_inbuf /softmmu/qtest.c:710:9
-    #10 0x55af39af4895 in qtest_read /softmmu/qtest.c:722:5
-    #11 0x55af3bfb0c43 in qemu_chr_be_write_impl /chardev/char.c:188:9
-    #12 0x55af3bfb0dc7 in qemu_chr_be_write /chardev/char.c:200:9
-    #13 0x55af3bfc50b3 in fd_chr_read /chardev/char-fd.c:68:9
-    #14 0x55af3c119474 in qio_channel_fd_source_dispatch /io/channel-watch.c:84:12
-    #15 0x7f0028f60897 in g_main_context_dispatch (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x4e897)
-    #16 0x55af3c51137b in glib_pollfds_poll /util/main-loop.c:217:9
-    #17 0x55af3c50eaab in os_host_main_loop_wait /util/main-loop.c:240:5
-    #18 0x55af3c50e444 in main_loop_wait /util/main-loop.c:516:11
-    #19 0x55af39b16d00 in qemu_main_loop /softmmu/vl.c:1676:9
-    #20 0x55af3c151261 in main /softmmu/main.c:49:5
-    #21 0x7f0027ae6e0a in __libc_start_main /build/glibc-GwnBeO/glibc-2.30/csu/../csu/libc-start.c:308:16
-    #22 0x55af38ff5729 in _start (/home/alxndr/Development/qemu/general-fuzz/build/hppa-softmmu/qemu-system-hppa+0x22d4729)
-
-AddressSanitizer can not provide additional info.
-SUMMARY: AddressSanitizer: SEGV /hw/display/artist.c:525:13 in block_move
-==12686==ABORTING
-
-The error occurs even with Message-Id: <email address hidden> applied (I collected the above trace with the patch-set applied)
-
-Thanks
--Alex
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1890312 b/results/classifier/deepseek-2-tmp/output/graphic/1890312
deleted file mode 100644
index ccc40ec4..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1890312
+++ /dev/null
@@ -1,42 +0,0 @@
-
-Segfault in artist_vram_read
-
-Hello,
-Reproducer:
-
-cat << EOF | ./hppa-softmmu/qemu-system-hppa -m 64 -display none \
--qtest stdio -accel qtest
-writew 0xf8118001 0x105a
-readq 0xf900f8ff
-EOF
-
-=================================================================
-==20118==ERROR: AddressSanitizer: SEGV on unknown address 0x7fc6fb847672 (pc 0x55ec9c0f6828 bp 0x7ffd91000230 sp 0x7ffd90ffffd0 T0)
-==20118==The signal is caused by a READ memory access.
-    #0 0x55ec9c0f6828 in artist_vram_read /hw/display/artist.c:1174:15
-    #1 0x55ec9b84a582 in memory_region_read_accessor /softmmu/memory.c:434:11
-    #2 0x55ec9b7d1adc in access_with_adjusted_size /softmmu/memory.c:539:18
-    #3 0x55ec9b7cd769 in memory_region_dispatch_read1 /softmmu/memory.c:1385:16
-    #4 0x55ec9b7cc855 in memory_region_dispatch_read /softmmu/memory.c:1414:9
-    #5 0x55ec9ae621de in flatview_read_continue /exec.c:3239:23
-    #6 0x55ec9ae64fb1 in flatview_read /exec.c:3279:12
-    #7 0x55ec9ae64af7 in address_space_read_full /exec.c:3292:18
-    #8 0x55ec9b87c990 in address_space_read /include/exec/memory.h:2429:18
-    #9 0x55ec9b87c990 in qtest_process_command /softmmu/qtest.c:485:13
-    #10 0x55ec9b870c08 in qtest_process_inbuf /softmmu/qtest.c:710:9
-    #11 0x55ec9b86f895 in qtest_read /softmmu/qtest.c:722:5
-    #12 0x55ec9dd2b2f3 in qemu_chr_be_write_impl /chardev/char.c:188:9
-    #13 0x55ec9dd2b477 in qemu_chr_be_write /chardev/char.c:200:9
-    #14 0x55ec9dd3f763 in fd_chr_read /chardev/char-fd.c:68:9
-    #15 0x55ec9de93b24 in qio_channel_fd_source_dispatch /io/channel-watch.c:84:12
-    #16 0x7fc7261ad897 in g_main_context_dispatch ()
-    #17 0x55ec9e28ba2b in glib_pollfds_poll /util/main-loop.c:217:9
-    #18 0x55ec9e28915b in os_host_main_loop_wait /util/main-loop.c:240:5
-    #19 0x55ec9e288af4 in main_loop_wait /util/main-loop.c:516:11
-    #20 0x55ec9b891d00 in qemu_main_loop /softmmu/vl.c:1676:9
-    #21 0x55ec9decb911 in main /softmmu/main.c:49:5
-
-The error occurs even with Message-Id: <email address hidden> applied (I collected the above trace with the patch-set applied)
-
-Thanks
--Alex
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1891 b/results/classifier/deepseek-2-tmp/output/graphic/1891
deleted file mode 100644
index 267f09ea..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1891
+++ /dev/null
@@ -1,49 +0,0 @@
-
-qemu 8.1.0 breaks gvt-g + qemu-ui-gtk w gl=on (black screen, qemu: eglCreateImageKHR failed)
-Description of problem:
-As of 8.1.0, qemu-ui-gtk renders a black window with the error `qemu: eglCreateImageKHR failed` repeatedly appearing in the command line.
-
-
-#
-Steps to reproduce:
-1. enable kernel modules, set parameters etc.
-2. create vgpu
-     `echo "$GVT_GUID" > "/sys/devices/pci0000:00/0000:00:02.0/mdev_supported_types/i915-GVTg_V4_2/create"`
-3. launch VM
-4. wait
-
-Instructions (a small part of which I wrote by trial and error) for the setup are on the [Arch Wiki](https://wiki.archlinux.org/title/Intel_GVT-g).
-
-#
-Additional information:
-Windows is installed directly to a second SSD, I dual-boot it.  
-I've been using this exact VM, from libvirt, for almost two years.  
-relevant sections:
-```
-    <hostdev mode="subsystem" type="mdev" managed="no" model="vfio-pci" display="off">
-      <source>
-        <address uuid="$GVT_GUID"/>
-      </source>
-    </hostdev>
-  </devices>
-  <qemu:commandline>
-    <qemu:arg value="-display"/>
-    <qemu:arg value="gtk,gl=on,zoom-to-fit=off"/>
-    <qemu:env name="DISPLAY" value=":0.0"/>
-  </qemu:commandline>
-  <qemu:override>
-    <qemu:device alias="hostdev0">
-      <qemu:frontend>
-        <qemu:property name="x-igd-opregion" type="bool" value="true"/>
-        <qemu:property name="driver" type="string" value="vfio-pci-nohotplug"/>
-        <qemu:property name="ramfb" type="bool" value="true"/>
-        <qemu:property name="display" type="string" value="on"/>
-        <qemu:property name="romfile" type="string" value="/home/user/VM/vbios_gvt_uefi.rom"/>
-      </qemu:frontend>
-    </qemu:device>
-  </qemu:override>
-```
-
-The patched vBIOS necessary to use DMA-BUF with OVMF is linked there too, but its [successors](https://github.com/patmagauran/i915ovmfPkg) doesn't work either.
-
-#
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1891749 b/results/classifier/deepseek-2-tmp/output/graphic/1891749
deleted file mode 100644
index eafc14a5..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1891749
+++ /dev/null
@@ -1,4 +0,0 @@
-
-CGA Mode 6 is only 100 pixels tall, when it's supposed to be 200
-
-I have written a program that used CGA Mode 6 (640x200 black and white). However qemu-system-i386 only displays the first 100 pixels, effectively limiting the resolution of mode 6 to 640x100. When running the same program on a real computer it uses the whole 640x200 pixels.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1898490 b/results/classifier/deepseek-2-tmp/output/graphic/1898490
deleted file mode 100644
index 5cd43da8..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1898490
+++ /dev/null
@@ -1,16 +0,0 @@
-
-gtk with virtio and opengl black screen
-
-qemu-system-x86_64 -name manjaro -enable-kvm -cpu host -smp cores=4,threads=1 -M q35 -m 8G -cdrom /mnt/Storage/ISO/manjaro-gnome-20.0.3-minimal-200606-linux56.iso -machine type=pc,accel=kvm -vga virtio -display sdl,gl=on Boots properly and has working 3d acceleration with virgl.
-
-Running qemu-system-x86_64 -name manjaro -enable-kvm -cpu host -smp cores=4,threads=1 -M q35 -m 8G -cdrom /mnt/Storage/ISO/manjaro-gnome-20.0.3-minimal-200606-linux56.iso -machine type=pc,accel=kvm -vga virtio -display gtk,gl=on however, (difference being gtk instead of sdl), the screen is black, and the vm still starts.
-
-System Specs
-Gentoo Linux 64bit
-Gentoo-Sources 5.8.13 Kernel
-Qemu 5.10.0-r1 compiled with USE="aio bzip2 caps curl fdt filecaps gtk jpeg ncurses nls opengl oss pin-upstream-blobs png pulseaudio sdl seccomp slirp spice usb usbredir vhost-net virgl vnc xattr xkb" PYTHON_TARGETS="python3_7" QEMU_SOFTMMU_TARGETS="x86_64" QEMU_USER_TARGETS="x86_64"
-
-Ryzen 7 2700x
-Nvidia 1070ti GPU
-
-I can confirm the same issue when using libvirt with opengl.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1899733 b/results/classifier/deepseek-2-tmp/output/graphic/1899733
deleted file mode 100644
index 3adeb335..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1899733
+++ /dev/null
@@ -1,21 +0,0 @@
-
-Qemu 5.1.0-1 GPU passthrough - MacOS vm starts only if hdmi is attached
-
-Hi,
-I have a macOS 10.15.7 vm with GPU passthrough (NVIDIA GTX Titan Black), libvirt xml has path to vbios too.
-Qemu 5.1.0-1 with libvirt 6.5.0-2 are installed in manjaro architect 20.1.1 (two kernels tried: 5.4.67 LTS and 5.8.11 stable, no difference).
-I have two monitors, one with hdmi and one with vga inputs.
-Usually the gpu is connected to one monitor with hdmi, the other one with DVI (on gpu)-->vga adapter, so:
-1st monitor: hdmi-->hdmi
-2nd monitor: DVI-->vga adapter-->vga
-
-With this setup, launching "virsh start Catalina" has no problem.
-
-If I detach the hdmi cable from monitor 1, I cannot start qemu anymore: the 2nd monitor turns black, it doesn't seem it has "no-signal", but only a black screen with the power led blinking (usually a window on the monitor floats around with "no signal" displayed when there is no signal to monitor).
-I say "qemu doesn't start" because in /var/log/libvirt/qemu/Catalina.log there's no trace.
-
-Detaching hdmi works with qemu 4.2 and libvirt 5.10, so this could be related to qemu update.
-
-Apologize, I know there aren't much information here, if someone can guide me to test the issue I would be grateful.
-
-Thanks for your attention
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1904315 b/results/classifier/deepseek-2-tmp/output/graphic/1904315
deleted file mode 100644
index 1d90f556..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1904315
+++ /dev/null
@@ -1,24 +0,0 @@
-
-CTRL+ALT is ignored on gtk window (configured with gtk and sdl)
-
-I am building and using qemu on Windows 10 via git.
-Building for targeting windows, on debian.
-
-Since meson is introduced, my executable, qemu-system-x86_64.exe, tends to ignore hotkeys
-(like CTRL+ATL+G, CTRL+ALT+2)
-
-As far as I have been investigating the issue, I am suspicious that gtk and sdl might be incompatible.
-With configure --disable-sdl, my executable works fine.
-My application doesn't require sdl.
-
-Possibly due to link order, especially SDLmain, I guess.
-
-I suggest;
-- Clarify that gtk and sdl are incompatible.
-- Tweak built script or startup not to prevent gtk and sdl each other.
-
-Excuse me, the issue has not been reproduced at home yet. I met it at work.
-(My manager said it's fine to report issues by me at home)
-I will construct reproducible environment at home, if my further investigation would be required.
-
-Thanks.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1906185 b/results/classifier/deepseek-2-tmp/output/graphic/1906185
deleted file mode 100644
index 219bee63..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1906185
+++ /dev/null
@@ -1,32 +0,0 @@
-
-Guest display resolution cannot be changed when using certain graphics/interface combinations
-
-Guest display resolution cannot be changed with certain virtual graphics card (-vga) and interface (-display) combinations.
-
-For example, resolution changing doesn't work with the following QEMU start commands, it resets to the default resolution immediately:
-
-QXL with SDL interface:
-qemu-system-x86_64 -enable-kvm -m 6G -cpu host -smp 3 -cdrom ./linux/kubuntu-20.04-desktop-amd64.iso -boot d -vga qxl -soundhw hda -display sdl
-
-QXL with GTK interface:
-qemu-system-x86_64 -enable-kvm -m 6G -cpu host -smp 3 -cdrom ./linux/kubuntu-20.04-desktop-amd64.iso -boot d -vga qxl -soundhw hda -display gtk
-
-QXL with "remote" SPICE interface via unix socket:
-qemu-system-x86_64 -enable-kvm -m 6G -cpu host -smp 3 -cdrom ./linux/kubuntu-20.04-desktop-amd64.iso -boot d -soundhw hda -vga qxl -device virtio-serial-pci -device virtserialport,chardev=spicechannel0,name=com.redhat.spice.0 -chardev spicevmc,id=spicechannel0,name=vdagent -spice unix,addr=/tmp/vm_spice.socket,disable-ticketing
-
-for "remote" access:
-remote-viewer spice+unix:///tmp/vm_spice.socket
-
-
-
-Other tested combinations:
--- virtio + SDL (GL on): works!
--- virtio + GTK (GL on): does not work properly. The resolution is changed but window size is not so the guest screen will look like garbage.
--- vmware: The initial Kubuntu setup screen is visible but booting does not progress to the desktop
--- std + GTK: works!
--- std + SDL: works!
-
-
-QEMU version: 5.1.0
-Guest: Kubuntu 20.04 64-bit (live) with 5.4.0-26 kernel; may occur with other guests as well
-Host: Arch Linux, with KDE desktop
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1906948 b/results/classifier/deepseek-2-tmp/output/graphic/1906948
deleted file mode 100644
index 2f49664f..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1906948
+++ /dev/null
@@ -1,29 +0,0 @@
-
-Enabling OpenGL for GUI doesn't work on old laptop
-
-QEMU start command is:
-
-qemu-system-x86_64 -enable-kvm -m 2G -cpu host -smp 2 -cdrom ./linuxmint-20-mate-64bit.iso -boot d -vga virtio -soundhw hda -display gtk,gl=on
-
-
-and QEMU crashes immediately on startup and gives these error messages:
-
-
-qemu_gl_create_compile_shader: compile vertex error
-0:2(10): error: GLSL ES 3.00 is not supported. Supported versions are: 1.10, 1.20, and 1.00 ES
-
-qemu_gl_create_compile_shader: compile fragment error
-0:2(10): error: GLSL ES 3.00 is not supported. Supported versions are: 1.10, 1.20, and 1.00 ES
-
-qemu_gl_create_compile_shader: compile vertex error
-0:2(10): error: GLSL ES 3.00 is not supported. Supported versions are: 1.10, 1.20, and 1.00 ES
-
-qemu_gl_create_compile_shader: compile fragment error
-0:2(10): error: GLSL ES 3.00 is not supported. Supported versions are: 1.10, 1.20, and 1.00 ES
-
-
-If I remove "gl=on" it will boot. Does this just mean that this hardware is too old to run QEMU with OpenGL enabled in GUI, or is this a bug? 
-
-Host OS is Debian 10, computer is a Lenovo laptop with Core i5-520M CPU and its integrated Intel HD graphics GPU.
-
-QEMU version is 3.1.0 from Debian repositories.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1907061 b/results/classifier/deepseek-2-tmp/output/graphic/1907061
deleted file mode 100644
index 75ea4dc5..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1907061
+++ /dev/null
@@ -1,16 +0,0 @@
-
-qemu-system-x86_64 minimizing window causes keyboard input lag globally
-
-After qemu window is minimized, it causes keyboard lag on the host for all applications, pressed keys will be delayed and very laggy, typing to notepad or any other text extremely slowly appear on the screen, queue is slowly processed.
-If qemu window is open back to normal size, keyboard is back to normal, everything is back to normal and stable, this behavior i have been testing since several months of qemu releases, i am reporting a bit late here, not breaking but it seems important and everytime i accidently minimize qemu, i remember it later and take qemu window to normal size back always, i try never minimize it anymore.
-This problem does not occur if using -display none
-Guest OS doesn't matter for this behavior, result is always same
-I am using:
-qemu 5.1.0.0
-qemu-system-x86_64w.exe
-Windows 10 build 2004
-4K screen dpi scaling set to 150%
-
-If requested, i can record a video to see the problem clearly, but i think all information i give already clear now.
-
-Thanks for making quality software, hope all bugs fixed
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1907952 b/results/classifier/deepseek-2-tmp/output/graphic/1907952
deleted file mode 100644
index 9c39fdce..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1907952
+++ /dev/null
@@ -1,45 +0,0 @@
-
-qemu-system-aarch64: with "-display gtk" arrow keys are received as just ^[ on ttyAMA0
-
-I originally observed this on Debian packaged qemu 5.2 at
-https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976808
-
-Today I checked out the latest git source at
-Sun, 13 Dec 2020 19:21:09 +0900
-and configured the source as follows:
-
-./configure --prefix=/usr --sysconfdir=/etc --libexecdir=/usr/lib/qemu \
- --localstatedir=/var --disable-blobs --disable-strip --localstatedir=/var \
- --libdir=/usr/lib/aarch64-linux-gnu \ 
- --firmwarepath=/usr/share/qemu:/usr/share/seabios:/usr/lib/ipxe/qemu \ 
- --target-list=aarch64-softmmu,arm-softmmu --disable-werror \ 
- --disable-user  --enable-gtk --enable-vnc
-then executed "make" on an ARM64 (not an x86_64) host,
-running the latest Debian testing.
-
-I did the following commands on an arm64 host with the Debian Installer Alpha 3 at
-https://cdimage.debian.org/cdimage/bullseye_di_alpha3/arm64/iso-cd/debian-bullseye-DI-alpha3-arm64-netinst.iso
-
-#!/bin/sh
-
-ARCH=arm64
-IMAGE=`pwd`/qemu-disk-${ARCH}.qcow2
-CDROM=`pwd`/debian-bullseye-DI-alpha3-${ARCH}-netinst.iso
-rm -f $IMAGE
-qemu-img create -f qcow2 -o compat=1.1 -o lazy_refcounts=on -o preallocation=off $IMAGE 20G
-cd /var/tmp
-cp /usr/share/AAVMF/AAVMF_VARS.fd .
-$HOME/qemu-git/qemu/build/qemu-system-aarch64 \
-    -display gtk -enable-kvm -machine virt -cpu host -m 3072 -smp 2\
-    -net nic,model=virtio -net user -object rng-random,filename=/dev/urandom,id=rng0 \
-    -device virtio-rng-pci,rng=rng0,id=rng-device0 \
-    -drive if=virtio,file=${IMAGE},index=0,format=qcow2,discard=unmap,detect-zeroes=unmap,media=disk \
-    -drive if=virtio,file=${CDROM},index=1,format=raw,readonly=on,media=cdrom \
-    -drive if=pflash,format=raw,unit=0,file=/usr/share/AAVMF/AAVMF_CODE.fd,readonly=on \
-    -drive if=pflash,format=raw,unit=1,file=`pwd`/AAVMF_VARS.fd
-
-Then 4 arrow keys on the physical keyboard are received as just "^[".
-
-This symptom was not observed on qemu-system-x86_64.
-This symptom was not observed with virt-manager on my arm64 host, neither.
-This seems unique to -display gtk of qemu-system-aarch64.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1908266 b/results/classifier/deepseek-2-tmp/output/graphic/1908266
deleted file mode 100644
index 31c420dd..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1908266
+++ /dev/null
@@ -1,4 +0,0 @@
-
-spice unnecessary forces nographic
-
-When spice is enabled, qemu does not give the graphical window. It should not imply -nographic but only -display none.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1910696 b/results/classifier/deepseek-2-tmp/output/graphic/1910696
deleted file mode 100644
index f937374b..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1910696
+++ /dev/null
@@ -1,10 +0,0 @@
-
-Qemu fails to start with error " There is no option group 'spice'"
-
-After upgrade from 5.1.0 to 5.2.0, qemu fails on start with error:
-`
-/usr/bin/qemu-system-x86_64 -S -name trinti -uuid f8ad2ff6-8808-4f42-8f0b-9e23acd20f84 -daemonize -cpu host -nographic -serial chardev:console -nodefaults -no-reboot -no-user-config -sandbox on,obsolete=deny,elevateprivileges=allow,spawn=deny,resourcecontrol=deny -readconfig /var/log/lxd/trinti/qemu.conf -pidfile /var/log/lxd/trinti/qemu.pid -D /var/log/lxd/trinti/qemu.log -chroot /var/lib/lxd/virtual-machines/trinti -smbios type=2,manufacturer=Canonical Ltd.,product=LXD -runas nobody: 
-qemu-system-x86_64:/var/log/lxd/trinti/qemu.conf:27: There is no option group 'spice'
-qemu-system-x86_64: -readconfig /var/log/lxd/trinti/qemu.conf: read config /var/log/lxd/trinti/qemu.conf: Invalid argument
-`
-Bisected to first bad commit: https://github.com/qemu/qemu/commit/cbe5fa11789035c43fd2108ac6f45848954954b5
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1916 b/results/classifier/deepseek-2-tmp/output/graphic/1916
deleted file mode 100644
index 296497d5..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1916
+++ /dev/null
@@ -1,29 +0,0 @@
-
-qemu-fixed-text-console.device not found error when using display set to anything but SDL
-Description of problem:
-When attempting to launch QEmu from the command line using any display option aside from `sdl`, QEmu fails to launch with this error message:
-
-```plaintext
-Unexpected error in object_property_find_err() at ../qom/object.c:1314:
-qemu: Property 'qemu-fixed-text-console.device' not found
-Aborted
-```
-
-This error is almost nonexistent when searching online. There is a mention of it in this chain of messages on the mailing list from about a week ago, but it doesn't seem to discuss any kind of way to remedy it. Link: https://www.mail-archive.com/qemu-devel@nongnu.org/msg988630.html
-
-I came across this issue because I was attempting to launch QEmu in other display modes, because for some reason if I launch with the `-display sdl` option, QEmu successfully starts up but then the display is black the majority of the time with some very brief flickers of the OS, and mouse/keyboard input don't seem to be correctly handled, making it unusable. So when trying to see if another display configuration could help me be able to resolve the black screen issue, I learned that I can't even launch with any other configuration due to the fixed text console not being found.
-
-I have been using these simple arguments for running the configure script:
-
-```plaintext
-../configure --enable-debug --target-list=x86_64-softmmu
-```
-
-I tried using the configure flags `--enable-gtk` and `--enable-sdl` to see if they made any difference, but it seemed like they did not (neither the black screen issue or the fixed text console device error changed) so I just started leaving them off.
-Steps to reproduce:
-1. Run configure script
-2. Run make to build QEmu
-3. Launch QEmu using `-display gtk` or with no `-display` option specified at all (also tried: `./qemu-system-x86_64 -m 6G -smp 2 -hda ../../vdisk1.qcow2`) and the error occurred.
-4. Error occurs
-Additional information:
-I am new to QEmu and am trying to use it as part of a college project, so if anyone wants to respond, please let me know if I can give any additional information at all that could help.
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1922430 b/results/classifier/deepseek-2-tmp/output/graphic/1922430
deleted file mode 100644
index 461175cc..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1922430
+++ /dev/null
@@ -1,35 +0,0 @@
-
-3d accel does not take care of 1280x960 setting
-
-openSuse 15.2
-kde plasma 5.21.3, frameworks 5.80.0
-libvirt 7.0.0
-qemu 5.2.0
-virgl renderer 0.8.2
-
-here is my invocation
-
-qemu-kvm -enable-kvm \
--m 2048 -smp 2 -cpu host \
--device virtio-vga,virgl=on -display gtk,gl=on \
--device usb-ehci \
--device usb-kbd \
--device usb-mouse \
--device usb-tablet \
--device ich9-intel-hda \
--device hda-duplex,audiodev=snd0 \
--audiodev pa,id=snd0 \
--device usb-host,vendorid=0x046d,productid=0x08e5 \
--boot menu=on \
--nic bridge \
-~/QEMU_VM/android_x86_7.1-r5.img \
-
-in the kernel command there is "vga=1280x960"
-
-with "-device qxl" no problem. I get immediately a  window of size 1280x960.
-
-with "-device virtio-vga,virgl=on -display gtk,gl=on"
-
-i get a tiny window.
-
-i must uncheck "zoom to fit" to get a window of size 1280x960.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1924914 b/results/classifier/deepseek-2-tmp/output/graphic/1924914
deleted file mode 100644
index c42480da..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1924914
+++ /dev/null
@@ -1,14 +0,0 @@
-
-Running sway in a QEMU VM results in a GPU hang of the guest (virtio-gpu driver)
-
-System is Arch Linux (guest and host OS).
-
-Problem:
-
-Basically, when using sway on a guest and running certain applications via Xwayland (on the guest), the GUI will freeze and won't be usable anymore, I can still ssh to the guest and run commands.
-
-This is the command I use to run my guest:
-
-qemu-system-x86_64 -enable-kvm -cdrom ~/Downloads/linux/archlinux/archlinux-2021.04.01-x86_64.iso -m 4G -vga virtio -nic user,hostfwd=tcp::10022-:22
-
-This doesn't happen when I use X with i3-wm.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/1926952 b/results/classifier/deepseek-2-tmp/output/graphic/1926952
deleted file mode 100644
index ae55f6ba..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/1926952
+++ /dev/null
@@ -1,37 +0,0 @@
-
-SPICE support broken with 6.0
-
-Using latest relase 6.0.0 while using Intel GVT-G DMA-BUF and SPICE for usb redirection Qemu won't start:
-
-qemu-system-x86_64: The console requires display DMABUF support.
-
-However just patching ui/console.c:
-
-if (flags & GRAPHIC_FLAGS_DMABUF &&
-        !displaychangelistener_has_dmabuf(dcl)) {
-        error_setg(errp, "The console requires display DMABUF support.");
-        return false;
-}
-
-to always return true for dmabuf part works just fine:
-
-if (flags & GRAPHIC_FLAGS_DMABUF &&
-        !displaychangelistener_has_dmabuf(dcl)) {
-        error_setg(errp, "The console requires display DMABUF support.");
-        return true;
-}
-
-This behavior wasn't in qemu 5.x version.
-
-To reproduce this bug need to use:
-
-/usr/bin/qemu-system-x86_64 \
--machine q35 \
--enable-kvm \
--no-user-config \
--nodefaults \
--no-hpet \
--display gtk,gl=on \
--device pcie-root-port,port=0x0,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x1 \
--device vfio-pci,id=hostdev2,driver=vfio-pci-nohotplug,romfile=/sys/devices/pci0000:00/0000:00:02.0/gvt_firmware,sysfsdev=/sys/bus/mdev/devices/1ae40c36-b180-4af0-8fab-c27de21f597d,x-igd-opregion=on,ramfb=on,display=on,xres=1920,yres=1080,bus=pcie.0,multifunction=on,addr=0x2 \
--spice port=5900,addr=127.0.0.1,disable-ticketing=on
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2002 b/results/classifier/deepseek-2-tmp/output/graphic/2002
deleted file mode 100644
index 9d524757..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2002
+++ /dev/null
@@ -1,4 +0,0 @@
-
-Need to be able to set WM_CLASS under X11
-Additional information:
-
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2052 b/results/classifier/deepseek-2-tmp/output/graphic/2052
deleted file mode 100644
index 8db3ec8d..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2052
+++ /dev/null
@@ -1,2 +0,0 @@
-
-sdl window partially catches mouse cursor
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2056 b/results/classifier/deepseek-2-tmp/output/graphic/2056
deleted file mode 100644
index b046d17f..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2056
+++ /dev/null
@@ -1,15 +0,0 @@
-
-macOS Cocoa title bar covers top of VM screen
-Description of problem:
-When using the Cocoa interface the title bar covers the top part of the VM screen. In Windows XP, using show-cursor=on and USB tablet (-usb -device usb-tablet,bus=usb-bus.0), the mouse cursor seems to be off by the height of the title bar; to click on a target the mouse cursor has to be below the target by about the height of the top bar.
-Steps to reproduce:
-1. Run Qemu using the Cocoa-interface (-display cocoa)
-Additional information:
-The problem exists in both Qemu 8.2.0 (compiled from source) as well as in the MacPorts version (version 8.0.5). Further testing shows the same problem in versions 6.2.0, 7.0.0, and 7.1.0. This problem did not exist in previous versions of macOS.
-
-A screenshot is enclosed:
-![Screenshot_2023-12-24_at_20.54.33](/uploads/c240185856ba412c71250d0c424345c0/Screenshot_2023-12-24_at_20.54.33.png)
-
-For similar reports, see: https://www.emaculation.com/forum/viewtopic.php?p=77350#p77350 and https://github.com/phil-opp/blog_os/issues/1249#issuecomment-1825933581 and https://68kmla.org/bb/index.php?threads/a-self-contained-qemu-based-a-ux-system-for-macos.45106/post-504970
-
-The problem exists on both Apple Silicon and Intel hardware.
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2067 b/results/classifier/deepseek-2-tmp/output/graphic/2067
deleted file mode 100644
index 20cf71b2..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2067
+++ /dev/null
@@ -1,2 +0,0 @@
-
-screen unblanking issue with debian 12 gui
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2068 b/results/classifier/deepseek-2-tmp/output/graphic/2068
deleted file mode 100644
index 61dd548c..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2068
+++ /dev/null
@@ -1,16 +0,0 @@
-
-Regression: 8.1.3 -> 8.2.0 breaks virtio vga driver
-Description of problem:
-I have a number of emulated arch linuxes using the same x11/kde configuration. After updating from 8.1.3 to 8.2.0, they all broke in the following way:
-- screen tearing/artifacts seen from bios up until sddm
-- sddm is possibly affected
-- kde/x11 has so many artifacts that its unusable. if i attempt to write in a console window, i can only see parts of what ive written if i attempt to gently resize the bottom of the window. clicking the menu item will only render the menu 1/6 times and only partly. however if I click where I remember the shutdown button to be, the system shuts down immediately, so thi seems to be purely a graphics issue.
-- starting with -vga qxl fixes all issues.
-Steps to reproduce:
-1. make new qemu, install arch/kde
-2. boot said qemu with -vga virtio option
-3. observe issue from the moment it boots
-Additional information:
-Using nVidia card and drivers on host.
-
-Removing x86-video-vesa on the guest system seemed to significant improve performance. There are still many artifacts but its almost usable with this driver removed.
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2085 b/results/classifier/deepseek-2-tmp/output/graphic/2085
deleted file mode 100644
index b8e543e3..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2085
+++ /dev/null
@@ -1,23 +0,0 @@
-
-screen doesn't update fully wth spice + virtio-vga graphics
-Description of problem:
-When using spice graphics with virtio-vga, display updates and missing and/or delayed making interaction unusable
-Steps to reproduce:
-Create a VM with spice graphics and virtio-vga with earlier mentioned command line
-
-Open ``remote-viewer spice://localhost:5900``
-
-Boot the Fedora 39 server network installer CDROM ISO
-
-When Ananconda starts, select 'continue' at the first language choice screen
-
-Select 'Root Account' config option
-
-Toggle between "Disable root account" and "Enable root account" options
-
-Observe when the password entry box is shown/hidden, the screen does not redraw correctly
-Additional information:
-See also
-
-https://bugzilla.redhat.com/show_bug.cgi?id=2256884
-https://bbs.archlinux.org/viewtopic.php?id=291606
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2116 b/results/classifier/deepseek-2-tmp/output/graphic/2116
deleted file mode 100644
index d04cf8a8..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2116
+++ /dev/null
@@ -1,29 +0,0 @@
-
-[CRASH] OpenGL acceleration except gtk: bad interaction between NVIDIA usermode opengl libraries and QEMU seccomp -sandbox on,spawn=deny, crashes immediately on startup with Bad system call
-Description of problem:
-When running any of the above command lines, QEMU crashes with Bad system call (core dumped). Not exclusive to spice; it seems this is caused by QEMU forking during OpenGL initialization after seccomp takes effect.
-Steps to reproduce:
-1. Run the above commandline
-2. Notice a Bad system call (core dumped)
-Additional information:
-This crash only happens if spawn=deny is set, resourcecontrol/obsolete/elevateprivileges don't cause crashes.
-
-The crash happens around the same time as an audit event is generated in dmesg: `audit: type=1326 audit(1705775880.776:14): auid=MYUSERID uid=MYUID gid=MYGID ses=REDACTED pid=REDACTED comm="qemu-system-x86" exe="/usr/bin/qemu-system-x86_64" sig=31 arch=c000003e syscall=56 compat=0 ip=REDACTED code=REDACTED`
-
-`ausyscall c000003e 56` tells me it's `clone` which (iirc) is the syscall used by glibc to implement fork() (I might be wrong about glibc part)
-
-Suggested solution: move seccomp activation until just before guest code starts executing? make frontends (ie -display gtk/sdl/whatever, including -spice) initialize before seccomp?
-
-Workaround: `chmod -x /bin/nvidia-modprobe` if not using the NVIDIA gpu or use this wrapper script (untested, not enterprise-ready, I am not responsible if unexpected things happen):
-- rename /bin/qemu-system-x86_64 to qemu-system-x86_64.real
-- put this in /bin/qemu-system-x86_64 and chmod +x it
-```sh
-#!/usr/bin/env sh
-chmod -x /bin/nvidia-modprobe
-qemu-system-x86_64.real $@ & disown
-sleep 10 # excessive but maybe safer?
-chmod +x /bin/nvidia-modprobe
-```
-Also, you can use -display gtk,gl=on instead, or (unknown security implications) remove spawn=deny from -sandbox args
-
-original bug report was https://gitlab.com/libvirt/libvirt/-/issues/585 but I realized this was more of a qemu issue than a libvirt one
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2172 b/results/classifier/deepseek-2-tmp/output/graphic/2172
deleted file mode 100644
index 19b8d097..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2172
+++ /dev/null
@@ -1,2 +0,0 @@
-
-Error "cannot enable SPICE if pixman is not available"
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2188 b/results/classifier/deepseek-2-tmp/output/graphic/2188
deleted file mode 100644
index e2808bd0..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2188
+++ /dev/null
@@ -1,11 +0,0 @@
-
-virtio_gpu_gl_update_cursor_data() ignores the cursor resource's pixel format
-Description of problem:
-The function virtio_gpu_gl_update_cursor_data() ignores the pixel format of the resource it's reading from. It literally uses memcpy() to copy the pointer data. This works just fins if both the guest OS and the display backend use the same pixel format. 
-
-The SDL backend seems to use a different pixel format to the GTK display backend. So, you'll get the correct colours in one, but not the other.
-Steps to reproduce:
-1. Run a VM using Virtio GPU using the GTK backend. Set the guest OS' mouse pointer to one that's red instead of white, and note the mouse pointer's actual colour
-2. Now run the same VM using the SDL display backend. Check the colour of the mouse pointer (that should be red)
-
-NOTE: The choice of guest OS shouldn't matter.
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2196 b/results/classifier/deepseek-2-tmp/output/graphic/2196
deleted file mode 100644
index 4363bdfb..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2196
+++ /dev/null
@@ -1,2 +0,0 @@
-
-Missing support for video hardware accelerate support in virgl (virtio-gpu)
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2200 b/results/classifier/deepseek-2-tmp/output/graphic/2200
deleted file mode 100644
index 3c1b876f..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2200
+++ /dev/null
@@ -1,10 +0,0 @@
-
-QEMU OpenGL of SDL and GTK not working properly on Windows hosts
-Description of problem:
-QEMU OpenGL of SDL and GTK not working properly on Windows hosts.
-Steps to reproduce:
-1.
-2.
-3.
-Additional information:
-
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2201 b/results/classifier/deepseek-2-tmp/output/graphic/2201
deleted file mode 100644
index cbf21002..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2201
+++ /dev/null
@@ -1,12 +0,0 @@
-
-Windows 11 Guests ExtendedDesktopSize Not Working
-Description of problem:
-Windows 11 VM with the latest virtio-win drivers installed (v0.1.240) does not respond to remote resize requests.
-Steps to reproduce:
-1. Create a Windows 11 VM with virtio-win drivers installed and virtio video enabled.
-2. Create a VNC session with resizeSession enabled.
-3. Try resizing the window.
-Additional information:
-The resolution can be resized within the VM itself (i.e., from display settings), just doesn't automatically resize when the viewing window changes. Other VMs (including Windows 10) created and viewed within the same setup do change with the window resize.
-
-The Chrome console log has a number of `Server did not accept resize request: Unknown reason` errors in it.
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2225 b/results/classifier/deepseek-2-tmp/output/graphic/2225
deleted file mode 100644
index 3043a4af..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2225
+++ /dev/null
@@ -1,12 +0,0 @@
-
-Mouse capture doesn't actually capture (GTK)
-Description of problem:
-The mouse is never actually captured by the window, you can always move it off screen, and because the guest OS has no awareness of the absolute mouse position there are many situations where you can't actually click something in the guest OS because the host mouse cursor is out of the window so clicking clicks on another program's window. It's unusable.
-
-It's clear that the problem is that the cursor isn't actually captured, if it ever was then the problem wouldn't occur. When the mouse is "uncaptured" we see the host cursor at all times and the guest cursor simply doesn't move, but when it's """captured""" the guest cursor still moves freely, it's just hidden while hovering the entire window (and not just the guest rectangle but really the whole thing) and the host cursor moves too at its own pace.
-
-It happens with `-display gtk` but not `-display sdl`.
-Steps to reproduce:
-1. Launch windowed guest
-2. Click on window
-3. Try to move mouse out of the window
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2252 b/results/classifier/deepseek-2-tmp/output/graphic/2252
deleted file mode 100644
index f66519c0..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2252
+++ /dev/null
@@ -1,12 +0,0 @@
-
-Poor VGA graphics when passing through a graphics card to a BIOS guest using the x-vga flag
-Description of problem:
-When passing through a GPU (in my case an Nvidia RTX 2070 Super) to a guest with BIOS firmware (using the x-vga flag to get a display out in BIOS mode), the VGA graphics used before an operating system loads proper graphics drivers seems to perform very poorly. Some symptoms of this are: GRUB and Windows Boot Manager are invisible, only showing a black screen (not sure if it affects all bootloaders) Windows 7 falls back to the more basic Vista boot animation during startup instead of the proper Starting Windows + orbs animation Windows 7 while using VGA graphics looks very low quality, with a pixelated look and a low color depth (attached below in additional information) Windows 10's setup just shows a black screen and fails to even boot. It seems to just restart after a bit (with any potential errors being invisible) Once graphics drivers are loaded inside Windows 7 or Linux in the guest, everything works fine. Seems like it's a firmware bug maybe?
-
-I've tested, and QEMU version 8.1 seems to be the last version without this bug, as 8.2 and up all have this issue. I'm not sure if this affects all graphics cards, as I've only tested this on an RTX 2070 super.
-Steps to reproduce:
-1. Create a guest with SeaBIOS firmware
-2. Pass through a graphics card using -vfio-pci
-3. Enable the x-vga flag
-Additional information:
-![notsogreatlookingwindows7](/uploads/ab6f7806f43dd0714e60b824cadec916/notsogreatlookingwindows7.png)
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/226 b/results/classifier/deepseek-2-tmp/output/graphic/226
deleted file mode 100644
index c93bd708..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/226
+++ /dev/null
@@ -1,2 +0,0 @@
-
-host window size does not change when guest video screen size changes while moving host window
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2282 b/results/classifier/deepseek-2-tmp/output/graphic/2282
deleted file mode 100644
index b66b3830..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2282
+++ /dev/null
@@ -1,2 +0,0 @@
-
-Corrupted output when using Intel Arc GPU with qemu+spice+virgl in headed mode
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2314 b/results/classifier/deepseek-2-tmp/output/graphic/2314
deleted file mode 100644
index 022748a5..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2314
+++ /dev/null
@@ -1,17 +0,0 @@
-
-Building QEMU 9.0.0 fails on MacOS 10.15.7 (error: initializing 'NSEdgeInsets' (aka 'struct NSEdgeInsets') with an expression of incompatible type 'id')
-Description of problem:
-QEMU fails to compile using Homebrew on OS X 10.15.7:
-```
-../ui/cocoa.m:542:18: error: initializing 'NSEdgeInsets' (aka 'struct NSEdgeInsets') with an expression of incompatible type 'id'
-    NSEdgeInsets insets = [[[self window] screen] safeAreaInsets];
-                 ^        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-1 error generated.
-```
-Steps to reproduce:
-1. Compile QEMU on OS X 10.15.7 using Homebrew
-2.
-3.
-Additional information:
-Build log
-[02.make.zip](/uploads/dfb618b86984ed6cf699d94bf9d6c9e1/02.make.zip)
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2315 b/results/classifier/deepseek-2-tmp/output/graphic/2315
deleted file mode 100644
index b49395de..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2315
+++ /dev/null
@@ -1,13 +0,0 @@
-
-Mouse cursor is flipped / inverted / upside-down with virtio-gpu in some Wayland compositors
-Description of problem:
-The mouse cursor is flipped:
-Steps to reproduce:
-1. Install a Linux system with a 6.8.x kernel inside the virtual machine
-2. Install sway / wayfire / hyprland, or kwin 6.0.4.1
-3. See the mouse cursor
-Additional information:
-The [kwin fix](https://invent.kde.org/plasma/kwin/-/commit/a31561c392adf5abcda0284e8049fafcb3701585) just makes use of dumb buffers instead of dmabuf.
-
-The mouse cursor should be pointing to the maximizing button at the top-right corner:
-![Screenshot](/uploads/f1c3db2129955159e9ce765dd29ae9eb/a.png)
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/232 b/results/classifier/deepseek-2-tmp/output/graphic/232
deleted file mode 100644
index 08c3d66e..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/232
+++ /dev/null
@@ -1,2 +0,0 @@
-
-I/O write make QXL abort in qxl_set_mode()
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2327 b/results/classifier/deepseek-2-tmp/output/graphic/2327
deleted file mode 100644
index 89e4aec2..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2327
+++ /dev/null
@@ -1,62 +0,0 @@
-
-negative shift exponent in cirrus_colorexpand_pattern_transp_0_24()
-Description of problem:
-My fuzzer detected a runtime error in cirrus_colorexpand_pattern_transp_0_24()
-
-The stack trace is:
-
-```
-../hw/display/cirrus_vga_rop2.h:216:23: runtime error: shift exponent -2 is negative
-    #0 0x5589a028c89a in cirrus_colorexpand_pattern_transp_0_24 hw/display/cirrus_vga_rop2.h:216:23
-    #1 0x5589a031e239 in cirrus_bitblt_common_patterncopy hw/display/cirrus_vga.c:689:5
-    #2 0x5589a032735d in cirrus_bitblt_cputovideo_next hw/display/cirrus_vga.c:820:13
-    #3 0x5589a032cde9 in cirrus_linear_write hw/display/cirrus_vga.c:2365:13
-    #4 0x5589a2982823 in memory_region_write_accessor system/memory.c:497:5
-    #5 0x5589a2981f05 in access_with_adjusted_size system/memory.c:573:18
-    #6 0x5589a297fe69 in memory_region_dispatch_write system/memory.c:1521:16
-    #7 0x5589a2a2193e in flatview_write_continue_step system/physmem.c:2749:18
-    #8 0x5589a2a211d4 in flatview_write_continue system/physmem.c:2779:19
-    #9 0x5589a29f9cfb in flatview_write system/physmem.c:2810:12
-    #10 0x5589a29f97c8 in address_space_write system/physmem.c:2930:18
-...
-```
-Steps to reproduce:
-Arguments:\
-export QEMU_ARGS="-display none -machine accel=qtest, -m 512M -machine\
-q35 -nodefaults -device cirrus-vga -display vnc=localhost:99 -L ../pc-bios/"\
-The base addresses of memory regions:
-
-* cirrus-io, 0x3b0
-* cirrus-low-memory, 0xa0000
-* cirrus-linear-io, 0xe0000000
-* cirrus-bitblt-mmio, 0xe1000000
-* cirrus-mmio, 0xe2000000
-
-Reproducer:
-
-```
-writeb 0xe2000108 0x642a8d58
-writeb 0xe2000117 0x335af91c
-writeb 0xe2000118 0x765861ed
-writeb 0xe200010d 0x7c3af934
-writeb 0xe2000140 0x33f13baf
-clock_step
-writeb 0xe01f0e68 0x6ea3696c
-writeb 0xe13bc720 0x11bb09ba
-readb 0xe2000133
-writeb 0xe033629b 0x80f19dd
-writeb 0xe134bba7 0x1eb198f9
-readb 0xe2000680
-writeb 0xe2000b84 0x3f0591fc
-clock_step
-writeb 0xe003469e 0xdbd627e
-writeb 0xe114f2bc 0x41adfe48
-readb 0xe2000cde
-readb 0xb269d
-writeb 0xe1368066 0x3c9ab77
-readb 0xe12a7fe1
-writeb 0xe0191988 0x7e18b0d1
-EOF
-```
-Additional information:
-Ack: Chuhong Yuan (hslester96@gmail.com)
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2338 b/results/classifier/deepseek-2-tmp/output/graphic/2338
deleted file mode 100644
index 04947790..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2338
+++ /dev/null
@@ -1,2 +0,0 @@
-
-(Feature request) Implement the "grab-on-hover=on" CLI option on the SDL frontend
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2348 b/results/classifier/deepseek-2-tmp/output/graphic/2348
deleted file mode 100644
index 74034c7e..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2348
+++ /dev/null
@@ -1,8 +0,0 @@
-
-Grabbing is not possible with menu-mode disabled
-Description of problem:
-When starting a Qemu and bringing it into Focus, I expected Ctrl + Alt + g to enable Input Grab mode. This does not occur when the menu-bar is hidden. It does occur when the menu-bar is visible.
-Steps to reproduce:
-1. Open a QEMU instance in a Arch / KDE host (not fullscreen)
-2. Focus the instance and attempt to enable Input Grabbing (Ctrl + Alt + G)
-3. Observe that Input Grab Mode is not toggled
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/237164 b/results/classifier/deepseek-2-tmp/output/graphic/237164
deleted file mode 100644
index e9a822c8..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/237164
+++ /dev/null
@@ -1,7 +0,0 @@
-
-kvm needs to correctly simulate a proper monitor
-
-Binary package hint: xorg
-
-With xserver-xor-video-cirrus 1.2.1, there should be no need to require special handling for kvm in dexconf any longer.
-See also: bug 193323.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2387 b/results/classifier/deepseek-2-tmp/output/graphic/2387
deleted file mode 100644
index 95bffe7e..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2387
+++ /dev/null
@@ -1,12 +0,0 @@
-
-Segmentation fault on booting from ISO when using GTK display with OpenGL enabled
-Description of problem:
-When trying to boot from the ISO mounted in the `-cdrom` argument, using a GTK display with OpenGL enabled gives a segmentation fault error. If using SDL instead, the whole application kinda freezes most of the times. I managed to get it working once, but I don't know how or why, seemed completely random. After installing it, I can boot from the disk normally with no errors.
-Steps to reproduce:
-1. Install QEMU for MSYS2 / UCRT64 as described [here](https://www.qemu.org/download/#windows)
-2. Download ISO from EndeavourOS website
-3. Run `qemu-img create -f qcow2 EndeavourOS.qcow2 64G` to create a disk file
-4. Run the script as described above in a `.sh` file
-5. See error
-Additional information:
-I have multiple VMs, included but not limited to Manjaro, Pop!\_OS and Debian, none of them gives this specific error. I also usually avoid SDL because I had multiple issues with the application window completely freezing in the past with "Not responding", and that does not happen with GTK.
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2391 b/results/classifier/deepseek-2-tmp/output/graphic/2391
deleted file mode 100644
index 46297067..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2391
+++ /dev/null
@@ -1,17 +0,0 @@
-
-virglrenderer related -device help failure
-Description of problem:
-When QEMU is compiled against a recent `virglrenderer` version, running the above command fails like this:
-```
-$ qemu-system-x86_64 -device virtio-vga-gl,help
-qemu-system-x86_64: -device virtio-vga-gl,help: failed to open module: /usr/bin/../lib/qemu/hw-display-virtio-gpu-gl.so: undefined symbol: qemu_egl_display
-```
-Steps to reproduce:
-1. build QEMU against latest `virglrenderer` (1.0.1)
-2. run the above command
-Additional information:
-The cause appears to be related to e8a2db94 cc @marcandre.lureau-rh
-
-Arch only recently updated to latest `virglrenderer` which has exposed the issue.
-
-Note that the device seems to function correctly in normal usage when combined with -display e.g. `-device virtio-vga-gl -display gtk,gl=on`
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2406 b/results/classifier/deepseek-2-tmp/output/graphic/2406
deleted file mode 100644
index a9f8d0bf..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2406
+++ /dev/null
@@ -1,8 +0,0 @@
-
-SDL UI on KMSDRM Frontend flips qemu-consoles
-Description of problem:
-If I launch qemu on the kms/drm console (without X11 or Wayland), the screen flips automatically between all qemu-consoles. The first (500?) milliseconds, there is the maschine output (boot messages), than the next (200?) milliseconds there is the monitor0 console, the next milliseconds, the serial0 console, and than the parallel0 console. And again from beginning (maschine, monitor0, serial0, parallel0, ... maschine, monitor0, serial0, parallel0, ...) - I dont press any key.
-
-If I disable monitor0, serial0, parallel0, all is fine, except one thing: I cannot issue a command on monitor0, because its disabled ;).
-Steps to reproduce:
-1. Start qemu without X11 and without wayland on the KMSDRM console.
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2407 b/results/classifier/deepseek-2-tmp/output/graphic/2407
deleted file mode 100644
index f6eaa887..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2407
+++ /dev/null
@@ -1,54 +0,0 @@
-
-"code should not be reached" in ati_2d_blt()
-Description of problem:
-My fuzzer detected a "code should not be reached" bug in ati_2d_blt()
-
-The stack trace is:
-
-```
-ERROR:include/qemu/bswap.h:418:stn_he_p: code should not be reached
-Bail out! ERROR:include/qemu/bswap.h:418:stn_he_p: code should not be reached
-==69534== ERROR: libFuzzer: deadly signal
-    #0 0x559e65667f5e in __sanitizer_print_stack_trace llvm-project-15.0.0.src/compiler-rt/lib/asan/asan_stack.cpp:87:3
-    #1 0x559e655a73bc in fuzzer::PrintStackTrace() llvm-project-15.0.0.src/compiler-rt/lib/fuzzer/FuzzerUtil.cpp:210:38
-    #2 0x559e65585a66 in fuzzer::Fuzzer::CrashCallback() (.part.0) llvm-project-15.0.0.src/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:236:18
-    #3 0x559e65585b2b in fuzzer::Fuzzer::CrashCallback() llvm-project-15.0.0.src/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:208:1
-    #4 0x559e65585b2b in fuzzer::Fuzzer::StaticCrashSignalCallback() llvm-project-15.0.0.src/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:207:19
-    #5 0x7fa8835e351f  (/lib/x86_64-linux-gnu/libc.so.6+0x4251f) (BuildId: c289da5071a3399de893d2af81d6a30c62646e1e)
-    #6 0x7fa8836379fb in __pthread_kill_implementation nptl/pthread_kill.c:43:17
-    #7 0x7fa8836379fb in __pthread_kill_internal nptl/pthread_kill.c:78:10
-    #8 0x7fa8836379fb in pthread_kill nptl/pthread_kill.c:89:10
-    #9 0x7fa8835e3475 in gsignal signal/../sysdeps/posix/raise.c:26:13
-    #10 0x7fa8835c97f2 in abort stdlib/abort.c:79:7
-    #11 0x7fa8848e5b56  (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x1eb56) (BuildId: c74e800dfd5f72649d673b44292f4a817e45150b)
-    #12 0x7fa88493f70e in g_assertion_message_expr (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x7870e) (BuildId: c74e800dfd5f72649d673b44292f4a817e45150b)
-    #13 0x559e65fc7d70 in stn_he_p include/qemu/bswap.h:418:1
-    #14 0x559e65fc55dc in ati_2d_blt hw/display/ati_2d.c:224:21
-    #15 0x559e65faccff in ati_mm_write hw/display/ati.c:857:9
-    #16 0x559e685b8363 in memory_region_write_accessor system/memory.c:497:5
-    #17 0x559e685b7a45 in access_with_adjusted_size system/memory.c:573:18
-    #18 0x559e685b59a9 in memory_region_dispatch_write system/memory.c:1521:16
-    #19 0x559e6865938e in flatview_write_continue_step system/physmem.c:2757:18
-    #20 0x559e68658c24 in flatview_write_continue system/physmem.c:2787:19
-    #21 0x559e6863024b in flatview_write system/physmem.c:2818:12
-    #22 0x559e6862fd18 in address_space_write system/physmem.c:2938:18
-...
-```
-Steps to reproduce:
-Arguments: `export QEMU_ARGS="-machine q35 -nodefaults -device ati-vga,romfile=\"\" -display vnc=localhost:99 -L ../pc-bios/"`
-
-The base addresses of memory regions:
-
-ati.mmregs: 0xe1000000
-
-Reproducer:
-
-```
-writew 0xe100146c 0x44e4c5c1
-writeb 0xe10016c0 0x773b93cf
-writeb 0xe10016e4 0x2beb6e13
-writel 0xe100143c 0x118b71f6
-EOF
-```
-Additional information:
-Ack: Chuhong Yuan (hslester96@gmail.com)
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2411 b/results/classifier/deepseek-2-tmp/output/graphic/2411
deleted file mode 100644
index 9fbfae4e..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2411
+++ /dev/null
@@ -1,12 +0,0 @@
-
-[SPICE] How to make SPICE work with GVT-g + DMA-BUF + egl-headless ?
-Description of problem:
-I try to use GVT-g + DMA-BUF in PVE , vGPU display output can be displayed normally on noVNC, 
-
-but when I try use SPICE, VM would not boot, come up with error: kvm: **The console requires display DMABUF support**.
-Steps to reproduce:
-1. Create a windows virtual machine
-2. Manually add args to the conf file, add the mdev device of GVT-g.
-3. Starting the Virtual Machine
-
-#
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2418 b/results/classifier/deepseek-2-tmp/output/graphic/2418
deleted file mode 100644
index 0a720593..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2418
+++ /dev/null
@@ -1,13 +0,0 @@
-
-[Gfxstream BUG]
-Description of problem:
-I tried to test gfxstream with qemu,I build qemu-9.0.1 with --enable-rutabaga-gfx flag,but after I have compiled and try to boot my Virtual Devices,it crashed and told me with "invalid rutabaga build parameters: gfxstream feature not enabled"
-
-![图片](/uploads/8a979b0808aee2dc173e648d67a46a05/图片.png){width=1276 height=99}
-Steps to reproduce:
-1.Compile the qemu with kvm,vhost,rutabaga_gfxstream,virgl support
-2.run the virtual machine with my command
-
-But I found an interesting thing:If I build and install AEMU&Gfxstream at /usr in place of /usr/local,I could boot Virtual Machine normally😂 
-
-Could developers solve the problems?Thanks!
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2425 b/results/classifier/deepseek-2-tmp/output/graphic/2425
deleted file mode 100644
index 889c0fb7..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2425
+++ /dev/null
@@ -1,8 +0,0 @@
-
-Add support for the 1366x768  resolution to the -vga std output
-Additional information:
-There is a Debian [issue](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700055) about it back from 2013. The is also a 2024 thread [thread](https://lists.nongnu.org/archive/html/qemu-discuss/2024-07/msg00003.html) about it on the `qemu-user` mailing list.
-
-I failed to make it a feature reqeust by keeping the template text  
-`/label ~"kind::Feature Request"`  
-at the end of the message: *Gitlab* removes it automatically.
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2443 b/results/classifier/deepseek-2-tmp/output/graphic/2443
deleted file mode 100644
index b20659b9..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2443
+++ /dev/null
@@ -1,19 +0,0 @@
-
-virtio-gpu-gl: "opengl is not available" message is too vague and doesn't suggest how to fix the problem
-Description of problem:
-I finally compiled qemu for Apple Silicon M2 Pro with opengl enabled and virtglrenderer enabled thanks to instruction from homebrew formula,
-but I did it without homebrew nor macports just manually compiling necessary libraries.
-Qemu was compiled succesfully with flags:
-````
-./configure --target-list=aarch64-softmmu,x86_64-softmmu --enable-cocoa  --enable-sdl --enable-virglrenderer --enable-vhost-net   --enable-spice-protocol --enable-tools --enable-opengl --enable-pixman --enable-vmnet
-````
-
-the device is clearly listed:
-````
-name "virtio-gpu-device", bus virtio-bus
-name "virtio-gpu-gl-device", bus virtio-bus
-name "virtio-gpu-gl-pci", bus PCI, alias "virtio-gpu-gl"
-name "virtio-gpu-pci", bus PCI, alias "virtio-gpu"
-````
-
-So why it not working and gives that info while opengl is clearly there and is enabled.
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2490 b/results/classifier/deepseek-2-tmp/output/graphic/2490
deleted file mode 100644
index af2433f4..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2490
+++ /dev/null
@@ -1,52 +0,0 @@
-
-Windows: virtio-vga-gl no longer works with current virglrenderer version
-Description of problem:
-Error occurs, when executing QEMU with virtio-vga-gl device using current virglrenderer:
-First the boot screen is shown as expected.
-After a short while the screen shows and keeps showing "virtio-vga-gl: Display output is not active."
-Console logs:
-```
-qemu: GtkGLArea console lacks DMABUF support.
-qemu: GtkGLArea console lacks DMABUF support.
-qemu: GtkGLArea console lacks DMABUF support.
-qemu: GtkGLArea console lacks DMABUF support.
-Realize gdk gl context failed: GL-Kontext kann nicht erstellt werden
-Realize gdk gl context failed: GL-Kontext kann nicht erstellt werden
-virtio_gpu_virgl_process_cmd: ctrl 0x103, error 0x1203
-virtio_gpu_virgl_process_cmd: ctrl 0x103, error 0x1203
-virtio_gpu_virgl_process_cmd: ctrl 0x103, error 0x1203
-```
-Steps to reproduce:
-1. Prepare current Msys2/Ucrt64 environment including virglrenderer 1.0.1 by installing QEMU as described in https://www.qemu.org/download/#windows
-2. `wget https://download.opensuse.org/distribution/leap/15.3/live/openSUSE-Leap-15.3-GNOME-Live-x86_64-Media.iso`
-3. `qemu-system-x86_64.exe -m 1024 -display gtk,gl=on -device virtio-vga-gl -cdrom openSUSE-Leap-15.3-GNOME-Live-x86_64-Media.iso`
-Additional information:
-virglrenderer may use certain D3D features starting with virglrenderer 1.0.0, see https://gitlab.freedesktop.org/virgl/virglrenderer/-/merge_requests/1103 for details
-
-Given virglrenderer >= 1.0.0, QEMU activates these D3D features since https://gitlab.com/qemu-project/qemu/-/commit/c1600f84ce011a056c9c432c8ad8d77f7f8b9e6f.
-
-But the current QEMU implementation is broken when using these D3D features. 
-
-git bisect finishes with:
-```
-574b64aa6754ba491f51024c5a823a674d48a658 is the first bad commit
-commit 574b64aa6754ba491f51024c5a823a674d48a658
-Author: Dmitry Osipenko <dmitry.osipenko@collabora.com>
-Date:   Mon Jan 29 10:39:21 2024 +0300
-
-    virtio-gpu: Correct virgl_renderer_resource_get_info() error check
-
-    virgl_renderer_resource_get_info() returns errno and not -1 on error.
-    Correct the return-value check.
-
-    Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
-    Signed-off-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
-    Message-Id: <20240129073921.446869-1-dmitry.osipenko@collabora.com>
-    Cc: qemu-stable@nongnu.org
-    Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
-    Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
-
- contrib/vhost-user-gpu/virgl.c | 6 +++---
- hw/display/virtio-gpu-virgl.c  | 2 +-
- 2 files changed, 4 insertions(+), 4 deletions(-)
-```
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/251 b/results/classifier/deepseek-2-tmp/output/graphic/251
deleted file mode 100644
index 66c666ad..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/251
+++ /dev/null
@@ -1,2 +0,0 @@
-
-Qemu DOS Quake - 640x480 and above resolutions - Unable to load VESA palette in dos prompt and game crashing are not working
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/253 b/results/classifier/deepseek-2-tmp/output/graphic/253
deleted file mode 100644
index 1ecda77a..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/253
+++ /dev/null
@@ -1,2 +0,0 @@
-
-Qemu Win98 VM with KVM videocard passthrough DOS mode video is not working for most of games..
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2539 b/results/classifier/deepseek-2-tmp/output/graphic/2539
deleted file mode 100644
index a494fb04..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2539
+++ /dev/null
@@ -1,2 +0,0 @@
-
-Crash in early_gtk_display_init() on macOS 14.6.1
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/254 b/results/classifier/deepseek-2-tmp/output/graphic/254
deleted file mode 100644
index 28862521..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/254
+++ /dev/null
@@ -1,2 +0,0 @@
-
-Windows 98 videocard passthrough - unable to load higher resolution -Desktop, after some games crashes, without whole physical machine reset..
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/262 b/results/classifier/deepseek-2-tmp/output/graphic/262
deleted file mode 100644
index 31479eeb..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/262
+++ /dev/null
@@ -1,2 +0,0 @@
-
-Broken scaling with gtk,gl=on on a hidpi display
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2621 b/results/classifier/deepseek-2-tmp/output/graphic/2621
deleted file mode 100644
index 1e8fb40e..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2621
+++ /dev/null
@@ -1,16 +0,0 @@
-
-virtgpu does not return error for misconfigured virgl command
-Description of problem:
-When ```virgl_renderer_submit_cmd``` reports error, cmd->error should be set. Otherwise driver cannot know if there is error.
-https://gitlab.com/qemu-project/qemu/-/blob/master/hw/display/virtio-gpu-virgl.c?ref_type=heads#L233
-
-Probably 0x1200 (unspec) or 0x1205 (invalid param) should return as error. 
-
-
-If there is problem in cmd virgl freezes drawing window.
-Steps to reproduce:
-1. Send misformated command to virgl over vgpu device
-2.
-3.
-Additional information:
-Misformated 3d commands stops opengl's drawings. Without returning error we cannot know any error, hence we cannot reset vgpu.
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2637 b/results/classifier/deepseek-2-tmp/output/graphic/2637
deleted file mode 100644
index 0cadaa5b..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2637
+++ /dev/null
@@ -1,54 +0,0 @@
-
-ubuntu 22.04 virtio-vga-gl notwork
-Description of problem:
-
-Steps to reproduce:
-1.qemu-system-x86_64 \
-    -m 2048 \
-    -smp 2 \
-    -hda /home/perilla/virt/redroid.qcow2 \
-    -boot d \
-    -net nic -net user,hostfwd=tcp::1122-:22,hostfwd=tcp::19000-:9000,hostfwd=tcp::15555-:5555 \
-    -vnc :0 \
-    -device virtio-vga-gl \
-    -display sdl,gl=on \
-    -enable-kvm 
-
-the machine can't startup normally
-
-host console output:
-qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]\n
-qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]\n
-gl_version 46 - core profile enabled\n
-
-after`gl_version` line, startup prograss stopped![image]
-
-vm console output:
-it seems different every startup progress
-
-first time:
-
-![image](/uploads/4bbdb263db3faa812aeb568e7e5d2c9f/image.png){width=764 height=467}
-second time:
-
-![image](/uploads/0d7c92b8f5b2e5241b15da1681b10eda/image.png){width=780 height=415}
-
-2.
-3.
-Additional information:
-when I use -device virtio-gpu, it works fine 
-qemu-system-x86_64 \
-    -m 2048 \
-    -smp 2 \
-    -hda /home/username/virt/redroid.qcow2 \
-    -boot d \
-    -net nic -net user,hostfwd=tcp::1122-:22,hostfwd=tcp::19000-:9000,hostfwd=tcp::15555-:5555 \
-    -vnc :0 \
-    -device virtio-gpu \
-    -display sdl,gl=on \
-    -enable-kvm \
-     -device qxl
-
-host console output:\n
-qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]\n
-qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]\n
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2670 b/results/classifier/deepseek-2-tmp/output/graphic/2670
deleted file mode 100644
index 78e2c191..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2670
+++ /dev/null
@@ -1,45 +0,0 @@
-
-The virglrenderer depency causes qemu native recipe building to fail for NXP QEMU
-Description of problem:
-nativesdk-qemu-8.2.2.imx-r0 do_compile: oe_runmake failed
-...
- [87/4472] Compiling C object libcommon.fa.p/hw_display_virtio-gpu.c.o
-| FAILED: libcommon.fa.p/hw_display_virtio-gpu.c.o
-...
- ../hw/display/virtio-gpu.c:36:10: fatal error: virglrenderer.h: No such file or directory
-|    36 | #include <virglrenderer.h>
-|       |          ^~~~~~~~~~~~~~~~~
-| compilation terminated.
-
-This issue was originally exposed after updating Yocto release to Scarthgap
-
-https://lists.yoctoproject.org/g/yocto/topic/building_sdk_fails_after/109275322
-
-which seems to relate to commit https://github.com/nxp-imx/imx-qemu/commit/628105edbd816458dbf154a128cc3dd3ac809c7e that seemingly induces dependency to virglrenderer.h for virtio_gpu driver.
-
-Enabling opengl in our Distribution features is not a solution because that pulls in VGA graphics dependencies to our target binaries and we have no graphics hardware on our system. I have tried to disable the virglrenderer through QEMU build configuration but that does not fix the issue.
-Steps to reproduce:
-1. Clone NXP BSP Scarthgap
-```
-$ mkdir nxp-bsp
-$ cd nxp-bsp
-nxp-bsp$ repo init -u https://github.com/nxp-imx/imx-manifest -b scarthgap -m imx-6.6.36-2.1.0.xml
-nxp-bsp$ repo sync
-```
-
-2. Remove opengl from `fsl-imx-xwayland` DISTRO_FEATURES
-
-```
-sources/meta-imx/meta-imx-sdk/conf/distro/fsl-imx-wayland.conf:
-...
-+DISTRO_FEATURES:remove = "opengl "
-...
-```
-
-3. Build qemu-native_8.2.2.imx
-
-```
-$ bitbake qemu-native_8.2.2.imx
-```
-Additional information:
-
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2679 b/results/classifier/deepseek-2-tmp/output/graphic/2679
deleted file mode 100644
index 5e3fc7d9..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2679
+++ /dev/null
@@ -1,2 +0,0 @@
-
-TCX emulation missing 1152x900 mode
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2680 b/results/classifier/deepseek-2-tmp/output/graphic/2680
deleted file mode 100644
index 21241fce..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2680
+++ /dev/null
@@ -1,15 +0,0 @@
-
-GTK accelerators (including releasing input grab) don't work in keyboard layouts that utilize AltGr on Windows
-Description of problem:
-With a non-QWERTY (in my case, Colemak) layout active, it's not possible to ungrab input from the window using the Ctrl-Alt-G. The key combination is simply ignored, whether the G is typed using the physical key G on the keyboard or the one where it would be mapped by the keyboard layout (physical T key for Colemak). Thankfully, because of #2225, the mouse cursor isn't actually captured, which allows me to move the mouse outside the window and close QEMU from the taskbar instead.
-
-Temporarily switching back to a QWERTY layout before the grab happens allows input to be released using the key combo. However this needs to be done before the capture as otherwise QEMU will simply intercept any shortcuts to toggle the layout.
-
-I suspect there's some mismatch between the input grabbing code and the GTK UI, where one is using the keyboard scancode to determine when to forward the key, but the GTK UI then uses the mapped letter from the layout and fails to activate the shortcut.
-Steps to reproduce:
-1. Configure a non-QWERTY layout (such as Dvorak or Colemak) in the system settings
-1. Launch QEMU (it's not necessary to load any guest, booting the BIOS is fine)
-2. Click on the window which will automatically capture input
-3. Try to release using the Ctrl-Shift-G shortcut (in either layout), which should be ignored
-Additional information:
-
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2724 b/results/classifier/deepseek-2-tmp/output/graphic/2724
deleted file mode 100644
index 1ae5de4f..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2724
+++ /dev/null
@@ -1,9 +0,0 @@
-
-Invalid DRM modifier in ScanoutDMABUF call
-Description of problem:
-`modifier` parameter in `ScanoutDMABUF` callback is always `0xffffffffffffff` (`DRM_FORMAT_RESERVED`)
-Steps to reproduce:
-1. Run QEMU with D-Bus display
-2. Connect D-Bus display client and print modifier
-Additional information:
-
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/280 b/results/classifier/deepseek-2-tmp/output/graphic/280
deleted file mode 100644
index e4ffdd89..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/280
+++ /dev/null
@@ -1,2 +0,0 @@
-
-(ARM64) qemu-x86_64+schroot(Debian bullseye) can't run chrome and can't load HTML
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2905 b/results/classifier/deepseek-2-tmp/output/graphic/2905
deleted file mode 100644
index 08acbe58..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2905
+++ /dev/null
@@ -1,25 +0,0 @@
-
-Windows Curses Display Infinite Loop
-Description of problem:
-The out-of-the-box `qemu-system-x86_64 -display curses` on Windows loops forever while displaying "VGA Blank Mode" instead of booting like `qemu-system-x86_64` does.
-
-This is caused by an infinite loop in the below simplified code in `curses_refresh` in `ui/curses.c`:
-```
-    int chr;
-    // ...trimmed
-    while (1) {
-        /* while there are any pending key strokes to process */
-        chr = console_getch(&maybe_keycode);
-
-        if (chr == -1) 
-            break;
-    // ...trimmed
-    }
-```
-`console_getch` has return type `wint_t`. However, on Windows, `wint_t` is `unsigned short`. Therefore when `console_getch` returns -1, the -1 value of `unsigned short` will be silently converted into the `int` value 65535. This causes `65535 == -1` to always be false, and the loop will never break. I can send a patch to qemu-devel which retypes `chr` to `wint_t` and replaces occurences of -1 with `WEOF` (an alias for `(wint_t) -1`).
-Steps to reproduce:
-1. Install `qemu-w64-setup-20250326.exe` Windows qemu from https://qemu.weilnetz.de/w64/2025/
-2. Run `./qemu-system-x86_64 -display curses`
-3. "VGA Blank Mode" will appear on the screen forever
-Additional information:
-
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2908 b/results/classifier/deepseek-2-tmp/output/graphic/2908
deleted file mode 100644
index 9280bad0..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2908
+++ /dev/null
@@ -1,11 +0,0 @@
-
-Display Output Not Sane After Driver Installation
-Description of problem:
-Using an S3 Diamond Stealth 3000 card through VFIO, after installing an official driver, either from the Windows disc or an updated download, the displayed output from the graphics card is not sane.
-Additional information:
-Driver: [https://theretroweb.com/expansioncards/s/diamond-stealth-3d-3000-pci#driver](https://theretroweb.com/expansioncards/s/diamond-stealth-3d-3000-pci#driver)  
-[https://diamond.retropc.se/driver/stealth/st3d3xx0/files.htm](https://diamond.retropc.se/driver/stealth/st3d3xx0/files.htm)
-
-Followed the instructions in the Readme. To install Standard VGA driver first then the Diamond 3000 driver. No change. It is not the only S3 card that I have tried that behaves like this. I have also used the bios rom downloaded directly from the card, again with no change.
-
-#
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2920 b/results/classifier/deepseek-2-tmp/output/graphic/2920
deleted file mode 100644
index c3bcdc81..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2920
+++ /dev/null
@@ -1,13 +0,0 @@
-
-VGA Passthrough I/O Lag on DOS (FreeDOS) System.
-Description of problem:
-VGA performance lags with passthrough when the OS is in graphics mode. It also seems to affect when key presses are registered with noticeable delay.
-Steps to reproduce:
-1. Install Doom (v1.9 Shareware.)
-2. Run setup and disable sound.
-3. Play game or watch demo.
-Additional information:
-I have tried multiple cards with no change in performance:
-
-**VGA compatible controller: S3 Graphics Ltd. 86c375 [ViRGE/DX] or 86c385 [ViRGE/GX] (rev 01) (prog-if 00 [VGA controller])   
-VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] R480 [Radeon X800 GTO] (prog-if 00 [VGA controller])**
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2929 b/results/classifier/deepseek-2-tmp/output/graphic/2929
deleted file mode 100644
index 0cff29a0..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2929
+++ /dev/null
@@ -1,8 +0,0 @@
-
-Ask to extend vhost-user protocol to carry implementation defined error contexts
-Additional information:
-I am working on the Google [crosvm](https://chromium.googlesource.com/crosvm/crosvm/) project, which implements some `vhost-user` clients/servers defined by [this QEMU doc](https://qemu-project.gitlab.io/qemu/interop/vhost-user.html). I am wondering if we could add a protocol feature/protocol header flag bit to allow the payload of the reply to carry detailed implementation defined error contexts?
-
-Specifically, I am working on the `vhost-user-gpu` device, which needs to send some memory mapping request to the frontend(the main process where VCPU lives), so that we can map some GPU memory to the guest. We are trying to diagnose a bug where the frontend can sometimes fail to perform the operation. However, we don't have access to the logs on the main process, so we are left with only very limited information on the `vhost-user-gpu` process. It could be helpful if we could send detailed implementation defined error contexts in the payload of the reply.
-
-I am wondering in order for the upstream QEMU to accept such "spec" change to the `vhost-user` protocol, what the process should be like? Thanks.
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2959 b/results/classifier/deepseek-2-tmp/output/graphic/2959
deleted file mode 100644
index b938d75b..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2959
+++ /dev/null
@@ -1,78 +0,0 @@
-
-int 0x10 teletype output cuts final character in custom MBR on QEMU (i386 real mode)
-Description of problem:
-When using QEMU to test a custom bootloader in 16-bit real mode (i386), the BIOS interrupt `int 0x10` with AH=0x0E (teletype output) fails to display the last character of the printed message. For example, printing `"hello"` only renders `"hell"`.
-
-This happens only with this exact combination:
-
-real mode `int 0x10` teletype output
-
-message ends with `13, 10, 0`
-
-`QEMU` output cuts off the last character consistently
-
-All buffer and code logic has been verified to be correct. The same code, when run on Bochs or physical hardware, prints properly.
-Steps to reproduce:
-1.Assemble the following boot.asm:
-```nasm
-[org 0x7C00]
-[BITS 16]
-
-_start:
-    cli
-    xor ax, ax
-    mov ds, ax
-    mov es, ax
-    mov ss, ax
-    mov sp, 0x7C00
-
-    mov si, msg
-    call print
-
-    hlt
-    jmp $
-
-print:
-    pusha
-.loop:
-    lodsb
-    or al, al
-    jz .done
-    mov ah, 0x0E
-    int 0x10
-    jmp .loop
-.done:
-    popa
-    ret
-
-msg db 'hello', 13, 10, 0
-times 510 - ($ - $$) db 0
-dw 0xAA55
-```
-
-2. Compile and run:
-```bash
-$ nasm -f bin boot.asm -o boot.img
-$ qemu-system-i386 -nographic -boot a -drive format=raw,file=boot.img,index=0,if=floppy
-```
-
-3. Output will be:
-```text
-Booting from Floppy...
-hell
-```
-Expected output:
-```text
-Booting from Floppy...
-hello
-```
-Additional information:
-- Adding padding (extra 13, 10) does not solve the problem.
-
-- Confirmed that boot.img includes all bytes (xxd dump is correct).
-
-- Tested on multiple machines with same QEMU version.
-
-- May relate to VGA character output buffer not flushing after last INT 0x10?
-
-- This makes QEMU inaccurate for BIOS-level debugging of bootloaders.
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/296 b/results/classifier/deepseek-2-tmp/output/graphic/296
deleted file mode 100644
index 5e21e401..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/296
+++ /dev/null
@@ -1,2 +0,0 @@
-
-Enabling OpenGL for GUI doesn't work on old laptop
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2965 b/results/classifier/deepseek-2-tmp/output/graphic/2965
deleted file mode 100644
index 79c1e61f..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2965
+++ /dev/null
@@ -1,15 +0,0 @@
-
-crash when interacting with the UI in any way during record/replay mode on macOS
-Description of problem:
-```
-**
-ERROR:../replay/replay-events.c:119:replay_add_event: assertion failed: (replay_mutex_locked())
-Bail out! ERROR:../replay/replay-events.c:119:replay_add_event: assertion failed: (replay_mutex_locked())
-fish: Job 1, 'qemu-system-x86_64 -icount shif…' terminated by signal SIGABRT (Abort)
-```
-Steps to reproduce:
-1. run the qemu command
-2. click in the window
-3. observe crash
-Additional information:
-[qemu-system-x86_64-2025-05-15-032037.ips](/uploads/2cccc7b967dacc8a18be8a3d0a0cf297/qemu-system-x86_64-2025-05-15-032037.ips)
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/298 b/results/classifier/deepseek-2-tmp/output/graphic/298
deleted file mode 100644
index a4446af5..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/298
+++ /dev/null
@@ -1,2 +0,0 @@
-
-OpenGL, Virtio-VGA, Virtio-GPU-PCI, GTK
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/2988 b/results/classifier/deepseek-2-tmp/output/graphic/2988
deleted file mode 100644
index bf5ebce5..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/2988
+++ /dev/null
@@ -1,8 +0,0 @@
-
-Absolute mouse mode is broken in SDL2
-Description of problem:
-Absolute mouse mode is broken in SDL2. Bisected at 30aa105640b0a2a541744b6584d57c9a4b86debd.
-
-Relative mouse mode has never worked in stretched SDL2 Display for display controllers that passed through cursor data and have positions warped by HOST UI backend. It looks like 30aa105640b0a2a541744b6584d57c9a4b86debd tried to fix this but it didn't work out. Scaling **"relative motions"** isn't straight-forward as what the commit had expected.
-
-Absolute mouse mode mode has always worked in stretched SDL2 Display. 30aa105640b0a2a541744b6584d57c9a4b86debd broke it without fixing anything.
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/315 b/results/classifier/deepseek-2-tmp/output/graphic/315
deleted file mode 100644
index 5b7c5201..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/315
+++ /dev/null
@@ -1,2 +0,0 @@
-
-3d accel does not take care of 1280x960 setting
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/370 b/results/classifier/deepseek-2-tmp/output/graphic/370
deleted file mode 100644
index 90674c61..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/370
+++ /dev/null
@@ -1,2 +0,0 @@
-
-Indentation should be done with spaces, not with TABs, in the UI, graphics, audio and USB subsystem
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/434 b/results/classifier/deepseek-2-tmp/output/graphic/434
deleted file mode 100644
index 39b537d1..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/434
+++ /dev/null
@@ -1,2 +0,0 @@
-
-Mouse pointer disappears when it is over console window
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/476 b/results/classifier/deepseek-2-tmp/output/graphic/476
deleted file mode 100644
index d86c2206..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/476
+++ /dev/null
@@ -1,2 +0,0 @@
-
-QEMU with x86-64 EFI disk image and 'nographic' option crashes WSL2 window
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/48 b/results/classifier/deepseek-2-tmp/output/graphic/48
deleted file mode 100644
index e353ab21..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/48
+++ /dev/null
@@ -1,2 +0,0 @@
-
-Hover effect color for "Full list of releases" button is low contrast
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/497 b/results/classifier/deepseek-2-tmp/output/graphic/497
deleted file mode 100644
index 1abcdaac..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/497
+++ /dev/null
@@ -1,20 +0,0 @@
-
-GVT-g + -spice error since qemu 6
-Description of problem:
-It doesn't work:
-```
-qemu-system-x86_64: The console requires display DMABUF support.
-```
-
-If I add `gl=on` to `-spice`, it reports:
-```
-can't register two opengl displays (spice-egl, egl-headless)
-```
-Steps to reproduce:
-1. Setup an Intel GVT-g vGPU
-2. Run the command
-3. See the error
-Additional information:
-Before 6.0.0 it worked.
-
-Using VNC instead of SPICE works.
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/498421 b/results/classifier/deepseek-2-tmp/output/graphic/498421
deleted file mode 100644
index cf4b0bec..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/498421
+++ /dev/null
@@ -1,4 +0,0 @@
-
-Emulated monitor EDID reports too few available graphics resolutions
-
-In a Windows guest, not very many resolution modes are available.  The available modes are restricted by what the virtual "monitor" EDID reports via DDC.  And apparently, your fake monitor has a short list of modes.  Please add some more modes like 1152x864, at least.  But what would be REALLY nice is much finer granularity so that users can set the guest res to be just enough smaller than the host display so that window decorations and such fit.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/502107 b/results/classifier/deepseek-2-tmp/output/graphic/502107
deleted file mode 100644
index c8b97134..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/502107
+++ /dev/null
@@ -1,49 +0,0 @@
-
-qemu-kvm 0.12.1.2 crashes booting Ubuntu 9.10 with "-vga std"
-
-I have an Ubuntu VM that works fine without "-vga std" but crashes if I add "-vga std".  This is the full command line:
-
-qemu-system-x86_64 -vga std -drive
-cache=writeback,index=0,media=disk,file=ubuntu.img -k en-us -m 2048 -smp 2 -vnc
-:3102 -usbdevice tablet -enable-kvm &
-
-I get this error:
-
- KVM internal error. Suberror: 1
-rax 00007f789177e000 rbx 0000000000000000 rcx 0000000000000000 rdx
-0000000000000000
-rsi 0000000000000000 rdi 00007f789177e000 rsp 00007fff361775e8 rbp
-00007fff36177600
-r8  000000000000ff80 r9  0000000000200000 r10 0000000000000000 r11
-00007f789100a3f0
-r12 00000000004017c0 r13 00007fff36178cf0 r14 0000000000000000 r15
-0000000000000000
-rip 00007f789100aa7b rflags 00013206
-cs 0033 (00000000/ffffffff p 1 dpl 3 db 0 s 1 type b l 1 g 1 avl 0)
-ds 0000 (00000000/ffffffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0)
-es 0000 (00000000/ffffffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0)
-ss 002b (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0)
-fs 0000 (7f78917906f0/ffffffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0)
-gs 0000 (00000000/ffffffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0)
-tr 0040 (ffff880001a09440/00002087 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0)
-ldt 0000 (00000000/ffffffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0)
-gdt ffff8800019fa000/7f
-idt ffffffff818fd000/fff
-cr0 80050033 cr2 2408000 cr3 379d4000 cr4 6f0 cr8 0 efer d01
-emulation failure, check dmesg for details
-
-I'm running kernel 2.6.32, and I have the kvm stuff compiled directly into the
-kernel.  There's nothing in dmesg about kvm at all.
-
-Note that in the VM grub comes up, but the VM dies when I boot the kernel.
-
-This command line works:
-
-qemu-system-x86_64 -drive cache=writeback,index=0,media=disk,file=ubuntu.img -k
-en-us -m 2048 -smp 2 -vnc :3102 -usbdevice tablet -enable-kvm &
-
-That is, removing "-vga std" fixes the problem.
-
-I recently added this option to both my Ubuntu and Windows XP VMs.  The Windows VM still works fine.  If Windows can detect that the graphics card has changed, then Ubuntu should also have no problem.  That being said, I added the std option when using 0.12.1.1, so there may be a qemu regression.
-
-I have reported this bug elsewhere:  http://bugs.gentoo.org/show_bug.cgi?id=299211
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/504368 b/results/classifier/deepseek-2-tmp/output/graphic/504368
deleted file mode 100644
index 7af9f56c..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/504368
+++ /dev/null
@@ -1,44 +0,0 @@
-
-sdl window intermittently scales instead of resizing
-
-Binary package hint: qemu-kvm
-
-Normally, the SDL output window for a VM resizes to match the VM's resolution.  However, intermittently the output is instead scaled within the window.  I can't seem to find any pattern to when the output is scaled versus when the window is resized.  I would prefer that the window be resized as needed to display the VM in a 1:1 manner.
-
-ProblemType: Bug
-Architecture: amd64
-Date: Thu Jan  7 10:30:10 2010
-DistroRelease: Ubuntu 9.10
-InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
-KvmCmdLine:
- UID        PID  PPID  C    SZ   RSS PSR STIME TTY          TIME CMD
- root     27618     1 38 241752 804668 1 10:05 ?        00:09:39 /usr/bin/kvm -S -M pc-0.11 -cpu qemu32 -m 768 -smp 1 -name win2k3 -uuid da414aa0-f18a-7a02-3d1b-1dbf13137bc9 -monitor unix:/var/run/libvirt/qemu/win2k3.monitor,server,nowait -localtime -boot c -drive file=/media/qpc-devel/testing/win2k3/testing.ovl,if=ide,index=0,boot=on -drive file=/media/qpc-devel/testing/win2k3/../../isos/en_win_srv_2003_r2_standard_cd1.iso,if=ide,media=cdrom,index=2 -net nic,macaddr=00:16:3e:d6:f5:60,vlan=0,model=ne2k_pci,name=ne2k_pci.0 -net tap,fd=18,vlan=0,name=tap.0 -serial pty -parallel none -usb -usbdevice tablet -vga cirrus
- root     28306     1 54 177732 545520 1 10:28 ?        00:00:49 /usr/bin/kvm -S -M pc-0.11 -cpu qemu32 -m 512 -smp 1 -name win2k -uuid 153d6125-acb5-70bc-c7d2-bcbf87c5be86 -monitor unix:/var/run/libvirt/qemu/win2k.monitor,server,nowait -localtime -boot c -drive file=/media/qpc-devel/testing/win2k/testing.ovl,if=ide,index=0,boot=on -drive file=/media/qpc-devel/testing/win2k/../../isos/windows_2000.iso,if=ide,media=cdrom,index=2 -net nic,macaddr=68:29:6b:13:50:c6,vlan=0,model=ne2k_pci,name=ne2k_pci.0 -net tap,fd=19,vlan=0,name=tap.0 -serial pty -parallel none -usb -usbdevice tablet -vga cirrus
-NonfreeKernelModules: nvidia
-Package: kvm 1:84+dfsg-0ubuntu16+0.11.0+0ubuntu6.3
-PccardctlIdent:
- Socket 0:
-   no product info available
-PccardctlStatus:
- Socket 0:
-   no card
-ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-16-generic root=UUID=30218f9a-6f90-4eab-9ba5-f54897e842cb ro quiet splash
-ProcEnviron:
- PATH=(custom, user)
- LANG=en_US.UTF-8
- SHELL=/bin/bash
-ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
-SourcePackage: qemu-kvm
-Uname: Linux 2.6.31-16-generic x86_64
-dmi.bios.date: 02/20/2008
-dmi.bios.vendor: LENOVO
-dmi.bios.version: 7LETB2WW (2.12 )
-dmi.board.vendor: LENOVO
-dmi.board.version: Not Available
-dmi.chassis.asset.tag: No Asset Information
-dmi.chassis.type: 10
-dmi.chassis.vendor: LENOVO
-dmi.chassis.version: Not Available
-dmi.modalias: dmi:bvnLENOVO:bvr7LETB2WW(2.12):bd02/20/2008:svnLENOVO:pn:pvrThinkPadT61p:rvnLENOVO:rn:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
-dmi.product.version: ThinkPad T61p
-dmi.sys.vendor: LENOVO
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/562 b/results/classifier/deepseek-2-tmp/output/graphic/562
deleted file mode 100644
index 020f425a..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/562
+++ /dev/null
@@ -1,2 +0,0 @@
-
-`ShaderTranslator.h` and `ShaderTranslator.cpp` files are missing and are not in ANGLE_ROOT/src/libShaderTranslator
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/564 b/results/classifier/deepseek-2-tmp/output/graphic/564
deleted file mode 100644
index 05f981aa..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/564
+++ /dev/null
@@ -1,14 +0,0 @@
-
-Enable opengl virtio-gpu virgl vulkan in windows build
-Additional information:
-```
-PS E:\scoopg\apps\qemu\current> ./qemu-system-x86_64.exe -drive file=E:\groot_02\vdisks\gparted-live.iso,if=virtio  -boot c -m 4096 -machine type=pc,accel=whpx,kernel-irqchip=off -smp 8,sockets=1,cores=8,threads=1 -vga virtio -display sdl,gl=on
-E:\scoopg\apps\qemu\current\qemu-system-x86_64.exe: OpenGL support is disabled
-```
-
-```
-PS E:\scoopg\apps\qemu\current> E:\scoopg\apps\qemu\current\qemu-system-x86_64.exe --version
-QEMU emulator version 6.0.93 (v6.1.0-rc3-11879-ge232c1bc00-dirty)
-Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers
-```
-#
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/568 b/results/classifier/deepseek-2-tmp/output/graphic/568
deleted file mode 100644
index 4445aea2..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/568
+++ /dev/null
@@ -1,27 +0,0 @@
-
-video memory option not working with Mac OS or Windows guest
-Description of problem:
-The vgamem_mb option tells the guest how much video memory it has access to. When I used this command '-device VGA,vgamem_mb=128', I expect the guest to report there is 128 MB of video memory. What actually happens is the guest does not seem to know how much video memory is actually available.
-Steps to reproduce:
-**Mac OS guest:**
-1. Run a Mac OS guest with this command: -device VGA,vgamem_mb=128
-2. In Mac OS X open the System Information application -> /Applications/Utilities/System Information. 
-3. Click on "Graphics/Displays".
-4. Look at the 'VRAM (Total)' field.
-The field only shows 3 MB of video ram.
-
-**Windows guest:**
-1. Run a Windows (Windows XP in my case) guest with this command: -device VGA,vgamem_mb=128
-2. Click on Start->Run.
-3. Enter 'dxdiag'.
-4. Push the OK button.
-5. Click on the Display tap in the DirectX Diagnostic Tool.
-6. Look at the Approv. Total Memory field.
-The field should say 128 MB but actually says N/A.
-Additional information:
-**Mac OS 8.5<br>**
-![Mac_OS_10.8](/uploads/b80d67c82ec1236067b3577add10c19c/Mac_OS_10.8.png)<br><br><br>
-**Windows XP<br>**
-![Windows_XP](/uploads/9db71f35faa360dfcebc2b8af84abf06/Windows_XP.png)<br><br><br>
-**Windows 7<br>**
-![Windows_7](/uploads/8645f1424ef1637300056c889df3d7de/Windows_7.png)
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/568614 b/results/classifier/deepseek-2-tmp/output/graphic/568614
deleted file mode 100644
index a15060b1..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/568614
+++ /dev/null
@@ -1,17 +0,0 @@
-
-x86_64 host curses interface: spacing/garbling
-
-Environment:
-Arch Linux x86_64, kernel 2.6.33, qemu 0.12.3
-
-Steps to reproduce:
-1. Have a host system running 64-bit Linux.
-2. Start a qemu VM with the -curses flag.
-
-Expected results:
-Text displayed looks as it would on a real text-mode display, and VM is therefore usable.
-
-Actual results:
-Text displayed contains an extra space between characters, causing text to flow off the right and bottom sides of the screen. This makes the curses interface unintelligible.
-
-The attached patch fixes this problem on 0.12.3 on my installation without changing behavior on a 32-bit machine.  I don't know enough of the semantics of console_ch_t to know if this is the "correct" fix or if there should be, say, an extra cast somewhere instead.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/58 b/results/classifier/deepseek-2-tmp/output/graphic/58
deleted file mode 100644
index 529b2390..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/58
+++ /dev/null
@@ -1,2 +0,0 @@
-
-Bitmaps with Extra Data cannot be removed
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/586 b/results/classifier/deepseek-2-tmp/output/graphic/586
deleted file mode 100644
index 1862bb7b..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/586
+++ /dev/null
@@ -1,2 +0,0 @@
-
-virtio-gpu: qemu 6.1.0 no longer enables virgl when using '-vga virtio'
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/589231 b/results/classifier/deepseek-2-tmp/output/graphic/589231
deleted file mode 100644
index eae5c039..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/589231
+++ /dev/null
@@ -1,10 +0,0 @@
-
-cirrus vga is very slow in qemu-kvm-0.12
-
-As has been reported multiple times (*), there were a regression in qemu-kvm from 0.11 to 0.12, which causes significant slowdown in cirrus vga emulation.  For windows guests, where "standard VGA" driver works reasonable well, -vga std is a good workaround. But for e.g. linux guests, where vesa driver is painfully slow by its own, that's not a solution.
-
-(*)
- debian qemu-kvm bug report #574988: http://bugs.debian.org/574988#17
- debian qemu bugreport (might be related): http://bugs.debian.org/575720
- kvm mailinglist thread: http://<email address hidden>/msg33459.html
- another kvm ml thread: http://<email address hidden>/msg32744.html
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/606 b/results/classifier/deepseek-2-tmp/output/graphic/606
deleted file mode 100644
index 0bf4c8d3..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/606
+++ /dev/null
@@ -1,2 +0,0 @@
-
-Gtk: gtk_clipboard_set_with_data: assertion 'targets != NULL' failed
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/610 b/results/classifier/deepseek-2-tmp/output/graphic/610
deleted file mode 100644
index 0280697a..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/610
+++ /dev/null
@@ -1,32 +0,0 @@
-
-after upgrade to 6.1.0, snapshot creation fails with "pre-save failed: qxl"
-Description of problem:
-When trying to create a snapshot using `virsh --connect qemu:///system snapshot-create-as <domain-name> <snapshot-name>` or virt-manager GUI, I get the following error:
-
-```
-Error: Error while writing VM state: Unknown error -1
-
-
-Traceback (most recent call last):
-  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in cb_wrapper
-    callback(asyncjob, *args, **kwargs)
-  File "/usr/share/virt-manager/virtManager/details/snapshots.py", line 237, in _do_create_snapshot
-    self.vm.create_snapshot(xml)
-  File "/usr/share/virt-manager/virtManager/object/domain.py", line 1124, in create_snapshot
-    self._backend.snapshotCreateXML(xml, flags)
-  File "/usr/lib/python3.9/site-packages/libvirt.py", line 3059, in snapshotCreateXML
-    raise libvirtError('virDomainSnapshotCreateXML() failed')
-libvirt.libvirtError: operation failed: Failed to take snapshot: pre-save failed: qxl
-Error: Error while writing VM state: Unknown error -1
-```
-Additional information:
-I'm using Arch Linux distro packages.
-The issue appeared after upgrading qemu-headless from 6.0.0 to 6.1.0.
-Downgrading back to 6.0.0 fixes the problem (snapshot are created
-successfully and work as expected).
-
-In a reply to my message to libvirt-users describing the issue [1],
-Daniel P. Berrangé confirmed that the error comes from QEMU and
-recommended reporting it here.
-
-[1] https://listman.redhat.com/archives/libvirt-users/2021-September/msg00007.html
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/612677 b/results/classifier/deepseek-2-tmp/output/graphic/612677
deleted file mode 100644
index 7bc38605..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/612677
+++ /dev/null
@@ -1,19 +0,0 @@
-
-qemu-kvm -curses displays garbled screen
-
-when I launch qemu-kvm -curses (even without a guest OS) I get a garbled output, here's a screenshot:
-http://kontsevoy.com/qemu.png
-
-some more info:
-
-myarch ~: uname -a
-Linux myarch 2.6.34-ARCH #1 SMP PREEMPT Mon Jul 5 22:12:11 CEST 2010 x86_64 Intel(R) Core(TM)2 Duo CPU P8700 @ 2.53GHz GenuineIntel GNU/Linux
-
-myarch ~: qemu-kvm --version
-QEMU PC emulator version 0.12.5 (qemu-kvm-0.12.5), Copyright (c) 2003-2008 Fabrice Bellard
-
-I also fetched the latest qemu-kvm from git repo and compiled it with simple ./configure&make
-The compiled version behaved similarly
-
-I also tried different terminal emulators: gnome-terminal and xterm - same thing
-I also tried real terminal (i.e. booted without X) - same thing
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/631 b/results/classifier/deepseek-2-tmp/output/graphic/631
deleted file mode 100644
index 57a8782a..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/631
+++ /dev/null
@@ -1,26 +0,0 @@
-
-QEMU locks out user interface after waking from laptop sleep
-Description of problem:
-If qemu is started on laptop from command line and set to full screen, screen activated with mouse click, then put to sleep by closing lid; after waking up by opening lid the user interface locks out, the mouse cursor doesn't show, mouse clicks and keys are unresponsive.
-
-A Ctrl-ALt-Fn terminal must then be used to locate and kill the qemu process. After which the system can recover if it is terminated. The system tends to be affected in other ways such as wifi being disabled and needs to manually enabled after. So it looks like it disrupts the system from fully restoring the awoken state.
-
-The terminal from which QEMU is running is also filled with debug output. The issue looks to be caused by the SDL backend not knowing what to do with a wake up code. The terminal window is filled with the following text: 
-`The key you just pressed is not recognized by SDL. To help get this fixed, please report this to the SDL forums/mailing list <https://discourse.libsdl.org/> X11 KeyCode 151 (143), X11 KeySym 0x1008FF2B (XF86WakeUp).`
-
-I have reduced the steps causing the bug to as little as needed with low dependencies.
-Steps to reproduce:
-1. Using a laptop, start a qemu session in full screen like so:
-  `./qemu-system-ppc -machine mac99,via=pmu -serial stdio -full-screen`
-2. Shut the lid so it sleeps.
-3. Shortly after open the lid.
-Additional information:
-I downloaded the 6.1.0 stable build and compiled it myself.
-
-The SDL issue appears to be low priority. I found some reports here but see no evidence of it being discussed.
-https://discourse.libsdl.org/t/key-not-recognised-by-sdl/24181
-
-
-
-
-![Screenshot_from_2021-09-21_22-56-13](/uploads/e2e7e80adcc3d562235a734aa8bad67b/Screenshot_from_2021-09-21_22-56-13.png)
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/665743 b/results/classifier/deepseek-2-tmp/output/graphic/665743
deleted file mode 100644
index 05c2768c..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/665743
+++ /dev/null
@@ -1,4 +0,0 @@
-
-Cocoa video corruption when guest uses RGB565 mode
-
-The cocoa video driver doesn't currently support when the guest uses RGB565 or HighColor mode resulting in corrupted video.  The initial graphics screen of recent Ubuntu installs is an example.  The attached patch against 0.13.0-release seems to fix the problem by introducing an indirect data provider that translates from RGB565 to RGB888, a mode that core graphics supports.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/671 b/results/classifier/deepseek-2-tmp/output/graphic/671
deleted file mode 100644
index 0af78f2b..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/671
+++ /dev/null
@@ -1,19 +0,0 @@
-
-gtk with virtio and opengl black screen
-Description of problem:
-Running the provided command line, the screen is black, and the vm still starts.
-I can confirm that turning off gl (with gl=off), everything works.
-
-These are line outputs printed out by QEMU:
-```
-gl_version 45 - core profile enabled
-vrend_renderer_fill_caps: Entering with stale GL error: 1280
-GLSL feature level 430
-virtio_input_hid_handle_status: unknown type 20
-virtio_input_hid_handle_status: unknown type 20
-```
-Steps to reproduce:
-1. Execute the provided command
-2. Wait
-Additional information:
-The bug was opened on launchpad by Ethan (ethannij). However, after the migration to github issues, the bug expired and no one reported here. This is the full launchpad discussion: https://bugs.launchpad.net/qemu/+bug/1898490
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/696 b/results/classifier/deepseek-2-tmp/output/graphic/696
deleted file mode 100644
index c398ab92..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/696
+++ /dev/null
@@ -1,10 +0,0 @@
-
-EDID does not reflected to window size when added through the commandline
-Description of problem:
-It seems some odd behavior on the guest screen. it shows me the size of default window (640x480) instead of override the value to 1740x720. This size (640x480) is first initialized on ui/console.c => QemuConsole *graphic_console_init and I did noticed that in hw/display/virtio-gpu-base.c=> static int virtio_gpu_ui_info the override value is not taking place instead it just took the value from ui/console.c (640x480). May I know, how do I achieved the right override edid value from the current provided interface.
-
-##Additional information
-I did noticed that the edid flag is always true (running this command) It is contradiction from the doc.
-Steps to reproduce:
-1. Run the qemu with the command mentioned
-2. Check the resolution of guest OS
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/696530 b/results/classifier/deepseek-2-tmp/output/graphic/696530
deleted file mode 100644
index 9f3d14e0..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/696530
+++ /dev/null
@@ -1,8 +0,0 @@
-
-qemu-0.13.0-r2 special keys different when using -alt-grab
-
-I use -alt-grab with qemu-0.13.0-r2 and special keys like Ctrl-Alt-f for full screen did not work for me with a windows guest. They work normally when omitting the -alt-grab startup parameter.
-
-After quite a long time, I found out that I have to add the shift key to the keys from the documentation when I use the -alt-grab option.
-
-Probably -ctrl-grab behaves similarly. It would be really nice to have this documented in the default documentation in the man page as has not been documented there yet.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/697197 b/results/classifier/deepseek-2-tmp/output/graphic/697197
deleted file mode 100644
index c5732e02..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/697197
+++ /dev/null
@@ -1,27 +0,0 @@
-
-Empty password allows access to VNC in libvirt
-
-The help in the /etc/libvirt/qemu.conf states
-
-"To allow access without passwords, leave this commented out. An empty
-string will still enable passwords, but be rejected by QEMU
-effectively preventing any use of VNC."
-
-yet setting:
-
-vnc_password=""
-
-allows access to the vnc console without any password prompt just as if it is hashed out completely.
-
-ProblemType: Bug
-DistroRelease: Ubuntu 10.10
-Package: libvirt-bin 0.8.3-1ubuntu14
-ProcVersionSignature: Ubuntu 2.6.35-24.42-server 2.6.35.8
-Uname: Linux 2.6.35-24-server x86_64
-Architecture: amd64
-Date: Tue Jan  4 12:18:35 2011
-InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.2)
-ProcEnviron:
- LANG=en_GB.UTF-8
- SHELL=/bin/bash
-SourcePackage: libvirt
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/700 b/results/classifier/deepseek-2-tmp/output/graphic/700
deleted file mode 100644
index ee9ed8bc..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/700
+++ /dev/null
@@ -1,2 +0,0 @@
-
-GTK display refresh rate is throttled
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/709584 b/results/classifier/deepseek-2-tmp/output/graphic/709584
deleted file mode 100644
index 7df31991..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/709584
+++ /dev/null
@@ -1,20 +0,0 @@
-
-Fullscreen mode splits screen over monitor boundaries on dual-monitor system
-
-I originally reported this for the Android SDK emulator, which is built on QEMU: http://code.google.com/p/android/issues/detail?id=14336
-
-Can confirm that this bug is present in stock QEMU shipped with Ubuntu 10.10:
-QEMU PC emulator version 0.12.5 (qemu-kvm-0.12.5), Copyright (c) 2003-2008 Fabrice Bellard
-
-Steps to reproduce:
-- get a Linux machine with multiple-monitor setup (tested using NVidia proprietary driver on Ubuntu 10.10 x86_64, with two monitors side-by-side in 'TwinView' configuration)
-- launch qemu
-- hit ctrl+alt+f to go into fullscreen mode
-
-Expected behavior:
-- emulator should take over one screen (either the first screen, largest screen, or screen the emulator is presently on)
-- emulator's display should center or scale to fit within available area of the taken-over screen
-
-Actual behavior:
-- emulator takes over both screens
-- emulator's display is split over the boundary between the two screens
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/711 b/results/classifier/deepseek-2-tmp/output/graphic/711
deleted file mode 100644
index 264e4149..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/711
+++ /dev/null
@@ -1,2 +0,0 @@
-
-ATI Rage video card emulation
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/731 b/results/classifier/deepseek-2-tmp/output/graphic/731
deleted file mode 100644
index 2eaf7fe1..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/731
+++ /dev/null
@@ -1,22 +0,0 @@
-
-Display resolution fixed by 800x600 with latest VirtIO drivers and guest additions
-Description of problem:
-Display resolution can't be changed to anything else than 800x600.
-Steps to reproduce:
-1. Install qemu/kvm
-2. Create virtual machine
-3. Setup Windows 10
-4. Install VirtIO-Drivers
-5. Install guest-agent
-6. Install qxl-drivers
-
-Steps 5 and 6 enable use of QXL-Display, but do not lead to allow for higher display resolutions than before.
-Additional information:
-![Screenshot_w10_2021-11-16_17_18_07](/uploads/0b9bcd234c917a4730b41c4c063d867c/Screenshot_w10_2021-11-16_17_18_07.png)
-![Screenshot_w10_2021-11-16_17_18_38](/uploads/1f4a1099b2274d61f4dec117cba4d06c/Screenshot_w10_2021-11-16_17_18_38.png)
-![Screenshot_w10_2021-11-16_17_26_17](/uploads/2d48b8f35673a144e1c961387aa2b433/Screenshot_w10_2021-11-16_17_26_17.png)
-Screen resolution is fixed by 800x600.
-Driver is installed, but seems to have a problem (Attention sign. Warning, Error: digital signatur could not be checked -- at least there is no how to to make the existing signature work).
-Latest available VirtIO-drivers where used as available from https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.iso 
-
-Older available drivers did not work too as expected. Same problem. Could not check older Windows 10 versions, because of lack of older install media.
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/75 b/results/classifier/deepseek-2-tmp/output/graphic/75
deleted file mode 100644
index 2777fa1a..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/75
+++ /dev/null
@@ -1,2 +0,0 @@
-
-Add -display SDL grab-on-hover option
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/752476 b/results/classifier/deepseek-2-tmp/output/graphic/752476
deleted file mode 100644
index d9c777a4..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/752476
+++ /dev/null
@@ -1,9 +0,0 @@
-
-monitor command mouse_button 1 moves mouse
-
-via the qemu -monitor interface, it is possible to move and click the mouse using
-mouse_move 20000 10000
-mouse_button 1
-but the mouse_button command always moves the mouse to (0,0) making it rather unusable to (auto-)trigger any widgets in the VM from the outside.
-
-Would be nice to have this available for my qemu/kvm based os-autoinst testing framework.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/761 b/results/classifier/deepseek-2-tmp/output/graphic/761
deleted file mode 100644
index 3b4be93f..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/761
+++ /dev/null
@@ -1,13 +0,0 @@
-
-With -display gtk,gl=on, the position of mouse does not show correctly
-Description of problem:
-With `-display gtk,gl=on`, the cursor of the mouse does not show correctly. So, it's very hard to use mouse on guest OS desktop to, say, open an application or to close it. The displayed mouse cursor is about 300x300 away from the actual mouse position.
-Steps to reproduce:
-1. Build qemu 6.2.0-rc2 using the following `./configure` options:
-```
---prefix=$HOME/.bin --target-list=x86_64-softmmu --enable-kvm --enable-vnc --enable-gtk --enable-vte --enable-xkbcommon --enable-sdl --enable-spice --enable-spice-protocol --enable-virglrenderer --enable-opengl --enable-guest-agent --enable-avx2 --enable-hax --enable-system --enable-linux-user --enable-libssh --enable-linux-aio --enable-linux-io-uring --enable-modules --enable-fuse --enable-fuse-lseek
-```
-2. Run the above QEMU command with `-display gtk,gl=on`.
-3. Try to open an application by clicking its icon on desktop and to close it by clicking the "X" icon.
-Additional information:
-
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/769 b/results/classifier/deepseek-2-tmp/output/graphic/769
deleted file mode 100644
index c5c3ba53..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/769
+++ /dev/null
@@ -1,17 +0,0 @@
-
-When the VM is about to enter GUI desktop or quit the system, the screen turns upside down.
-Description of problem:
-When the VM is about to enter GUI desktop, the remaining booting message on the screen turns upside down. I was wondering if it is a designed feature or a bug. I like it because when I see it I'm ensured I'll enter the VM's GUI desktop soon without any problem.
-
-An edit: This happens also at the quitting time when I type "sudo shutdown now" in the terminal.
-Steps to reproduce:
-1. Build qemu using the following `./configure` options:
-```
---prefix=$HOME/.bin --target-list=x86_64-softmmu --enable-kvm --enable-vnc --enable-gtk --enable-vte --enable-xkbcommon --enable-sdl --enable-spice --enable-spice-protocol --enable-virglrenderer --enable-opengl --enable-guest-agent --enable-avx2 --enable-avx512f --enable-hax --enable-system --enable-linux-user --enable-libssh --enable-linux-aio --enable-linux-io-uring --enable-modules --enable-gio --enable-fuse --enable-fuse-lseek
-```
-2. Install Red Hat Enterprise Linux 8.5 in qemu
-3. Run qemu using the above command line, or type "sudo shutdown now" in the terminal after VM starts.
-Additional information:
-![image](/uploads/b8d277e4b05417cc8b0a7905bdcd27a4/image.png)
-
-![image](/uploads/94afd242ef1fac44aa504bdc6661a6ad/image.png)
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/775604 b/results/classifier/deepseek-2-tmp/output/graphic/775604
deleted file mode 100644
index bc64f620..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/775604
+++ /dev/null
@@ -1,12 +0,0 @@
-
-Could not open SDL display when running XP as guest
-
-When running XP as guest on Linux 2.6.38 x86_64 (Arch Linux) in full screen qemu will crash. Dropping to 1400x900 or below does not have a problem nor does windowed mode.
-
-1. Running:
-qemu-system-x86_64 -vga std -full-screen Virtual_Machines/Windows_XP/Windows_XP.img
-
-Produces error:
-Could not open SDL display (1920x1200x0): No video mode large enough for 1920x1200
-
-qemu-kvm version 0.14.0-1
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/776 b/results/classifier/deepseek-2-tmp/output/graphic/776
deleted file mode 100644
index bd3ab7f1..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/776
+++ /dev/null
@@ -1,26 +0,0 @@
-
-Windows guest fails to start on 6.1.0 - opengl is not available
-Description of problem:
-I've created a Windows 10 guest with virt-manager. The VM started successfully with qemu 6.0.0-3. After upgrading to 6.1.0
-it fails with the following error:
-
-```
-2021-12-14T19:11:52.884272Z qemu-system-x86_64: warning: This feature depends on other features that were not requested: CPUID.8000000AH:EDX.svme-addr-chk [bit 28]
-2021-12-14T19:11:52.885199Z qemu-system-x86_64: warning: This feature depends on other features that were not requested: CPUID.8000000AH:EDX.svme-addr-chk [bit 28]
-2021-12-14T19:11:52.885852Z qemu-system-x86_64: warning: This feature depends on other features that were not requested: CPUID.8000000AH:EDX.svme-addr-chk [bit 28]
-2021-12-14T19:11:52.886485Z qemu-system-x86_64: warning: This feature depends on other features that were not requested: CPUID.8000000AH:EDX.svme-addr-chk [bit 28]
-2021-12-14T19:11:52.887098Z qemu-system-x86_64: warning: This feature depends on other features that were not requested: CPUID.8000000AH:EDX.svme-addr-chk [bit 28]
-2021-12-14T19:11:52.887773Z qemu-system-x86_64: warning: This feature depends on other features that were not requested: CPUID.8000000AH:EDX.svme-addr-chk [bit 28]
-2021-12-14T19:11:52.912523Z qemu-system-x86_64: -device virtio-vga-gl,id=video0,max_outputs=1,bus=pcie.0,addr=0x1: opengl is not available
-2021-12-14 19:11:53.109+0000: shutting down, reason=failed
-```
-
-Upgrading to 6.2.0.rc4 did not fix it. Downgrading to 6.0.0-3 made it work again. This makes it clear to me that the bug was introduce in qemu > 6.0.0 and seems to be not fix by now.
-
-I was able to start the guest on 6.1.0 by disabling 3D acceleration.
-Steps to reproduce:
-1. Create Windows 10 guest VM
-2. Start with qemu 6.0.0 -> Works
-3. Start with qemu 6.1.0 -> Broken
-Additional information:
-People on Reddit mention the same characteristic of this bug -> https://www.reddit.com/r/Fedora/comments/qqw3sq/qemu_video_virtio_opengl_not_available_after/
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/779 b/results/classifier/deepseek-2-tmp/output/graphic/779
deleted file mode 100644
index d6652bd7..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/779
+++ /dev/null
@@ -1,14 +0,0 @@
-
-VNC server not work
-Description of problem:
-I've created a sandbox guest with kata containers. The VM started successfully, but vnc server not listen unix socket.
-
-`root@bootstrap02:~# netstat -anp | grep 1989153`  
-`unix  3      [ ]         STREAM     CONNECTED     369610592 1989153/qemu-system  /run/vc/vm/bash/qmp.sock`  
-`root@bootstrap02:~# lsof -p 1989153 | grep unix`  
-`qemu-syst 1989153 root  108u     unix 0xffff912740d3b800        0t0  369610592 /run/vc/vm/bash/qmp.sock type=STREAM`
-Steps to reproduce:
-1.Create Linux sandbox guest VM  
-2.connect vnc server
-Additional information:
-
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/784 b/results/classifier/deepseek-2-tmp/output/graphic/784
deleted file mode 100644
index c3c8abd8..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/784
+++ /dev/null
@@ -1,14 +0,0 @@
-
-max_hostmem does not work with virtio-vga-gl
-Description of problem:
-With property `max_hostmem=1000`, I hope the virgl VGA device can have 1GB video memory. But, after the VM starts, the command `glxinfo -B` returns "Video memory: 0MB", which I think means the virgl VGA does not obtain any video memory, or `max_hostmem=1000` does not work with `virtio-vga-gl`. Is it a bug or virgl has other property parameter to specify video memory?
-Steps to reproduce:
-1. Build qemu using the following `./configure` options:
-```
---prefix=$HOME/.bin --target-list=x86_64-softmmu --enable-kvm --enable-vnc --enable-gtk --enable-vte --enable-xkbcommon --enable-sdl --enable-spice --enable-spice-protocol --enable-virglrenderer --enable-opengl --enable-guest-agent --enable-avx2 --enable-avx512f --enable-hax --enable-system --enable-linux-user --enable-libssh --enable-linux-aio --enable-linux-io-uring --enable-modules --enable-gio --enable-fuse --enable-fuse-lseek
-```
-2. Install Red Hat Enterprise Linux 8.5 in qemu
-3. Run qemu using the above command line.
-4. Type `glxinfo -B` in VM terminal
-Additional information:
-![image](/uploads/c0bfb7a336493387ee90ffe7e6209dfe/image.png)
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/787 b/results/classifier/deepseek-2-tmp/output/graphic/787
deleted file mode 100644
index 5b284229..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/787
+++ /dev/null
@@ -1,13 +0,0 @@
-
-6.2.0 Regression with Intel GVT-g
-Description of problem:
-Until version 6.1.0 the Intel GVT-g graphics passtrought was working flawless. But, since the version 6.2.0 the machine with the exact same configuration is not working anymore, presenting an error that the graphics device was not found.
-
-```
-qemu-system-x86_64: -set device.hostdev0.x-igd-opregion=on: there is no device "hostdev0" defined
-```
-
-Downgrade to 6.1.0 fixes the problem.
-Steps to reproduce:
-1. Create a virtual machine with GVT-g
-2. Try to run the machine.
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/821 b/results/classifier/deepseek-2-tmp/output/graphic/821
deleted file mode 100644
index 89d0aef3..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/821
+++ /dev/null
@@ -1,2 +0,0 @@
-
-[SOLVED] ReactOS video problems...
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/835 b/results/classifier/deepseek-2-tmp/output/graphic/835
deleted file mode 100644
index 22426336..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/835
+++ /dev/null
@@ -1,10 +0,0 @@
-
-SDL display does not handle ps2 relative packets
-Description of problem:
-The main problem: while tracing relative events input_event_rel all mouse events are positive and seems to be the absolute x and y mouse position. When that happens ps2 sends a +x -y of a full 127 count.
-Steps to reproduce:
-1. Trace input_event_rel
-2. Observe that when moving the mouse the trace always shows positive values, that doesn't depend on what direction you move the mouse
-3. Observe that the xrel and yrel is more like absolute positions
-Additional information:
-I noticed searching on sdl2 docs and some issues related to SDL2 mouse events that when you do not specify SDL_HINT_MOUSE_RELATIVE_MODE_WARP weird things happens, i tried adding SDL_SetHint(SDL_HINT_MOUSE_RELATIVE_MODE_WARP, "1"); at the end of the sdl2 init function and the mouse events started to show normal values. I'm not sure if that's the correct way to solve the bug, but it seems to be.
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/839 b/results/classifier/deepseek-2-tmp/output/graphic/839
deleted file mode 100644
index d49afea7..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/839
+++ /dev/null
@@ -1,51 +0,0 @@
-
-qxl in COLO secondary node cause QEMU to segmentation fault
-Description of problem:
-After COLO checkpoint, the Secondary VM's qemu received segmentation fault while releasing qxl resources in interface_release_resource() routine.     
-i have used gdb and qemu trace to debug Secondary VM's qemu. the object 'qxl->last_release' is null and object 'ring->items[prod].el' != 0, it leads to null pointer dereference.     
-During COLO checkpoint,the Secondary VM's qemu has loaded Primary VM's qxl states,so i think it not need to release qxl resources.
-Steps to reproduce:
-1.Startup Primary VM and Secondary VM of COLO mode, and gdb to Secondary VM's qemu.     
-2.Connect to Primary VM's spice server.         
-3.Secondary VM's qemu will receiveing segmentation fault.
-Additional information:
-gdb to Secondary VM's qemu:     
-   ``` 
-Program received signal SIGSEGV, Segmentation fault.      
-[Switching to Thread 0x7ff9e3bff700 (LWP 44703)]     
-0x0000555555b2e8d6 in interface_release_resource (sin=0x555557d7c8a8, ext=...) at ../hw/display/qxl.c:783     
-783	        qxl->last_release->next = ext.info->id;    
-(gdb) bt   
-#0  0x0000555555b2e8d6 in interface_release_resource (sin=0x555557d7c8a8, ext=...) at ../hw/display/qxl.c:783    
-#1  0x00007fffd7751dd1 in red_drawable_unref () at /lib64/libspice-server.so.1    
-#2  0x00007fffd771eabe in drawable_unref () at /lib64/libspice-server.so.1    
-#3  0x00007fffd77206a7 in draw_until () at /lib64/libspice-server.so.1   
-#4  0x00007fffd771f7cd in display_channel_draw () at /lib64/libspice-server.so.1   
-#5  0x00007fffd7721b51 in display_channel_process_draw () at /lib64/libspice-server.so.1   
-#6  0x00007fffd7752142 in red_process_display () at /lib64/libspice-server.so.1
-#7  0x00007fffd77521fb in worker_source_dispatch () at /lib64/libspice-server.so.1
-#8  0x00007fffd6c2f049 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
-#9  0x00007fffd6c2f3a8 in g_main_context_iterate.isra.19 () at /lib64/libglib-2.0.so.0
-#10 0x00007fffd6c2f67a in g_main_loop_run () at /lib64/libglib-2.0.so.0
-#11 0x00007fffd775166a in red_worker_main () at /lib64/libspice-server.so.1
-#12 0x00007fffd5658dd5 in start_thread () at /lib64/libpthread.so.0
-#13 0x00007fffd538202d in clone () at /lib64/libc.so.6
-(gdb) frame 0
-#0  0x0000555555b2e8d6 in interface_release_resource (sin=0x555557d7c8a8, ext=...) at ../hw/display/qxl.c:783
-783	        qxl->last_release->next = ext.info->id;
-(gdb) print qxl->last_release
-$1 = (QXLReleaseInfo *) 0x0
-   ```
-
-qemu trace log:
-   ```
-44840@1643012769.363844:colo_send_message Send 'checkpoint-reply' message
-44840@1643012773.579053:colo_receive_message Receive 'vmstate-send' message
-44840@1643012773.978838:colo_receive_message Receive 'vmstate-size' message
-44840@1643012773.979041:colo_send_message Send 'vmstate-received' message
-44840@1643012774.180598:qxl_pre_load 0
-44703@1643012774.180660:qxl_ring_res_put 0 #res=20
-44840@1643012774.182627:qxl_post_load 0 native
-44840@1643012774.197993:colo_vm_state_change Change 'stop' => 'run'
-44840@1643012774.198030:colo_send_message Send 'vmstate-loaded' message
-   ```
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/865 b/results/classifier/deepseek-2-tmp/output/graphic/865
deleted file mode 100644
index a6793e3a..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/865
+++ /dev/null
@@ -1,46 +0,0 @@
-
-virtio-vga gtk,gl=on Black Screen or GLXGears picture
-Description of problem:
-Blank screen for tab with name `virtio-vga` on GTK interface, however, if I run `glxgears` before running the machine, I see the following image: 
-
-![image](/uploads/08d426ab748826e4f291e2e5ed838288/image.png)
-Steps to reproduce:
-1.Run the invocation command provided above
-
-#
-Additional information:
-The host when the problem is occurring is a Dell Precision 5110 laptop that have Hybrid Graphics. I am running X11 with nvidia as the main driver, I am not using nouveau, I am using the nvidia drivers installed by the debian package, here the corresponding information for the nvida card:
-
-```
-nvidia-smi
-```
-```
-Thu Feb 10 23:32:21 2022       
-+-----------------------------------------------------------------------------+
-| NVIDIA-SMI 460.91.03    Driver Version: 460.91.03    CUDA Version: 11.2     |
-|-------------------------------+----------------------+----------------------+
-| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
-| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
-|                               |                      |               MIG M. |
-|===============================+======================+======================|
-|   0  Quadro M1000M       On   | 00000000:01:00.0 Off |                  N/A |
-| N/A   44C    P8    N/A /  N/A |    846MiB /  2004MiB |      6%      Default |
-|                               |                      |                  N/A |
-+-------------------------------+----------------------+----------------------+
-                                                                               
-+-----------------------------------------------------------------------------+
-| Processes:                                                                  |
-|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
-|        ID   ID                                                   Usage      |
-|=============================================================================|
-|    0   N/A  N/A      6926      G   /usr/lib/xorg/Xorg                528MiB |
-|    0   N/A  N/A      7223      G   ...b/firefox-esr/firefox-esr      238MiB |
-|    0   N/A  N/A      7363      G   ...b/firefox-esr/firefox-esr        0MiB |
-|    0   N/A  N/A    276992      G   ...b/firefox-esr/firefox-esr        0MiB |
-|    0   N/A  N/A    282023      G   ...b/firefox-esr/firefox-esr        0MiB |
-|    0   N/A  N/A    282630      G   ...b/firefox-esr/firefox-esr        0MiB |
-|    0   N/A  N/A    322305      G   qemu-system-x86_64                 70MiB |
-+-----------------------------------------------------------------------------+
-```
-
-##
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/868 b/results/classifier/deepseek-2-tmp/output/graphic/868
deleted file mode 100644
index 9c3847b9..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/868
+++ /dev/null
@@ -1,16 +0,0 @@
-
-Graphic session freezes and logs out
-Description of problem:
-Graphic session freezes and logs out resetting user session. I've tried with both X and Wayland.
-The session does not last longer than 10-15 mins while working with:
-    VSCode
-    Firefox browser (no more than 5 open tabs - nothing heavy)
-
-If only using console, the problem does not seem occur, or maybe it takes longer, but haven't been able to reproduce it.
-Steps to reproduce:
-No steps. Just using common apps (vscode editor and ffox browser) for 10-15 mins causes the problem. Standard sites: gitlab, stacoverflow.
-Additional information:
-I used this configuration for +1 year without issues. I guess some updates to either Ubuntu or Lubuntu causes the problem.
-I deleted the guest VM and started with a fresh new Lubuntu 20.04 LTS AS IS no exttra software and the problem persists.
-
-Happy to provide any info you may require. I've looked around in the logs but couldnn't find anything useful.
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/87 b/results/classifier/deepseek-2-tmp/output/graphic/87
deleted file mode 100644
index 68b74a28..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/87
+++ /dev/null
@@ -1,2 +0,0 @@
-
-doesn't clear screen on boot
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/878019 b/results/classifier/deepseek-2-tmp/output/graphic/878019
deleted file mode 100644
index ccd39c53..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/878019
+++ /dev/null
@@ -1,11 +0,0 @@
-
-0.15.1 black screen and 100% cpu on start
-
-Trying the freshly compiled 0.15.1 (command line: "qemu"), the window stays black, it uses 100% cpu, and can't be killed with ctrl-c, has to be killed with killall -9.
-
-Strace shows it's waiting on a futex forever?
-
-Build config:
-./configure --prefix=/usr/local --interp-prefix=/usr/local/share/qemu \
---enable-mixemu --disable-brlapi --enable-io-thread --audio-drv-list="oss alsa sdl" \
---disable-opengl
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/886147 b/results/classifier/deepseek-2-tmp/output/graphic/886147
deleted file mode 100644
index 74830aa1..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/886147
+++ /dev/null
@@ -1,12 +0,0 @@
-
-Cannot make program Icon on my desktop with rightmouse key
-
-Howdy Xubuntu users
-
-How can I make a "starter program Icon on my desktop" with the mouse command right key.
-
-I do not seen the commands when I hit the right key of my mouse.
-
-Hope to see some info in my pigeon-hole.
-
-Spidey-Westland
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/891 b/results/classifier/deepseek-2-tmp/output/graphic/891
deleted file mode 100644
index 8f25c6ce..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/891
+++ /dev/null
@@ -1,2 +0,0 @@
-
-how to know  jpeg-wan-compression  is in force
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/90 b/results/classifier/deepseek-2-tmp/output/graphic/90
deleted file mode 100644
index d593a15a..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/90
+++ /dev/null
@@ -1,2 +0,0 @@
-
-vga/std lacks few wide screen modes.
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/901 b/results/classifier/deepseek-2-tmp/output/graphic/901
deleted file mode 100644
index 565d7d62..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/901
+++ /dev/null
@@ -1,11 +0,0 @@
-
-Bad screen behavior with adaptive sync
-Description of problem:
-KDE Wayland has freesync automatically enabled for full screen applications[[1]](https://wiki.archlinux.org/title/Variable_refresh_rate#Wayland_configuration). When using a VM in full screen mode, the screen starts having a strange behavior, like "blinking". I've tried windows 10, Linux Mint, MX Linux and Ubuntu 21.10.
-The problem disappears if using Xorg or disabling freesync trough KDE settings.
-Steps to reproduce:
-1. On KDE Wayland, check if freesync is activated in settings> screen> adaptive synchronization 
-2. Launch any vm in fuul screen mode
-3. Observe the screen
-Additional information:
-
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/918791 b/results/classifier/deepseek-2-tmp/output/graphic/918791
deleted file mode 100644
index 142a16d6..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/918791
+++ /dev/null
@@ -1,29 +0,0 @@
-
-qemu-kvm dies when using vmvga driver and unity in the guest
-
-12.04's qemu-kvm has been unstable for me and Marc Deslauriers and I figured out it has something to do with the interaction of qemu-kvm, unity and the vmvga driver. This is a regression over qemu-kvm in 11.10.
-
-TEST CASE:
-1. start a VM that uses unity (eg, 11.04, 11.10 or 12.04). My tests use unity-2d on an amd64 host and amd64 guests
-2. on 11.04 and 11.10, open empathy via the messaging indicator and click 'Chat'. On 12.04, open empathy via the messaging indicator and click 'Chat', close the empathy wizard, move the empathy window over the unity luancher (so it autohides), then do 'ctrl+alt+t' to open a terminal
-
-When the launcher tries to auto(un)hide, qemu-kvm dies with this:
-[10574.958149] do_general_protection: 132 callbacks suppressed
-[10574.958154] kvm[13192] general protection ip:7fab9680ea0f sp:7ffff4440148 error:0 in qemu-system-x86_64[7fab966c4000+2c9000]
-
-Relevant libvirt xml:
-    <video>
-      <model type='vmvga' vram='9216' heads='1'/>
-      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
-    </video>
-
-If I change to using 'cirrus', then qemu-kvm no longer crashes. Eg:
-    <video>
-      <model type='cirrus' vram='9216' heads='1'/>
-      <alias name='video0'/>
-      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
-    </video>
-
-The workaround is therefore to use the cirrus driver instead of vmvga, however being able to kill qemu-kvm in this manner is not ideal. Also, unfortunately unity-2d does not run with with cirrus driver under 11.04, so the security and SRU teams are unable to properly test updates in GUI applications under unity when using the current 12.04 qemu-kvm.
-
-I tried to report this via apport, but apport complained about a CRC error, so I could not.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/922076 b/results/classifier/deepseek-2-tmp/output/graphic/922076
deleted file mode 100644
index 57f5433c..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/922076
+++ /dev/null
@@ -1,14 +0,0 @@
-
-doesn't clear screen on boot
-
-When I start Linux in Qemu via "qemu -kernel /vmlinuz ...", opens Qemu window, it shows message "Starting Seabios (version 0.5.1-2010...)", and then Linux writes messages like "Loading, please wait..." on top of previous message!
-
-For example, I can see "Loading, please wait...on 0.5.1-2010...)"
-
-So, Qemu doesn't clean screan before booting OS.
-
-Moreover, when I start Linux via "qemu /disk-image", Qemu shows "Starting Seabios (version 0.5.1-2010...)", then switches to graphical mode, shows GRUB, then switches back to text mode and shows "Starting Seabios" again! And again Linux prints messages on top of Seabios messages, and we see a mix of symbols on screen.
-
-Also, I found another bug! I am learning now to write kernels. And I see that operator "*(char *)0xb8000 = 0" in C code of kernel doesn't clean first charaster of screen in Qemu in "-curses" mode! If I want to real clean this charaster, I must type "*(char *)0xb8000 = ' '".
-
-I attach a kernel (x86, multiboot) with this bug. Just type "make" (you need gcc) and "qemu -curses -kernel kernel". You will see that screen is not cleared, but kernel tries to clean it. If you change 0 to ' ', all will work!
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/926 b/results/classifier/deepseek-2-tmp/output/graphic/926
deleted file mode 100644
index bda9d38a..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/926
+++ /dev/null
@@ -1,2 +0,0 @@
-
-block-backend assertion with Cocoa UI
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/939437 b/results/classifier/deepseek-2-tmp/output/graphic/939437
deleted file mode 100644
index 6e732b5e..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/939437
+++ /dev/null
@@ -1,9 +0,0 @@
-
-spice is not supported by this qemu build.(ubuntu 12.04)
-
-$ kvm -spice port=5900,addr=127.0.0.1,disable-ticketing
-kvm: -spice port=5900,addr=127.0.0.1,disable-ticketing: there is no option group "spice"
-spice is not supported by this qemu build.
-
-$ kvm -version
-QEMU emulator version 1.0 (qemu-kvm-1.0), Copyright (c) 2003-2008 Fabrice Bellard
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/939443 b/results/classifier/deepseek-2-tmp/output/graphic/939443
deleted file mode 100644
index 2d4d6096..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/939443
+++ /dev/null
@@ -1,7 +0,0 @@
-
-qemu-system-x86_64 can no support 1366x768
-
-My laptop resolution is 1366x768, but can not support at -vga vmware the -vga std.
-
-$ kvm -version
-QEMU emulator version 1.0 (qemu-kvm-1.0), Copyright (c) 2003-2008 Fabrice Bellard
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/962 b/results/classifier/deepseek-2-tmp/output/graphic/962
deleted file mode 100644
index 897b0e87..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/962
+++ /dev/null
@@ -1,20 +0,0 @@
-
-Screenshot images are skewed
-Description of problem:
-1. Start a guest with SPICE
-2. Connect with a SPICE client
-3. Resize screen to a width that is not a multiple of 4 (e. g. 487x956)
-4. Take a screenshot
-
-The screenshot ppm file will contain the actual dimensions in the header, e. g.
-```
-P6
-487 956
-255
-```
-but the image data will contain more than that (e. g. 488 * 956 * 3 bytes).
-As a result, when displaying the image it appears skewed.
-Steps to reproduce:
-See above.
-Additional information:
-I'm not familiar with qemu code nor the pixman library, but I assume that in [this line](https://gitlab.com/qemu-project/qemu/-/blob/bc6ec396d471d9e4aae7e2ff8b72e11da9a97665/ui/console.c#L316) `get_stride` is wrong. Instead, it should write `width*3` bytes.
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/978 b/results/classifier/deepseek-2-tmp/output/graphic/978
deleted file mode 100644
index e0803182..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/978
+++ /dev/null
@@ -1,2 +0,0 @@
-
-Running QEMU with "-vga help" crashes if there is no default VGA card
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/986318 b/results/classifier/deepseek-2-tmp/output/graphic/986318
deleted file mode 100644
index 328b0617..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/986318
+++ /dev/null
@@ -1,6 +0,0 @@
-
-[sdl] Mouse grab breaks GNOME 3 screensaver unlock screen
-
-When the GNOME 3 screensaver activates with the mouse cursor over the SDL window, the screensaver will not unlock unless the gnome-shell process is killed and restarted manually. This seems to be related to the fact that the key strokes are grabbed by SDL, but the screensaver will not allow the Ctrl and Alt keys to be passed to QEMU to exit the mouse grab.
-
-Qemu-kvm 1.0.1, QEMU 1.0.1, kernel 3.2.15.
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/986770 b/results/classifier/deepseek-2-tmp/output/graphic/986770
deleted file mode 100644
index 8ea5bdd6..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/986770
+++ /dev/null
@@ -1,7 +0,0 @@
-
-Oops: spice configured but not active
-
-with latest qemu-kvm from git i have following problem:
-
- /usr/bin/kvm -daemonize -smp 4 -cpu host -vga qxl -enable-kvm -m 4096 -localtime -drive file=/home/sss/vm/win_xp/tmp_sys.img,if=virtio,media=disk,cache=none -drive file=/home/sss/vm/data.img,if=virtio,media=disk,cache=none -net nic,vlan=0,model=virtio,macaddr=6a:94:fc:2d:b9:04 -net tap,vlan=0,ifname=vtap0,script=no -usb -usbdevice tablet -name "Windows XP qt" -spice port=5934,addr=127.0.0.1,ipv4,playback-compression=off,disable-ticketing -monitor telnet::4448,server,nowait -device virtio-serial -chardev spicevmc,id=vdagent,name=vdagent -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 -balloon virtio
-qemu-system-x86_64: Oops: spice configured but not active
\ No newline at end of file
diff --git a/results/classifier/deepseek-2-tmp/output/graphic/996 b/results/classifier/deepseek-2-tmp/output/graphic/996
deleted file mode 100644
index 489b75c7..00000000
--- a/results/classifier/deepseek-2-tmp/output/graphic/996
+++ /dev/null
@@ -1,27 +0,0 @@
-
-Alt-TAB minimizes a full screen key-grabbed SDL window
-Description of problem:
-I was made aware of a case where a qemu seems to respond to a keyboard event `Alt+Tab` that isn't meant for it.
-
-When running in "SDL + full-screen + keys being grabbed by the guest" (see steps to reproduce below) one would expect `Alt+Tab` to do nothing on the host. But it does minimize the qemu window.
-
-This does not happen if:
-- using GTK instead of SDL
-- not being in full-screen mode
-
-No error message or warning appears while this happens.
-Steps to reproduce:
-You do not need and workload to run inside qemu for this
-
-1. `qemu-system-x86_64 -display sdl`
-2. Get your key grabbed: `click inside the window`
-3. Go full screen: `Alt+Ctrl+F`
-4. Press `Alt+Tab`
-5. Expected: nothing, Experienced: window minimizes
-
-Note: it even is reproducible if running the qemu binary from another system through SSH with X11 forwarding.
-
-P.S.
-I haven't had a chance yet to try qemu 7.0 from git, but will in a bit.
-It is easy enough to reproduce that I considered it worth filing without.
-For the start it would be great to hear if others see that as well or not. In case of the latter we'd have to compare library versions (currently I use sdl 2.0.20+dfsg-2build1).
author	Christian Krinitsin <mail@krinitsin.com>	2025-07-03 07:27:52 +0000
committer	Christian Krinitsin <mail@krinitsin.com>	2025-07-03 07:27:52 +0000
commit	d0c85e36e4de67af628d54e9ab577cc3fad7796a (patch)
tree	f8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/deepseek-2-tmp/output/graphic
parent	7f4364274750eb8cb39a3e7493132fca1c01232e (diff)
download	emulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz emulator-bug-study-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip