diff options
Diffstat (limited to 'results/classifier/gemma3:12b/graphic')
359 files changed, 8659 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/graphic/1020 b/results/classifier/gemma3:12b/graphic/1020 new file mode 100644 index 00000000..2f17ce59 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1020 @@ -0,0 +1,17 @@ + +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: + + +Same data, but in mode 0x05 + + +Same script as in bad display but run under 86Box + diff --git a/results/classifier/gemma3:12b/graphic/1022023 b/results/classifier/gemma3:12b/graphic/1022023 new file mode 100644 index 00000000..5e0e46e5 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1022023 @@ -0,0 +1,7 @@ + +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/gemma3:12b/graphic/1036 b/results/classifier/gemma3:12b/graphic/1036 new file mode 100644 index 00000000..be15bc6f --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1036 @@ -0,0 +1,16 @@ + +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/gemma3:12b/graphic/1037606 b/results/classifier/gemma3:12b/graphic/1037606 new file mode 100644 index 00000000..d7a75499 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1037606 @@ -0,0 +1,6 @@ + +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/gemma3:12b/graphic/104 b/results/classifier/gemma3:12b/graphic/104 new file mode 100644 index 00000000..c5c31cdf --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/104 @@ -0,0 +1,2 @@ + +Cursor jumps on shape change with vmware vga diff --git a/results/classifier/gemma3:12b/graphic/1054558 b/results/classifier/gemma3:12b/graphic/1054558 new file mode 100644 index 00000000..f3ee8d9f --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1054558 @@ -0,0 +1,7 @@ + +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/gemma3:12b/graphic/1062201 b/results/classifier/gemma3:12b/graphic/1062201 new file mode 100644 index 00000000..7d7b59f4 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1062201 @@ -0,0 +1,28 @@ + +qemu core dumped by kvm-spice + +Hi there, + +I am trying to use kvm-spice to start the qemu virtual machines. They start fine with the /usr/ bin/kvm command, but when I use the kvm-spice command the VM will not start and the core is dumped. + +Command I used: +kvm-spice -cpu host -enable-kvm -name win-7 -m 3000 -drive file=/var/vmmachines/win-7.img -net nic,model=rtl8139 -net user -localtime -usb -vga qxl -global qxl-vga.vram_size=67108864 -spice port=5901,disable-ticketing -boot d + + +Response: +do_spice_init: starting 0.10.1 +spice_server_add_interface: SPICE_INTERFACE_MIGRATION +spice_server_add_interface: SPICE_INTERFACE_KEYBOARD +spice_server_add_interface: SPICE_INTERFACE_MOUSE +spice_server_add_interface: SPICE_INTERFACE_QXL +red_worker_main: begin +display_channel_create: create display channel +cursor_channel_create: create cursor channel +kvm-spice: /build/buildd/qemu-linaro-1.0.50-2012.03/exec.c:2641: register_subpage: Assertion `existing.mr->subpage || existing.mr == &io_mem_unassigned' failed. +Aborted (core dumped) + + +I am running Ubuntu 12.04 sserver for this. Any information about this issue would be appreciated, i'm stuck on this one. + +Kind regards, +Tom \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1107 b/results/classifier/gemma3:12b/graphic/1107 new file mode 100644 index 00000000..357381ab --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1107 @@ -0,0 +1,25 @@ + +Virtual monitor heads are not "connected" until viewed in a front end +Description of problem: +When you attach a virtual GPU to a guest, qemu appears to only "attach" a virtual monitor to an output port when that virtual display is +viewed using the GUI. For example, when you boot using the above command line, there will be four displays in ```/sys/class/drm/``` on the guest, +```card0-Virtual-1``` through to ```card0-Virtual-4```. In each of these directories, there is an "enabled" file, which contains either +"enabled" or "disabled". These contain "disabled" until you switch tab/view to look at it using the GUI, at which point they change to "enabled". + +This causes a problem for us because Weston will not initialise displays that do not have a monitor attached, meaning the system we are trying +to boot fails because not all the Weston display surfaces are available. + +There does not appear to be a command line option to force virtual monitors to be attached to virtual displays immediately. Looking through the +Gtk user interface code (and the other front ends) there does not appear to be a call into the qemu core that requests the connection of a virtual +monitor to the virtual displays - my guess is that qemu only connects a monitor when a render request first happens (or similar), but I have not followed the code paths deeper than the source files in ```QEMU/ui/```. + +I also tried using the ```screengrab``` command to screenshot each head, but this does not need sufficient to cause the display to be marked +enabled in the guest. + +While we could possibly automate the GUI using some external tool, we ultimately need to run this in a CI environment using +```egl-headless``` or similar. +Steps to reproduce: +1. Launch qemu with virtio-gpu-gl setting max_outputs > 1 +2. On guest, ```cat /sys/drm/class/card0-Virtual-2``` - it reads "disabled" +3. On host, switch the view to look at the second display ("virtio-gpu-gl-pci.1") +4. On guest, ```cat /sys/drm/class/card0-Virtual-2``` - it now reads "enabled" diff --git a/results/classifier/gemma3:12b/graphic/1109 b/results/classifier/gemma3:12b/graphic/1109 new file mode 100644 index 00000000..0b2e250a --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1109 @@ -0,0 +1,43 @@ + +rpi3b frame buffer segfault +Description of problem: +I'm compiling a series of bare metal Raspberry Pi labs for the RPi 3B. One particular lab that I tried to compile and run, which makes use of the framebuffer, causes QEMU to segfault when trying to draw to the framebuffer. It looks like the value of `dst` passed into `draw_line_s16` is bogus and this causes the segfault. I'm not familiar enough with the code in QEMU to immediately know why `dst` is bogus. + +The lab I'm trying to run (the code compiled to `kernel8.img`) is here: https://github.com/bztsrc/raspi3-tutorial/tree/master/09_framebuffer + +A gdb stacktrace of the segfault is here: + +``` +Thread 1 "qemu-system-aar" received signal SIGSEGV, Segmentation fault. +0x00005555559580c0 in rgb_to_pixel32 (b=<optimized out>, g=<optimized out>, r=<optimized out>) + at /home/rhett/qemu/include/ui/pixel_ops.h:46 +46 return (r << 16) | (g << 8) | b; +(gdb) bt +#0 0x00005555559580c0 in rgb_to_pixel32 (b=<optimized out>, g=<optimized out>, r=<optimized out>) + at /home/rhett/qemu/include/ui/pixel_ops.h:46 +#1 draw_line_src16 + (opaque=opaque@entry=0x7fffe84d1c30, dst=dst@entry=0x7fffe8235010 <error: Cannot access memory at address 0x7fffe8235010>, src=0x7fff94300004 "", src@entry=0x7fff94300000 "", width=639, width@entry=640, deststep=deststep@entry=0) at ../hw/display/bcm2835_fb.c:131 +#2 0x0000555555953977 in framebuffer_update_display + (ds=<optimized out>, mem_section=<optimized out>, cols=640, rows=480, src_width=1280, dest_row_pitch=2560, dest_col_pitch=0, invalidate=1, fn=0x555555957fe0 <draw_line_src16>, opaque=0x7fffe84d1c30, first_row=0x7fffffffdb90, last_row=0x7fffffffdb94) + at ../hw/display/framebuffer.c:107 +#3 0x0000555555957eeb in fb_update_display (opaque=0x7fffe84d1c30) at ../hw/display/bcm2835_fb.c:203 +#4 0x00005555558a9146 in graphic_hw_update (con=0x555556b9bc00) at ../ui/console.c:230 +#5 0x00005555558a7fea in dpy_refresh (s=0x5555571c6aa0) at ../ui/console.c:1842 +#6 gui_update (opaque=opaque@entry=0x5555571c6aa0) at ../ui/console.c:165 +#7 0x0000555556068ecd in timerlist_run_timers (timer_list=0x555556b15350) at ../util/qemu-timer.c:576 +#8 timerlist_run_timers (timer_list=0x555556b15350) at ../util/qemu-timer.c:501 +#9 0x00005555560690c0 in qemu_clock_run_timers (type=<optimized out>) at ../util/qemu-timer.c:672 +#10 qemu_clock_run_all_timers () at ../util/qemu-timer.c:672 +#11 0x0000555556064bf6 in main_loop_wait (nonblocking=nonblocking@entry=0) at ../util/main-loop.c:607 +#12 0x0000555555b0a4f9 in qemu_main_loop () at ../softmmu/runstate.c:726 +#13 0x000055555589ec74 in qemu_main (envp=0x0, argv=<optimized out>, argc=<optimized out>) at ../softmmu/main.c:36 +#14 main (argc=<optimized out>, argv=<optimized out>) at ../softmmu/main.c:45 +``` +Steps to reproduce: +1. Clone the git repo for the labs I linked above +2. `cd raspi3-tutorial/09_framebuffer` +3. `make` +4. `make run` +5. Segfault + +I have found this on QEMU 5.2, QEMU 7.0, and the bleeding edge of the github repo diff --git a/results/classifier/gemma3:12b/graphic/1110 b/results/classifier/gemma3:12b/graphic/1110 new file mode 100644 index 00000000..319b3f77 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1110 @@ -0,0 +1,4 @@ + +Add vhost-user-gpu support for cross architecture emulation +Additional information: +host:Android 12 with Linux kernel 4.14.186+ diff --git a/results/classifier/gemma3:12b/graphic/1119861 b/results/classifier/gemma3:12b/graphic/1119861 new file mode 100644 index 00000000..79aae87c --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1119861 @@ -0,0 +1,20 @@ + +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/gemma3:12b/graphic/1135567 b/results/classifier/gemma3:12b/graphic/1135567 new file mode 100644 index 00000000..baccd786 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1135567 @@ -0,0 +1,24 @@ + +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/gemma3:12b/graphic/1157368 b/results/classifier/gemma3:12b/graphic/1157368 new file mode 100644 index 00000000..afbaaefa --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1157368 @@ -0,0 +1,8 @@ + +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/gemma3:12b/graphic/1172 b/results/classifier/gemma3:12b/graphic/1172 new file mode 100644 index 00000000..a0634e8d --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1172 @@ -0,0 +1,60 @@ + +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/gemma3:12b/graphic/1177774 b/results/classifier/gemma3:12b/graphic/1177774 new file mode 100644 index 00000000..f96db5b1 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1177774 @@ -0,0 +1,24 @@ + +Gtk+ frontend fails to build + +The QEMU Gtk+ frontend fails to build.. + +cc -I/home/ports/pobj/qemu-1.5.0-rc0/qemu-1.5.0-rc0/tcg -I/home/ports/pobj/qemu-1.5.0-rc0/qemu-1.5.0-rc0/tcg/i386 -I. -I/home/ports/pobj/qemu-1.5.0-rc0/qemu-1.5.0-rc0 -I/home/ports/pobj/qemu-1.5.0-rc0/qemu-1.5.0-rc0/include -Iui -Iui -fPIE -DPIE -m64 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -I/usr/local/include -I/usr/X11R6/include -Wno-redundant-decls -DTIME_MAX=INT_MAX -Wendif-labels -Wmissing-include-dirs -Wnested-externs -Wformat-security -Wformat-y2k -Winit-self -Wold-style-definition -fstack-protector-all -I/usr/local/include -I/usr/local/include/p11-kit-1 -I/usr/include -I/usr/local/include/libpng -I/usr/local/include -I/usr/include -I/usr/X11R6/include/pixman-1 -I/home/ports/pobj/qemu-1.5.0-rc0/qemu-1.5.0-rc0/dtc/libfdt -pthread -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include -I/home/ports/pobj/qemu-1.5.0-rc0/qemu-1.5.0-rc0/tests -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/pango-1.0 -I/usr/local/include/gio-unix-2.0/ -I/usr/X11R6/include -I/usr/local/include/cairo -I/usr/local/include/atk-1.0 -I/usr/X11R6/include/pixman-1 -I/usr/local/include/libpng -I/usr/local/include/gdk-pixbuf-2.0 -I/usr/local/include/harfbuzz -pthread -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include -I/usr/X11R6/include/freetype2 -I/usr/local/include/vte-0.0 -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/pango-1.0 -I/usr/X11R6/include -I/usr/local/include/atk-1.0 -I/usr/local/include/gdk-pixbuf-2.0 -I/usr/local/include/harfbuzz -I/usr/local/include/gio-unix-2.0/ -pthread -I/usr/local/include/cairo -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include -I/usr/X11R6/include/pixman-1 -I/usr/X11R6/include/freetype2 -I/usr/local/include/libpng -MMD -MP -MT ui/gtk.o -MF ui/gtk.d -O2 -pipe -c -o ui/gtk.o ui/gtk.c +In file included from /usr/local/include/gtk-2.0/gtk/gtk.h:234, + from ui/gtk.c:44: +/usr/local/include/gtk-2.0/gtk/gtkitemfactory.h:47: warning: function declaration isn't a prototype +ui/gtk.c:58:17: warning: pty.h: No such file or directory +ui/gtk.c: In function 'gd_vc_init': +ui/gtk.c:1142: error: storage size of 'tty' isn't known +ui/gtk.c:1162: warning: implicit declaration of function 'openpty' +ui/gtk.c:1162: warning: nested extern declaration of 'openpty' +ui/gtk.c:1166: warning: implicit declaration of function 'tcgetattr' +ui/gtk.c:1166: warning: nested extern declaration of 'tcgetattr' +ui/gtk.c:1167: warning: implicit declaration of function 'cfmakeraw' +ui/gtk.c:1167: warning: nested extern declaration of 'cfmakeraw' +ui/gtk.c:1168: warning: implicit declaration of function 'tcsetattr' +ui/gtk.c:1168: warning: nested extern declaration of 'tcsetattr' +ui/gtk.c:1168: error: 'TCSAFLUSH' undeclared (first use in this function) +ui/gtk.c:1168: error: (Each undeclared identifier is reported only once +ui/gtk.c:1168: error: for each function it appears in.) +ui/gtk.c:1142: warning: unused variable 'tty' \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1186935 b/results/classifier/gemma3:12b/graphic/1186935 new file mode 100644 index 00000000..6dfa4457 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1186935 @@ -0,0 +1,15 @@ + +[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/gemma3:12b/graphic/1187319 b/results/classifier/gemma3:12b/graphic/1187319 new file mode 100644 index 00000000..52d390e9 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1187319 @@ -0,0 +1,9 @@ + +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/gemma3:12b/graphic/1191457 b/results/classifier/gemma3:12b/graphic/1191457 new file mode 100644 index 00000000..9f99ae5e --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1191457 @@ -0,0 +1,4 @@ + +broken build without sdl + +vl.c fails to build if not using sdl since no_frame variable is only defined if CONFIG_SDL, while QEMU_OPTION_no_frame tries to set it without ifdef \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1193555 b/results/classifier/gemma3:12b/graphic/1193555 new file mode 100644 index 00000000..eaeb2199 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1193555 @@ -0,0 +1,12 @@ + +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/gemma3:12b/graphic/1193564 b/results/classifier/gemma3:12b/graphic/1193564 new file mode 100644 index 00000000..2416f3ea --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1193564 @@ -0,0 +1,4 @@ + +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/gemma3:12b/graphic/1209 b/results/classifier/gemma3:12b/graphic/1209 new file mode 100644 index 00000000..d3f71065 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1209 @@ -0,0 +1,6 @@ + +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/gemma3:12b/graphic/1210 b/results/classifier/gemma3:12b/graphic/1210 new file mode 100644 index 00000000..98779522 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1210 @@ -0,0 +1,9 @@ + +qemu segfaults on PNG screendump +Description of problem: +Attempting to produce a screendump via the monitor in the PNG format leads to a segmentation fault (but the screen dump is produced correctly). +Steps to reproduce: +1. Launch QEMU +2. Go to the monitoring screen () +3. execute the command: `screendump /tmp/dump.png -f png` +4. observe the crash (segfault) diff --git a/results/classifier/gemma3:12b/graphic/1216368 b/results/classifier/gemma3:12b/graphic/1216368 new file mode 100644 index 00000000..e91a4c10 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1216368 @@ -0,0 +1,18 @@ + +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/gemma3:12b/graphic/1228 b/results/classifier/gemma3:12b/graphic/1228 new file mode 100644 index 00000000..83ac503a --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1228 @@ -0,0 +1,44 @@ + +-display curses only recognizes escape characters if pressed very quickly +Description of problem: +The system start and runs perfectly fine, but when I try to exit the escape commands does not seem to work. + +I have tried all the ones from here: +https://www.qemu.org/docs/master/system/keys.html +https://www.qemu.org/docs/master/system/mux-chardev.html + +When using the graphical display, the escape characters works as expected but when using -display curses, they do not. +Steps to reproduce: +1. Start qemu with the command provided +2. Try to exit using ctrl + x a - Not working +3. Try to exit using alt + 2 - Not working + +The same issues occurs when running qemu on a Linux machine (Ubunt) via Visual Studio Code / ssh. + +I'm guessing this is a macOS specific issue or maybe something to do with my Locale (sv-SE). +Additional information: +Linux 0.01 build: +https://github.com/mariuz/linux-0.01 + +**Tests using showkey** + +Alt + 2 from mobile ssh client (Terminus) -> Ubuntu machine +``` +^[2 27 0033 0x1b + 50 0062 0x32 +``` + +Option + 2 from macOS Terminal + ssh -> Ubuntu machine +``` +@ 64 0100 0x40 +``` + +Esc + 2 from macOS Terminal + ssh -> Ubuntu machine +``` +^[ 27 0033 0x1b +2 50 0062 0x32 +``` + +**Update** + +It seems to work if I press ESC + 2 at exactly the same time. diff --git a/results/classifier/gemma3:12b/graphic/1239008 b/results/classifier/gemma3:12b/graphic/1239008 new file mode 100644 index 00000000..c372a178 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1239008 @@ -0,0 +1,21 @@ + +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/gemma3:12b/graphic/1243639 b/results/classifier/gemma3:12b/graphic/1243639 new file mode 100644 index 00000000..4586431f --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1243639 @@ -0,0 +1,63 @@ + +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/gemma3:12b/graphic/1249 b/results/classifier/gemma3:12b/graphic/1249 new file mode 100644 index 00000000..a368437f --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1249 @@ -0,0 +1,2 @@ + +qemu-edid Division By Zero -- by misuse of the option "-d" diff --git a/results/classifier/gemma3:12b/graphic/1257334 b/results/classifier/gemma3:12b/graphic/1257334 new file mode 100644 index 00000000..463091c2 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1257334 @@ -0,0 +1,4 @@ + +diffuse handling of image creation from another path + +see attachement! \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1274170 b/results/classifier/gemma3:12b/graphic/1274170 new file mode 100644 index 00000000..928039cc --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1274170 @@ -0,0 +1,4 @@ + +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/gemma3:12b/graphic/1276 b/results/classifier/gemma3:12b/graphic/1276 new file mode 100644 index 00000000..125044f1 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1276 @@ -0,0 +1,16 @@ + +[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/gemma3:12b/graphic/128 b/results/classifier/gemma3:12b/graphic/128 new file mode 100644 index 00000000..71de6e7a --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/128 @@ -0,0 +1,2 @@ + +man page is missing suboptions for "-display" diff --git a/results/classifier/gemma3:12b/graphic/1285 b/results/classifier/gemma3:12b/graphic/1285 new file mode 100644 index 00000000..92783a11 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1285 @@ -0,0 +1,21 @@ + +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/gemma3:12b/graphic/1288 b/results/classifier/gemma3:12b/graphic/1288 new file mode 100644 index 00000000..37ac4c0d --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1288 @@ -0,0 +1,10 @@ + +GPU passing through guest crashes +Description of problem: +First and foremost, I don't know if this is a QEMU, KVM or GPU driver issue. +I began emailing libvirt project and they advised me to contact you, then KVM and then GPU driver developer(NVIDIA). +Host is crashing from time to time. I have guest's kernel dumps(~2GB each). +Steps to reproduce: +Unfortunately, I don't have steps to reproduce. +Additional information: +I'm aware I'm not running the latest qmeu version but I'm willing to install developer version and try to reproduce or test patch if developer requires it. diff --git a/results/classifier/gemma3:12b/graphic/1290558 b/results/classifier/gemma3:12b/graphic/1290558 new file mode 100644 index 00000000..281b2e87 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1290558 @@ -0,0 +1,14 @@ + +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/gemma3:12b/graphic/1294898 b/results/classifier/gemma3:12b/graphic/1294898 new file mode 100644 index 00000000..f64f223b --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1294898 @@ -0,0 +1,79 @@ + +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/gemma3:12b/graphic/1301 b/results/classifier/gemma3:12b/graphic/1301 new file mode 100644 index 00000000..134f904f --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1301 @@ -0,0 +1,18 @@ + +qemu-system-ppc in Homebrew on macOS has mouse warps and ghost clicks +Description of problem: +The QEMU version in Homebrew (Intel macOS host, PowerPC Mac OS 9 guest) has random warping of the mouse cursor as well as ghost clicks which begin as soon as the operating system finishes loading. Video demonstration: https://youtu.be/DjXO0hwHArk + +Notably, the exact same version of the QEMU source code with the same build arguments built *outside* of the Homebrew environment does not have this issue. I copied the following arguments from the QEMU Homebrew formula, and tried building QEMU on the command line: + + ../configure --prefix=/Users/josh/Desktop/qemu-homebrew-build --cc=clang --host-cc=clang --disable-bsd-user --disable-guest-agent --enable-capstone --enable-curses --enable-libssh --enable-slirp --enable-vde --enable-virtfs --enable-zstd --extra-cflags=-DNCURSES_WIDECHAR=1 --disable-sdl --smbd=/usr/local/sbin/samba-dot-org-smbd --disable-gtk --enable-cocoa --target-list=ppc-softmmu + +This creates a `qemu-system-ppc` binary which is 15MB in size and works perfectly. By contrast, the exact same build commands within the Homebrew build process create a binary which is 10MB in size (!!!) and has this mouse warping and ghost clicks issue. This occurs whether QEMU was installed with `brew install qemu` or `brew install --build-from-source qemu`. Providing the `--HEAD` argument also makes no difference. The list of linked libraries (via `otool -L qemu-system-ppc`) is the same between the two versions. + +The only way I can reproduce this issue outside of Homebrew is to dump the Homebrew environmental variables (with `env`) to a file and then set up those same environmental variables with the `source` command, after which the resulting `qemu-system-ppc` binary is now 10MB in size like the Homebrew version, and has the mouse issue like the Homebrew version. I'll attach the file with the Homebrew environmental variables. It seems that the issue must lie somewhere in there, but I'm really pushing the limits of my abilities, so I could definitely use some ideas and/or insights. +Steps to reproduce: +1. Install QEMU via `brew install qemu` +2. Start QEMU with an image of Mac OS 9 +3. After the boot process completes, the issue manifests +Additional information: +[Homebrew_ENV_Variables.txt](/uploads/2393aed8f29fa9c32bcaca44281bd2a5/Homebrew_ENV_Variables.txt) diff --git a/results/classifier/gemma3:12b/graphic/1308 b/results/classifier/gemma3:12b/graphic/1308 new file mode 100644 index 00000000..7ac8c857 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1308 @@ -0,0 +1,2 @@ + +Qemu headless build process is stopped, complaining about a missing pixman.h diff --git a/results/classifier/gemma3:12b/graphic/1315257 b/results/classifier/gemma3:12b/graphic/1315257 new file mode 100644 index 00000000..3bc6f658 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1315257 @@ -0,0 +1,51 @@ + +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/gemma3:12b/graphic/1326533 b/results/classifier/gemma3:12b/graphic/1326533 new file mode 100644 index 00000000..2369b574 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1326533 @@ -0,0 +1,20 @@ + +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/gemma3:12b/graphic/1329 b/results/classifier/gemma3:12b/graphic/1329 new file mode 100644 index 00000000..d835525c --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1329 @@ -0,0 +1,13 @@ + +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/gemma3:12b/graphic/1335 b/results/classifier/gemma3:12b/graphic/1335 new file mode 100644 index 00000000..95f8e3e1 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1335 @@ -0,0 +1,2 @@ + +hot to dump bitmap to disk diff --git a/results/classifier/gemma3:12b/graphic/1336801 b/results/classifier/gemma3:12b/graphic/1336801 new file mode 100644 index 00000000..85cc0610 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1336801 @@ -0,0 +1,13 @@ + +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/gemma3:12b/graphic/1338591 b/results/classifier/gemma3:12b/graphic/1338591 new file mode 100644 index 00000000..57ad5e4f --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1338591 @@ -0,0 +1,20 @@ + +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/gemma3:12b/graphic/1346 b/results/classifier/gemma3:12b/graphic/1346 new file mode 100644 index 00000000..f1ede425 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1346 @@ -0,0 +1,36 @@ + +simulate x86_64 virtio-gpu-gl qemu report error +Description of problem: +when I run the below command, it can run ok, and myos can get the virtio-gpu feature,but it less 3d feature. + ``` + ./qemu-system-x86_64 -nographic -M q35 -m 1024 -cpu Nehalem -smp 8 -kernel myos -device virtio-gpu + ``` +so I delete ```-nographic``` and modify the device to : +``` +-device virtio-gpu-gl -display sdl,gl=on +``` +but qemu tells me ERROR: +``` +qemu-system-x86_64: ../ui/console-gl.c:105: surface_gl_update_texture: Assertion `gls' failed. +``` +Additional information: +I modify the code qemu/ui/sdl2-gl.c function sdl2_gl_switch(): + +` +#if 0 +if (is_placeholder(new_surface) && qemu_console_get_index(dcl->con)) { + qemu_gl_fini_shader(scon->gls); + scon->gls = NULL; + sdl2_window_destroy(scon); + return; + } +#endif +` +and, qemu can run myos with ```-nographic```, and i can get 3d feature: + ``` + ./qemu-system-x86_64 -nographic -M q35 -m 1024 -cpu Nehalem -smp 8 -kernel myos -device virtio-gpu-gl -display sdl,gl=on + ``` + +I think there is something bug. + +thanks diff --git a/results/classifier/gemma3:12b/graphic/1352130 b/results/classifier/gemma3:12b/graphic/1352130 new file mode 100644 index 00000000..47957be1 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1352130 @@ -0,0 +1,31 @@ + +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/gemma3:12b/graphic/1357226 b/results/classifier/gemma3:12b/graphic/1357226 new file mode 100644 index 00000000..79bf5302 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1357226 @@ -0,0 +1,12 @@ + +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/gemma3:12b/graphic/1361618 b/results/classifier/gemma3:12b/graphic/1361618 new file mode 100644 index 00000000..bf90c3c3 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1361618 @@ -0,0 +1,13 @@ + +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/gemma3:12b/graphic/1368791 b/results/classifier/gemma3:12b/graphic/1368791 new file mode 100644 index 00000000..1f001a6c --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1368791 @@ -0,0 +1,13 @@ + +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/gemma3:12b/graphic/1374905 b/results/classifier/gemma3:12b/graphic/1374905 new file mode 100644 index 00000000..a492dbb2 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1374905 @@ -0,0 +1,28 @@ + +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/gemma3:12b/graphic/1379688 b/results/classifier/gemma3:12b/graphic/1379688 new file mode 100644 index 00000000..97708624 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1379688 @@ -0,0 +1,6 @@ + +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/gemma3:12b/graphic/1392468 b/results/classifier/gemma3:12b/graphic/1392468 new file mode 100644 index 00000000..33f87b60 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1392468 @@ -0,0 +1,6 @@ + +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/gemma3:12b/graphic/1399957 b/results/classifier/gemma3:12b/graphic/1399957 new file mode 100644 index 00000000..9dc807ab --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1399957 @@ -0,0 +1,13 @@ + +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/gemma3:12b/graphic/1405176 b/results/classifier/gemma3:12b/graphic/1405176 new file mode 100644 index 00000000..6fa60035 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1405176 @@ -0,0 +1,6 @@ + +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/gemma3:12b/graphic/1412098 b/results/classifier/gemma3:12b/graphic/1412098 new file mode 100644 index 00000000..05ddc9b4 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1412098 @@ -0,0 +1,15 @@ + +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/gemma3:12b/graphic/1415 b/results/classifier/gemma3:12b/graphic/1415 new file mode 100644 index 00000000..f5b38ba3 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1415 @@ -0,0 +1,90 @@ + +Abort in xlnx_dp_change_graphic_fmt() +Description of problem: +xlnx_dp_change_graphic_fmt() will directly abort if either graphic format or the +video format is not supported. + +Replacing abort() in xlnx_dp_change_graphic_fmt() to `return` might be OK but I +am not sure what side effect there is. +Steps to reproduce: +``` +export QEMU=/path/to/to/qemu-system-aarch64 + +cat << EOF | $QEMU \ +-machine xlnx-zcu102 -monitor none -serial none \ +-display none -nodefaults -qtest stdio +writel 0xfd4ab000 0xcf6e998 +EOF +``` +Additional information: +``` +==20455==WARNING: ASan doesn't fully support makecontext/swapcontext functions and may produce false positives in some cases! +INFO: found LLVMFuzzerCustomMutator (0x564934146c90). Disabling -len_control by default. +INFO: Running with entropic power schedule (0xFF, 100). +INFO: Seed: 4022227410 +INFO: Loaded 1 modules (618619 inline 8-bit counters): 618619 [0x5649372a5000, 0x56493733c07b), +INFO: Loaded 1 PC tables (618619 PCs): 618619 [0x564936933f40,0x5649372a46f0), +./qemu-videzzo-aarch64-target-videzzo-fuzz-xlnx-dp: Running 1 inputs 1 time(s) each. +INFO: Reading pre_seed_input if any ... +INFO: Executing pre_seed_input if any ... +INFO: -max_len is not provided; libFuzzer will not generate inputs larger than 4096 bytes +Matching objects by name , *.core*, *.v_blend*, *.av_buffer_manager*, *.audio* +This process will fuzz the following MemoryRegions: + * xlnx.v-dp.audio[0] (size 50) + * xlnx.v-dp.av_buffer_manager[0] (size 238) + * xlnx.v-dp.core[0] (size 3b0) + * xlnx.v-dp.v_blend[0] (size 1e0) +This process will fuzz through the following interfaces: + * clock_step, EVENT_TYPE_CLOCK_STEP, 0xffffffff +0xffffffff, 255,255 + * xlnx.v-dp.core, EVENT_TYPE_MMIO_READ, 0xfd4a0000 +0x3b0, 4,4 + * xlnx.v-dp.core, EVENT_TYPE_MMIO_WRITE, 0xfd4a0000 +0x3b0, 4,4 + * xlnx.v-dp.v_blend, EVENT_TYPE_MMIO_READ, 0xfd4aa000 +0x1e0, 4,4 + * xlnx.v-dp.v_blend, EVENT_TYPE_MMIO_WRITE, 0xfd4aa000 +0x1e0, 4,4 + * xlnx.v-dp.av_buffer_manager, EVENT_TYPE_MMIO_READ, 0xfd4ab000 +0x238, 4,4 + * xlnx.v-dp.av_buffer_manager, EVENT_TYPE_MMIO_WRITE, 0xfd4ab000 +0x238, 4,4 + * xlnx.v-dp.audio, EVENT_TYPE_MMIO_READ, 0xfd4ac000 +0x50, 1,4 + * xlnx.v-dp.audio, EVENT_TYPE_MMIO_WRITE, 0xfd4ac000 +0x50, 1,4 +INFO: A corpus is not provided, starting from an empty corpus +#2 INITED cov: 3 ft: 4 corp: 1/1b exec/s: 0 rss: 489Mb +Running: crash-8b178268936b24c569a421d702ef5b6d911c99e7 +aarch64: xlnx_dp_change_graphic_fmt: unsupported graphic format 2304 +==20455== ERROR: libFuzzer: deadly signal + #0 0x56492f51f10e in __sanitizer_print_stack_trace /root/llvm-project/compiler-rt/lib/asan/asan_stack.cpp:86:3 + #1 0x56492f46dd81 in fuzzer::PrintStackTrace() /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerUtil.cpp:210:38 + #2 0x56492f446cb6 in fuzzer::Fuzzer::CrashCallback() (.part.0) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:236:18 + #3 0x56492f446d82 in fuzzer::Fuzzer::CrashCallback() /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:208:1 + #4 0x56492f446d82 in fuzzer::Fuzzer::StaticCrashSignalCallback() /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:207:19 + #5 0x7f7a315a641f (/lib/x86_64-linux-gnu/libpthread.so.0+0x1441f) + #6 0x7f7a313b800a in __libc_signal_restore_set /build/glibc-SzIz7B/glibc-2.31/signal/../sysdeps/unix/sysv/linux/internal-signals.h:86:3 + #7 0x7f7a313b800a in raise /build/glibc-SzIz7B/glibc-2.31/signal/../sysdeps/unix/sysv/linux/raise.c:48:3 + #8 0x7f7a31397858 in abort /build/glibc-SzIz7B/glibc-2.31/stdlib/abort.c:79:7 + #9 0x56492f54f65a in __wrap_abort /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/less_crashes_wrappers.c:24:12 + #10 0x56492fe7e0d7 in xlnx_dp_change_graphic_fmt /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/display/xlnx_dp.c:644:9 + #11 0x56492fe7be58 in xlnx_dp_avbufm_write /root/videzzo/videzzo_qemu/qemu/build-san-6/../hw/display/xlnx_dp.c:1046:9 + #12 0x5649330fa313 in memory_region_write_accessor /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/memory.c:492:5 + #13 0x5649330f9c51 in access_with_adjusted_size /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/memory.c:554:18 + #14 0x5649330f8576 in memory_region_dispatch_write /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/memory.c:1514:16 + #15 0x56493318672e in flatview_write_continue /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/physmem.c:2825:23 + #16 0x56493317486b in flatview_write /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/physmem.c:2867:12 + #17 0x564933174328 in address_space_write /root/videzzo/videzzo_qemu/qemu/build-san-6/../softmmu/physmem.c:2963:18 + #18 0x56492f55f0cb in qemu_writel /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/videzzo_qemu.c:1088:5 + #19 0x56492f55d544 in dispatch_mmio_write /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/videzzo_qemu.c:1229:28 + #20 0x56493414264f in videzzo_dispatch_event /root/videzzo/videzzo.c:1122:5 + #21 0x5649341399cb in __videzzo_execute_one_input /root/videzzo/videzzo.c:272:9 + #22 0x5649341398a0 in videzzo_execute_one_input /root/videzzo/videzzo.c:313:9 + #23 0x56492f56610c in videzzo_qemu /root/videzzo/videzzo_qemu/qemu/build-san-6/../tests/qtest/videzzo/videzzo_qemu.c:1504:12 + #24 0x564934146f32 in LLVMFuzzerTestOneInput /root/videzzo/videzzo.c:1891:18 + #25 0x56492f447826 in fuzzer::Fuzzer::ExecuteCallback(unsigned char*, unsigned long) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerLoop.cpp:594:17 + #26 0x56492f42a454 in fuzzer::RunOneTest(fuzzer::Fuzzer*, char const*, unsigned long) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:323:21 + #27 0x56492f4353fe in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char*, unsigned long)) /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerDriver.cpp:885:19 + #28 0x56492f4219e6 in main /root/llvm-project/compiler-rt/lib/fuzzer/FuzzerMain.cpp:20:30 + #29 0x7f7a31399082 in __libc_start_main /build/glibc-SzIz7B/glibc-2.31/csu/../csu/libc-start.c:308:16 + #30 0x56492f421a3d in _start (/root/videzzo/videzzo_qemu/out-san/qemu-videzzo-aarch64-target-videzzo-fuzz-xlnx-dp+0x3291a3d) + +NOTE: libFuzzer has rudimentary signal handlers. + Combine libFuzzer with AddressSanitizer or similar for better crash reports. +SUMMARY: libFuzzer: deadly signal +MS: 0 ; base unit: 0000000000000000000000000000000000000000 +0x0,0xc,0x1c,0xb0,0x4a,0xfd,0x0,0x0,0x0,0x0,0x4,0x0,0x0,0x0,0x4,0x2,0x48,0x40,0x1,0x0,0x0,0x0,0x0,0x0,0x0,0xa,0x20,0xa1,0x4a,0xfd,0x0,0x0,0x0,0x0,0x4,0x0,0x0,0x0,0x0,0xe,0x8,0xc0,0x4a,0xfd,0x0,0x0,0x0,0x0,0x2,0x0,0x0,0x0,0x0,0x8,0x0,0x0,0x4a,0xfd,0x0,0x0,0x0,0x0,0x4,0x0,0x0,0x0,0x4,0x2,0x3e,0xc6,0x1,0x0,0x0,0x0,0x0,0x0,0x0,0xc,0x78,0xb1,0x4a,0xfd,0x0,0x0,0x0,0x0,0x4,0x0,0x0,0x0,0x1,0x9,0x4,0x2,0x4a,0xfd,0x0,0x0,0x0,0x0,0x4,0x0,0x0,0x0,0xc2,0x1b,0xe,0x7b,0x0,0x0,0x0,0x0,0x1,0xb,0x84,0xa1,0x4a,0xfd,0x0,0x0,0x0,0x0,0x4,0x0,0x0,0x0,0xd8,0x1f,0x9a,0x30,0x0,0x0,0x0,0x0,0x0,0x8,0x70,0x0,0x4a,0xfd,0x0,0x0,0x0,0x0,0x4,0x0,0x0,0x0,0x1,0x9,0xec,0x2,0x4a,0xfd,0x0,0x0,0x0,0x0,0x4,0x0,0x0,0x0,0x50,0x62,0xd6,0x13,0x0,0x0,0x0,0x0,0x0,0xa,0x18,0xa0,0x4a,0xfd,0x0,0x0,0x0,0x0,0x4,0x0,0x0,0x0,0x1,0xd,0x0,0xb0,0x4a,0xfd,0x0,0x0,0x0,0x0,0x4,0x0,0x0,0x0,0x98,0xe9,0xf6,0xc,0x0,0x0,0x0,0x0, +\x00\x0c\x1c\xb0J\xfd\x00\x00\x00\x00\x04\x00\x00\x00\x04\x02H@\x01\x00\x00\x00\x00\x00\x00\x0a \xa1J\xfd\x00\x00\x00\x00\x04\x00\x00\x00\x00\x0e\x08\xc0J\xfd\x00\x00\x00\x00\x02\x00\x00\x00\x00\x08\x00\x00J\xfd\x00\x00\x00\x00\x04\x00\x00\x00\x04\x02>\xc6\x01\x00\x00\x00\x00\x00\x00\x0cx\xb1J\xfd\x00\x00\x00\x00\x04\x00\x00\x00\x01\x09\x04\x02J\xfd\x00\x00\x00\x00\x04\x00\x00\x00\xc2\x1b\x0e{\x00\x00\x00\x00\x01\x0b\x84\xa1J\xfd\x00\x00\x00\x00\x04\x00\x00\x00\xd8\x1f\x9a0\x00\x00\x00\x00\x00\x08p\x00J\xfd\x00\x00\x00\x00\x04\x00\x00\x00\x01\x09\xec\x02J\xfd\x00\x00\x00\x00\x04\x00\x00\x00Pb\xd6\x13\x00\x00\x00\x00\x00\x0a\x18\xa0J\xfd\x00\x00\x00\x00\x04\x00\x00\x00\x01\x0d\x00\xb0J\xfd\x00\x00\x00\x00\x04\x00\x00\x00\x98\xe9\xf6\x0c\x00\x00\x00\x00 +``` diff --git a/results/classifier/gemma3:12b/graphic/1423 b/results/classifier/gemma3:12b/graphic/1423 new file mode 100644 index 00000000..5fe4d6df --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1423 @@ -0,0 +1,14 @@ + +QEMU 6.2.0 fullscreen problem +Description of problem: +After running the command above, clicking on "Try Ubuntu" and adjusting the guest display resolution in GNOME to the native resolution, pressing ctrl+alt+f yields a "fullscreen" that only covers the QEMU window but not the entire host screen. This is not the case when switching to fullscreen while the boot screen is active or running `qemu-system-x86_64 -display gtk,full-screen=on`. + +The problem also occurs when replacing `-device qxl-vga` by `-device VGA,vgamem_mb=64`. The problem however does not occur when using `-device virtio-vga` instead of `-device qxl-vga` or `-display sdl` instead of `-display gtk`. +Steps to reproduce: +1. Run the command above +2. Click "Try Ubuntu" +3. Set guest resolution to native resolution (1920x1200 in my case) +4. Move the window a bit off the corners to observe the effect +5. Press ctrl+alt+f +Additional information: +The bug has also been [reported here](https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2000739). diff --git a/results/classifier/gemma3:12b/graphic/1425597 b/results/classifier/gemma3:12b/graphic/1425597 new file mode 100644 index 00000000..e084138a --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1425597 @@ -0,0 +1,15 @@ + +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/gemma3:12b/graphic/1431 b/results/classifier/gemma3:12b/graphic/1431 new file mode 100644 index 00000000..5af17d65 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1431 @@ -0,0 +1,51 @@ + +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: + + diff --git a/results/classifier/gemma3:12b/graphic/1439800 b/results/classifier/gemma3:12b/graphic/1439800 new file mode 100644 index 00000000..d86f17fe --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1439800 @@ -0,0 +1,9 @@ + +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/gemma3:12b/graphic/1455 b/results/classifier/gemma3:12b/graphic/1455 new file mode 100644 index 00000000..84d80a4e --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1455 @@ -0,0 +1,4 @@ + +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/gemma3:12b/graphic/1455254 b/results/classifier/gemma3:12b/graphic/1455254 new file mode 100644 index 00000000..22a00e49 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1455254 @@ -0,0 +1,59 @@ + +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/gemma3:12b/graphic/1461 b/results/classifier/gemma3:12b/graphic/1461 new file mode 100644 index 00000000..749592b2 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1461 @@ -0,0 +1,2 @@ + +Virgl on Upstream windows builds? diff --git a/results/classifier/gemma3:12b/graphic/1466 b/results/classifier/gemma3:12b/graphic/1466 new file mode 100644 index 00000000..3c0e7f80 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1466 @@ -0,0 +1,8 @@ + +GTK: mouse position incorrect in HiDPI environment +Description of problem: +With `usb-tablet` mode the guest cursor position should be consistent with the host cursor since QEMU can position the mouse absolutely. +The guest position is off from the host cursor position, it seems the position is not being divided by the scaling factor before it is passed on to the guest. +Steps to reproduce: +1. Run any guest with a graphical interface (e.g. Fedora Workstation or Windows 10) +2. Notice how the guest mouse is not consistent with the host mouse at all diff --git a/results/classifier/gemma3:12b/graphic/1479717 b/results/classifier/gemma3:12b/graphic/1479717 new file mode 100644 index 00000000..f4c563d9 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1479717 @@ -0,0 +1,6 @@ + +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/gemma3:12b/graphic/1485180 b/results/classifier/gemma3:12b/graphic/1485180 new file mode 100644 index 00000000..94d49de7 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1485180 @@ -0,0 +1,22 @@ + +Ctrl Alt G -- Multiple Virtual Machines + +I'm using Fedora 22. + +Firstly, what works: +A single VM instance, running Windows. Although, I am keeping this (GTK) window focused. + +What really fails: +If I have two running VM's, WIndows XP and Windows Vista: +1. I press Ctrl-Alt-G to get the focus. +2. That works first time. +3. Then I press Ctrl-Alt-G again. +4. Then Alt-Tab to the other machine (switching from XP to Vista, or back.) +5. Then press Ctrl-Alt-G to gain focus: +- Problem is that now the Ctrl-Alt-G, although showing in the title bar, only grabs the mouse, but NOT the keyboard. That is to say, whilst in Ctrl-Alt-G mode the second time, pressing Alt-Tab jumps back to the other VM! + +Pressing Alt-F4 quits!!!!!!!!!!!!! Regardless of whether Ctrl-Alt-G mode or not! +But only when running two VM's. + +Thanks +Misha \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1488212 b/results/classifier/gemma3:12b/graphic/1488212 new file mode 100644 index 00000000..bc4bd4df --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1488212 @@ -0,0 +1,12 @@ + +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/gemma3:12b/graphic/1500935 b/results/classifier/gemma3:12b/graphic/1500935 new file mode 100644 index 00000000..fd09fbb7 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1500935 @@ -0,0 +1,13 @@ + +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/gemma3:12b/graphic/1505062 b/results/classifier/gemma3:12b/graphic/1505062 new file mode 100644 index 00000000..2dc1bca5 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1505062 @@ -0,0 +1,22 @@ + +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/gemma3:12b/graphic/1529764 b/results/classifier/gemma3:12b/graphic/1529764 new file mode 100644 index 00000000..56722414 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1529764 @@ -0,0 +1,10 @@ + +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/gemma3:12b/graphic/1530 b/results/classifier/gemma3:12b/graphic/1530 new file mode 100644 index 00000000..e0a1b598 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1530 @@ -0,0 +1,12 @@ + +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/gemma3:12b/graphic/1530386 b/results/classifier/gemma3:12b/graphic/1530386 new file mode 100644 index 00000000..7eed137a --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1530386 @@ -0,0 +1,9 @@ + +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/gemma3:12b/graphic/1545024 b/results/classifier/gemma3:12b/graphic/1545024 new file mode 100644 index 00000000..c1a6a8f0 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1545024 @@ -0,0 +1,148 @@ + +compiling on armv7 crashes compile qlx.o + +If i try to compile qemu on armv7 cpu i get this error: + + LINK qemu-nbd + CC qemu-img.o + LINK qemu-img + LINK qemu-io + LINK qemu-bridge-helper + CC qmp-marshal.o + CC hw/display/qxl.o +{standard input}: Assembler messages: +{standard input}:1704: Error: bad instruction `lock' +{standard input}:1704: Error: bad instruction `addl $0,0(%rsp)' +{standard input}:1864: Error: bad instruction `lock' +{standard input}:1864: Error: bad instruction `addl $0,0(%rsp)' +{standard input}:5239: Error: bad instruction `lock' +{standard input}:5239: Error: bad instruction `addl $0,0(%rsp)' +{standard input}:5731: Error: bad instruction `lock' +{standard input}:5731: Error: bad instruction `addl $0,0(%rsp)' +{standard input}:11923: Error: bad instruction `lock' +{standard input}:11923: Error: bad instruction `addl $0,0(%rsp)' +{standard input}:13960: Error: bad instruction `lock' +{standard input}:13960: Error: bad instruction `addl $0,0(%rsp)' +{standard input}:14349: Error: bad instruction `lock' +{standard input}:14349: Error: bad instruction `addl $0,0(%rsp)' +/home/fleixi/git/qemu/rules.mak:57: recipe for target 'hw/display/qxl.o' failed +make: *** [hw/display/qxl.o] Error 1 + +Build options are: + + ./configure --target-list=i386-softmmu +Install prefix /usr/local +BIOS directory /usr/local/share/qemu +binary directory /usr/local/bin +library directory /usr/local/lib +module directory /usr/local/lib/qemu +libexec directory /usr/local/libexec +include directory /usr/local/include +config directory /usr/local/etc +local state directory /usr/local/var +Manual directory /usr/local/share/man +ELF interp prefix /usr/gnemul/qemu-%M +Source path /home/fleixi/git/qemu +C compiler cc +Host C compiler cc +C++ compiler c++ +Objective-C compiler cc +ARFLAGS rv +CFLAGS -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -g -mcpu=cortex-a15.cortex-a7 -mfloat-abi=hard -mfpu=neon-vfpv4 -O2 -pipe -ffast-math -ftree-vectorize -mvectorize-with-neon-quad -fstack-protector --param=ssp-buffer-size=4 +QEMU_CFLAGS -I/usr/include/pixman-1 -Werror -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -Wendif-labels -Wmissing-include-dirs -Wempty-body -Wnested-externs -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wold-style-declaration -Wold-style-definition -Wtype-limits -fstack-protector-strong -I/usr/include/libpng12 -I/usr/local/include/spice-server -I/usr/local/include -I/usr/local/include/spice-1 -I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -I/usr/include/pixman-1 +LDFLAGS -Wl,--warn-common -g +make make +install install +python python -B +smbd /usr/sbin/smbd +module support no +host CPU arm +host big endian no +target list i386-softmmu +tcg debug enabled no +gprof enabled no +sparse enabled no +strip binaries yes +profiler no +static build no +pixman system +SDL support no +GTK support yes +GTK GL support no +GNUTLS support no +GNUTLS hash no +libgcrypt no +nettle no +libtasn1 no +VTE support no +curses support no +virgl support no +curl support yes +mingw32 support no +Audio drivers oss +Block whitelist (rw) +Block whitelist (ro) +VirtFS support no +VNC support yes +VNC SASL support yes +VNC JPEG support yes +VNC PNG support yes +xen support no +brlapi support no +bluez support yes +Documentation no +PIE no +vde support no +netmap support no +Linux AIO support no +ATTR/XATTR support yes +Install blobs yes +KVM support yes +RDMA support no +TCG interpreter no +fdt support no +preadv support yes +fdatasync yes +madvise yes +posix_madvise yes +sigev_thread_id yes +uuid support no +libcap-ng support no +vhost-net support yes +vhost-scsi support yes +Trace backends log +spice support yes (0.12.10/0.12.6) +rbd support no +xfsctl support no +smartcard support no +libusb no +usb net redir no +OpenGL support no +libiscsi support no +libnfs support no +build guest agent yes +QGA VSS support no +QGA w32 disk info no +QGA MSI support no +seccomp support no +coroutine backend ucontext +coroutine pool yes +GlusterFS support no +Archipelago support no +gcov gcov +gcov enabled no +TPM support yes +libssh2 support no +TPM passthrough no +QOM debugging yes +vhdx no +lzo support no +snappy support no +bzip2 support yes +NUMA host support no +tcmalloc support no +jemalloc support no + +testet with qemu-git branch stable-2.4 and git master + +Shoulded the configure detecting "bigendian" too? \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1546680 b/results/classifier/gemma3:12b/graphic/1546680 new file mode 100644 index 00000000..1ab21d4a --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1546680 @@ -0,0 +1,6 @@ + +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/gemma3:12b/graphic/1547012 b/results/classifier/gemma3:12b/graphic/1547012 new file mode 100644 index 00000000..d405d79c --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1547012 @@ -0,0 +1,34 @@ + +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/gemma3:12b/graphic/1548170 b/results/classifier/gemma3:12b/graphic/1548170 new file mode 100644 index 00000000..b90aac66 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1548170 @@ -0,0 +1,18 @@ + +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/gemma3:12b/graphic/1553999 b/results/classifier/gemma3:12b/graphic/1553999 new file mode 100644 index 00000000..f45287ee --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1553999 @@ -0,0 +1,11 @@ + +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/gemma3:12b/graphic/1555076 b/results/classifier/gemma3:12b/graphic/1555076 new file mode 100644 index 00000000..ca3a1a60 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1555076 @@ -0,0 +1,34 @@ + +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/gemma3:12b/graphic/1556372 b/results/classifier/gemma3:12b/graphic/1556372 new file mode 100644 index 00000000..be67f982 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1556372 @@ -0,0 +1,11 @@ + +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/gemma3:12b/graphic/1567254 b/results/classifier/gemma3:12b/graphic/1567254 new file mode 100644 index 00000000..dc466132 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1567254 @@ -0,0 +1,34 @@ + +qemu-2.5.1 will not run with gtk3/vte + +Using qemu-2.5.1 and compiling without gtk3 and vte-2.90. + +This works: + +CC="gcc -mtune=generic -Os -pipe" CXX="g++ -mtune=generic -Os -pipe -fno-exceptions -fno-rtti" ./configure --prefix=/usr/local --localstatedir=/var --libexecdir=/usr/local/lib/qemu --interp-prefix=/usr/local/share/qemu --audio-drv-list="oss alsa sdl" --target-list="i386-softmmu i386-linux-user x86_64-softmmu x86_64-linux-user" --smbd=/usr/local/sbin/smbd --disable-curses + +find . -name config-host.mak -type f -exec sed -i 's/-O2//g' {} \; + +make +sudo make install + +If I then add gtk3 and vte-2.90 development files and compile again, this fails with or without --disable-docs: + + sudo make install +... +make -C po install +make[1]: Entering directory '/usr/src/qemu-2.5.1/po' + GEN tr.mo +/bin/sh: msgfmt: not found +Makefile:13: recipe for target 'tr.mo' failed +make[1]: *** [tr.mo] Error 127 +make[1]: Leaving directory '/usr/src/qemu-2.5.1/po' +Makefile:443: recipe for target 'install' failed +make: *** [install] Error 2 + +If I then add gettext and re-compile, "qemu-system-x86_64 -blah-blah" opens a window, displays the bios message and stops. + +* configure script should check for gettext +* if "--disable-docs" is passed, "make install" should not try to install docs +* qemu should work when compiled with gtk3 and vte +* why does qemu insist on vte-2.90, when vte-2.91 has been out +/- 2 years? \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1568356 b/results/classifier/gemma3:12b/graphic/1568356 new file mode 100644 index 00000000..fc3db1ac --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1568356 @@ -0,0 +1,13 @@ + +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/gemma3:12b/graphic/1571084 b/results/classifier/gemma3:12b/graphic/1571084 new file mode 100644 index 00000000..d434f4b9 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1571084 @@ -0,0 +1,139 @@ + +Qemu 2.x dont build on last Gtk dev 3.0+ + +here the build exit + +ui/gtk.c: In function ‘gd_mouse_set’: +ui/gtk.c:479:5: error: ‘gdk_display_get_device_manager’ is deprecated: Use 'gdk_display_get_default_seat' instead [-Werror=deprecated-declarations] + mgr = gdk_display_get_device_manager(dpy); + ^ +In file included from /usr/local/include/gtk-3.0/gdk/gdkscreen.h:32:0, + from /usr/local/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31, + from /usr/local/include/gtk-3.0/gdk/gdk.h:32, + from /usr/local/include/gtk-3.0/gtk/gtk.h:30, + from /home/amigaone/src/qemu/include/ui/gtk.h:9, + from ui/gtk.c:42: +/usr/local/include/gtk-3.0/gdk/gdkdisplay.h:170:20: note: declared here + GdkDeviceManager * gdk_display_get_device_manager (GdkDisplay *display); + ^ +ui/gtk.c:482:5: error: ‘gdk_device_manager_get_client_pointer’ is deprecated [-Werror=deprecated-declarations] + gdk_device_warp(gdk_device_manager_get_client_pointer(mgr), + ^ +In file included from /usr/local/include/gtk-3.0/gdk/gdkdisplay.h:32:0, + from /usr/local/include/gtk-3.0/gdk/gdkscreen.h:32, + from /usr/local/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31, + from /usr/local/include/gtk-3.0/gdk/gdk.h:32, + from /usr/local/include/gtk-3.0/gtk/gtk.h:30, + from /home/amigaone/src/qemu/include/ui/gtk.h:9, + from ui/gtk.c:42: +/usr/local/include/gtk-3.0/gdk/gdkdevicemanager.h:44:14: note: declared here + GdkDevice * gdk_device_manager_get_client_pointer (GdkDeviceManager *device_manager); + ^ +ui/gtk.c: In function ‘gd_grab_devices’: +ui/gtk.c:1316:5: error: ‘gdk_display_get_device_manager’ is deprecated: Use 'gdk_display_get_default_seat' instead [-Werror=deprecated-declarations] + GdkDeviceManager *mgr = gdk_display_get_device_manager(display); + ^ +In file included from /usr/local/include/gtk-3.0/gdk/gdkscreen.h:32:0, + from /usr/local/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31, + from /usr/local/include/gtk-3.0/gdk/gdk.h:32, + from /usr/local/include/gtk-3.0/gtk/gtk.h:30, + from /home/amigaone/src/qemu/include/ui/gtk.h:9, + from ui/gtk.c:42: +/usr/local/include/gtk-3.0/gdk/gdkdisplay.h:170:20: note: declared here + GdkDeviceManager * gdk_display_get_device_manager (GdkDisplay *display); + ^ +ui/gtk.c:1317:5: error: ‘gdk_device_manager_list_devices’ is deprecated [-Werror=deprecated-declarations] + GList *devs = gdk_device_manager_list_devices(mgr, GDK_DEVICE_TYPE_MASTER); + ^ +In file included from /usr/local/include/gtk-3.0/gdk/gdkdisplay.h:32:0, + from /usr/local/include/gtk-3.0/gdk/gdkscreen.h:32, + from /usr/local/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31, + from /usr/local/include/gtk-3.0/gdk/gdk.h:32, + from /usr/local/include/gtk-3.0/gtk/gtk.h:30, + from /home/amigaone/src/qemu/include/ui/gtk.h:9, + from ui/gtk.c:42: +/usr/local/include/gtk-3.0/gdk/gdkdevicemanager.h:41:14: note: declared here + GList * gdk_device_manager_list_devices (GdkDeviceManager *device_manager, + ^ +ui/gtk.c:1327:13: error: ‘gdk_device_grab’ is deprecated: Use 'gdk_seat_grab' instead [-Werror=deprecated-declarations] + gdk_device_grab(dev, win, GDK_OWNERSHIP_NONE, FALSE, + ^ +In file included from /usr/local/include/gtk-3.0/gdk/gdkdnd.h:33:0, + from /usr/local/include/gtk-3.0/gdk/gdkevents.h:34, + from /usr/local/include/gtk-3.0/gdk/gdkdisplay.h:31, + from /usr/local/include/gtk-3.0/gdk/gdkscreen.h:32, + from /usr/local/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31, + from /usr/local/include/gtk-3.0/gdk/gdk.h:32, + from /usr/local/include/gtk-3.0/gtk/gtk.h:30, + from /home/amigaone/src/qemu/include/ui/gtk.h:9, + from ui/gtk.c:42: +/usr/local/include/gtk-3.0/gdk/gdkdevice.h:250:15: note: declared here + GdkGrabStatus gdk_device_grab (GdkDevice *device, + ^ +ui/gtk.c:1330:13: error: ‘gdk_device_ungrab’ is deprecated: Use 'gdk_seat_ungrab' instead [-Werror=deprecated-declarations] + gdk_device_ungrab(dev, GDK_CURRENT_TIME); + ^ +In file included from /usr/local/include/gtk-3.0/gdk/gdkdnd.h:33:0, + from /usr/local/include/gtk-3.0/gdk/gdkevents.h:34, + from /usr/local/include/gtk-3.0/gdk/gdkdisplay.h:31, + from /usr/local/include/gtk-3.0/gdk/gdkscreen.h:32, + from /usr/local/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31, + from /usr/local/include/gtk-3.0/gdk/gdk.h:32, + from /usr/local/include/gtk-3.0/gtk/gtk.h:30, + from /home/amigaone/src/qemu/include/ui/gtk.h:9, + from ui/gtk.c:42: +/usr/local/include/gtk-3.0/gdk/gdkdevice.h:259:15: note: declared here + void gdk_device_ungrab (GdkDevice *device, + ^ +ui/gtk.c: In function ‘gd_grab_pointer’: +ui/gtk.c:1392:5: error: ‘gdk_display_get_device_manager’ is deprecated: Use 'gdk_display_get_default_seat' instead [-Werror=deprecated-declarations] + GdkDeviceManager *mgr = gdk_display_get_device_manager(display); + ^ +In file included from /usr/local/include/gtk-3.0/gdk/gdkscreen.h:32:0, + from /usr/local/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31, + from /usr/local/include/gtk-3.0/gdk/gdk.h:32, + from /usr/local/include/gtk-3.0/gtk/gtk.h:30, + from /home/amigaone/src/qemu/include/ui/gtk.h:9, + from ui/gtk.c:42: +/usr/local/include/gtk-3.0/gdk/gdkdisplay.h:170:20: note: declared here + GdkDeviceManager * gdk_display_get_device_manager (GdkDisplay *display); + ^ +ui/gtk.c:1400:5: error: ‘gdk_device_manager_get_client_pointer’ is deprecated [-Werror=deprecated-declarations] + gdk_device_get_position(gdk_device_manager_get_client_pointer(mgr), + ^ +In file included from /usr/local/include/gtk-3.0/gdk/gdkdisplay.h:32:0, + from /usr/local/include/gtk-3.0/gdk/gdkscreen.h:32, + from /usr/local/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31, + from /usr/local/include/gtk-3.0/gdk/gdk.h:32, + from /usr/local/include/gtk-3.0/gtk/gtk.h:30, + from /home/amigaone/src/qemu/include/ui/gtk.h:9, + from ui/gtk.c:42: +/usr/local/include/gtk-3.0/gdk/gdkdevicemanager.h:44:14: note: declared here + GdkDevice * gdk_device_manager_get_client_pointer (GdkDeviceManager *device_manager); + ^ +ui/gtk.c: In function ‘gd_ungrab_pointer’: +ui/gtk.c:1432:5: error: ‘gdk_display_get_device_manager’ is deprecated: Use 'gdk_display_get_default_seat' instead [-Werror=deprecated-declarations] + GdkDeviceManager *mgr = gdk_display_get_device_manager(display); + ^ +In file included from /usr/local/include/gtk-3.0/gdk/gdkscreen.h:32:0, + from /usr/local/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31, + from /usr/local/include/gtk-3.0/gdk/gdk.h:32, + from /usr/local/include/gtk-3.0/gtk/gtk.h:30, + from /home/amigaone/src/qemu/include/ui/gtk.h:9, + from ui/gtk.c:42: +/usr/local/include/gtk-3.0/gdk/gdkdisplay.h:170:20: note: declared here + GdkDeviceManager * gdk_display_get_device_manager (GdkDisplay *display); + ^ +ui/gtk.c:1434:5: error: ‘gdk_device_manager_get_client_pointer’ is deprecated [-Werror=deprecated-declarations] + gdk_device_warp(gdk_device_manager_get_client_pointer(mgr), + ^ +In file included from /usr/local/include/gtk-3.0/gdk/gdkdisplay.h:32:0, + from /usr/local/include/gtk-3.0/gdk/gdkscreen.h:32, + from /usr/local/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31, + from /usr/local/include/gtk-3.0/gdk/gdk.h:32, + from /usr/local/include/gtk-3.0/gtk/gtk.h:30, + from /home/amigaone/src/qemu/include/ui/gtk.h:9, + from ui/gtk.c:42: +/usr/local/include/gtk-3.0/gdk/gdkdevicemanager.h:44:14: note: declared here + GdkDevice * gdk_device_manager_get_client_pointer (GdkDeviceManager *device_manager); + ^ \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1577937 b/results/classifier/gemma3:12b/graphic/1577937 new file mode 100644 index 00000000..6f8ec2ea --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1577937 @@ -0,0 +1,24 @@ + +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/gemma3:12b/graphic/1578192 b/results/classifier/gemma3:12b/graphic/1578192 new file mode 100644 index 00000000..2228cb57 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1578192 @@ -0,0 +1,57 @@ + +GTK+ interface doesn't translate keycodes properly with Wayland backend + +I already posted this on the mailing list (https://lists.nongnu.org/archive/html/qemu-devel/2016-05/msg00119.html) but I decided to do a formal bug report so it can be tracked and doesn't get lost. + +... I'm no expert, but it looks like GTK+ key events come in at the ui/gtk.c:gd_key_event callback function, which calls ui/gtk.c:gd_map_keycode to translate the GTK+ keycode into the Qemu keycode before sending it on using qemu_input_event_send_key_number. The problem is that gd_map_keycode is incomplete when GTK+ is running on a backend other than X11. + +static int gd_map_keycode(GtkDisplayState *s, GdkDisplay *dpy, int gdk_keycode) +{ + int qemu_keycode; + +#ifdef GDK_WINDOWING_WIN32 + if (GDK_IS_WIN32_DISPLAY(dpy)) { + qemu_keycode = MapVirtualKey(gdk_keycode, MAPVK_VK_TO_VSC); + switch (qemu_keycode) { + case 103: /* alt gr */ + qemu_keycode = 56 | SCANCODE_GREY; + break; + } + return qemu_keycode; + } +#endif + + if (gdk_keycode < 9) { + qemu_keycode = 0; + } else if (gdk_keycode < 97) { + qemu_keycode = gdk_keycode - 8; +#ifdef GDK_WINDOWING_X11 + } else if (GDK_IS_X11_DISPLAY(dpy) && gdk_keycode < 158) { + if (s->has_evdev) { + qemu_keycode = translate_evdev_keycode(gdk_keycode - 97); + } else { + qemu_keycode = translate_xfree86_keycode(gdk_keycode - 97); + } +#endif + } else if (gdk_keycode == 208) { /* Hiragana_Katakana */ + qemu_keycode = 0x70; + } else if (gdk_keycode == 211) { /* backslash */ + qemu_keycode = 0x73; + } else { + qemu_keycode = 0; + } + + return qemu_keycode; +} + +In my case, I'm using GTK+'s Wayland backend, so keycodes 97 through 157 (this includes KEY_HOME(102), KEY_PAGEUP(104), KEY_PAGEDOWN(109), KEY_END(107), etc.) are never translated into a qemu_keycode, and the final 'else' block is hit, causing gd_map_keycode to return 0, which is an invalid keycode and thus cannot be handled by xen-kbdfront. At least that's my best guess as to what is happening. + +The solution that comes to mind is provide an alternative to translate_{evdev,xfree86}_keycode that is compatable with Wayland/libinput, but I don't know exactly which API would provide this functionality, much less do I have a patch. Intuition tells me that translate_evdev_keycode would probably work under Wayland because Weston uses libinput which uses evdev as its backend, but I don't know this for a fact, and I don't know if it would be the Right Way (i.e. Wayland or libinput might provide an API for this purpose, but I don't know). + +I may try to do some testing with translate_evdev_keycode on Wayland and also look into any possible APIs for keycode translation, but I just wanted to put it out there and get some feedback awhile. + +Qemu 2.2.1 from Xen 4.6.1 (relevant code appears unchanged in Qemu master) +GTK+ 3.18.7 +Wayland 1.9.0 +Weston 1.9.0 +libinput 1.2.3 \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1581796 b/results/classifier/gemma3:12b/graphic/1581796 new file mode 100644 index 00000000..074559a5 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1581796 @@ -0,0 +1,14 @@ + +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/gemma3:12b/graphic/1581936 b/results/classifier/gemma3:12b/graphic/1581936 new file mode 100644 index 00000000..aa46017a --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1581936 @@ -0,0 +1,67 @@ + +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/gemma3:12b/graphic/1585 b/results/classifier/gemma3:12b/graphic/1585 new file mode 100644 index 00000000..1658d729 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1585 @@ -0,0 +1,28 @@ + +Incorrect VGA text mode rendering +Description of problem: +All of my physical machines use black as `DarkGray` and have the text starting from `White+DarkGray` blink (watch the video below). The ISO I'm using is a minimal kernel I've written to check VGA text mode (provided by the BIOS at `0xb8000` with a 80x25 resolution) handling on multiple emulators and machines. +Changing the emulated CPU and display driver doesn't change this behaviour. + +Hyper-V: color test shows correct colors, all text starting from `White+DarkGray` is blinking + + + +AMD Athlon 64 X2 6000+ + NVIDIA Quadro 400 on actual hardware: same as Hyper-V +I've tested this with multiple physical GPUs and they all have the same behaviour and color palette. + + + +QEMU: dark gray is the wrong color and the text doesn't blink +Changing the emulated device doesn't change this behaviour. + + + +I think QEMU should emulate the hardware as close as possible and therefore atleast have the blinking text. +Consider this a low priority issue. +Steps to reproduce: +1. Download ISO from the link above +2. Run the QEMU command above +3. See the text not blink +Additional information: + diff --git a/results/classifier/gemma3:12b/graphic/1588473 b/results/classifier/gemma3:12b/graphic/1588473 new file mode 100644 index 00000000..345ae81d --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1588473 @@ -0,0 +1,20 @@ + +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/gemma3:12b/graphic/1592351 b/results/classifier/gemma3:12b/graphic/1592351 new file mode 100644 index 00000000..6145b840 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1592351 @@ -0,0 +1,23 @@ + +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/gemma3:12b/graphic/1600112 b/results/classifier/gemma3:12b/graphic/1600112 new file mode 100644 index 00000000..2462c4f7 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1600112 @@ -0,0 +1,8 @@ + +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/gemma3:12b/graphic/1606708 b/results/classifier/gemma3:12b/graphic/1606708 new file mode 100644 index 00000000..b5b26d3e --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1606708 @@ -0,0 +1,22 @@ + +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/gemma3:12b/graphic/1607 b/results/classifier/gemma3:12b/graphic/1607 new file mode 100644 index 00000000..505ec88c --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1607 @@ -0,0 +1,2 @@ + +QEMU calls glXMakeCurrent which is current in another thread when running VM with SDL diff --git a/results/classifier/gemma3:12b/graphic/1610 b/results/classifier/gemma3:12b/graphic/1610 new file mode 100644 index 00000000..03e063ac --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1610 @@ -0,0 +1,2 @@ + +support of directX in windows guest diff --git a/results/classifier/gemma3:12b/graphic/1611 b/results/classifier/gemma3:12b/graphic/1611 new file mode 100644 index 00000000..48e692fc --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1611 @@ -0,0 +1,2 @@ + +How to test rutabaga_gfx/gfxstream patches diff --git a/results/classifier/gemma3:12b/graphic/1611979 b/results/classifier/gemma3:12b/graphic/1611979 new file mode 100644 index 00000000..d71d2e1b --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1611979 @@ -0,0 +1,4 @@ + +GTK+ interface, backspace is broken in the monitor console + +this has been broken for over 2 years \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1614521 b/results/classifier/gemma3:12b/graphic/1614521 new file mode 100644 index 00000000..75c78f06 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1614521 @@ -0,0 +1,4 @@ + +-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/gemma3:12b/graphic/1615079 b/results/classifier/gemma3:12b/graphic/1615079 new file mode 100644 index 00000000..b4fc17ae --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1615079 @@ -0,0 +1,4 @@ + +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/gemma3:12b/graphic/1615212 b/results/classifier/gemma3:12b/graphic/1615212 new file mode 100644 index 00000000..a5c52980 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1615212 @@ -0,0 +1,4 @@ + +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/gemma3:12b/graphic/1617114 b/results/classifier/gemma3:12b/graphic/1617114 new file mode 100644 index 00000000..14532b6e --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1617114 @@ -0,0 +1,20 @@ + +Qemu 2.6.0 freezes with windows guests + +When launching qemu with the same command line as before 2.6.0, with SDL display, with virtio, for a win-10 guest: + +qemu-system-x86_64 -enable-kvm -name win-10 -machine type=pc,accel=kvm -cpu host -smp cores=1,threads=2,sockets=1 -m 2.7G -balloon virtio -drive file=/home/<username>/.qemu/imgs/win10-coe.qcow2,index=0,media=disk,if=virtio -drive file=/usr/share/virtio/virtio-win.iso,index=1,media=cdrom -drive file=/usr/share/spice-guest-tools/spice-guest-tools.iso,index=2,media=cdrom -net nic,model=virtio -net tap,ifname=tap0,script=no,downscript=no,vhost=on -usbdevice tablet -usb -display sdl -vga qxl -soundhw ac97 -rtc base=localtime -usbdevice host:0b0e:0032 -usbdevice host:0b0e:0348 -usbdevice host:0b0e:0410 + +Qemu at some point just freezes with no error message at all with newer version 2.6.0-1. + +Reverting to prior version 2.5.1-1, things go back to normal. + +A simple way to accelerate the freeze is to have qemu launch in a workspace/desktop, and then move to a different workspace/desktop, and then move back to the qemu workspace/desktop, and you'll find out it's frozen. + +BTW, there's no way to get into qemu monitor mode terminal at all once frozen. The monitor terminal shows up, but does nothing... + +Perhaps it's useful to notice that I have up to date win-10 virtio drivers for ethernet, scsi/storage, qxl-dod, balloon, and serial interface drivers. The ISO version used is 0.1.118.1 (virtio-win AUR package). + +Using the standard (std) qemu video driver, rather than the qxl-dod one makes no difference BTW. + +Just in case, running on up to date x86-64 Arch, plain qemu command line. \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1618122 b/results/classifier/gemma3:12b/graphic/1618122 new file mode 100644 index 00000000..f95b0d8f --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1618122 @@ -0,0 +1,46 @@ + +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/gemma3:12b/graphic/1619438 b/results/classifier/gemma3:12b/graphic/1619438 new file mode 100644 index 00000000..f2845be8 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1619438 @@ -0,0 +1,4 @@ + +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/gemma3:12b/graphic/1620660 b/results/classifier/gemma3:12b/graphic/1620660 new file mode 100644 index 00000000..f62b52f7 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1620660 @@ -0,0 +1,8 @@ + +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/gemma3:12b/graphic/1622 b/results/classifier/gemma3:12b/graphic/1622 new file mode 100644 index 00000000..7ead2375 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1622 @@ -0,0 +1,2 @@ + +PNG screendump has R/B channels swapped diff --git a/results/classifier/gemma3:12b/graphic/1635339 b/results/classifier/gemma3:12b/graphic/1635339 new file mode 100644 index 00000000..81912fbc --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1635339 @@ -0,0 +1,12 @@ + +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/gemma3:12b/graphic/1644 b/results/classifier/gemma3:12b/graphic/1644 new file mode 100644 index 00000000..e9cbd907 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1644 @@ -0,0 +1,15 @@ + +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/gemma3:12b/graphic/1649042 b/results/classifier/gemma3:12b/graphic/1649042 new file mode 100644 index 00000000..f0870abb --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1649042 @@ -0,0 +1,36 @@ + +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/gemma3:12b/graphic/1656710 b/results/classifier/gemma3:12b/graphic/1656710 new file mode 100644 index 00000000..d79f3539 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1656710 @@ -0,0 +1,12 @@ + +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/gemma3:12b/graphic/1656711 b/results/classifier/gemma3:12b/graphic/1656711 new file mode 100644 index 00000000..e943ce9f --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1656711 @@ -0,0 +1,16 @@ + +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/gemma3:12b/graphic/1658634 b/results/classifier/gemma3:12b/graphic/1658634 new file mode 100644 index 00000000..64ec6db8 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1658634 @@ -0,0 +1,8 @@ + +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/gemma3:12b/graphic/1665789 b/results/classifier/gemma3:12b/graphic/1665789 new file mode 100644 index 00000000..a1982d99 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1665789 @@ -0,0 +1,8 @@ + +More resolutions for vga displays + +Would it be possible to add more resolutions for vga displays (which I am accessing via vnc instead of spice)? In particular: + +- 1080 wide x 1920 high (rotate 1920 x 1080 screen) + +- 1920 wide x 1080 + 1980 high (1920 x 1080 screen on top of 1600 x 900 screen) \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/167 b/results/classifier/gemma3:12b/graphic/167 new file mode 100644 index 00000000..c68f590b --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/167 @@ -0,0 +1,2 @@ + +qemu 4.0 doesnt support glsl 3.0 but yes older versions, that have no sense IMO diff --git a/results/classifier/gemma3:12b/graphic/1670509 b/results/classifier/gemma3:12b/graphic/1670509 new file mode 100644 index 00000000..d9e809fb --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1670509 @@ -0,0 +1,8 @@ + +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/gemma3:12b/graphic/1674925 b/results/classifier/gemma3:12b/graphic/1674925 new file mode 100644 index 00000000..537c6d09 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1674925 @@ -0,0 +1,22 @@ + +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/gemma3:12b/graphic/1675108 b/results/classifier/gemma3:12b/graphic/1675108 new file mode 100644 index 00000000..2ab1cc23 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1675108 @@ -0,0 +1,23 @@ + +Cocoa UI always crashes on startup + +Commit 8bb93c6f99a42c2e0943bc904b283cd622d302c5 ("ui/console: ensure graphic updates don't race with TCG vCPUs") causes the graphic update to run on a non-main thread, which Cocoa is not happy with. It crashes immediately after startup. + +$ i386-softmmu/qemu-system-i386 +2017-03-22 10:09:25.113 qemu-system-i386[15968:9538245] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'nextEventMatchingMask should only be called from the Main Thread!' +*** First throw call stack: +( + 0 CoreFoundation 0x00007fff91e72e7b __exceptionPreprocess + 171 + 1 libobjc.A.dylib 0x00007fffa6a5ccad objc_exception_throw + 48 + 2 AppKit 0x00007fff900953fd -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 4471 + 3 qemu-system-i386 0x0000000104f75a49 cocoa_refresh + 233 + 4 qemu-system-i386 0x0000000104e0312c process_queued_cpu_work + 140 + 5 qemu-system-i386 0x0000000104d1a73c qemu_tcg_rr_cpu_thread_fn + 284 + 6 libsystem_pthread.dylib 0x00007fffa7557aab _pthread_body + 180 + 7 libsystem_pthread.dylib 0x00007fffa75579f7 _pthread_body + 0 + 8 libsystem_pthread.dylib 0x00007fffa75571fd thread_start + 13 +) +libc++abi.dylib: terminating with uncaught exception of type NSException +Abort trap: 6 + +System: macOS 10.12.3, Xcode 8.2.1 \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1675549 b/results/classifier/gemma3:12b/graphic/1675549 new file mode 100644 index 00000000..cf48e2be --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1675549 @@ -0,0 +1,15 @@ + +tcg softmmu i386 crashes on BE hardware + +Hi, +today i try to test qemu 2.9rc 1 with qemu-system-i386 if i set display as sdl and i push a key on keyboard qemu exit with an error + +translate-common.c:34:tcg_handle_interrupt: assertion failed: (qemu_mutex_iothread_locked()) + +This issue was not present on qemu 2.8.0 + +Test Machine PowerMac G5 Quad Fedora 25 Server PPC64 +Qemu build with target-list=i386-softmuu --with-sdlabi=2.0 + +Ciao +Luigi \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1685 b/results/classifier/gemma3:12b/graphic/1685 new file mode 100644 index 00000000..a882d1fe --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1685 @@ -0,0 +1,60 @@ + +QEMU segfaults when I restart Windows 11 VM with virtio-vga-gl +Description of problem: +When I restart the Windows 11 VM with the virtio GPU DoD driver installed, QEMU crashes with a SIGSEGV. This also happens if I try to uninstall this driver in the Device Manager. I attached the backtrace. +Steps to reproduce: +1. Install Windows 11 into the VM; +2. Install virtio GPU DoD driver; +3. Click Start -> Power -> Restart. +Additional information: +virtio-win version: 0.1.229 + +Backtrace: +``` +Thread 1 "qemu-system-x86" received signal SIGSEGV, Segmentation fault. +[Switching to Thread 0x7ffff64a3e80 (LWP 118206)] +_mesa_TexParameteri () at ../mesa-23.1.1/src/mesa/main/texparam.c:1248 +1248 texObj = _mesa_get_texobj_by_target_and_texunit(ctx, target, +(gdb) bt +#0 _mesa_TexParameteri() () at ../mesa-23.1.1/src/mesa/main/texparam.c:1248 +#1 0x00007ffece03cba2 in _mesa_unmarshal_TexParameteri () at src/mapi/glapi/gen/marshal_generated0.c:5332 +#2 0x00007ffecdf1bb30 in glthread_unmarshal_batch() () at ../mesa-23.1.1/src/mesa/main/glthread.c:122 +#3 0x00007ffecdf269c2 in _mesa_glthread_finish () at ../mesa-23.1.1/src/mesa/main/glthread.c:382 +#4 _mesa_glthread_finish() () at ../mesa-23.1.1/src/mesa/main/glthread.c:347 +#5 0x00007ffecdebd20f in dri_make_current () at ../mesa-23.1.1/src/gallium/frontends/dri/dri_context.c:303 +#6 dri_make_current () at ../mesa-23.1.1/src/gallium/frontends/dri/dri_context.c:287 +#7 driBindContext() () at ../mesa-23.1.1/src/gallium/frontends/dri/dri_util.c:701 +#8 0x00007ffee6e8693f in dri3_bind_context () at ../mesa-23.1.1/src/glx/dri3_glx.c:181 +#9 0x00007ffee6e78075 in MakeContextCurrent () at ../mesa-23.1.1/src/glx/glxcurrent.c:149 +#10 0x00007ffee7c84e73 in InternalMakeCurrentVendor + (dpy=dpy@entry=0x5555570fe3b0, draw=draw@entry=90177544, read=read@entry=90177544, ctxInfo=ctxInfo@entry=0x5555579418b0, callerOpcode=callerOpcode@entry=5 '\005', threadState=threadState@entry=0x55555702fbe0, vendor=0x55555707f520) at ../libglvnd-v1.6.0/src/GLX/libglx.c:871 +#11 0x00007ffee7c8bce1 in CommonMakeCurrent (dpy=0x5555570fe3b0, draw=90177544, read=90177544, context=0x55555780f760, callerOpcode=<optimized out>) + at ../libglvnd-v1.6.0/src/GLX/libglx.c:1053 +#12 0x00007ffff51f90b1 in X11_GL_MakeCurrent (_this=0x5555570c1aa0, window=<optimized out>, context=0x55555780f760) + at /usr/src/debug/sdl2/SDL2-2.26.5/src/video/x11/SDL_x11opengl.c:865 +#13 0x00007ffff51d0a3f in SDL_GL_MakeCurrent_REAL (window=0x5555570048b0, ctx=0x55555780f760) at /usr/src/debug/sdl2/SDL2-2.26.5/src/video/SDL_video.c:4120 +#14 0x00007ffff6492b86 in sdl2_gl_switch () at ../qemu-8.0.2/ui/sdl2-gl.c:83 +#15 0x000055555598efe2 in displaychangelistener_gfx_switch () at ../qemu-8.0.2/ui/console.c:1158 +#16 0x00005555559997aa in dpy_gfx_replace_surface () at ../qemu-8.0.2/ui/console.c:1815 +#17 0x0000555555d03398 in vga_draw_graphic () at ../qemu-8.0.2/hw/display/vga.c:1589 +#18 vga_update_display () at ../qemu-8.0.2/hw/display/vga.c:1789 +#19 vga_update_display () at ../qemu-8.0.2/hw/display/vga.c:1762 +#20 0x0000555555998acb in graphic_hw_update () at ../qemu-8.0.2/ui/console.c:234 +#21 0x00007ffff6493952 in sdl2_gl_refresh () at ../qemu-8.0.2/ui/sdl2-gl.c:113 +#22 0x000055555599d79a in dpy_refresh () at ../qemu-8.0.2/ui/console.c:1852 +#23 gui_update () at ../qemu-8.0.2/ui/console.c:169 +#24 0x0000555555fd9690 in timerlist_run_timers () at ../qemu-8.0.2/util/qemu-timer.c:576 +#25 0x0000555555fd97b4 in timerlist_run_timers () at ../qemu-8.0.2/util/qemu-timer.c:509 +#26 qemu_clock_run_timers () at ../qemu-8.0.2/util/qemu-timer.c:590 +#27 qemu_clock_run_all_timers () at ../qemu-8.0.2/util/qemu-timer.c:672 +#28 0x0000555555fd9a53 in main_loop_wait () at ../qemu-8.0.2/util/main-loop.c:603 +#29 0x0000555555e1ab17 in qemu_main_loop () at ../qemu-8.0.2/softmmu/runstate.c:731 +--Type <RET> for more, q to quit, c to continue without paging--c +#30 qemu_default_main () at ../qemu-8.0.2/softmmu/main.c:37 +#31 0x00007ffff6c15850 in __libc_start_call_main (main=main@entry=0x55555598baa0 <main>, argc=argc@entry=33, argv=argv@entry=0x7fffffffd338) + at ../sysdeps/nptl/libc_start_call_main.h:58 +#32 0x00007ffff6c1590a in __libc_start_main_impl + (main=0x55555598baa0 <main>, argc=33, argv=0x7fffffffd338, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffd328) + at ../csu/libc-start.c:360 +#33 0x000055555598e6f5 in _start () +``` diff --git a/results/classifier/gemma3:12b/graphic/169 b/results/classifier/gemma3:12b/graphic/169 new file mode 100644 index 00000000..fa5c9fbd --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/169 @@ -0,0 +1,2 @@ + +[RFC] dma buf: support sprite plane diff --git a/results/classifier/gemma3:12b/graphic/1703795 b/results/classifier/gemma3:12b/graphic/1703795 new file mode 100644 index 00000000..3b385128 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1703795 @@ -0,0 +1,6 @@ + +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/gemma3:12b/graphic/1708215 b/results/classifier/gemma3:12b/graphic/1708215 new file mode 100644 index 00000000..3e0d0460 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1708215 @@ -0,0 +1,26 @@ + +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/gemma3:12b/graphic/1713825 b/results/classifier/gemma3:12b/graphic/1713825 new file mode 100644 index 00000000..7de09e61 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1713825 @@ -0,0 +1,58 @@ + +Booting Windows 2016 with qxl video crashes qemu + +launched from libvirt. + +qemu version: 2.9.0 +host: Linux <hostname> 4.9.34-gentoo #1 SMP Sat Jul 29 13:28:43 PDT 2017 x86_64 Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz GenuineIntel GNU/Linux +guest: Windows 2016 64 bit + +Thread 28 (Thread 0x7f0e2edff700 (LWP 29860)): +#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 + set = {__val = {18446744067266837079, 139698892694944, 139699853745096, 139700858749789, 4222451712, 139694281220640, 139694281220741, 139694281220640, 139694281220640, 139694281220810, + 139694281220940, 139694281220640, 139694281220940, 0, 0, 0}} + pid = <optimized out> + tid = <optimized out> +#1 0x00007f0ea40b644a in __GI_abort () at abort.c:89 + save_stage = 2 + act = {__sigaction_handler = {sa_handler = 0x7f0e2edfe5c0, sa_sigaction = 0x7f0e2edfe5c0}, sa_mask = {__val = {139694281219872, 139698106269697, 139698892695344, 4, 2676511744, 0, 139698892695144, 0, + 139698892694912, 1, 4737316546111099904, 139700859888720, 4737316546111099904, 139700862161824, 139700911349760, 94211934977482}}, sa_flags = 416, + sa_restorer = 0x55af6ceb0500 <__PRETTY_FUNCTION__.36381>} + sigs = {__val = {32, 0 <repeats 15 times>}} +#2 0x00007f0ea40abab6 in __assert_fail_base (fmt=<optimized out>, assertion=assertion@entry=0x55af6ceafdca "offset < qxl->vga.vram_size", + file=file@entry=0x55af6ceaeaa0 "/var/tmp/portage/app-emulation/qemu-2.9.0-r2/work/qemu-2.9.0/hw/display/qxl.c", line=line@entry=416, + function=function@entry=0x55af6ceb0500 <__PRETTY_FUNCTION__.36381> "qxl_ram_set_dirty") at assert.c:92 + str = 0x7f0d1c026220 "\340r\002\034\r\177" + total = 4096 +#3 0x00007f0ea40abb81 in __GI___assert_fail (assertion=assertion@entry=0x55af6ceafdca "offset < qxl->vga.vram_size", + file=file@entry=0x55af6ceaeaa0 "/var/tmp/portage/app-emulation/qemu-2.9.0-r2/work/qemu-2.9.0/hw/display/qxl.c", line=line@entry=416, + function=function@entry=0x55af6ceb0500 <__PRETTY_FUNCTION__.36381> "qxl_ram_set_dirty") at assert.c:101 +No locals. +#4 0x000055af6cc58805 in qxl_ram_set_dirty (qxl=<optimized out>, ptr=<optimized out>) at /var/tmp/portage/app-emulation/qemu-2.9.0-r2/work/qemu-2.9.0/hw/display/qxl.c:416 + base = <optimized out> + offset = <optimized out> + qxl = <optimized out> + ptr = <optimized out> + base = <optimized out> + offset = <optimized out> +#5 0x000055af6cc5b9e2 in interface_release_resource (sin=0x55af71a91ed0, ext=...) at /var/tmp/portage/app-emulation/qemu-2.9.0-r2/work/qemu-2.9.0/hw/display/qxl.c:767 + qxl = 0x55af71a91450 + ring = <optimized out> + item = <optimized out> + id = 18446690739814400920 + __func__ = "interface_release_resource" +#6 0x00007f0ea510afa8 in red_drawable_unref (red_drawable=0x7f0d1c026120) at red-worker.c:101 +No locals. +#7 0x00007f0ea510b609 in red_drawable_unref (red_drawable=<optimized out>) at red-worker.c:104 +No locals. +#8 0x00007f0ea510eae9 in drawable_unref (drawable=drawable@entry=0x7f0e68285ac0) at display-channel.c:1438 + display = 0x55af71dbd3c0 + __FUNCTION__ = "drawable_unref" +#9 0x00007f0ea51109f7 in draw_until (display=display@entry=0x55af71dbd3c0, surface=surface@entry=0x7f0e6828aae8, last=0x7f0e68285ac0) at display-channel.c:1637 + container = 0x0 + now = 0x7f0e68285ac0 +#10 0x00007f0ea510f93f in display_channel_draw (display=0x55af71dbd3c0, area=0x7f0e2edfe8e0, surface_id=<optimized out>) at display-channel.c:1729 + surface = 0x7f0e6828aae8 + last = <optimized out> + __FUNCTION__ = "display_channel_draw" + __func__ = "display_channel_draw" \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1723731 b/results/classifier/gemma3:12b/graphic/1723731 new file mode 100644 index 00000000..35db7797 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1723731 @@ -0,0 +1,22 @@ + +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/gemma3:12b/graphic/1727 b/results/classifier/gemma3:12b/graphic/1727 new file mode 100644 index 00000000..dfe1e9ab --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1727 @@ -0,0 +1,82 @@ + +virtio-gpu-gl-pci console tries to make GL context before widget is realized leading to crash +Description of problem: +When `-vga none` is added to the command line, there is no crash. + +When it is not, two `GtkGLArea` widgets are created: one for VGA and one for `virtio-gpu-gl-pci`. Only the first one is realized, but the virgl code tries to create a GL context for the second. In `gd_gl_area_create_context`, `gtk_widget_get_window(vc->gfx.drawing_area)` evaluates to NULL a crash follows: + +``` +qemu: Gdk: gdk_window_create_gl_context: assertion 'GDK_IS_WINDOW (window)' failed +qemu: Gdk: gdk_gl_context_set_required_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_realize: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_make_current: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_get_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gtk: gtk_gl_area_make_current: assertion 'gtk_widget_get_realized (widget)' failed +qemu: Gdk: gdk_window_create_gl_context: assertion 'GDK_IS_WINDOW (window)' failed +qemu: Gdk: gdk_gl_context_set_required_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_realize: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_make_current: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_get_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gtk: gtk_gl_area_make_current: assertion 'gtk_widget_get_realized (widget)' failed +qemu: Gdk: gdk_window_create_gl_context: assertion 'GDK_IS_WINDOW (window)' failed +qemu: Gdk: gdk_gl_context_set_required_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_realize: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_make_current: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_get_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gtk: gtk_gl_area_make_current: assertion 'gtk_widget_get_realized (widget)' failed +qemu: Gdk: gdk_window_create_gl_context: assertion 'GDK_IS_WINDOW (window)' failed +qemu: Gdk: gdk_gl_context_set_required_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_realize: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_make_current: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_get_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gtk: gtk_gl_area_make_current: assertion 'gtk_widget_get_realized (widget)' failed +qemu: Gdk: gdk_window_create_gl_context: assertion 'GDK_IS_WINDOW (window)' failed +qemu: Gdk: gdk_gl_context_set_required_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_realize: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_make_current: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_get_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gtk: gtk_gl_area_make_current: assertion 'gtk_widget_get_realized (widget)' failed +qemu: Gdk: gdk_window_create_gl_context: assertion 'GDK_IS_WINDOW (window)' failed +qemu: Gdk: gdk_gl_context_set_required_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_realize: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_make_current: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_get_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gtk: gtk_gl_area_make_current: assertion 'gtk_widget_get_realized (widget)' failed +qemu: Gdk: gdk_window_create_gl_context: assertion 'GDK_IS_WINDOW (window)' failed +qemu: Gdk: gdk_gl_context_set_required_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_realize: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_make_current: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_get_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gtk: gtk_gl_area_make_current: assertion 'gtk_widget_get_realized (widget)' failed +qemu: Gdk: gdk_window_create_gl_context: assertion 'GDK_IS_WINDOW (window)' failed +qemu: Gdk: gdk_gl_context_set_required_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_realize: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_make_current: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_get_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gtk: gtk_gl_area_make_current: assertion 'gtk_widget_get_realized (widget)' failed +qemu: Gdk: gdk_window_create_gl_context: assertion 'GDK_IS_WINDOW (window)' failed +qemu: Gdk: gdk_gl_context_set_required_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_realize: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_make_current: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_get_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gtk: gtk_gl_area_make_current: assertion 'gtk_widget_get_realized (widget)' failed +qemu: Gdk: gdk_window_create_gl_context: assertion 'GDK_IS_WINDOW (window)' failed +qemu: Gdk: gdk_gl_context_set_required_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_realize: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_make_current: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_get_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gtk: gtk_gl_area_make_current: assertion 'gtk_widget_get_realized (widget)' failed +qemu: Gdk: gdk_window_create_gl_context: assertion 'GDK_IS_WINDOW (window)' failed +qemu: Gdk: gdk_gl_context_set_required_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_realize: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_make_current: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gdk: gdk_gl_context_get_version: assertion 'GDK_IS_GL_CONTEXT (context)' failed +qemu: Gtk: gtk_gl_area_make_current: assertion 'gtk_widget_get_realized (widget)' failed +qemu: Gdk: gdk_gl_context_make_current: assertion 'GDK_IS_GL_CONTEXT (context)' failed +gl_version 0 - compat profile +WARNING: running without ARB/KHR robustness in place may crash +qemu-system-x86_64: ../libepoxy/src/dispatch_common.c:872: epoxy_get_proc_address: Assertion `0 && "Couldn't find current GLX or EGL context.\n"' failed. +``` +Steps to reproduce: +1. Get OVMF. On Arch Linux, you can install the `edk2-ovmf` package. On other distros, find a similar package and modify the path in the command accordingly. +2. Run the command above. diff --git a/results/classifier/gemma3:12b/graphic/1729501 b/results/classifier/gemma3:12b/graphic/1729501 new file mode 100644 index 00000000..5a799d82 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1729501 @@ -0,0 +1,70 @@ + +qemu crashes with assertion error `off_cur_end >= off_cur' failed + +My host environment: Xen + QEMU + +git clones today's xen git and qemut git (2017-10-31) + +xen -- git://xenbits.xen.org/xen.git +commit 24fb44e971a62b345c7b6ca3c03b454a1e150abe + +qemu -- https://github.com/qemu/qemu +commit 47ba789c97c8d201d01058b00a14d8a9a85fcfe9 + +QEMU was compiled using: +./configure --prefix=/mnt/bin/ --enable-xen --target-list=i386-softmmu --extra-cflags="-I/mnt/xen/tools/include -I/mnt/xen/tools/libxc -I/mnt/xen/tools/xenstore" --extra-ldflags="-L/mnt/xen/tools/libxc -L/mnt/xen/tools/xenstore" --enable-debug --enable-debug-stack-usage + +Xen was configured with the above QEMU distribution: +./configure --with-system-qemu=/mnt/bin/bin/qemu-system-i386 + +QEMU command line: +/mnt/bin/bin/qemu-system-i386 -xen-domid 28 -chardev socket,id=libxl-cmd,path=/var/run/xen/qmp-libxl-28,server,nowait -no-shutdown -mon chardev=libxl-cmd,mode=control -chardev socket,id=libxenstat-cmd,path=/var/run/xen/qmp-libxenstat-28,server,nowait -mon chardev=libxenstat-cmd,mode=control -nodefaults -no-user-config -name ubu_hvm -vnc 0.0.0.0:1,to=99 -display none -serial pty -device cirrus-vga,vgamem_mb=8 -boot order=c -smp 2,maxcpus=2 -device rtl8139,id=nic0,netdev=net0,mac=00:16:3e:74:34:32 -netdev type=tap,id=net0,ifname=vif28.0-emu,script=no,downscript=no -device rtl8139,id=nic1,netdev=net1,mac=00:16:3e:5f:48:e4 -netdev type=tap,id=net1,ifname=vif28.1-emu,script=no,downscript=no -machine xenfv -m 1504 -drive file=/mnt/10G.hdd,if=ide,index=0,media=disk,format=raw,cache=writeback + +Produce: +I run a fuzzer program in guest vm, it may set incorrect values for graphics registers, sequencer registers and other registers. + +Seeing the following error from /var/log/xen/qemu-dm-<vm-name>.log: +qemu-system-i386: hw/display/cirrus_vga.c:712: cirrus_invalidate_region: Assertion `off_cur_end >= off_cur' failed. + +I can reproduce it at anytime, if you need to gather more diagnostic information or try test patches, I'm happy to help. + + +gdb bt: +#0 0x00007f81a64f8c37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 +#1 0x00007f81a64fc028 in __GI_abort () at abort.c:89 +#2 0x00007f81a64f1bf6 in __assert_fail_base (fmt=0x7f81a6646018 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", + assertion=assertion@entry=0x55d70cf8cdf2 "off_cur_end >= off_cur", file=file@entry=0x55d70cf8cda9 "hw/display/cirrus_vga.c", line=line@entry=712, + function=function@entry=0x55d70cf8db60 <__PRETTY_FUNCTION__.40643> "cirrus_invalidate_region") at assert.c:92 +#3 0x00007f81a64f1ca2 in __GI___assert_fail (assertion=0x55d70cf8cdf2 "off_cur_end >= off_cur", file=0x55d70cf8cda9 "hw/display/cirrus_vga.c", line=712, + function=0x55d70cf8db60 <__PRETTY_FUNCTION__.40643> "cirrus_invalidate_region") at assert.c:101 +#4 0x000055d70cb66445 in cirrus_invalidate_region (s=0x55d70ee3a4b0, off_begin=4190568, off_pitch=1842, bytesperline=5056, lines=2922) at hw/display/cirrus_vga.c:712 +#5 0x000055d70cb6660c in cirrus_bitblt_common_patterncopy (s=0x55d70ee3a4b0) at hw/display/cirrus_vga.c:752 +#6 0x000055d70cb6676d in cirrus_bitblt_videotovideo_patterncopy (s=0x55d70ee3a4b0) at hw/display/cirrus_vga.c:786 +#7 0x000055d70cb670c5 in cirrus_bitblt_videotovideo (s=0x55d70ee3a4b0) at hw/display/cirrus_vga.c:986 +#8 0x000055d70cb678bf in cirrus_bitblt_start (s=0x55d70ee3a4b0) at hw/display/cirrus_vga.c:1136 +#9 0x000055d70cb6880b in cirrus_vga_write_gr (s=0x55d70ee3a4b0, reg_index=42, reg_value=228) at hw/display/cirrus_vga.c:1652 +#10 0x000055d70cb6ab86 in cirrus_vga_ioport_write (opaque=0x55d70ee3a4b0, addr=975, val=228, size=1) at hw/display/cirrus_vga.c:2754 +#11 0x000055d70c91d9c0 in memory_region_write_accessor (mr=0x55d70ee4af70, addr=31, value=0x7fffdaaeaf38, size=1, shift=8, mask=255, attrs=...) + at /mnt/qemu/memory.c:560 +#12 0x000055d70c91dc3a in access_with_adjusted_size (addr=30, value=0x7fffdaaeaf38, size=2, access_size_min=1, access_size_max=1, + access_fn=0x55d70c91d8c9 <memory_region_write_accessor>, mr=0x55d70ee4af70, attrs=...) at /mnt/qemu/memory.c:627 +#13 0x000055d70c920f48 in memory_region_dispatch_write (mr=0x55d70ee4af70, addr=30, data=58410, size=2, attrs=...) at /mnt/qemu/memory.c:1503 +#14 0x000055d70c8c51e0 in flatview_write_continue (fv=0x55d70ecb66d0, addr=974, attrs=..., buf=0x7fffdaaeb0f0 "*\344W\026\377\177", len=4, addr1=30, l=2, + mr=0x55d70ee4af70) at /mnt/qemu/exec.c:2951 +#15 0x000055d70c8c5390 in flatview_write (fv=0x55d70ecb66d0, addr=974, attrs=..., buf=0x7fffdaaeb0f0 "*\344W\026\377\177", len=4) at /mnt/qemu/exec.c:3002 +#16 0x000055d70c8c5406 in address_space_write (as=0x55d70d70d5e0 <address_space_io>, addr=974, attrs=..., buf=0x7fffdaaeb0f0 "*\344W\026\377\177", len=4) + at /mnt/qemu/exec.c:3014 +#17 0x000055d70c914fb3 in cpu_outl (addr=974, val=374858794) at /mnt/qemu/ioport.c:81 +#18 0x000055d70ca0253f in do_outp (addr=974, size=4, val=374858794) at /mnt/qemu/hw/i386/xen/xen-hvm.c:782 +#19 0x000055d70ca02888 in cpu_ioreq_pio (req=0x7fffdaaeb210) at /mnt/qemu/hw/i386/xen/xen-hvm.c:852 +#20 0x000055d70ca02f2e in handle_ioreq (state=0x55d70e0cf3d0, req=0x7fffdaaeb210) at /mnt/qemu/hw/i386/xen/xen-hvm.c:961 +#21 0x000055d70ca0343e in cpu_handle_ioreq (opaque=0x55d70e0cf3d0) at /mnt/qemu/hw/i386/xen/xen-hvm.c:1089 +#22 0x000055d70ce75d69 in aio_dispatch_handlers (ctx=0x55d70e098550) at util/aio-posix.c:406 +#23 0x000055d70ce75f0b in aio_dispatch (ctx=0x55d70e098550) at util/aio-posix.c:437 +#24 0x000055d70ce70b46 in aio_ctx_dispatch (source=0x55d70e098550, callback=0x0, user_data=0x0) at util/async.c:261 +#25 0x00007f81a7215e04 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 +#26 0x000055d70ce74455 in glib_pollfds_poll () at util/main-loop.c:214 +#27 0x000055d70ce7456a in os_host_main_loop_wait (timeout=16061710) at util/main-loop.c:261 +#28 0x000055d70ce7463f in main_loop_wait (nonblocking=0) at util/main-loop.c:515 +#29 0x000055d70ca8e6a6 in main_loop () at vl.c:1995 +#30 0x000055d70ca96815 in main (argc=42, argv=0x7fffdaaeb888, envp=0x7fffdaaeb9e0) at vl.c:4897 \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1730 b/results/classifier/gemma3:12b/graphic/1730 new file mode 100644 index 00000000..4258381f --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1730 @@ -0,0 +1,17 @@ + +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/gemma3:12b/graphic/1730099 b/results/classifier/gemma3:12b/graphic/1730099 new file mode 100644 index 00000000..de1b1438 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1730099 @@ -0,0 +1,10 @@ + +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/gemma3:12b/graphic/1730101 b/results/classifier/gemma3:12b/graphic/1730101 new file mode 100644 index 00000000..c87aa9a5 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1730101 @@ -0,0 +1,6 @@ + +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/gemma3:12b/graphic/1739 b/results/classifier/gemma3:12b/graphic/1739 new file mode 100644 index 00000000..fae27eb4 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1739 @@ -0,0 +1,37 @@ + +Build process is broken in /audio/dbusaudio.c:36: pixman.h cannot be found +Description of problem: +Hello. + +I try to build qemu using commit aa1048e33c. But build process stop in /audio/dbusaudio.c with this error log: + +``` +[979/9916] Generating audio-dbus.modin...d (wrapped by meson to capture output) +FAILED: audio-dbus.modinfo +/home/fred/qemu-git/src/qemu/build-full/pyvenv/bin/meson --internal exe --capture audio-dbus.modinfo -- /home/fred/qemu-git/src/qemu/build-full/pyvenv/bin/python3 /home/fred/qemu-git/src/qemu/scripts/modinfo-collect.py ../audio/dbusaudio.c +--- stderr --- +In file included from /home/fred/qemu-git/src/qemu/include/ui/console.h:4, + from /home/fred/qemu-git/src/qemu/ui/dbus.h:31, + from ../audio/dbusaudio.c:36: +/home/fred/qemu-git/src/qemu/include/ui/qemu-pixman.h:12:10: fatal error: pixman.h: No such file or directory + 12 | #include <pixman.h> + | ^~~~~~~~~~ +compilation terminated. +``` + +Of course I have pixman.h which could be find in pixman package: + +``` +pacman -Ql pixman | grep pixman.h +pixman /usr/include/pixman-1/pixman.h +``` + +Used configuration: ```--prefix=/usr --sysconfdir=/etc --localstatedir=/var --libexecdir=/usr/lib/qemu --smbd=/usr/bin/smbd --enable-modules --enable-sdl --disable-werror``` + +The last time I got a buildable qemu was with commit 79dbd910c9, 3 days ago. +Steps to reproduce: +1. Grab latest commit +2. Use this configure line: ```--prefix=/usr --sysconfdir=/etc --localstatedir=/var --libexecdir=/usr/lib/qemu --smbd=/usr/bin/smbd --enable-modules --enable-sdl --disable-werror``` +3. make and wait +Additional information: + diff --git a/results/classifier/gemma3:12b/graphic/1745316 b/results/classifier/gemma3:12b/graphic/1745316 new file mode 100644 index 00000000..66cfecbc --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1745316 @@ -0,0 +1,175 @@ + +SDL1.x>SDL2 regressions: non-usbtablet mouse position reporting is broken, and VGA/compatmonitor/serial/etc view switching is unusable + +Hi, + +I almost exclusively use -sdl when I use QEMU. The GTK UI (I'm on Linux) distinctly takes a few extra seconds to start on every boot, and I don't really ever use the extra controls it provides. I hope the SDL-based UI never goes away :) + +The SDL 1.2 > SDL 2.0 update (committed between June 8-20 2017) introduced the following two regressions: + +- PS/2 and serial mouse position reporting became completely broken (only usbtablet works) + +- The compatmonitor/serial/parallel "views" try to open new windows, which does not play well on my system at all + +First of all, here are the bisection details: + +https://github.com/qemu/qemu/commit/269c20b2bbd2aa8531e0cdc741fb166f290d7a2b + (June 8 2017): the last version that works + +https://github.com/qemu/qemu/commit/7e56accdaf35234b69c33c85e4a44a5d56325e53 + (June 20 2017): the first version that fails + +Here are the changelists between these two revisions: + +https://github.com/qemu/qemu/compare/269c20b...7e56acc +(compare direction: OLD to NEW) (Commits: 60 Files changed: 85) + +https://github.com/qemu/qemu/compare/7e56acc...269c20b +(compare direction: NEW to OLD) (Commits: 41 Files changed: 108) + +(Someone else more familiar with Git might know why GitHub returns results for both compare directions. I'm including both links just in case.) + +I've found that configuring commit 7e56acc using --with-sdlapi=1.2 completely remedies all issues. Thus, I think the issue is with SDL 2. + +== #1: Broken mouse position reporting ===================== + +This surfaces immediately with older operating systems. I first experienced it when trying to install OS/2 for the first time, and thought there was something wrong with OS/2. Then I experienced the same issues in Windows 3.1 and MS-DOS applications and I knew something was up with QEMU. + +In a nice coincidence, I've recently been playing around with prehistorically ancient Linux systems, and while looking around a Linux 0.99-based SLS system from 1992 I discovered a low-level (console) mouse-testing utility buried in /usr/X386. This utility only works when I configure QEMU to use a serial mouse, but it reveals some very interesing data: the dx and dy values ("d" = "delta", right?) received by the kernel do not contain relative values such as -1, -10, 2, 5, etc, but instead absolute values such as 0, 12, 37, 112, 329, etc. + +Similarly, if I configure Windows 3.1 to use a serial mouse, the mouse position jumps exponentially around the screen relative to my mouse movements (it's very hard to control), consistent with delta values being reported as absolute instead of relative. + +I found that the DOS CuteMouse driver comes with a mouse-testing program. CuteMouse absolutely refuses to detect QEMU's serial mouse for some reason (?!), but when QEMU is running in PS/2 mode, the mouse tester that comes with CuteMouse reports that the mouse at 632,192 no matter how much I move the mouse around the window. If I look carefully I can see the DOS cursor flickering back and forth as I move the mouse and the tester rewrites the line showing the position info, so I don't think the test program is broken. + +I got curious and wondered if this was actually an internal SDL bug. However, the following test program reports perfect values for me: + +--8<-------------------------------------------------------- + +#include <stdio.h> +#include "SDL2/SDL.h" +int main(void) { + SDL_Init(SDL_INIT_VIDEO); + SDL_Window *window = SDL_CreateWindow("Mouse test", + SDL_WINDOWPOS_UNDEFINED, SDL_WINDOWPOS_UNDEFINED, + 640, 480, SDL_WINDOW_RESIZABLE + ); + if (window == NULL) { + perror(SDL_GetError()); + exit(1); + } + for (;;) { + SDL_Event event; + while (SDL_PollEvent(&event)) { + if (event.type == SDL_MOUSEMOTION) { + printf( + "x=%d y=%d xrel=%d yrel=%d\n", + event.motion.x, event.motion.y, + event.motion.xrel, event.motion.yrel + ); + } + if ( + event.type == SDL_KEYDOWN || + event.type == SDL_QUIT + ) { + SDL_DestroyWindow(window); + SDL_Quit(); + exit(0); + } + } + } +} + +(gcc ... -lSDL2) + +------------------------------------------------------------ + +Unfortunately it would seem the issue is QEMU-specific. + +--- + +Finding modern test targets to verify mouse functionality with was actually a small challenge. I tested Ubuntu, Lubuntu and even GParted, but the recent Linux kernels in all three systems automatically loaded the usbtablet module early in the boot process, completely hiding the bug. + +I've found two actively-maintained somewhat-mainstream platforms that make for good tests. These are both ISOs: + +- ReactOS: + - http://www.reactos.org/download + - pick "Download LiveCD" and then "proceed with the download" at + bottom-right of popup + +- Tiny Core Linux: + - http://distro.ibiblio.org/tinycorelinux/downloads.html + - pick TinyCore (16MB) + +ReactOS is a very good example, as it's actively maintained and is probably heavily tested in QEMU (albeit apparently without SDL(2)). + +Tiny Core is a bit of a mixed bag. It's actively maintained and uses a recent kernel (without usbdevice). It also uses a resurrected low-memory XFree86 target that was officially dropped decades ago for its graphics (and mouse input). It could be argued that Tiny Core's mild obscurity makes it an even better test target. + +--- + +I've attached to this report the mouse test utilities I've played with. Both are faster to iterate with than waiting for Tiny Core or ReactOS to boot. + +----- FreeDOS + CuteMouse + mousetst ----- + +This boots completely and is ready to look at the mouse position in around a second. It automatically starts the mouse tester on startup and APM-shuts-down QEMU when you exit the mouse tester with ESC. I can highly recommend this version for iteration/verification. + +$ qemu-system-i386 -fda freedos-mousetest.img +$ qemu-system-i386 -fda freedos-mousetest.img -sdl + + +----- Linux-0.99 (SLS) + 'mouse.c' ----- + +This is a heavily stripped-down SLS configuration containing just the mouse testing utility. + +$ qemu-system-i386 -boot a -fda sls-boot.img -hda sls-mousetest.img \ + -serial msmouse + +$ qemu-system-i386 -boot a -fda sls-boot.img -hda sls-mousetest.img \ + -serial msmouse -sdl + +Login as root (no password), and then + +# ./mouse Microsoft /dev/ttyS0 + +Also, the following produces junk results, but I'm including it because it may be interesting anyway: + +$ qemu-system-i386 -boot a -fda sls-boot.img -hda sls-mousetest.img -sdl + +and + +# ./mouse Microsoft /dev/ps2aux + +The reason I think this is noteworthy is that the button state affects the reported values (incorrectly, but they do still change), but moving the mouse does not. So while the interpretation is wrong, the behavior seems to be similar to that reported by CuteMouse's mouse tester. (Unless the position fields are being perfectly skipped over.) + +When you're done with this image - `halt` takes several seconds and there's really no point. Just closing QEMU manually is faster. (This is also why I used the shorter -[hf]da syntax - writes to the disk images are not relevant.) + +(Also - since I can't possibly leave this info out :) - http://www.oldlinux.org/Linux.old/distributions/SLS/, `sls-1.0.tar.bz2`. This is a turnkey disk image that Just Works(TM). `boot.img` attached below is in fact the same as `a.img` in this archive.) + +--- + +In case it's useful, I included a Windows 3.1 test image when I reported https://bugs.launchpad.net/qemu/+bug/1745312. This image (which happens to be configured for PS/2) can be found in this folder: https://drive.google.com/drive/folders/1WdZVBh5Trs9HLC186-nHyKeqaSxfyM2c + +For reference: this image includes a lot of cruft as it's an active test image I've used for a lot of different things. It contains a full copy of the contents of the Win3.1 installation disks in W31INST. You can `deltree c:\windows` and reinstall by running `setup` in that directory (takes 3-5 minutes), or `subst a: c:\w31inst` before starting Windows and you'll be able to use Windows Setup to switch to a serial mouse. + +== #2: SDL view switching unusability ====================== + +This issue is (somewhat) more straightforward to demonstrate. Simply + +$ qemu-system-i386 -sdl + +and then hit CTRL+ALT+2 (or 3 or 4). + +On my system, when I do this, QEMU creates and destroys new windows in an infinite loop for as long as I have CTRL+ALT+n held down. I have to hit `2` really quickly! + +I've also observed that some internal contention can frequently cause the compatmonitor window to become blind to the Enter key. It seems to be that this occurs most often when the windowmanager I'm using (tested using i3 and openbox) has focus-follows-mouse enabled and the mouse is over the area of the screen where the compatmonitor window opens itself. Perhaps this is caused by the CTRL+ALT capture code interacting badly with window focus state? (I'm very very interested to hear if you cannot reproduce this.) + +I initially thought all of these changes/glitches were due to some kind of messed-up "upgrade" / deliberate feature that happened to be broken on my system. But the only (obviously-)UI-related tasks I found in the changelist above just mention upgrading SDL, with no particular UI work (that I can see). It looks like this is actually an SDL thing - unless some (preparatory?) changes occurred in QEMU before the commit window I discovered. I have no idea. + +A couple things about fixing this that I want to mention: + +The way the GTK UI does things, views can be switched inside the same window, or they can be detached into new windows. This provides the best of both worlds - and there are situations where I do want both behaviors. + +If QEMU is not averse to burying an obscure option somewhere that lets me pick whether SDL will open views in new windows or the same window, that could be very nice - and it would bring the SDL UI to perfect feature parity with the GTK UI, too. But I'm not sure what QEMU's stance on obscure options is. + +That said, my preference for the SDL 1.x way of doing things is admittedly very probably biased by the usability issues created by this bug. Incidentally, I've taken to using `-serial null -monitor stdio`. But for that to work I have to remember to add it ahead of time, and I do often forget, heh. + +I'll be very interested to play with QEMU view switching once this is less glitchy. If the fixed implementation still opens new windows, I'll see what I think of that once it works stably. :) \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1746394 b/results/classifier/gemma3:12b/graphic/1746394 new file mode 100644 index 00000000..8e5236e9 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1746394 @@ -0,0 +1,4 @@ + +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/gemma3:12b/graphic/175 b/results/classifier/gemma3:12b/graphic/175 new file mode 100644 index 00000000..f254b7ce --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/175 @@ -0,0 +1,2 @@ + +qmp monitor deadlock (with spice events for ex) diff --git a/results/classifier/gemma3:12b/graphic/1755912 b/results/classifier/gemma3:12b/graphic/1755912 new file mode 100644 index 00000000..a40c0992 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1755912 @@ -0,0 +1,69 @@ + +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/gemma3:12b/graphic/1762558 b/results/classifier/gemma3:12b/graphic/1762558 new file mode 100644 index 00000000..58fe33cc --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1762558 @@ -0,0 +1,29 @@ + +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/gemma3:12b/graphic/1766841 b/results/classifier/gemma3:12b/graphic/1766841 new file mode 100644 index 00000000..59cae4f9 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1766841 @@ -0,0 +1,21 @@ + +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/gemma3:12b/graphic/1775011 b/results/classifier/gemma3:12b/graphic/1775011 new file mode 100644 index 00000000..cea5afc0 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1775011 @@ -0,0 +1,21 @@ + +-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/gemma3:12b/graphic/1777672 b/results/classifier/gemma3:12b/graphic/1777672 new file mode 100644 index 00000000..565b77af --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1777672 @@ -0,0 +1,68 @@ + +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/gemma3:12b/graphic/1778182 b/results/classifier/gemma3:12b/graphic/1778182 new file mode 100644 index 00000000..e5dacd0d --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1778182 @@ -0,0 +1,23 @@ + +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/gemma3:12b/graphic/1779649 b/results/classifier/gemma3:12b/graphic/1779649 new file mode 100644 index 00000000..9f20a0c7 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1779649 @@ -0,0 +1,8 @@ + +Suspending a domain works with a 3.16 gues kernel but not with a 4.16 one + +Suspending a domain with `systemctl suspend` works with a guest 3.16 kernel (jessie), the domain goes into `pmsuspend` in libvirt but doesn't work anymore with a 4.16 one (sid) where: + - With a QXL card: the spice display just goes black and the domain stays `running` in libvirt but is "dead" + - With a VGA card: the screen goes black and comes back immediately, the domain stays fine + +Qemu: Master, 281bd281222776229d5dbf84d1a5c6d8d9d2a34b \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1779650 b/results/classifier/gemma3:12b/graphic/1779650 new file mode 100644 index 00000000..924cd840 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1779650 @@ -0,0 +1,6 @@ + +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/gemma3:12b/graphic/1780812 b/results/classifier/gemma3:12b/graphic/1780812 new file mode 100644 index 00000000..b6e8de9a --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1780812 @@ -0,0 +1,10 @@ + +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/gemma3:12b/graphic/1780815 b/results/classifier/gemma3:12b/graphic/1780815 new file mode 100644 index 00000000..74ed1b89 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1780815 @@ -0,0 +1,8 @@ + +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/gemma3:12b/graphic/1781515 b/results/classifier/gemma3:12b/graphic/1781515 new file mode 100644 index 00000000..90c03ed8 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1781515 @@ -0,0 +1,14 @@ + +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/gemma3:12b/graphic/1782 b/results/classifier/gemma3:12b/graphic/1782 new file mode 100644 index 00000000..89c1a40c --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1782 @@ -0,0 +1,59 @@ + +8.1.0rc0: Build failure compiling with clang on windows +Description of problem: +Building in Clang64 environment finally fails with: +``` +... +[1416/2001] Compiling C object libcommon.fa.p/ui_dbus-listener.c.obj +FAILED: libcommon.fa.p/ui_dbus-listener.c.obj +"cc" "-m64" "-mcx16" "-Ilibcommon.fa.p" "-Isubprojects/dtc/libfdt" "-I../subprojects/dtc/libfdt" "-Iui" "-I../ui" "-IC:/msys64/clang64/include/pixman-1" "-IC:/msys64/clang64/include/glib-2.0" "-IC:/msys64/clang64/lib/glib-2.0/include" "-IC:/msys64/clang64/include/ncursesw" "-fcolor-diagnostics" "-Wall" "-Winvalid-pch" "-std=gnu11" "-O2" "-g" "-fstack-protector-strong" "-Wundef" "-Wwrite-strings" "-Wmissing-prototypes" "-Wstrict-prototypes" "-Wredundant-decls" "-Wold-style-definition" "-Wtype-limits" "-Wformat-security" "-Wformat-y2k" "-Winit-self" "-Wignored-qualifiers" "-Wempty-body" "-Wnested-externs" "-Wendif-labels" "-Wexpansion-to-defined" "-Wmissing-format-attribute" "-Wno-initializer-overrides" "-Wno-missing-include-dirs" "-Wno-shift-negative-value" "-Wno-string-plus-int" "-Wno-typedef-redefinition" "-Wno-tautological-type-limit-compare" "-Wno-psabi" "-Wno-gnu-variable-sized-type-not-at-end" "-Wthread-safety" "-iquote" "." "-iquote" "C:/msys64/home/helge/qemu-8.1.0-rc0" "-iquote" "C:/msys64/home/helge/qemu-8.1.0-rc0/include" "-iquote" "C:/msys64/home/helge/qemu-8.1.0-rc0/host/include/x86_64" "-iquote" "C:/msys64/home/helge/qemu-8.1.0-rc0/host/include/generic" "-iquote" "C:/msys64/home/helge/qemu-8.1.0-rc0/tcg/i386" "-D_GNU_SOURCE" "-D_FILE_OFFSET_BITS=64" "-D_LARGEFILE_SOURCE" "-fno-strict-aliasing" "-fno-common" "-fwrapv" "-fno-pie" "-DNCURSES_WIDECHAR" "-DNCURSES_WIDECHAR=1" -MD -MQ libcommon.fa.p/ui_dbus-listener.c.obj -MF "libcommon.fa.p/ui_dbus-listener.c.obj.d" -o libcommon.fa.p/ui_dbus-listener.c.obj "-c" ../ui/dbus-listener.c +../ui/dbus-listener.c:355:10: error: call to undeclared function 'd3d_texture2d_release0'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration] + if (!d3d_texture2d_release0(tex, &err)) { + ^ +../ui/dbus-listener.c:360:10: error: call to undeclared function 'd3d_texture2d_share'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration] + if (!d3d_texture2d_share(tex, &share_handle, &err)) { + ^ +../ui/dbus-listener.c:392:10: error: call to undeclared function 'd3d_texture2d_acquire0'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration] + if (!d3d_texture2d_acquire0(tex, &err)) { + ^ +3 errors generated. +ninja: build stopped: subcommand failed. +make[1]: *** [Makefile:162: run-ninja] Error 1 +make[1]: Leaving directory '/home/helge/qemu-8.1.0-rc0/build' +make: *** [GNUmakefile:11: all] Error 2 + +... +``` +Steps to reproduce: +1. Open Clang64 console +2. `pacman -Syu` +3. `pacman -S binutils mingw-w64-clang-x86_64-toolchain mingw-w64-clang-x86_64-glib2 mingw-w64-clang-x86_64-ninja mingw-w64-clang-x86_64-pixman mingw-w64-clang-x86_64-python mingw-w64-clang-x86_64-python-sphinx mingw-w64-clang-x86_64-python-sphinx_rtd_theme` +4. `wget https://download.qemu.org/qemu-8.1.0-rc0.tar.xz` +5. `tar -xf qemu-8.1.0-rc0.tar.xz` +6. `cd qemu-8.1.0-rc0` +7. `./configure --target-list=x86_64-softmmu` +8. `make` +Additional information: +The used cc is clang in Msys2/Clang64 environment: +``` +$ md5sum /clang64/bin/cc.exe /clang64/bin/clang.exe +bb70e04a10456b05b07f14d190ad9015 */clang64/bin/cc.exe +bb70e04a10456b05b07f14d190ad9015 */clang64/bin/clang.exe +``` + +On manually repeating the command in build directory a different error is shown: +``` +$ cd build +$ "cc" "-m64" "-mcx16" "-Ilibcommon.fa.p" "-Isubprojects/dtc/libfdt" "-I../subprojects/dtc/libfdt" "-Iui" "-I../ui" "-IC:/msys64/clang64/include/pixman-1" "-IC:/msys64/clang64/include/glib-2.0" "-IC:/msys64/clang64/lib/glib-2.0/include" "-IC:/msys64/clang64/include/ncursesw" "-fcolor-diagnostics" "-Wall" "-Winvalid-pch" "-std=gnu11" "-O2" "-g" "-fstack-protector-strong" "-Wundef" "-Wwrite-strings" "-Wmissing-prototypes" "-Wstrict-prototypes" "-Wredundant-decls" "-Wold-style-definition" "-Wtype-limits" "-Wformat-security" "-Wformat-y2k" "-Winit-self" "-Wignored-qualifiers" "-Wempty-body" "-Wnested-externs" "-Wendif-labels" "-Wexpansion-to-defined" "-Wmissing-format-attribute" "-Wno-initializer-overrides" "-Wno-missing-include-dirs" "-Wno-shift-negative-value" "-Wno-string-plus-int" "-Wno-typedef-redefinition" "-Wno-tautological-type-limit-compare" "-Wno-psabi" "-Wno-gnu-variable-sized-type-not-at-end" "-Wthread-safety" "-iquote" "." "-iquote" "C:/msys64/home/helge/qemu-8.1.0-rc0" "-iquote" "C:/msys64/home/helge/qemu-8.1.0-rc0/include" "-iquote" "C:/msys64/home/helge/qemu-8.1.0-rc0/host/include/x86_64" "-iquote" "C:/msys64/home/helge/qemu-8.1.0-rc0/host/include/generic" "-iquote" "C:/msys64/home/helge/qemu-8.1.0-rc0/tcg/i386" "-D_GNU_SOURCE" "-D_FILE_OFFSET_BITS=64" "-D_LARGEFILE_SOURCE" "-fno-strict-aliasing" "-fno-common" "-fwrapv" "-fno-pie" "-DNCURSES_WIDECHAR" "-DNCURSES_WIDECHAR=1" -MD -MQ libcommon.fa.p/ui_dbus-listener.c.obj -MF "libcommon.fa.p/ui_dbus-listener.c.obj.d" -o libcommon.fa.p/ui_dbus-listener.c.obj "-c" ../ui/dbus-listener.c +../ui/dbus-listener.c:236:9: error: expected expression + Error *err = NULL; + ^ +../ui/dbus-listener.c:240:56: error: use of undeclared identifier 'err' + if (!d3d_texture2d_release0(ddl->d3d_texture, &err)) { + ^ +../ui/dbus-listener.c:241:30: error: use of undeclared identifier 'err' + error_report_err(err); + ^ +3 errors generated. + +``` diff --git a/results/classifier/gemma3:12b/graphic/1784900 b/results/classifier/gemma3:12b/graphic/1784900 new file mode 100644 index 00000000..f0dae0ff --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1784900 @@ -0,0 +1,41 @@ + +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/gemma3:12b/graphic/1785197 b/results/classifier/gemma3:12b/graphic/1785197 new file mode 100644 index 00000000..a2879f29 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1785197 @@ -0,0 +1,41 @@ + +qemu 2.12.0 crash during install windows 10 with vga + +Same issue as https://www.qubes-os.org/doc/windows-vm/ , it's not easy to reproduced. +cpu_physical_memory_snapshot_get_dirty: Assertion `start + length <= snap->end’ failed + +Qemu version is 2.12.0. +(gdb) bt +#0 0x00007f504ed6fc37 in raise () from /lib/x86_64-linux-gnu/libc.so.6 +#1 0x00007f504ed73028 in abort () from /lib/x86_64-linux-gnu/libc.so.6 +#2 0x00007f504ed68bf6 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 +#3 0x00007f504ed68ca2 in __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6 +#4 0x00005585bbdc9641 in cpu_physical_memory_snapshot_get_dirty (snap=snap@entry=0x5585bfdc2ff0, start=<optimized out>, length=<optimized out>) + at /qemu-2.12/exec.c:1264 +#5 0x00005585bbe2b4de in memory_region_snapshot_get_dirty (mr=mr@entry=0x5585c06e3d10, snap=snap@entry=0x5585bfdc2ff0, addr=<optimized out>, + size=<optimized out>) at /qemu-2.12/memory.c:1997 +#6 0x00005585bbe552a4 in vga_draw_graphic (full_update=0, s=0x5585c06e3d00) at /qemu-2.12/hw/display/vga.c:1671 +#7 vga_update_display (opaque=0x5585c06e3d00) at /qemu-2.12/hw/display/vga.c:1767 +#8 0x00005585bc0d9a8f in qemu_spice_display_refresh (ssd=0x5585c06e3930) at /qemu-2.12/ui/spice-display.c:478 +#9 0x00005585bc0ced72 in dpy_refresh (s=0x5585c081b2a0) at /qemu-2.12/ui/console.c:1629 +#10 gui_update (opaque=0x5585c081b2a0) at /qemu-2.12/ui/console.c:203 +#11 0x00005585bc1d333c in timerlist_run_timers (timer_list=0x5585bee1f950) at /qemu-2.12/util/qemu-timer.c:536 +#12 0x00005585bc1d35a3 in qemu_clock_run_timers (type=QEMU_CLOCK_REALTIME) at /qemu-2.12/util/qemu-timer.c:547 +#13 qemu_clock_run_all_timers () at /qemu-2.12/util/qemu-timer.c:674 +#14 0x00005585bc1d3aa4 in main_loop_wait (nonblocking=<optimized out>) at /qemu-2.12/util/main-loop.c:528 +#15 0x00005585bbdc2f8a in main_loop () at /qemu-2.12/vl.c:1973 +#16 main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at /qemu-2.12/vl.c:4804 + +(gdb) frame 5 +(gdb) p/x *snap +$1 = {start = 0x1000c0000, end = 0x1000c0000, dirty = 0x5585bfdc3000} + +Here the snap->start is identical to snap->end , I think something is wrong. +In function vga_draw_graphic, the snap is allocated from region_start/region_end. + snap = memory_region_snapshot_and_clear_dirty(&s->vram, region_start, + region_end - region_start, + DIRTY_MEMORY_VGA); +Is that possible for region_start== region_end ? + +Commandline: +/usr/bin/kvm -name guest=win10-2,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/run/lib/libvirt/qemu/domain-51-win10-2/master-key.aes -machine pc-i440fx-2.12,accel=kvm,usb=off,system=windows,dump-guest-core=off -cpu qemu64,hv_time,hv_relaxed,hv_spinlocks=0x2000 -m size=4194304k,slots=10,maxmem=34359738368k -realtime mlock=off -smp 2,maxcpus=24,sockets=24,cores=1,threads=1 -numa node,nodeid=0,cpus=0-23,mem=4096 -uuid cb871760-e684-4926-8f0b-270f7ff35539 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/run/lib/libvirt/qemu/domain-51-win10-2/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -chardev socket,id=charmonitor_cas,path=/run/lib/libvirt/qemu/domain-51-win10-2/monitor.sock.cas,server,nowait -mon chardev=charmonitor_cas,id=monitor_cas,mode=control -rtc base=localtime,clock=vm,driftfix=slew -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device usb-ehci,id=usb1,bus=pci.0,addr=0x4 -device nec-usb-xhci,id=usb2,bus=pci.0,addr=0x5 -device virtio-scsi-pci,id=scsi1,bus=pci.0,addr=0x6 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x7 -device usb-hub,id=hub0,bus=usb.0,port=1 -drive file=/vms/images/win10-2,format=qcow2,if=none,id=drive-virtio-disk0,cache=directsync,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x8,pci_hotpluggable=on,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/vms/isos/virtio-win10.vfd,format=raw,if=none,id=drive-fdc0-0-0,readonly=on,cache=directsync,aio=native -global isa-fdc.driveA=drive-fdc0-0-0 -global isa-fdc.bootindexA=4 -drive file=/vms/nfs/windows_msdn_iso/cn_windows_10_multi-edition_version_1709_updated_sept_2017_x64_dvd_100090804.iso,format=raw,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,bootindex=2 -netdev tap,fd=62,id=hostnet0,vhost=on,vhostfd=63 -device virtio-net-pci,pci_hotpluggable=on,netdev=hostnet0,id=net0,mac=0c:da:41:1d:11:5b,bus=pci.0,addr=0x3,bootindex=3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/win10-2.agent,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0,port=2 -vnc 0.0.0.0:0 -spice port=5901,tls-port=5902,addr=0.0.0.0,disable-ticketing,x509-dir=/etc/pki/libvirt-spice,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=16777216,vram64_size_mb=0,vgamem_mb=16,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x9 -msg timestamp=on \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1787 b/results/classifier/gemma3:12b/graphic/1787 new file mode 100644 index 00000000..49138d9b --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1787 @@ -0,0 +1,14 @@ + +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： + +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/gemma3:12b/graphic/1788665 b/results/classifier/gemma3:12b/graphic/1788665 new file mode 100644 index 00000000..62890e33 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1788665 @@ -0,0 +1,43 @@ + +Low 2D graphics performance with Windows 10 (1803) VGA passthrough VM using "Spectre" protection + +Windows 10 (1803) VM using VGA passthrough via qemu script. + +After upgrading Windows 10 Pro VM to version 1803, or possibly after applying the March/April security updates from Microsoft, the VM would show low 2D graphics performance (sluggishness in 2D applications and low Passmark results). + +Turning off Spectre vulnerability protection in Windows remedies the issue. + +Expected behavior: +qemu/kvm hypervisor to expose firmware capabilities of host to guest OS - see https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/CVE-2017-5715-and-hyper-v-vms + +Background: + +Starting in March or April Microsoft began to push driver updates in their updates / security updates. See https://support.microsoft.com/en-us/help/4073757/protect-your-windows-devices-against-spectre-meltdown + +One update concerns the Intel microcode - see https://support.microsoft.com/en-us/help/4100347. It is activated by default within Windows. + +Once the updates are applied within the Windows guest, 2D graphics performance drops significantly. Other performance benchmarks are not affected. + +A bare metal Windows installation does not display a performance loss after the update. See https://heiko-sieger.info/low-2d-graphics-benchmark-with-windows-10-1803-kvm-vm/ + +Similar reports can be found here: +https://www.reddit.com/r/VFIO/comments/97unx4/passmark_lousy_2d_graphics_performance_on_windows/ + +Hardware: + +6 core Intel Core i7-3930K (-MT-MCP-) + +Host OS: +Linux Mint 19/Ubuntu 18.04 +Kernel: 4.15.0-32-generic x86_64 +Qemu: QEMU emulator version 2.11.1 +Intel microcode (host): 0x714 +dmesg | grep microcode +[ 0.000000] microcode: microcode updated early to revision 0x714, date = 2018-05-08 +[ 2.810683] microcode: sig=0x206d7, pf=0x4, revision=0x714 +[ 2.813340] microcode: Microcode Update Driver: v2.2. + +Note: I manually updated the Intel microcode on the host from 0x713 to 0x714. However, both microcode versions produce the same result in the Windows guest. + +Guest OS: +Windows 10 Pro 64 bit, release 1803 \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1788701 b/results/classifier/gemma3:12b/graphic/1788701 new file mode 100644 index 00000000..c30f145d --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1788701 @@ -0,0 +1,8 @@ + +"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/gemma3:12b/graphic/1789 b/results/classifier/gemma3:12b/graphic/1789 new file mode 100644 index 00000000..dfa36d67 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1789 @@ -0,0 +1,18 @@ + +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/gemma3:12b/graphic/1793297 b/results/classifier/gemma3:12b/graphic/1793297 new file mode 100644 index 00000000..e321a723 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1793297 @@ -0,0 +1,11 @@ + +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/gemma3:12b/graphic/1795799 b/results/classifier/gemma3:12b/graphic/1795799 new file mode 100644 index 00000000..af4047d0 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1795799 @@ -0,0 +1,31 @@ + +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/gemma3:12b/graphic/1799792 b/results/classifier/gemma3:12b/graphic/1799792 new file mode 100644 index 00000000..246a3137 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1799792 @@ -0,0 +1,13 @@ + +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/gemma3:12b/graphic/1800 b/results/classifier/gemma3:12b/graphic/1800 new file mode 100644 index 00000000..476aa067 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1800 @@ -0,0 +1,33 @@ + +8.1.0-rc1 Regression: donkey in qemu advent calender 03/2020 has graphical artifacts +Description of problem: +The game donkey shows graphical artifacts on playing. On changing the lane the car remains on its previous land as well. +A git bisect identified commit 592134617c98f37b8b39c6dd684e5a1832c071d2 as culprit +Steps to reproduce: +1. Download http://qemu-advent-calendar.org/2020/download/gw-basic.tar.xz +2. Start VM using command + ``` + qemu-system-i386 -m 16M -drive if=ide,format=qcow2,file=gwbasic.qcow2 + ``` +3. Wait for GW-Basic prompt and enter (see README): F3 - donkey - <ENTER> - F2 +4. Play to see graphical artifacts +Additional information: +``` +$ git bisect bad +592134617c98f37b8b39c6dd684e5a1832c071d2 is the first bad commit +commit 592134617c98f37b8b39c6dd684e5a1832c071d2 +Author: Richard Henderson +Date: Sun Oct 30 12:07:32 2022 +1100 + + accel/tcg: Reorg system mode store helpers + + Instead of trying to unify all operations on uint64_t, use + mmu_lookup() to perform the basic tlb hit and resolution. + Create individual functions to handle access by size. + + Reviewed-by: Peter Maydell <peter.maydell@linaro.org> + Signed-off-by: Richard Henderson <richard.henderson@linaro.org> + + accel/tcg/cputlb.c | 394 +++++++++++++++++++++++++---------------------------- + 1 file changed, 186 insertions(+), 208 deletions(-) +``` diff --git a/results/classifier/gemma3:12b/graphic/1800156 b/results/classifier/gemma3:12b/graphic/1800156 new file mode 100644 index 00000000..7fad058c --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1800156 @@ -0,0 +1,6 @@ + +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/gemma3:12b/graphic/1800401 b/results/classifier/gemma3:12b/graphic/1800401 new file mode 100644 index 00000000..5027c33e --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1800401 @@ -0,0 +1,30 @@ + +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/gemma3:12b/graphic/1802684 b/results/classifier/gemma3:12b/graphic/1802684 new file mode 100644 index 00000000..6ca6ed6d --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1802684 @@ -0,0 +1,62 @@ + +QEMU gui crashes on macOS Mojave + +QEMU release 3.0.0 as well as a recent head build + +/usr/local/Cellar/qemu/HEAD-03c1ca1 (147 files, 257.2MB) + Built from source on 2018-11-06 at 13:41:32 with: --with-gtk+3 --with-sdl2 --with-libusb +/usr/local/Cellar/qemu/3.0.0 (137 files, 261.6MB) * + Poured from bottle on 2018-11-10 at 22:58:32 with: --with-gtk+3 --with-libusb --with-sdl2 + +Crashes when attempting to use any gui interface (tried SDL and default Cocoa): + +2018-11-10 22:58:41.799 qemu-system-aarch64[42982:1102466] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'NSWindow drag regions should only be invalidated on the Main Thread!' +*** First throw call stack: +( + 0 CoreFoundation 0x00007fff3ea96ecd __exceptionPreprocess + 256 + 1 libobjc.A.dylib 0x00007fff6ab49720 objc_exception_throw + 48 + 2 CoreFoundation 0x00007fff3eab095d -[NSException raise] + 9 + 3 AppKit 0x00007fff3bfb13fa -[NSWindow(NSWindow_Theme) _postWindowNeedsToResetDragMarginsUnlessPostingDisabled] + 324 + 4 AppKit 0x00007fff3bfb6850 -[NSView setFrameSize:] + 2082 + 5 AppKit 0x00007fff3c02747d -[NSVisualEffectView setFrameSize:] + 171 + 6 AppKit 0x00007fff3c0811b1 -[NSTitlebarView setFrameSize:] + 84 + 7 AppKit 0x00007fff3bfb5859 -[NSView setFrame:] + 478 + 8 AppKit 0x00007fff3c081154 -[NSTitlebarView resizeWithOldSuperviewSize:] + 100 + 9 AppKit 0x00007fff3bfbc95e -[NSView resizeSubviewsWithOldSize:] + 502 + 10 AppKit 0x00007fff3bfb66d9 -[NSView setFrameSize:] + 1707 + 11 AppKit 0x00007fff3c9773c0 -[NSTitlebarContainerView setFrameSize:] + 142 + 12 AppKit 0x00007fff3bfb5859 -[NSView setFrame:] + 478 + 13 AppKit 0x00007fff3bfbcdb5 -[NSView resizeWithOldSuperviewSize:] + 776 + 14 AppKit 0x00007fff3bfbc95e -[NSView resizeSubviewsWithOldSize:] + 502 + 15 AppKit 0x00007fff3bfb66d9 -[NSView setFrameSize:] + 1707 + 16 AppKit 0x00007fff3c024570 -[NSThemeFrame setFrameSize:] + 495 + 17 AppKit 0x00007fff3c011223 -[NSWindow _setFrame:updateBorderViewSize:] + 966 + 18 AppKit 0x00007fff3c010b46 -[NSWindow _oldPlaceWindow:] + 547 + 19 AppKit 0x00007fff3c010151 -[NSWindow _setFrameCommon:display:stashSize:] + 3006 + 20 AppKit 0x00007fff3c00f57d -[NSWindow _setFrame:display:allowImplicitAnimation:stashSize:] + 192 + 21 AppKit 0x00007fff3c019ff8 -[NSWindow setFrame:display:animate:] + 567 + 22 qemu-system-aarch64 0x000000010b7b2abf qemu-system-aarch64 + 3668671 + 23 qemu-system-aarch64 0x000000010b7b6356 qemu-system-aarch64 + 3683158 + 24 qemu-system-aarch64 0x000000010b7ad836 qemu-system-aarch64 + 3647542 + 25 qemu-system-aarch64 0x000000010b4ce769 qemu-system-aarch64 + 636777 + 26 qemu-system-aarch64 0x000000010b487c24 qemu-system-aarch64 + 347172 + 27 qemu-system-aarch64 0x000000010b487a15 qemu-system-aarch64 + 346645 + 28 qemu-system-aarch64 0x000000010b4878f1 qemu-system-aarch64 + 346353 + 29 qemu-system-aarch64 0x000000010b4414aa qemu-system-aarch64 + 58538 + 30 qemu-system-aarch64 0x000000010b4f78c3 qemu-system-aarch64 + 805059 + 31 qemu-system-aarch64 0x000000010b487c24 qemu-system-aarch64 + 347172 + 32 qemu-system-aarch64 0x000000010b487a15 qemu-system-aarch64 + 346645 + 33 qemu-system-aarch64 0x000000010b4878f1 qemu-system-aarch64 + 346353 + 34 qemu-system-aarch64 0x000000010b4b8f57 qemu-system-aarch64 + 548695 + 35 qemu-system-aarch64 0x000000010b49c3af qemu-system-aarch64 + 431023 + 36 ??? 0x00000001117891f3 0x0 + 4588081651 +) +libc++abi.dylib: terminating with uncaught exception of type NSException +fish: 'qemu-system-aarch64 -M raspi3 -…' terminated by signal SIGABRT (Abort) + + +macOS Mojave 10.14.2 Beta (18C38b) +Qemu in the same configuration used to work in High Sierra, started crashing only after upgrade to Mojave. + +Command line: +`qemu-system-aarch64 -M raspi3 -d in_asm -serial stdio -kernel $1.bin` \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1802915 b/results/classifier/gemma3:12b/graphic/1802915 new file mode 100644 index 00000000..1dc9b833 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1802915 @@ -0,0 +1,8 @@ + +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/gemma3:12b/graphic/1803 b/results/classifier/gemma3:12b/graphic/1803 new file mode 100644 index 00000000..3801fcdd --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1803 @@ -0,0 +1,15 @@ + +8.x x86_64 system emulation/tcg regression (general protection fault) +Description of problem: +Running the ISO available at https://repo.chimera-linux.org/live/20230611/chimera-linux-x86_64-LIVE-20230611-gnome.iso with the above qemu command line, the graphical environment fails to come up. The system boots, and login prompt shows up; then graphical environment startup is attempted, with Wayland (you can tell as the login prompt cursor no longer blinks, being "frozen" for possibly up to a few minutes due to emulation cost). Then the graphical startup crashes (you can tell because the cursor starts blinking again) and an X11-based startup is attempted (you can tell by the X11 cross cursor) which however never fully comes up either. +Steps to reproduce: +1. Download the ISO and run with the command line above. +2. See the issue. +Additional information: +It is possible to then switch to tty2 (View->compatmonitor0, `sendkey ctrl-alt-f2`), log in as `root:chimera` or `anon:chimera` as the console prompt instructs, and type in `dmesg` (as `root`) or `doas dmesg` (as `anon`) and see that the `dmesg` contains a number of general protection faults, like this: + + + +The system used to work, but I am not sure which is the last version of QEMU where this worked, I believe 7.x. In 8.0.3 (likewise running in a Chimera environment, but it was also tested on Alpine, and I had somebody on Arch Linux test it with 8.0.2 just to rule out possible issues caused by a musl-based host environment) it crashes. It only appears to affect the `x86_64` guest architecture, as the other-architecture ISOs have graphical environment come up fine after some minutes (e.g. `ppc64le` with `qemu-system-ppc64 -M pseries-2.11,cap-htm=off -m 2048 -boot d -cdrom chimera-linux-ppc64le-LIVE-20230611-gnome.iso` works just fine). It also appears to only affect TCG emulation, as KVM likewise works fine (same command line, just `-enable-kvm` added). + +Apologies for a large testcase, but it seems to need specific graphical-adjacent services to reproduce. It should be consistently reproducible though. diff --git a/results/classifier/gemma3:12b/graphic/1805697 b/results/classifier/gemma3:12b/graphic/1805697 new file mode 100644 index 00000000..ff6aced3 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1805697 @@ -0,0 +1,16 @@ + +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/gemma3:12b/graphic/1808824 b/results/classifier/gemma3:12b/graphic/1808824 new file mode 100644 index 00000000..e76b5519 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1808824 @@ -0,0 +1,8 @@ + +Mouse leaves VM window when Grab on Hover isn't selected Windows 10 and Intel HAX + +On Windows 10.0.17134 I have been having the problem that the mouse will leave the VM window after a short time when grab on hover isn't selected. The VM will then try to grab on Hover and the mouse will grab in weird places and it will become very unwieldy to control the mouse in the VM window. + +This is exasperated by super slow response making it nearly unusable if the Intel® Hardware Accelerated Execution Manager (Intel® HAXM) is not currently installed on my machine. + +I know they are different things but they compounded on each other when you have a mouse that is not staying in the VM window and the VM's visualized cpu is acting VERY slow the system is unusable. \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1810105 b/results/classifier/gemma3:12b/graphic/1810105 new file mode 100644 index 00000000..1f5f8703 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1810105 @@ -0,0 +1,24 @@ + +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/gemma3:12b/graphic/1815371 b/results/classifier/gemma3:12b/graphic/1815371 new file mode 100644 index 00000000..322ff865 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1815371 @@ -0,0 +1,34 @@ + + SPICE session's connection_id's are not unique + +From: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920897 + +===== + +When creating a virtual machine with qemu (e.g. via libvirt) including a SPICE server, the client_id of the SPICE session is not unique. For example, starting multiple virtual machines on the same libvirtd, the client_id is the same for all virtual machine's SPICE sessions. + + +A description of the client_id can be found in + +https://www.spice-space.org/static/docs/spice_protocol.pdf under section 2.11. c) : + + +"UINT32 connection_id - In case of a new session (i.e., channel type is RED_CHANNEL_MAIN) this field is set to zero, and in response the server will allocate session id and will send it via the RedLinkReply message. In case of all other channel types, this field will be equal to the allocated session id" + + +The relevant code for generating client ids in libspice-server1 can be found here: https://gitlab.freedesktop.org/spice/spice/blob/v0.12.8/server/reds.c#L1614 + +This uses rand() to generate the random id, but qemu (at least in the case of qemu-system-x86) fails to initialize the RNG seed (with e.g. srand()). + + +The result is, that every SPICE session started (by e.g. libvirtd) has the same client_id. Usually, this is not a problem, but running something like a SPICE proxy, relying on the client_id to correctly route connections, this creates problems. + + +Adding something like 'srand(time(NULL));' to qemu (in vl.c) solves this issue. Related (as seen in some VNC patches, e.g. 'CVE-2017-15124/04-ui-avoid-pointless-VNC-updates-if-framebuffer-isn-t-.patch/ui/vnc.c' ): srand(time(NULL)+getpid()+getpid()*987654+rand()); + + +Tested on Debian 9.7 with kernel 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64 GNU/Linux. + + + +===== \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1819908 b/results/classifier/gemma3:12b/graphic/1819908 new file mode 100644 index 00000000..cc2b52ef --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1819908 @@ -0,0 +1,14 @@ + +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/gemma3:12b/graphic/1820247 b/results/classifier/gemma3:12b/graphic/1820247 new file mode 100644 index 00000000..944d29b0 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1820247 @@ -0,0 +1,132 @@ + +QEMU random crash caused by libspice-server + +Hi, + +One of our OpenStack instances crashed. It seems there was some problem related to SPICE. Attaching what we had in qemu log. Also sending our versions: + +Linux pre-node1 4.18.0-13-generic #14~18.04.1-Ubuntu SMP Thu Dec 6 14:09:52 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux + +QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.9) +Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers + + +root@pre-node1:~# cat /var/log/libvirt/qemu/instance-00000038.log +2019-03-10 20:39:36.510+0000: starting up libvirt version: 4.0.0, package: 1ubuntu8.6 (Christian Ehrhardt <email address hidden> Fri, 09 Nov 2018 07:42:01 +0100), qemu version: 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.9), hostname: pre-node1 +LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin QEMU_AUDIO_DRV=spice /usr/bin/kvm-spice -name guest=instance-00000038,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-5-instance-00000038/master-key.aes -machine pc-i440fx-bionic,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu Skylake-Server-IBRS,ss=on,hypervisor=on,tsc_adjust=on,clflushopt=on,pku=on,ssbd=on,xsaves=on -m 2048 -realtime mlock=on -smp 2,sockets=1,cores=1,threads=2 -object memory-backend-file,id=ram-node0,prealloc=yes,mem-path=/dev/hugepages/libvirt/qemu/5-instance-00000038,share=yes,size=2147483648,host-nodes=0,policy=bind -numa node,nodeid=0,cpus=0-1,memdev=ram-node0 -uuid 3c3d04f3-4b25-4ea5-8836-0e06eef9dcb7 -smbios 'type=1,manufacturer=OpenStack Foundation,product=OpenStack Nova,version=18.1.1,serial=93fa1a55-ba3a-4a99-80b3-3a7bb4e964af,uuid=3c3d04f3-4b25-4ea5-8836-0e06eef9dcb7,family=Virtual Machine' -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-5-instance-00000038/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -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=0x3 -drive file=/var/lib/nova/instances/3c3d04f3-4b25-4ea5-8836-0e06eef9dcb7/disk,format=qcow2,if=none,id=drive-virtio-disk0,cache=none,discard=ignore,throttling.iops-read=5000,throttling.iops-write=5000 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -add-fd set=0,fd=29 -chardev pty,id=charserial0,logfile=/dev/fdset/0,logappend=on -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -spice port=5900,addr=10.252.0.101,disable-ticketing,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -device vfio-pci,host=25:04.1,id=hostdev0,bus=pci.0,addr=0x5 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -msg timestamp=on +2019-03-10T20:39:36.568276Z qemu-system-x86_64: -chardev pty,id=charserial0,logfile=/dev/fdset/0,logappend=on: char device redirected to /dev/pts/2 (label charserial0) +inputs_channel_detach_tablet: +main_channel_link: add main channel client +main_channel_client_handle_pong: net test: latency 32.760000 ms, bitrate 33384953 bps (31.838372 Mbps) +red_qxl_set_cursor_peer: +inputs_connect: inputs channel client create + +(process:65324): Spice-WARNING **: 16:35:23.769: Failed to create channel client: Client 0x55e7c157e970: duplicate channel type 2 id 0 +red_qxl_set_cursor_peer: + +(process:65324): Spice-WARNING **: 16:35:24.142: Failed to create channel client: Client 0x55e7c157e970: duplicate channel type 4 id 0 + +(process:65324): Spice-CRITICAL **: 16:35:24.142: cursor-channel.c:353:cursor_channel_connect: condition `ccc != NULL' failed +2019-03-13 15:35:31.785+0000: shutting down, reason=crashed + + + + +I am also attaching some gdb information extracted from qemu crash dump file. These are backtraces of particular threads within the crashed QEMU process. + + +Thread 9 (Thread 0x7f69649ea5c0 (LWP 65324)): +#0 0x00007f695f02d2b7 in __libc_write (fd=26, buf=0x7ffc33f5b330, nbytes=56) at ../sysdeps/unix/sysv/linux/write.c:27 +#1 0x00007f695ff30ed3 in () at /usr/lib/x86_64-linux-gnu/libspice-server.so.1 +#2 0x00007f695ff316ce in () at /usr/lib/x86_64-linux-gnu/libspice-server.so.1 +#3 0x00007f695ff52db6 in () at /usr/lib/x86_64-linux-gnu/libspice-server.so.1 +#4 0x00007f695ff58e38 in () at /usr/lib/x86_64-linux-gnu/libspice-server.so.1 +#5 0x00007f695ff5f463 in () at /usr/lib/x86_64-linux-gnu/libspice-server.so.1 +#6 0x00007f695ff5f7bb in () at /usr/lib/x86_64-linux-gnu/libspice-server.so.1 +#7 0x000055e7bec94584 in () +#8 0x000055e7bec94e58 in aio_dispatch () +#9 0x000055e7bec91e3e in () +#10 0x00007f695fa45387 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 +#11 0x000055e7bec940a7 in main_loop_wait () +#12 0x000055e7be8b8486 in main () + +Thread 8 (Thread 0x7f68b78fc700 (LWP 61873)): +#0 0x00007f695f02c8c2 in futex_abstimed_wait_cancelable (private=0, abstime=0x7f68b78fb900, expected=0, futex_word=0x55e7c1531d78) + at ../sysdeps/unix/sysv/linux/futex-internal.h:205 +#1 0x00007f695f02c8c2 in do_futex_wait (sem=sem@entry=0x55e7c1531d78, abstime=abstime@entry=0x7f68b78fb900) at sem_waitcommon.c:111 +#2 0x00007f695f02c9d3 in __new_sem_wait_slow (sem=0x55e7c1531d78, abstime=0x7f68b78fb900) at sem_waitcommon.c:181 +#3 0x000055e7bec976cf in qemu_sem_timedwait () +#4 0x000055e7bec928bc in () +#5 0x00007f695f0236db in start_thread (arg=0x7f68b78fc700) at pthread_create.c:463 +#6 0x00007f695ed4c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 + +Thread 7 (Thread 0x7f688f7fe700 (LWP 61366)): +#0 0x00007f695f02c8c2 in futex_abstimed_wait_cancelable (private=0, abstime=0x7f688f7fd900, expected=0, futex_word=0x55e7c1531d78) + at ../sysdeps/unix/sysv/linux/futex-internal.h:205 +#1 0x00007f695f02c8c2 in do_futex_wait (sem=sem@entry=0x55e7c1531d78, abstime=abstime@entry=0x7f688f7fd900) at sem_waitcommon.c:111 +#2 0x00007f695f02c9d3 in __new_sem_wait_slow (sem=0x55e7c1531d78, abstime=0x7f688f7fd900) at sem_waitcommon.c:181 +#3 0x000055e7bec976cf in qemu_sem_timedwait () +#4 0x000055e7bec928bc in () +#5 0x00007f695f0236db in start_thread (arg=0x7f688f7fe700) at pthread_create.c:463 +#6 0x00007f695ed4c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 + +Thread 6 (Thread 0x7f687effd700 (LWP 61362)): +#0 0x00007f695f02c8c2 in futex_abstimed_wait_cancelable (private=0, abstime=0x7f687effc900, expected=0, futex_word=0x55e7c1531d78) + at ../sysdeps/unix/sysv/linux/futex-internal.h:205 +#1 0x00007f695f02c8c2 in do_futex_wait (sem=sem@entry=0x55e7c1531d78, abstime=abstime@entry=0x7f687effc900) at sem_waitcommon.c:111 +#2 0x00007f695f02c9d3 in __new_sem_wait_slow (sem=0x55e7c1531d78, abstime=0x7f687effc900) at sem_waitcommon.c:181 +#3 0x000055e7bec976cf in qemu_sem_timedwait () +#4 0x000055e7bec928bc in () +#5 0x00007f695f0236db in start_thread (arg=0x7f687effd700) at pthread_create.c:463 +#6 0x00007f695ed4c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 + +Thread 5 (Thread 0x7f68b58f1700 (LWP 60991)): +#0 0x00007f695f02c8c2 in futex_abstimed_wait_cancelable (private=0, abstime=0x7f68b58f0900, expected=0, futex_word=0x55e7c1531d78) + at ../sysdeps/unix/sysv/linux/futex-internal.h:205 +#1 0x00007f695f02c8c2 in do_futex_wait (sem=sem@entry=0x55e7c1531d78, abstime=abstime@entry=0x7f68b58f0900) at sem_waitcommon.c:111 +#2 0x00007f695f02c9d3 in __new_sem_wait_slow (sem=0x55e7c1531d78, abstime=0x7f68b58f0900) at sem_waitcommon.c:181 +#3 0x000055e7bec976cf in qemu_sem_timedwait () +#4 0x000055e7bec928bc in () +#5 0x00007f695f0236db in start_thread (arg=0x7f68b58f1700) at pthread_create.c:463 +#6 0x00007f695ed4c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 + +Thread 4 (Thread 0x7f69564a2700 (LWP 65331)): +#0 0x00007f695ed46839 in syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 +#1 0x000055e7bec9790b in qemu_event_wait () +#2 0x000055e7beca7ebe in () +#3 0x00007f695f0236db in start_thread (arg=0x7f69564a2700) at pthread_create.c:463 +#4 0x00007f695ed4c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 + +Thread 3 (Thread 0x7f695449d700 (LWP 65363)): +#0 0x00007f695ed415d7 in ioctl () at ../sysdeps/unix/syscall-template.S:78 +#1 0x000055e7be910547 in kvm_vcpu_ioctl () +#2 0x000055e7be910684 in kvm_cpu_exec () +#3 0x000055e7be8ed3f4 in () +#4 0x00007f695f0236db in start_thread (arg=0x7f695449d700) at pthread_create.c:463 +#5 0x00007f695ed4c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 + +Thread 2 (Thread 0x7f6952b4f700 (LWP 65366)): +#0 0x00007f695ed415d7 in ioctl () at ../sysdeps/unix/syscall-template.S:78 +#1 0x000055e7be910547 in kvm_vcpu_ioctl () +---Type <return> to continue, or q <return> to quit--- +#2 0x000055e7be910684 in kvm_cpu_exec () +#3 0x000055e7be8ed3f4 in () +#4 0x00007f695f0236db in start_thread (arg=0x7f6952b4f700) at pthread_create.c:463 +#5 0x00007f695ed4c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 + +Thread 1 (Thread 0x7f6951a40700 (LWP 65368)): +#0 0x00007f695ec69e97 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 +#1 0x00007f695ec6b801 in __GI_abort () at abort.c:79 +#2 0x00007f695ff81cc9 in () at /usr/lib/x86_64-linux-gnu/libspice-server.so.1 +#3 0x00007f695ff63929 in () at /usr/lib/x86_64-linux-gnu/libspice-server.so.1 +#4 0x00007f695ff314f1 in () at /usr/lib/x86_64-linux-gnu/libspice-server.so.1 +#5 0x00007f695ff37d7b in () at /usr/lib/x86_64-linux-gnu/libspice-server.so.1 +#6 0x00007f695fa451f5 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 +#7 0x00007f695fa455c0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 +#8 0x00007f695fa458d2 in g_main_loop_run () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 +#9 0x00007f695ff63b3a in () at /usr/lib/x86_64-linux-gnu/libspice-server.so.1 +#10 0x00007f695f0236db in start_thread (arg=0x7f6951a40700) at pthread_create.c:463 +#11 0x00007f695ed4c88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 + +Regards, +Premysl \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1821839 b/results/classifier/gemma3:12b/graphic/1821839 new file mode 100644 index 00000000..6db8de3a --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1821839 @@ -0,0 +1,170 @@ + +qemu 4.0 doesnt support glsl 3.0 but yes older versions, that have no sense IMO + +tested on qemu 4.0.rc1 on rpi3, mesa 19.x +maybe I am a bit confused, but why it can use and older version from my mesa driver, it should pickup the right version instead of going to the latest. + +pi@pi:~/Desktop/armbian/windows_95_vdi $ qemu-system-i386 -cpu qemu32 -m 32 -display sdl,gl=on -device virtio-vga,virgl=on -soundhw sb16 +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 + +the sames happen on mesa 13.x (default mesa included on raspbian) + +GLXINFO + +pi@pi:~/Desktop/armbian/windows_95_vdi $ glxinfo +name of display: :0 +display: :0 screen: 0 +direct rendering: Yes +server glx vendor string: SGI +server glx version string: 1.4 +server glx extensions: + GLX_ARB_create_context, GLX_ARB_create_context_profile, + GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, + GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, + GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, + GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_texture_from_pixmap, + GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, + GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, + GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, + GLX_SGI_make_current_read, GLX_SGI_swap_control +client glx vendor string: Mesa Project and SGI +client glx version string: 1.4 +client glx extensions: + GLX_ARB_context_flush_control, GLX_ARB_create_context, + GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, + GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, + GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, + GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, + GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, + GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, + GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, + GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, + GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, + GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, + GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, + GLX_SGI_swap_control, GLX_SGI_video_sync +GLX version: 1.4 +GLX extensions: + GLX_ARB_create_context, GLX_ARB_create_context_profile, + GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, + GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, + GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, + GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, + GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, + GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, + GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, + GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, + GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, + GLX_SGI_swap_control, GLX_SGI_video_sync +Extended renderer info (GLX_MESA_query_renderer): + Vendor: Broadcom (0x14e4) + Device: VC4 V3D 2.1 (0xffffffff) + Version: 19.1.0 + Accelerated: yes + Video memory: 938MB + Unified memory: yes + Preferred profile: compat (0x2) + Max core profile version: 0.0 + Max compat profile version: 2.1 + Max GLES1 profile version: 1.1 + Max GLES[23] profile version: 2.0 +OpenGL vendor string: Broadcom +OpenGL renderer string: VC4 V3D 2.1 +OpenGL version string: 2.1 Mesa 19.1.0-devel (git-f1122f78b7) +OpenGL shading language version string: 1.20 +OpenGL extensions: + GL_AMD_shader_trinary_minmax, GL_APPLE_packed_pixels, + GL_ARB_ES2_compatibility, GL_ARB_buffer_storage, + GL_ARB_clear_buffer_object, GL_ARB_color_buffer_float, + GL_ARB_compressed_texture_pixel_storage, GL_ARB_copy_buffer, + GL_ARB_debug_output, GL_ARB_depth_texture, GL_ARB_draw_buffers, + GL_ARB_draw_elements_base_vertex, GL_ARB_explicit_attrib_location, + GL_ARB_explicit_uniform_location, GL_ARB_fragment_coord_conventions, + GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, + GL_ARB_fragment_shader, GL_ARB_framebuffer_object, + GL_ARB_framebuffer_sRGB, GL_ARB_get_program_binary, + GL_ARB_get_texture_sub_image, GL_ARB_half_float_pixel, + GL_ARB_half_float_vertex, GL_ARB_internalformat_query, + GL_ARB_internalformat_query2, GL_ARB_invalidate_subdata, + GL_ARB_map_buffer_alignment, GL_ARB_map_buffer_range, GL_ARB_multi_bind, + GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_occlusion_query, + GL_ARB_occlusion_query2, GL_ARB_pixel_buffer_object, + GL_ARB_point_parameters, GL_ARB_point_sprite, + GL_ARB_program_interface_query, GL_ARB_provoking_vertex, + GL_ARB_robustness, GL_ARB_sampler_objects, GL_ARB_separate_shader_objects, + GL_ARB_shader_objects, GL_ARB_shading_language_100, GL_ARB_shadow, + GL_ARB_sync, GL_ARB_texture_barrier, GL_ARB_texture_border_clamp, + GL_ARB_texture_compression, GL_ARB_texture_cube_map, + GL_ARB_texture_env_add, GL_ARB_texture_env_combine, + GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3, + GL_ARB_texture_mirrored_repeat, GL_ARB_texture_multisample, + GL_ARB_texture_non_power_of_two, GL_ARB_texture_rectangle, + GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, + GL_ARB_texture_swizzle, GL_ARB_transpose_matrix, + GL_ARB_vertex_array_object, GL_ARB_vertex_attrib_binding, + GL_ARB_vertex_buffer_object, GL_ARB_vertex_program, GL_ARB_vertex_shader, + GL_ARB_window_pos, GL_ATI_blend_equation_separate, GL_ATI_draw_buffers, + GL_ATI_fragment_shader, GL_ATI_separate_stencil, + GL_ATI_texture_env_combine3, GL_EXT_abgr, GL_EXT_bgra, + GL_EXT_blend_color, GL_EXT_blend_equation_separate, + GL_EXT_blend_func_separate, GL_EXT_blend_minmax, GL_EXT_blend_subtract, + GL_EXT_compiled_vertex_array, GL_EXT_copy_texture, + GL_EXT_draw_range_elements, GL_EXT_fog_coord, GL_EXT_framebuffer_blit, + GL_EXT_framebuffer_multisample, GL_EXT_framebuffer_multisample_blit_scaled, + GL_EXT_framebuffer_object, GL_EXT_framebuffer_sRGB, + GL_EXT_gpu_program_parameters, GL_EXT_multi_draw_arrays, + GL_EXT_packed_depth_stencil, GL_EXT_packed_pixels, + GL_EXT_pixel_buffer_object, GL_EXT_point_parameters, + GL_EXT_provoking_vertex, GL_EXT_rescale_normal, GL_EXT_secondary_color, + GL_EXT_separate_specular_color, GL_EXT_shader_integer_mix, + GL_EXT_shadow_funcs, GL_EXT_stencil_two_side, GL_EXT_stencil_wrap, + GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, + GL_EXT_texture_cube_map, GL_EXT_texture_edge_clamp, + GL_EXT_texture_env_add, GL_EXT_texture_env_combine, + GL_EXT_texture_env_dot3, GL_EXT_texture_lod_bias, GL_EXT_texture_object, + GL_EXT_texture_rectangle, GL_EXT_texture_sRGB, GL_EXT_texture_sRGB_decode, + GL_EXT_texture_swizzle, GL_EXT_vertex_array, GL_IBM_multimode_draw_arrays, + GL_IBM_rasterpos_clip, GL_IBM_texture_mirrored_repeat, + GL_INGR_blend_func_separate, GL_KHR_context_flush_control, GL_KHR_debug, + GL_KHR_no_error, GL_KHR_texture_compression_astc_ldr, + GL_KHR_texture_compression_astc_sliced_3d, GL_MESA_pack_invert, + GL_MESA_tile_raster_order, GL_MESA_window_pos, GL_NV_blend_square, + GL_NV_fog_distance, GL_NV_light_max_exponent, GL_NV_packed_depth_stencil, + GL_NV_texgen_reflection, GL_NV_texture_barrier, + GL_NV_texture_env_combine4, GL_NV_texture_rectangle, GL_OES_EGL_image, + GL_OES_read_format, GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp, + GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, GL_SUN_multi_draw_arrays + +OpenGL ES profile version string: OpenGL ES 2.0 Mesa 19.1.0-devel (git-f1122f78b7) +OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16 +OpenGL ES profile extensions: + GL_APPLE_texture_max_level, GL_EXT_blend_minmax, + GL_EXT_compressed_ETC1_RGB8_sub_texture, GL_EXT_discard_framebuffer, + GL_EXT_draw_buffers, GL_EXT_draw_elements_base_vertex, GL_EXT_frag_depth, + GL_EXT_map_buffer_range, GL_EXT_multi_draw_arrays, + GL_EXT_occlusion_query_boolean, GL_EXT_read_format_bgra, + GL_EXT_separate_shader_objects, GL_EXT_texture_border_clamp, + GL_EXT_texture_format_BGRA8888, GL_EXT_unpack_subimage, + GL_KHR_context_flush_control, GL_KHR_debug, GL_KHR_no_error, + GL_KHR_texture_compression_astc_ldr, + GL_KHR_texture_compression_astc_sliced_3d, GL_MESA_tile_raster_order, + GL_NV_draw_buffers, GL_NV_fbo_color_attachments, GL_NV_read_buffer, + GL_NV_read_depth, GL_NV_read_depth_stencil, GL_NV_read_stencil, + GL_OES_EGL_image, GL_OES_EGL_image_external, GL_OES_EGL_sync, + GL_OES_compressed_ETC1_RGB8_texture, GL_OES_depth24, GL_OES_depth_texture, + GL_OES_draw_elements_base_vertex, GL_OES_element_index_uint, + GL_OES_fbo_render_mipmap, GL_OES_get_program_binary, GL_OES_mapbuffer, + GL_OES_packed_depth_stencil, GL_OES_required_internalformat, + GL_OES_rgb8_rgba8, GL_OES_stencil8, GL_OES_surfaceless_context, + GL_OES_texture_3D, GL_OES_texture_border_clamp, GL_OES_texture_npot, + GL_OES_vertex_array_object, GL_OES_vertex_half_float \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1827005 b/results/classifier/gemma3:12b/graphic/1827005 new file mode 100644 index 00000000..accd3a2a --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1827005 @@ -0,0 +1,14 @@ + +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/gemma3:12b/graphic/1827772 b/results/classifier/gemma3:12b/graphic/1827772 new file mode 100644 index 00000000..bf5723bd --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1827772 @@ -0,0 +1,16 @@ + +[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/gemma3:12b/graphic/1828272 b/results/classifier/gemma3:12b/graphic/1828272 new file mode 100644 index 00000000..935b5a47 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1828272 @@ -0,0 +1,22 @@ + +4.0 breaks keyboard autorepeat in guests with xserver + +Description: +In a linux/bsd guest within X, pressing and holding a key for a short time causes an endless repeat of that key in the guest. The release of the key gets ignored. +Example 1: pressing and holding 'a' for a few seconds results in typing of 'aaaaaaaaaaaa...' endlessly. +Example 2: pressing and holding 'Backspace' for a few seconds results in deleting all your previously typed text. + +It doesn't happen within a VT in the guest. It also doesn't happen with guests that run windows, reactos or haiku for example. + +The problem goes away, when disabling xorgs autorepeat function via "xset -r" in the host. +Normally, this setting should not have any effect on the guest, since it has it's own autorepeat setting. So there is some conflict here. + +Steps to reproduce: +Start any linux/bsd guest system with xserver, open a terminal, press and hold a key for a short time: Look how it gets typed endlessly (Try a few times if it doesn't happen immediately). +The easiest way is to run a linux live cd, like this (Link to example iso :http://download.grml.org/grml64-full_2018.12.iso) +$ qemu-system-x86_64 -enable-kvm -m 512 -boot d -cdrom grml64-full_2018.12.iso + + +Qemu version info: +QEMU emulator version 4.0.0 +Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1829945 b/results/classifier/gemma3:12b/graphic/1829945 new file mode 100644 index 00000000..1c5a20a3 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1829945 @@ -0,0 +1,11 @@ + +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/gemma3:12b/graphic/1829964 b/results/classifier/gemma3:12b/graphic/1829964 new file mode 100644 index 00000000..ea73f60f --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1829964 @@ -0,0 +1,34 @@ + +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/gemma3:12b/graphic/1831486 b/results/classifier/gemma3:12b/graphic/1831486 new file mode 100644 index 00000000..1b7bd04c --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1831486 @@ -0,0 +1,38 @@ + +qmp monitor deadlock (with spice events for ex) + +If an event is emitted during monitor_flush_locked() it will deadlock. + +Thread 1 (Thread 0x7f14f1854000 (LWP 7245)): +#0 0x00007f14fc30592d in __lll_lock_wait () at /lib64/libpthread.so.0 +#1 0x00007f14fc2fedc9 in pthread_mutex_lock () at /lib64/libpthread.so.0 +#2 0x000055de60e19327 in qemu_mutex_lock_impl (mutex=0x55de61859e58, file=0x55de60f1a640 "/home/elmarco/src/qq/monitor.c", line=438) at /home/elmarco/src/qq/util/qemu-thread-posix.c:66 +#3 0x000055de6085c5af in monitor_puts (mon=0x55de61859d30, str=0x55de62a61d30 "{\"timestamp\": {\"seconds\": 1559585795, \"microseconds\": 508720}, \"event\": \"SPICE_DISCONNECTED\", \"data\": {\"server\": {\"port\": \"/tmp/.9IW52Z/spice.sock\", \"family\": \"unix\", \"host\": \"localhost\"}, \"client\": {"...) at /home/elmarco/src/qq/monitor.c:438 +#4 0x000055de6085c85a in qmp_send_response (mon=0x55de61859d30, rsp=0x55de61ed19a0) at /home/elmarco/src/qq/monitor.c:493 +#5 0x000055de6085c8ee in monitor_qapi_event_emit (event=QAPI_EVENT_SPICE_DISCONNECTED, qdict=0x55de61ed19a0) at /home/elmarco/src/qq/monitor.c:521 +#6 0x000055de6085c9ea in monitor_qapi_event_queue_no_reenter (event=QAPI_EVENT_SPICE_DISCONNECTED, qdict=0x55de61ed19a0) at /home/elmarco/src/qq/monitor.c:546 +#7 0x000055de6085cd7a in qapi_event_emit (event=QAPI_EVENT_SPICE_DISCONNECTED, qdict=0x55de61ed19a0) at /home/elmarco/src/qq/monitor.c:621 +#8 0x000055de60e04bc3 in qapi_event_send_spice_disconnected (server=0x55de61ee7b30, client=0x55de620c9090) at qapi/qapi-events-ui.c:101 +#9 0x000055de60c84381 in channel_event (event=3, info=0x55de6222f4c0) at /home/elmarco/src/qq/ui/spice-core.c:234 +#10 0x00007f14fc70ba3b in reds_handle_channel_event (reds=<optimized out>, event=3, info=0x55de6222f4c0) at reds.c:318 +#11 0x00007f14fc6f407b in main_dispatcher_self_handle_channel_event (info=0x55de6222f4c0, event=3, self=0x55de61a5b0b0) at main-dispatcher.c:191 +#12 0x00007f14fc6f407b in main_dispatcher_channel_event (self=0x55de61a5b0b0, event=event@entry=3, info=0x55de6222f4c0) at main-dispatcher.c:191 +#13 0x00007f14fc713cf3 in red_stream_push_channel_event (s=s@entry=0x55de6222f400, event=event@entry=3) at red-stream.c:416 +#14 0x00007f14fc713d2b in red_stream_free (s=0x55de6222f400) at red-stream.c:390 +#15 0x00007f14fc6fa67c in red_channel_client_finalize (object=0x55de62511360) at red-channel-client.c:347 +#16 0x00007f14fe4cfcf0 in g_object_unref () at /lib64/libgobject-2.0.so.0 +#17 0x00007f14fc6fca12 in red_channel_client_push (rcc=0x55de62511360) at red-channel-client.c:1340 +#18 0x00007f14fc6fca12 in red_channel_client_push (rcc=0x55de62511360) at red-channel-client.c:1303 +#19 0x00007f14fc6cd479 in red_char_device_send_msg_to_client (client=<optimized out>, msg=0x55de62512c00, dev=0x55de61a5b3b0) at char-device.c:307 +#20 0x00007f14fc6cd479 in red_char_device_send_msg_to_clients (msg=0x55de62512c00, dev=0x55de61a5b3b0) at char-device.c:307 +#21 0x00007f14fc6cd479 in red_char_device_read_from_device (dev=0x55de61a5b3b0) at char-device.c:355 +#22 0x000055de60a27dba in spice_chr_write (chr=0x55de61924c00, buf=0x55de6236c070 "{\"return\": {}, \"id\": 2}\r\n", len=25) at /home/elmarco/src/qq/chardev/spice.c:201 +#23 0x000055de60d89e29 in qemu_chr_write_buffer (s=0x55de61924c00, buf=0x55de6236c070 "{\"return\": {}, \"id\": 2}\r\n", len=25, offset=0x7ffcd5e1a860, write_all=false) at /home/elmarco/src/qq/chardev/char.c:113 +#24 0x000055de60d89f96 in qemu_chr_write (s=0x55de61924c00, buf=0x55de6236c070 "{\"return\": {}, \"id\": 2}\r\n", len=25, write_all=false) at /home/elmarco/src/qq/chardev/char.c:148 +#25 0x000055de60d8cf78 in qemu_chr_fe_write (be=0x55de61859d30, buf=0x55de6236c070 "{\"return\": {}, \"id\": 2}\r\n", len=25) at /home/elmarco/src/qq/chardev/char-fe.c:42 +#26 0x000055de6085c40f in monitor_flush_locked (mon=0x55de61859d30) at /home/elmarco/src/qq/monitor.c:404 +#27 0x000055de6085c614 in monitor_puts (mon=0x55de61859d30, str=0x55de622f6a40 "{\"return\": {}, \"id\": 2}\n") at /home/elmarco/src/qq/monitor.c:446 +#28 0x000055de6085c85a in qmp_send_response (mon=0x55de61859d30, rsp=0x55de61ecf960) at /home/elmarco/src/qq/monitor.c:493 +#29 0x000055de60865902 in monitor_qmp_respond (mon=0x55de61859d30, rsp=0x55de61ecf960) at /home/elmarco/src/qq/monitor.c:4128 +#30 0x000055de60865a19 in monitor_qmp_dispatch (mon=0x55de61859d30, req=0x55de622ec000) at /home/elmarco/src/qq/monitor.c:4157 +#31 0x000055de60865ce2 in monitor_qmp_bh_dispatcher (data=0x0) at /home/elmarco/src/qq/monitor.c:4224 \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1835729 b/results/classifier/gemma3:12b/graphic/1835729 new file mode 100644 index 00000000..1d4c0499 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1835729 @@ -0,0 +1,10 @@ + +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/gemma3:12b/graphic/1835732 b/results/classifier/gemma3:12b/graphic/1835732 new file mode 100644 index 00000000..03bbba16 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1835732 @@ -0,0 +1,12 @@ + +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/gemma3:12b/graphic/1836762 b/results/classifier/gemma3:12b/graphic/1836762 new file mode 100644 index 00000000..350b70bf --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1836762 @@ -0,0 +1,140 @@ + +Many leaks from qemu_spice_create_update + +tag: v4.1.0-rc0 + +Compiled with --enable-sanitizers + +$ qemu-system-x86_64 -device qxl-vga ... +[guest exits calling 'hlt'] +==20452==ERROR: LeakSanitizer: detected memory leaks + +Direct leak of 167616 byte(s) in 582 object(s) allocated from: + #0 0x561146f2c8ef in calloc (x86_64-softmmu/qemu-system-x86_64+0x18248ef) + #1 0x7f73af3dde1d in g_malloc0 (/lib64/libglib-2.0.so.0+0x54e1d) + #2 0x561148c6d547 in qemu_spice_create_update qemu/ui/spice-display.c:222:21 + #3 0x561148c6ba2b in qemu_spice_display_refresh qemu/ui/spice-display.c:488:9 + #4 0x561148172eff in display_refresh qemu/hw/display/qxl.c:2030:9 + #5 0x561148c2748f in dpy_refresh qemu/ui/console.c:1629:13 + #6 0x561148c263f1 in gui_update qemu/ui/console.c:206:5 + #7 0x561149558e6b in timerlist_run_timers qemu/util/qemu-timer.c:574:9 + #8 0x5611495591de in qemu_clock_run_timers qemu/util/qemu-timer.c:588:12 + #9 0x56114955a489 in qemu_clock_run_all_timers qemu/util/qemu-timer.c:708:25 + #10 0x56114955b235 in main_loop_wait qemu/util/main-loop.c:519:5 + #11 0x561147c587b3 in main_loop qemu/vl.c:1791:9 + #12 0x561147c4976d in main qemu/vl.c:4473:5 + #13 0x7f73ac5c4412 in __libc_start_main (/lib64/libc.so.6+0x24412) + +Direct leak of 5184 byte(s) in 18 object(s) allocated from: + #0 0x561146f2c8ef in calloc (x86_64-softmmu/qemu-system-x86_64+0x18248ef) + #1 0x7f73af3dde1d in g_malloc0 (/lib64/libglib-2.0.so.0+0x54e1d) + #2 0x561148c6e3e7 in qemu_spice_create_update qemu/ui/spice-display.c:243:13 + #3 0x561148c6ba2b in qemu_spice_display_refresh qemu/ui/spice-display.c:488:9 + #4 0x561148172eff in display_refresh qemu/hw/display/qxl.c:2030:9 + #5 0x561148c2748f in dpy_refresh qemu/ui/console.c:1629:13 + #6 0x561148c263f1 in gui_update qemu/ui/console.c:206:5 + #7 0x561149558e6b in timerlist_run_timers qemu/util/qemu-timer.c:574:9 + #8 0x5611495591de in qemu_clock_run_timers qemu/util/qemu-timer.c:588:12 + #9 0x56114955a489 in qemu_clock_run_all_timers qemu/util/qemu-timer.c:708:25 + #10 0x56114955b235 in main_loop_wait qemu/util/main-loop.c:519:5 + #11 0x561147c587b3 in main_loop qemu/vl.c:1791:9 + #12 0x561147c4976d in main qemu/vl.c:4473:5 + #13 0x7f73ac5c4412 in __libc_start_main (/lib64/libc.so.6+0x24412) + +Direct leak of 2560 byte(s) in 4 object(s) allocated from: + #0 0x561146f2cb46 in realloc (x86_64-softmmu/qemu-system-x86_64+0x1824b46) + #1 0x7f73ac04c420 (/lib64/libfontconfig.so.1+0x21420) + +Direct leak of 22 byte(s) in 1 object(s) allocated from: + #0 0x561146f2c6af in __interceptor_malloc (x86_64-softmmu/qemu-system-x86_64+0x18246af) + #1 0x7f73ae781953 in XGetAtomName (/lib64/libX11.so.6+0x2a953) + +Indirect leak of 54936 byte(s) in 510 object(s) allocated from: + #0 0x561146f2c6af in __interceptor_malloc (x86_64-softmmu/qemu-system-x86_64+0x18246af) + #1 0x7f73af3dddc5 in g_malloc (/lib64/libglib-2.0.so.0+0x54dc5) + #2 0x561148c6d547 in qemu_spice_create_update qemu/ui/spice-display.c:222:21 + #3 0x561148c6ba2b in qemu_spice_display_refresh qemu/ui/spice-display.c:488:9 + #4 0x561148172eff in display_refresh qemu/hw/display/qxl.c:2030:9 + #5 0x561148c2748f in dpy_refresh qemu/ui/console.c:1629:13 + #6 0x561148c263f1 in gui_update qemu/ui/console.c:206:5 + #7 0x561149558e6b in timerlist_run_timers qemu/util/qemu-timer.c:574:9 + #8 0x5611495591de in qemu_clock_run_timers qemu/util/qemu-timer.c:588:12 + #9 0x56114955a489 in qemu_clock_run_all_timers qemu/util/qemu-timer.c:708:25 + #10 0x56114955b235 in main_loop_wait qemu/util/main-loop.c:519:5 + #11 0x561147c587b3 in main_loop qemu/vl.c:1791:9 + #12 0x561147c4976d in main qemu/vl.c:4473:5 + #13 0x7f73ac5c4412 in __libc_start_main (/lib64/libc.so.6+0x24412) + +Indirect leak of 30720 byte(s) in 23 object(s) allocated from: + #0 0x561146f2c6af in __interceptor_malloc (x86_64-softmmu/qemu-system-x86_64+0x18246af) + #1 0x7f73af3dddc5 in g_malloc (/lib64/libglib-2.0.so.0+0x54dc5) + #2 0x561148c6e3e7 in qemu_spice_create_update qemu/ui/spice-display.c:243:13 + #3 0x561148c6ba2b in qemu_spice_display_refresh qemu/ui/spice-display.c:488:9 + #4 0x561148172eff in display_refresh qemu/hw/display/qxl.c:2030:9 + #5 0x561148c2748f in dpy_refresh qemu/ui/console.c:1629:13 + #6 0x561148c263f1 in gui_update qemu/ui/console.c:206:5 + #7 0x561149558e6b in timerlist_run_timers qemu/util/qemu-timer.c:574:9 + #8 0x5611495591de in qemu_clock_run_timers qemu/util/qemu-timer.c:588:12 + #9 0x56114955a489 in qemu_clock_run_all_timers qemu/util/qemu-timer.c:708:25 + #10 0x56114955b235 in main_loop_wait qemu/util/main-loop.c:519:5 + #11 0x561147c587b3 in main_loop qemu/vl.c:1791:9 + #12 0x561147c4976d in main qemu/vl.c:4473:5 + #13 0x7f73ac5c4412 in __libc_start_main (/lib64/libc.so.6+0x24412) + +Indirect leak of 8288 byte(s) in 259 object(s) allocated from: + #0 0x561146f2c6af in __interceptor_malloc (x86_64-softmmu/qemu-system-x86_64+0x18246af) + #1 0x7f73ac0385af (/lib64/libfontconfig.so.1+0xd5af) + +Indirect leak of 4068 byte(s) in 303 object(s) allocated from: + #0 0x561146e78f40 in __interceptor_strdup (x86_64-softmmu/qemu-system-x86_64+0x1770f40) + #1 0x7f73ac04bc44 in FcValueSave (/lib64/libfontconfig.so.1+0x20c44) + +Indirect leak of 2336 byte(s) in 73 object(s) allocated from: + #0 0x561146f2c8ef in calloc (x86_64-softmmu/qemu-system-x86_64+0x18248ef) + #1 0x7f73ac04c9cc (/lib64/libfontconfig.so.1+0x219cc) + +Indirect leak of 1536 byte(s) in 48 object(s) allocated from: + #0 0x561146f2c8ef in calloc (x86_64-softmmu/qemu-system-x86_64+0x18248ef) + #1 0x7f73ac04bf0c (/lib64/libfontconfig.so.1+0x20f0c) + +Indirect leak of 1440 byte(s) in 5 object(s) allocated from: + #0 0x561146f2c8ef in calloc (x86_64-softmmu/qemu-system-x86_64+0x18248ef) + #1 0x7f73af3dde1d in g_malloc0 (/lib64/libglib-2.0.so.0+0x54e1d) + #2 0x561148c6e3e7 in qemu_spice_create_update qemu/ui/spice-display.c:243:13 + #3 0x561148c6ba2b in qemu_spice_display_refresh qemu/ui/spice-display.c:488:9 + #4 0x561148172eff in display_refresh qemu/hw/display/qxl.c:2030:9 + #5 0x561148c2748f in dpy_refresh qemu/ui/console.c:1629:13 + #6 0x561148c263f1 in gui_update qemu/ui/console.c:206:5 + #7 0x561149558e6b in timerlist_run_timers qemu/util/qemu-timer.c:574:9 + #8 0x5611495591de in qemu_clock_run_timers qemu/util/qemu-timer.c:588:12 + #9 0x56114955a489 in qemu_clock_run_all_timers qemu/util/qemu-timer.c:708:25 + #10 0x56114955b235 in main_loop_wait qemu/util/main-loop.c:519:5 + #11 0x561147c587b3 in main_loop qemu/vl.c:1791:9 + #12 0x561147c4976d in main qemu/vl.c:4473:5 + #13 0x7f73ac5c4412 in __libc_start_main (/lib64/libc.so.6+0x24412) + +Indirect leak of 1440 byte(s) in 5 object(s) allocated from: + #0 0x561146f2c8ef in calloc (x86_64-softmmu/qemu-system-x86_64+0x18248ef) + #1 0x7f73af3dde1d in g_malloc0 (/lib64/libglib-2.0.so.0+0x54e1d) + #2 0x561148c6d547 in qemu_spice_create_update qemu/ui/spice-display.c:222:21 + #3 0x561148c6ba2b in qemu_spice_display_refresh qemu/ui/spice-display.c:488:9 + #4 0x561148172eff in display_refresh qemu/hw/display/qxl.c:2030:9 + #5 0x561148c2748f in dpy_refresh qemu/ui/console.c:1629:13 + #6 0x561148c263f1 in gui_update qemu/ui/console.c:206:5 + #7 0x561149558e6b in timerlist_run_timers qemu/util/qemu-timer.c:574:9 + #8 0x5611495591de in qemu_clock_run_timers qemu/util/qemu-timer.c:588:12 + #9 0x56114955a489 in qemu_clock_run_all_timers qemu/util/qemu-timer.c:708:25 + #10 0x56114955b235 in main_loop_wait qemu/util/main-loop.c:519:5 + #11 0x561147c587b3 in main_loop qemu/vl.c:1791:9 + #12 0x561147c4976d in main qemu/vl.c:4473:5 + #13 0x7f73ac5c4412 in __libc_start_main (/lib64/libc.so.6+0x24412) + +Indirect leak of 384 byte(s) in 12 object(s) allocated from: + #0 0x561146f2c8ef in calloc (x86_64-softmmu/qemu-system-x86_64+0x18248ef) + #1 0x7f73ac04bd9e (/lib64/libfontconfig.so.1+0x20d9e) + +Indirect leak of 96 byte(s) in 2 object(s) allocated from: + #0 0x561146f2c6af in __interceptor_malloc (x86_64-softmmu/qemu-system-x86_64+0x18246af) + #1 0x7f73ac045e51 in FcLangSetCreate (/lib64/libfontconfig.so.1+0x1ae51) + +SUMMARY: AddressSanitizer: 280628 byte(s) leaked in 1847 allocation(s). \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1837049 b/results/classifier/gemma3:12b/graphic/1837049 new file mode 100644 index 00000000..99b50bb6 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1837049 @@ -0,0 +1,124 @@ + +qemu-system-ppc segfaults with -display sdl + +Hello. + +I was trying to debug this segfault: +https://lists.nongnu.org/archive/html/qemu-ppc/2019-07/msg00186.html + +I recompiled latest qemu from git (commit 0b18cfb8f1828c905139b54c8644b0d8f4aad879 ), using this configure line: +./configure --target-list=i386-softmmu,x86_64-softmmu,ppc-softmmu --audio-drv-list=alsa --disable-werror --extra-cflags="-Og" --enable-debug-tcg + +after this I tried original line under gdb, it was still segfaulting: + +--------------copy----------------- +gdb ./ppc-softmmu/qemu-system-ppc +GNU gdb (GDB) 7.11.1 +Copyright (C) 2016 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 "i586-slackware-linux". +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 ./ppc-softmmu/qemu-system-ppc...done. +warning: File "/dev/shm/qemu/.gdbinit" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load". +To enable execution of this file add + add-auto-load-safe-path /dev/shm/qemu/.gdbinit +line to your configuration file "/home/guest/.gdbinit". +To completely disable this security protection add + set auto-load safe-path / +line to your configuration file "/home/guest/.gdbinit". +For more information about this security protection see the +"Auto-loading safe path" section in the GDB manual. E.g., run from the shell: + info "(gdb)Auto-loading safe path" +(gdb) run -M mac99,via=pmu -L ../queue-vga/pc-bios -cdrom /mnt/sdb1/PPC-img/lubuntu-16.04-desktop-powerpc.iso -m 512 -display sdl,gl=on -vga std -d guest_errors,unimp -boot d -cpu G4 -g 1024x768x24 -device ES1370 +Starting program: /dev/shm/qemu/ppc-softmmu/qemu-system-ppc -M mac99,via=pmu -L ../queue-vga/pc-bios -cdrom /mnt/sdb1/PPC-img/lubuntu-16.04-desktop-powerpc.iso -m 512 -display sdl,gl=on -vga std -d guest_errors,unimp -boot d -cpu G4 -g 1024x768x24 -device ES1370 +[Thread debugging using libthread_db enabled] +Using host libthread_db library "/lib/libthread_db.so.1". +[New Thread 0xf560cb40 (LWP 8100)] +[New Thread 0xf4c1ab40 (LWP 8101)] +[New Thread 0xec1b7b40 (LWP 8102)] +[New Thread 0xc5821b40 (LWP 8104)] +[Thread 0xf4c1ab40 (LWP 8101) exited] +[New Thread 0xf4c1ab40 (LWP 8119)] + +Thread 4 "qemu-system-ppc" received signal SIGSEGV, Segmentation fault. +[Switching to Thread 0xec1b7b40 (LWP 8102)] +0xf26c2e44 in code_gen_buffer () +(gdb) bt full +#0 0xffffffff in code_gen_buffer () +#1 0x56710cf6 in cpu_exec (itb=<optimized out>, cpu=<optimized out>) at /dev/shm/qemu/accel/tcg/cpu-exec.c:173 + env = <optimized out> + ret = <optimized out> + last_tb = <optimized out> + tb_exit = <optimized out> + tb_ptr = 0xf26c2cc0 <code_gen_buffer+103976094> "‹]ш…Ы\017ЊБ\020" + ret = 0 + insns_left = <optimized out> + cflags = <optimized out> + tb = 0x5722fe58 + last_tb = <optimized out> + tb_exit = <optimized out> + cc = <optimized out> + __func__ = "cpu_exec" + ret = <optimized out> + sc = <optimized out> +#2 0x56710cf6 in cpu_exec (tb_exit=<synthetic pointer>, last_tb=<synthetic pointer>, tb=<optimized out>, cpu=<optimized out>) at /dev/shm/qemu/accel/tcg/cpu-exec.c:621 + ret = 0 + insns_left = <optimized out> + cflags = <optimized out> + tb = 0x5722fe58 + last_tb = <optimized out> + tb_exit = <optimized out> + cc = <optimized out> + __func__ = "cpu_exec" + ret = <optimized out> + sc = <optimized out> +#3 0x56710cf6 in cpu_exec (cpu=0x573db8f8) at /dev/shm/qemu/accel/tcg/cpu-exec.c:732 + cflags = <optimized out> + tb = 0x5722fe58 + last_tb = <optimized out> + tb_exit = <optimized out> + cc = <optimized out> + __func__ = "cpu_exec" + ret = <optimized out> + sc = <optimized out> +#4 0x566cfade in tcg_cpu_exec (cpu=0x573db8f8) at /dev/shm/qemu/cpus.c:1435 + ret = <optimized out> +#5 0x566d1e6d in qemu_tcg_rr_cpu_thread_fn (arg=0x573db8f8) at /dev/shm/qemu/cpus.c:1537 + r = <optimized out> + cpu = 0x573db8f8 + __PRETTY_FUNCTION__ = "qemu_tcg_rr_cpu_thread_fn" +#6 0x56b56fe0 in qemu_thread_start (args=0x57400668) at util/qemu-thread-posix.c:502 + __cancel_buf = {__cancel_jmp_buf = {{__cancel_jmp_buf = {1461911128, 1463813736, 1461911128, -333745816, 247778263, 1392237730}, __mask_was_saved = 0}}, __pad = {0xec1b70d0, 0x0, 0x0, 0x0}} + __cancel_routine = 0x56b57040 <qemu_thread_atexit_notify> + __not_first_call = <optimized out> + qemu_thread_args = 0x57400668 + start_routine = 0x566d1a30 <qemu_tcg_rr_cpu_thread_fn> + arg = 0x573db8f8 + r = <optimized out> +#7 0xffffffff in start_thread () at /lib/libpthread.so.0 +#8 0xffffffff in clone () at /lib/libc.so.6 +(gdb) quit +A debugging session is active. + + Inferior 1 [process 8096] will be killed. + +Quit anyway? (y or n) y +--------------copy end---------- + +But when I take away -display sdl, or replace it with -display gtk - same line was booting to desktop! + +Changing cpu to G3 also allowed boot: + +./ppc-softmmu/qemu-system-ppc -M mac99,via=pmu -L ../queue-vga/pc-bios -cdrom /mnt/sdb1/PPC-img/lubuntu-16.04-desktop-powerpc.iso -m 512 -display sdl -vga std -d guest_errors,unimp -boot d -cpu G3 -g 1024x768x24 -device ES1370 + +This is 32-bit qemu complied with Slackware's gcc 5.5.0. +64-bit qemu works fine. \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1837218 b/results/classifier/gemma3:12b/graphic/1837218 new file mode 100644 index 00000000..63348878 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1837218 @@ -0,0 +1,21 @@ + +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/gemma3:12b/graphic/1843151 b/results/classifier/gemma3:12b/graphic/1843151 new file mode 100644 index 00000000..42630364 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1843151 @@ -0,0 +1,14 @@ + +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/gemma3:12b/graphic/1844053 b/results/classifier/gemma3:12b/graphic/1844053 new file mode 100644 index 00000000..276e9e19 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1844053 @@ -0,0 +1,62 @@ + +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/gemma3:12b/graphic/1847906 b/results/classifier/gemma3:12b/graphic/1847906 new file mode 100644 index 00000000..ddbd4ee1 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1847906 @@ -0,0 +1,9 @@ + +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/gemma3:12b/graphic/1854204 b/results/classifier/gemma3:12b/graphic/1854204 new file mode 100644 index 00000000..65a91beb --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1854204 @@ -0,0 +1,7 @@ + +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/gemma3:12b/graphic/1857449 b/results/classifier/gemma3:12b/graphic/1857449 new file mode 100644 index 00000000..59b39f97 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1857449 @@ -0,0 +1,29 @@ + +QEMU x86_64 -nographic full system breaks host Bash terminal line wrapping state after simulation ends, requires reset or "tput smam" to fix it + +QEMU 4.2.0 compiled from source, Ubuntu 19.10, open a fresh new gnome terminal. + +If you print 1000 = chars on the host terminal, then they do wrap around the end of the terminal: + +printf "=%.0s" {0..1000} + +However, if you first run QEMU: + +x86_64-softmmu/qemu-system-x86_64 -nographic + +and then quit it in any way, e.g. with Ctrl + A, and then re-run on the host terminal: + +printf "=%.0s" {0..1000} + +then the signs don't wrap around anymore, they just go "off the terminal to the right". + +This can be fixed with either: + +reset +tpam smam + +but unfortunately those don't work in tmux for some reason: https://github.com/tmux/tmux/issues/969 + +I consider this buggy behavior, QEMU should restore the original terminal state if possible. + +Related: https://github.com/cirosantilli/linux-kernel-module-cheat/issues/110 \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1859254 b/results/classifier/gemma3:12b/graphic/1859254 new file mode 100644 index 00000000..4d36bf61 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1859254 @@ -0,0 +1,32 @@ + +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/gemma3:12b/graphic/1859723 b/results/classifier/gemma3:12b/graphic/1859723 new file mode 100644 index 00000000..a79707cb --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1859723 @@ -0,0 +1,8 @@ + +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/gemma3:12b/graphic/1860 b/results/classifier/gemma3:12b/graphic/1860 new file mode 100644 index 00000000..c481d4dd --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1860 @@ -0,0 +1,11 @@ + +virtio-gpu: Only black screen observed after resuming when guest vm do S3 +Description of problem: +On Xen hypervisor, host(dom0) is PVH, guest(domU) is hvm, config virtio-gpu for guest. + +## +Steps to reproduce: +1. In guest vm run "sudo su root" & "echo mem \> /sys/power/state" +2. In host run "sudo xl trigger \<guest id\> s3resume" +Additional information: +## diff --git a/results/classifier/gemma3:12b/graphic/1862 b/results/classifier/gemma3:12b/graphic/1862 new file mode 100644 index 00000000..182014d0 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1862 @@ -0,0 +1,19 @@ + +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: + + + diff --git a/results/classifier/gemma3:12b/graphic/1864814 b/results/classifier/gemma3:12b/graphic/1864814 new file mode 100644 index 00000000..98f7b152 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1864814 @@ -0,0 +1,15 @@ + +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/gemma3:12b/graphic/1865248 b/results/classifier/gemma3:12b/graphic/1865248 new file mode 100644 index 00000000..d293be5b --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1865248 @@ -0,0 +1,12 @@ + +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/gemma3:12b/graphic/1871267 b/results/classifier/gemma3:12b/graphic/1871267 new file mode 100644 index 00000000..fa514b16 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1871267 @@ -0,0 +1,10 @@ + +Multiple (Repeating) Keystrokes in macOS + +Hi, + +I am finding this issue with v4.2.0, or the latest master - on a Windows host, with macOS guest. It happens using gtk (SPICE?) or VNC. When I get to a place to enter a keystroke, I quite reliably get multiple of the same key (i.e. press A, get AAAA). + +Thinking there may be a basic setting to address this? I did try it in Linux (kvm), no issue there. + +Thanks! \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1873339 b/results/classifier/gemma3:12b/graphic/1873339 new file mode 100644 index 00000000..99f68282 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1873339 @@ -0,0 +1,8 @@ + +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/gemma3:12b/graphic/1873341 b/results/classifier/gemma3:12b/graphic/1873341 new file mode 100644 index 00000000..668ad037 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1873341 @@ -0,0 +1,12 @@ + +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/gemma3:12b/graphic/1876 b/results/classifier/gemma3:12b/graphic/1876 new file mode 100644 index 00000000..1d9223e9 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1876 @@ -0,0 +1,2 @@ + +Host wayland gtk problem diff --git a/results/classifier/gemma3:12b/graphic/1877794 b/results/classifier/gemma3:12b/graphic/1877794 new file mode 100644 index 00000000..6206662f --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1877794 @@ -0,0 +1,4 @@ + +Constant Folding on 64-bit Subtraction causes SIGILL on linux-user glxgears ppc64le to x86_64 by way of generating bad shift instruction with c=-1 + +Hello, I've been recently working on my own little branch of QEMU implementing the drm IOCTLs, when I discovered that glxgears seems to crash in GLXSwapBuffers(); with a SIGILL. I investigated this for about 2 weeks, manually trying to trace the call stack, only to find that we seemingly crash in a bad shift instruction. Originally intended to be an shr_i64 generated to an RLDICL, we end up with an all ones(-1) c value, which gets thrown to the macro for generating the MB, and replaces the instruction with mostly ones. This new instruction, FFFFFFE0 is invalid on ppc64le, and crashes in a host SIGILL in codegen_buffer. I tried to see if the output of translate.c had this bad instruction, but all I got were two (shr eax, cl) instructions, and upon creating a test program with shr (eax, cl) in it, nothing happened. Then figuring that there was nothing actually wrong with the instruction in the first place, I turned my eye to the optimizer, and completely disabled constant folding for arithmetic instructions. This seemed to actually resolve the issue, and then I slowly enabled constant folding again on various instructions only to find that enabling not on the shifts, but on subtraction seemed to cause the bug to reappear. I am bewildered and frankly at this point I'm not sure I have a chance in hell of figuring out what causes it, so I'm throwing it here. \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1880326 b/results/classifier/gemma3:12b/graphic/1880326 new file mode 100644 index 00000000..3631879b --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1880326 @@ -0,0 +1,326 @@ + +memory writes make artist_rop8() crash + +As of commit d19f1ab0, LLVM libFuzzer found: + +================================================================= +==6814==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x7fd89f97bd5a at pc 0x55dc44594db5 bp 0x7ffd6f461b40 sp 0x7ffd6f461b38 +READ of size 1 at 0x7fd89f97bd5a thread T0 + #0 0x55dc44594db4 in artist_rop8 + #1 0x55dc44595fd9 in draw_line + #2 0x55dc445937e4 in draw_line_size + #3 0x55dc4458ee9d in artist_reg_write + #4 0x55dc43f77ba7 in memory_region_write_accessor + #5 0x55dc43f775b8 in access_with_adjusted_size + #6 0x55dc43f762b3 in memory_region_dispatch_write + #7 0x55dc43dbb322 in flatview_write_continue + #8 0x55dc43dab2e2 in flatview_write + #9 0x55dc43daae14 in address_space_write + +0x7fd89f97bd5a is located 1122 bytes to the right of 16777464-byte region [0x7fd89e97b800,0x7fd89f97b8f8) +allocated by thread T0 here: + #0 0x55dc43d87abf in operator new(unsigned long) + #1 0x55dc43c4274d in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char const*, unsigned long)) + #2 0x55dc43c3a526 in main (qemu-fuzz-hppa+0x982526) + #3 0x7fd8d05edf42 in __libc_start_main (/lib64/libc.so.6+0x23f42) + +SUMMARY: AddressSanitizer: heap-buffer-overflow (qemu-fuzz-hppa+0x12dcdb4) in artist_rop8 +Shadow bytes around the buggy address: + 0x0ffb93f27750: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0ffb93f27760: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0ffb93f27770: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0ffb93f27780: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0ffb93f27790: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa +=>0x0ffb93f277a0: fa fa fa fa fa fa fa fa fa fa fa[fa]fa fa fa fa + 0x0ffb93f277b0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0ffb93f277c0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0ffb93f277d0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0ffb93f277e0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0ffb93f277f0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa +Shadow byte legend (one shadow byte represents 8 application bytes): + Addressable: 00 + Partially addressable: 01 02 03 04 05 06 07 + Heap left redzone: fa + Freed heap region: fd + Stack left redzone: f1 + Stack mid redzone: f2 + Stack right redzone: f3 + Stack after return: f5 + Stack use after scope: f8 + Global redzone: f9 + Global init order: f6 + Poisoned by user: f7 + Container overflow: fc + Array cookie: ac + Intra object redzone: bb + ASan internal: fe + Left alloca redzone: ca + Right alloca redzone: cb + Shadow gap: cc +==6814==ABORTING + +How to reproduce: + +qemu-system-hppa -S -qtest stdio -accel qtest -display none < EOF +writeb 0xf8100081 0x40 +writeb 0xf81000c5 0x40 +writeb 0xf8100e44 0x2b +writeb 0xf8100e44 0x56 +writeb 0xf8100e44 0x10 +writeb 0xf8100600 0x0 +writeb 0xf8100821 0x21 +writeb 0xf8100b01 0x14 +writew 0xf8100044 0x1245 +writeb 0xf8100a0e 0x50 +writeb 0xf8100a02 0x49 +writeb 0xf8100821 0x0 +writew 0xf8100014 0x0 +writeb 0xf8100e46 0x46 +writeb 0xf8100052 0xe +writeb 0xf8100621 0x14 +writeb 0xf8100b01 0x14 +writew 0xf8100044 0x1241 +writeb 0xf8100b02 0x25 +writeb 0xf8100b01 0x4 +writeb 0xf8100e46 0xb0 +writeb 0xf8100b02 0x0 +writel 0xf81000c4 0x49494949 +writeb 0xf8100b02 0x10 +writew 0xf8100010 0x11 +writew 0xf8100044 0x1212 +writew 0xf8100044 0x1245 +writew 0xf8100050 0xe2a +writeb 0xf8100002 0x11 +writeb 0xf8100081 0xec +writeb 0xf8100081 0xec +writeb 0xf810030e 0xe +writeb 0xf810000e 0x44 +writeb 0xf8100000 0xe +writeb 0xf8100044 0xe +writeb 0xf8100000 0xe +writeb 0xf810030e 0x13 +writeb 0xf8100b44 0x2a +writeb 0xf8100bf8 0x4 +writeb 0xf8100007 0x45 +writeb 0xf81000ff 0xff +writew 0xf8100044 0xf042 +writew 0xf8100000 0x45 +writew 0xf8100044 0xf042 +writeb 0xf8100000 0xc5 +writeb 0xf81000ff 0xff +writel 0xf8100044 0x101364ff +writel 0xf81000c4 0xfba0a0a0 +writeb 0xf8100000 0x2a +writeb 0xf81000c5 0x40 +writeb 0xf81000ff 0xdf +writew 0xf8100000 0x4144 +writeb 0xf81000df 0x0 +writew 0xf8100044 0x4400 +writel 0xf8100044 0x101364ff +writel 0xf81000c4 0xfb490045 +writeb 0xf8100000 0x2a +writeb 0xf81000c5 0x40 +writel 0xf8100044 0x101364ff +writel 0xf8100bc4 0x49004545 +writeb 0xf8100000 0x2a +writeb 0xf81000c5 0x40 +writeb 0xf810000e 0x21 +writeb 0xf8100000 0x2a +writeb 0xf81000c3 0x40 +writeb 0xf81000ff 0xdf +writew 0xf8100044 0x1210 +writew 0xf8100044 0x1210 +writew 0xf8100010 0x4412 +writew 0xf8100010 0x4412 +writew 0xf8100044 0x1210 +writew 0xf8100044 0x1210 +writew 0xf8100044 0x1210 +writew 0xf8100000 0x4144 +writew 0xf8100044 0x4400 +writew 0xf8100000 0x4144 +writew 0xf81000bc 0xc100 +writew 0xf8100000 0x4144 +writew 0xf81000bc 0xc100 +writew 0xf8100044 0x1210 +writel 0xf8100044 0xfb53000a +writew 0xf8100044 0x1210 +writel 0xf8100044 0xfb53000a +writew 0xf8100044 0x1210 +writel 0xf8100044 0xfba7000a +writew 0xf8100044 0x1210 +writew 0xf8100044 0x1210 +writew 0xf8100000 0x4144 +writew 0xf8100000 0x4144 +writew 0xf8100000 0x4144 +writew 0xf8100044 0x4400 +writew 0xf8100044 0x4411 +writew 0xf8100044 0x1210 +writew 0xf8100044 0x1210 +writew 0xf8100044 0x1210 +writew 0xf8100044 0x1212 +writew 0xf8100044 0x4445 +writeb 0xf81000ff 0xff +writeb 0xf8100121 0x14 +writeb 0xf8100121 0x14 +writeb 0xf8100421 0x0 +writeb 0xf8100421 0x28 +writeb 0xf8100000 0x2a +writeb 0xf81000c5 0x40 +writeb 0xf8100040 0x0 +writeb 0xf8100007 0x45 +writeb 0xf8100007 0x45 +writeb 0xf8100bf8 0x4 +writeb 0xf8100bf8 0x4 +writeb 0xf8100bf8 0x4 +writeb 0xf8100bf8 0x4 +writeb 0xf8100bf8 0x4 +writew 0xf8100060 0x11 +writew 0xf8100060 0x11 +writew 0xf8100060 0x17 +writeb 0xf8100446 0x46 +writeb 0xf8100604 0x50 +writeb 0xf8100821 0x21 +writeb 0xf8100108 0x21 +writeb 0xf810010c 0x21 +writeb 0xf8100081 0xec +writeb 0xf8100041 0xec +writel 0xf8100044 0x101364ff +writel 0xf81000c4 0xfba0a0a0 +writel 0xf8100044 0x101364ff +writel 0xf81000c4 0xfba0a0a0 +writel 0xf8100044 0x101364ff +writel 0xf81000c4 0xfba0a0a0 +writeb 0xf8100052 0x24 +writew 0xf8100000 0x4144 +writeb 0xf81000df 0x0 +writew 0xf8100044 0x4400 +writew 0xf8100000 0x4144 +writeb 0xf81000df 0x41 +writeb 0xf8100504 0x50 +writew 0xf8100010 0x4412 +writew 0xf8100010 0x4412 +writew 0xf8100094 0x4145 +writel 0xf8100044 0x10424410 +writel 0xf81000a0 0xa0a0492a +writel 0xf8100044 0x10040000 +writeb 0xf8100007 0x44 +writeb 0xf81000ff 0xff +writeb 0xf8100007 0x44 +writeb 0xf81000ff 0x4 +writel 0xf8100044 0x10134900 +writeb 0xf8100000 0x2a +writeb 0xf81000c5 0x40 +writeb 0xf8100000 0x2a +writeb 0xf81000c5 0x40 +writew 0xf8100040 0x1212 +writew 0xf8100044 0x1245 +writew 0xf8100040 0x1212 +writew 0xf8100040 0x5002 +writew 0xf8100040 0x5002 +writew 0xf8100040 0x502a +writeb 0xf8100081 0x40 +writeb 0xf810005d 0x40 +writeb 0xf8100030 0x5d +writeb 0xf8100e44 0x44 +writeb 0xf8100044 0x3 +writeb 0xf8100044 0x3 +writeb 0xf8100044 0x13 +writew 0xf8100044 0x1210 +writew 0xf8100044 0x1210 +writew 0xf8100044 0x1210 +writew 0xf8100044 0x6d10 +writeb 0xf8100044 0x6d +writeb 0xf8100000 0x2a +writeb 0xf8100044 0x40 +writeb 0xf8100045 0xec +writew 0xf8100044 0x1210 +writew 0xf8100044 0x1245 +writel 0xf8100044 0x101364ff +writel 0xf81000c4 0xfba0a0a0 +writel 0xf8100044 0x101364ff +writel 0xf8100044 0x101364ff +writel 0xf8100044 0x101364ff +writel 0xf8100008 0xfba0a0a0 +writel 0xf8100044 0x4208fba0 +writew 0xf8100010 0x4412 +writew 0xf8100010 0x4412 +writew 0xf8100010 0x4412 +writew 0xf8100010 0x4412 +writew 0xf8100010 0x4412 +writew 0xf8100000 0x4144 +writeb 0xf810030e 0xe +writeb 0xf810030e 0xe +writeb 0xf810032b 0xe +writeb 0xf810032b 0xe +writew 0xf8100010 0x4412 +writew 0xf81000ca 0x4441 +writew 0xf8100010 0x4412 +writew 0xf8100010 0x4412 +writew 0xf8100010 0x4412 +writew 0xf8100010 0x4412 +writeb 0xf8100080 0xe +writeb 0xf8100080 0xd8 +writeb 0xf8100080 0x26 +writeb 0xf8100040 0x80 +writeb 0xf8100040 0x26 +writeb 0xf81000c3 0x40 +writeb 0xf81000ff 0xdf +writeb 0xf81000c3 0x40 +writeb 0xf81000ff 0xdf +writew 0xf8100014 0x4000 +writeb 0xf8100000 0xe +writeb 0xf8100000 0x9e +writeb 0xf8100000 0x3c +writeb 0xf8100000 0x3c +writeb 0xf8100000 0x3c +writew 0xf8100000 0x4144 +writeb 0xf81000df 0x41 +writeb 0xf8100007 0x45 +writeb 0xf81000ff 0xff +writeb 0xf8100007 0xb4 +writeb 0xf81000ff 0xff +writeb 0xf8100007 0xb4 +writeb 0xf8100007 0xb4 +writel 0xf8100044 0x10139c05 +writel 0xf81000c4 0xfba0a0a0 +writeb 0xf8100604 0x50 +writeb 0xf8100021 0xe +writeb 0xf8100021 0xe +writeb 0xf8100021 0xe +writeb 0xf8100021 0x90 +writew 0xf8100010 0x11 +writew 0xf8100010 0x11 +writew 0xf8100010 0x11 +writeb 0xf8100021 0xe +writeb 0xf8100021 0xe +writeb 0xf8100021 0xe +writeb 0xf8100021 0xe +writeb 0xf8100021 0xe +writew 0xf8100010 0x4412 +writew 0xf8100010 0x4412 +writew 0xf8100010 0x4412 +writew 0xf8100010 0x4412 +writew 0xf8100010 0x4412 +writeb 0xf8100021 0xe +writeb 0xf8100021 0xe +writeb 0xf8100021 0x21 +writeb 0xf8100021 0x21 +writeb 0xf8100000 0x0 +writeb 0xf8100e04 0x46 +EOF + +Program terminated with signal SIGSEGV, Segmentation fault. +#0 0x000056367b2085c0 in artist_rop8 (s=0x56367d38b510, dst=0x7f9f972fffff <error: Cannot access memory at address 0x7f9f972fffff>, val=0 '\000') at hw/display/artist.c:284 +284 *dst &= ~plane_mask; +(gdb) bt +#0 0x000056367b2085c0 in artist_rop8 (s=0x56367d38b510, dst=0x7f9f972fffff <error: Cannot access memory at address 0x7f9f972fffff>, val=0 '\000') at hw/display/artist.c:284 +#1 0x000056367b209325 in draw_line (s=0x56367d38b510, x1=-20480, y1=-1, x2=0, y2=17920, update_start=true, skip_pix=-1, max_pix=-1) at hw/display/artist.c:646 +#2 0x000056367b2095a0 in draw_line_size (s=0x56367d38b510, update_start=true) at hw/display/artist.c:696 +#3 0x000056367b20a214 in artist_reg_write (opaque=0x56367d38b510, addr=1052164, val=70, size=1) at hw/display/artist.c:932 +#4 0x000056367b06ea7c in memory_region_write_accessor (mr=0x56367d38ba10, addr=1052164, value=0x7fff112132d8, size=1, shift=0, mask=255, attrs=...) at memory.c:483 +#5 0x000056367b06ec33 in access_with_adjusted_size (addr=1052164, value=0x7fff112132d8, size=1, access_size_min=1, access_size_max=4, access_fn= + 0x56367b06e999 <memory_region_write_accessor>, mr=0x56367d38ba10, attrs=...) at memory.c:540 +#6 0x000056367b071bb4 in memory_region_dispatch_write (mr=0x56367d38ba10, addr=1052164, data=70, op=MO_8, attrs=...) at memory.c:1477 +#7 0x000056367b00fe33 in flatview_write_continue (fv=0x56367d6f9fa0, addr=4161801732, attrs=..., ptr=0x7fff112134e0, len=1, addr1=1052164, l=1, mr=0x56367d38ba10) at exec.c:3147 +#8 0x000056367b00ff81 in flatview_write (fv=0x56367d6f9fa0, addr=4161801732, attrs=..., buf=0x7fff112134e0, len=1) at exec.c:3190 +#9 0x000056367b0102eb in address_space_write (as=0x56367cff99c0, addr=4161801732, attrs=..., buf=0x7fff112134e0, len=1) at exec.c:3289 \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1882851 b/results/classifier/gemma3:12b/graphic/1882851 new file mode 100644 index 00000000..705a4db9 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1882851 @@ -0,0 +1,21 @@ + +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/gemma3:12b/graphic/1884302 b/results/classifier/gemma3:12b/graphic/1884302 new file mode 100644 index 00000000..95e95e53 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1884302 @@ -0,0 +1,19 @@ + +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/gemma3:12b/graphic/1884990 b/results/classifier/gemma3:12b/graphic/1884990 new file mode 100644 index 00000000..a2db3eb6 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1884990 @@ -0,0 +1,7 @@ + +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/gemma3:12b/graphic/1886306 b/results/classifier/gemma3:12b/graphic/1886306 new file mode 100644 index 00000000..ed2e5fd8 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1886306 @@ -0,0 +1,10 @@ + +qemu running slow when the window is in background + +Reported by <jedinix> on IRC: + +QEMU almost freezes when running with `GDK_BACKEND=x11` set and the parameter `gl=on` added to the `-display` option. + +GDK_BACKEND=x11 qemu-system-x86_64 -nodefaults -no-user-config -enable-kvm -machine q35 -cpu host -m 4G -display gtk,gl=on -vga std -usb -device usb-kbd -drive file=/tmp/Win10.qcow2,media=disk,format=qcow2 -drive file=~/Downloads/Win10_2004_EnglishInternational_x64.iso,media=cdrom + +Leaving out `GDK_BACKEND=x11` or `gl=on` fixes the issue. \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1888492 b/results/classifier/gemma3:12b/graphic/1888492 new file mode 100644 index 00000000..0546489a --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1888492 @@ -0,0 +1,56 @@ + +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/gemma3:12b/graphic/1888606 b/results/classifier/gemma3:12b/graphic/1888606 new file mode 100644 index 00000000..34fe5f00 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1888606 @@ -0,0 +1,140 @@ + +Heap-use-after-free in virtio_gpu_ctrl_response + +Hello, +Here is a reproducer (build with --enable-sanitizers): +cat << EOF | ./i386-softmmu/qemu-system-i386 -nographic -M pc -nodefaults -m 512M -device virtio-vga -qtest stdio +outl 0xcf8 0x80001018 +outl 0xcfc 0xe0800000 +outl 0xcf8 0x80001020 +outl 0xcf8 0x80001004 +outw 0xcfc 0x7 +writeq 0xe0801024 0x10646c00776c6cff +writeq 0xe080102d 0xe0801000320000 +writeq 0xe0801015 0x12b2901ba000000 +write 0x10646c02 0x1 0x2c +write 0x999 0x1 0x25 +write 0x8 0x1 0x78 +write 0x2c7 0x1 0x32 +write 0x2cb 0x1 0xff +write 0x2cc 0x1 0x7e +writeq 0xe0803000 0xf2b8f0540ff83 +EOF + +The ASAN trace: +==29798==ERROR: AddressSanitizer: heap-use-after-free on address 0x60d0000050e8 at pc 0x560629814761 bp 0x7ffe916eb1e0 sp 0x7ffe916eb1d8 +READ of size 8 at 0x60d0000050e8 thread T0 + #0 0x560629814760 in virtio_gpu_ctrl_response /home/alxndr/Development/qemu/hw/display/virtio-gpu.c:181:42 + #1 0x56062981adc8 in virtio_gpu_ctrl_response_nodata /home/alxndr/Development/qemu/hw/display/virtio-gpu.c:193:5 + #2 0x56062981adc8 in virtio_gpu_simple_process_cmd /home/alxndr/Development/qemu/hw/display/virtio-gpu.c:791:9 + #3 0x5606298175f8 in virtio_gpu_process_cmdq /home/alxndr/Development/qemu/hw/display/virtio-gpu.c:820:9 + #4 0x56062a8f1c96 in aio_bh_poll /home/alxndr/Development/qemu/util/async.c:164:13 + #5 0x56062a887b9d in aio_dispatch /home/alxndr/Development/qemu/util/aio-posix.c:380:5 + #6 0x56062a8f6b1c in aio_ctx_dispatch /home/alxndr/Development/qemu/util/async.c:306:5 + #7 0x7f0d5e1cf9ed in g_main_context_dispatch (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x4e9ed) + #8 0x56062a919571 in glib_pollfds_poll /home/alxndr/Development/qemu/util/main-loop.c:217:9 + #9 0x56062a919571 in os_host_main_loop_wait /home/alxndr/Development/qemu/util/main-loop.c:240:5 + #10 0x56062a919571 in main_loop_wait /home/alxndr/Development/qemu/util/main-loop.c:516:11 + #11 0x560629094a64 in qemu_main_loop /home/alxndr/Development/qemu/softmmu/vl.c:1676:9 + #12 0x56062a749ab5 in main /home/alxndr/Development/qemu/softmmu/main.c:49:5 + #13 0x7f0d5cd55e0a in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x26e0a) + #14 0x5606288ba889 in _start (/home/alxndr/Development/qemu/build/i386-softmmu/qemu-system-i386+0x24d0889) + +0x60d0000050e8 is located 56 bytes inside of 136-byte region [0x60d0000050b0,0x60d000005138) +freed by thread T0 here: + #0 0x56062893250d in free (/home/alxndr/Development/qemu/build/i386-softmmu/qemu-system-i386+0x254850d) + #1 0x560629827730 in virtio_gpu_reset /home/alxndr/Development/qemu/hw/display/virtio-gpu.c:1160:9 + #2 0x560628e81d34 in virtio_reset /home/alxndr/Development/qemu/hw/virtio/virtio.c:1999:9 + #3 0x560629f08773 in virtio_pci_reset /home/alxndr/Development/qemu/hw/virtio/virtio-pci.c:1841:5 + #4 0x560629043ab6 in memory_region_write_accessor /home/alxndr/Development/qemu/softmmu/memory.c:483:5 + #5 0x560629043473 in access_with_adjusted_size /home/alxndr/Development/qemu/softmmu/memory.c:544:18 + #6 0x560629042c99 in memory_region_dispatch_write /home/alxndr/Development/qemu/softmmu/memory.c + #7 0x560628990a37 in flatview_write_continue /home/alxndr/Development/qemu/exec.c:3176:23 + #8 0x56062899041a in address_space_write_cached_slow /home/alxndr/Development/qemu/exec.c:3789:12 + #9 0x560628e6f9bb in vring_used_write /home/alxndr/Development/qemu/hw/virtio/virtio.c:347:5 + #10 0x560628e6f9bb in virtqueue_split_fill /home/alxndr/Development/qemu/hw/virtio/virtio.c:788:5 + #11 0x560628e6f9bb in virtqueue_fill /home/alxndr/Development/qemu/hw/virtio/virtio.c:852:9 + #12 0x560628e7205e in virtqueue_push /home/alxndr/Development/qemu/hw/virtio/virtio.c:917:5 + #13 0x560629814246 in virtio_gpu_ctrl_response /home/alxndr/Development/qemu/hw/display/virtio-gpu.c:180:5 + #14 0x56062981adc8 in virtio_gpu_ctrl_response_nodata /home/alxndr/Development/qemu/hw/display/virtio-gpu.c:193:5 + #15 0x56062981adc8 in virtio_gpu_simple_process_cmd /home/alxndr/Development/qemu/hw/display/virtio-gpu.c:791:9 + #16 0x5606298175f8 in virtio_gpu_process_cmdq /home/alxndr/Development/qemu/hw/display/virtio-gpu.c:820:9 + #17 0x56062a8f1c96 in aio_bh_poll /home/alxndr/Development/qemu/util/async.c:164:13 + #18 0x56062a887b9d in aio_dispatch /home/alxndr/Development/qemu/util/aio-posix.c:380:5 + #19 0x56062a8f6b1c in aio_ctx_dispatch /home/alxndr/Development/qemu/util/async.c:306:5 + #20 0x7f0d5e1cf9ed in g_main_context_dispatch (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x4e9ed) + +previously allocated by thread T0 here: + #0 0x56062893278d in malloc (/home/alxndr/Development/qemu/build/i386-softmmu/qemu-system-i386+0x254878d) + #1 0x7f0d5e1d5500 in g_malloc (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x54500) + #2 0x560628e7844b in virtqueue_split_pop /home/alxndr/Development/qemu/hw/virtio/virtio.c:1524:12 + #3 0x560628e7844b in virtqueue_pop /home/alxndr/Development/qemu/hw/virtio/virtio.c:1693:16 + #4 0x560629829633 in virtio_gpu_handle_ctrl /home/alxndr/Development/qemu/hw/display/virtio-gpu.c:878:15 + #5 0x560629829633 in virtio_gpu_ctrl_bh /home/alxndr/Development/qemu/hw/display/virtio-gpu.c:893:5 + #6 0x56062a8f1c96 in aio_bh_poll /home/alxndr/Development/qemu/util/async.c:164:13 + #7 0x56062a887b9d in aio_dispatch /home/alxndr/Development/qemu/util/aio-posix.c:380:5 + #8 0x56062a8f6b1c in aio_ctx_dispatch /home/alxndr/Development/qemu/util/async.c:306:5 + #9 0x7f0d5e1cf9ed in g_main_context_dispatch (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x4e9ed) + + +With -trace virtio\* -trace pci\* : +[I 1595480025.666147] OPENED +31900@1595480025.706962:virtio_set_status vdev 0x633000019640 val 0 +31900@1595480025.710297:virtio_set_status vdev 0x633000019640 val 0 +[R +0.046276] outl 0xcf8 0x80001018 +OK +[S +0.046313] OK +[R +0.046332] outl 0xcfc 0xe0800000 +31900@1595480025.712490:pci_cfg_write virtio-vga 02:0 @0x18 <- 0xe0800000 +OK +[S +0.046356] OK +[R +0.046365] outl 0xcf8 0x80001020 +OK +[S +0.046370] OK +[R +0.046379] outl 0xcf8 0x80001004 +OK +[S +0.046383] OK +[R +0.046391] outw 0xcfc 0x7 +31900@1595480025.712544:pci_cfg_write virtio-vga 02:0 @0x4 <- 0x7 +31900@1595480025.712551:pci_update_mappings_add d=0x633000000800 00:02.0 2,0xe0800000+0x4000 +OK +[S +0.047572] OK +[R +0.047597] writeq 0xe0801024 0x10646c00776c6cff +OK +[S +0.047610] OK +[R +0.047619] writeq 0xe080102d 0xe0801000320000 +OK +[S +0.047627] OK +[R +0.047636] writeq 0xe0801015 0x12b2901ba000000 +OK +[S +0.047650] OK +[R +0.047660] write 0x10646c02 0x1 0x2c +OK +[S +0.047769] OK +[R +0.047782] write 0x999 0x1 0x25 +OK +[S +0.047907] OK +[R +0.047920] write 0x8 0x1 0x78 +OK +[S +0.047927] OK +[R +0.047935] write 0x2c7 0x1 0x32 +OK +[S +0.047941] OK +[R +0.047949] write 0x2cb 0x1 0xff +OK +[S +0.047954] OK +[R +0.047962] write 0x2cc 0x1 0x7e +OK +[S +0.047967] OK +[R +0.047975] writeq 0xe0803000 0xf2b8f0540ff83 +31900@1595480025.714133:virtio_queue_notify vdev 0x633000019640 n 0 vq 0x7fe20b13d800 +OK +[S +0.047996] OK +31900@1595480025.714386:virtio_notify vdev 0x633000019640 vq 0x7fe20b13d800 +31900@1595480025.714406:virtio_gpu_features virgl 0 +31900@1595480025.714413:virtio_notify vdev 0x633000019640 vq 0x7fe20b13d800 +31900@1595480025.714421:virtio_set_status vdev 0x633000019640 val 0 +*CRASH* + +Please let me know if I can provide any further info. +-Alex \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/189 b/results/classifier/gemma3:12b/graphic/189 new file mode 100644 index 00000000..b9e560a4 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/189 @@ -0,0 +1,2 @@ + +Intel GVT-g works in X11, segfaults in wayland diff --git a/results/classifier/gemma3:12b/graphic/1890370 b/results/classifier/gemma3:12b/graphic/1890370 new file mode 100644 index 00000000..f1b607e3 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1890370 @@ -0,0 +1,75 @@ + +Segfault in artist vram_bit_write + +Hello, +Reproducer: + +cat << EOF | ./hppa-softmmu/qemu-system-hppa -m 64 -display none \ +-qtest stdio -accel qtest +writeq 0xf810049f 0xffffffffffffffff +writew 0xf8118001 0xff7c +writew 0xf8118000 0x8300 +writeq 0xf81005fb 0x5c18006400189e +EOF + + +SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior /hw/display/artist.c:402:17 in +AddressSanitizer:DEADLYSIGNAL +================================================================= +==23157==ERROR: AddressSanitizer: SEGV on unknown address 0x7f17563fffff (pc 0x560ce3ad742c bp 0x7ffe310c62e0 sp 0x7ffe310c5a60 T0) +==23157==The signal is caused by a WRITE memory access. + #0 0x560ce3ad742c in vram_bit_write /hw/display/artist.c:402:43 + #1 0x560ce3acf2ab in artist_reg_write /hw/display/artist.c:892:9 + #2 0x560ce31c37a3 in memory_region_write_accessor /softmmu/memory.c:483:5 + #3 0x560ce31c2adc in access_with_adjusted_size /softmmu/memory.c:539:18 + #4 0x560ce31c0873 in memory_region_dispatch_write /softmmu/memory.c:1466:16 + #5 0x560ce286e056 in flatview_write_continue /exec.c:3176:23 + #6 0x560ce2856866 in flatview_write /exec.c:3216:14 + #7 0x560ce2856387 in address_space_write /exec.c:3308:18 + #8 0x560ce326a604 in qtest_process_command /softmmu/qtest.c:452:13 + #9 0x560ce3261c08 in qtest_process_inbuf /softmmu/qtest.c:710:9 + #10 0x560ce3260895 in qtest_read /softmmu/qtest.c:722:5 + #11 0x560ce571d343 in qemu_chr_be_write_impl /chardev/char.c:188:9 + #12 0x560ce571d4c7 in qemu_chr_be_write /chardev/char.c:200:9 + #13 0x560ce57317b3 in fd_chr_read /chardev/char-fd.c:68:9 + #14 0x560ce5885b74 in qio_channel_fd_source_dispatch /io/channel-watch.c:84:12 + #15 0x7f1665259897 in g_main_context_dispatch (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x4e897) + #16 0x560ce5c7da7b in glib_pollfds_poll /util/main-loop.c:217:9 + #17 0x560ce5c7b1ab in os_host_main_loop_wait /util/main-loop.c:240:5 + #18 0x560ce5c7ab44 in main_loop_wait /util/main-loop.c:516:11 + #19 0x560ce3282d00 in qemu_main_loop /softmmu/vl.c:1676:9 + #20 0x560ce58bd961 in main /softmmu/main.c:49:5 + #21 0x7f1663ddfe0a in __libc_start_main /build/glibc-GwnBeO/glibc-2.30/csu/../csu/libc-start.c:308:16 + #22 0x560ce2761729 in _start (/home/alxndr/Development/qemu/general-fuzz/build/hppa-softmmu/qemu-system-hppa+0x22d4729) + + +With -trace artist\* + +[I 1596601002.853158] OPENED +[R +0.047035] writeq 0xf810049f 0xffffffffffffffff +24590@1596601002.900238:artist_reg_write 1 0x10049f <- 0xff +24590@1596601002.900258:artist_reg_write 4 0x1004a0 VRAM_IDX <- 0xffffffff +24590@1596601002.900269:artist_reg_write 2 0x1004a4 <- 0xffff +24590@1596601002.900280:artist_reg_write 1 0x1004a6 <- 0xff +OK +[S +0.047130] OK +[R +0.047159] writew 0xf8118001 0xff7c +24590@1596601002.900331:artist_reg_write 1 0x118001 CMAP_BM_ACCESS <- 0xff +24590@1596601002.900344:artist_reg_write 1 0x118002 CMAP_BM_ACCESS <- 0x7c +OK +[S +0.047194] OK +[R +0.047213] writew 0xf8118000 0x8300 +24590@1596601002.900383:artist_reg_write 2 0x118000 CMAP_BM_ACCESS <- 0x8300 +OK +[S +0.047231] OK +[R +0.047243] writeq 0xf81005fb 0x5c18006400189e +24590@1596601002.900410:artist_reg_write 1 0x1005fb <- 0x0 +24590@1596601002.900418:artist_reg_write 4 0x1005fc <- 0x5c180064 +24590@1596601002.900424:artist_reg_write 2 0x100600 VRAM_WRITE_INCR_X <- 0x18 +/home/alxndr/Development/qemu/general-fuzz/hw/display/artist.c:402:17: runtime error: store to misaligned address 0x7fd01d3fffff for type 'uint32_t' (aka 'unsigned int'), which requires 4 byte alignment +0x7fd01d3fffff: note: pointer points here +<memory cannot be printed> +SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior /home/alxndr/Development/qemu/general-fuzz/hw/display/artist.c:402:17 in +AddressSanitizer:DEADLYSIGNAL + +-Alex \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1890545 b/results/classifier/gemma3:12b/graphic/1890545 new file mode 100644 index 00000000..0e26a270 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1890545 @@ -0,0 +1,26 @@ + +(ARM64) qemu-x86_64+schroot(Debian bullseye) can't run chrome and can't load HTML + +First I creat a file system that is debian(bullseye amd64)on arm64 machine，then I download google-chrome，however, when I ran Google browser, some errors occurred. + +$ google-chrome --no-sandbox +or +$ qemu-x86_64-static google-chrome --no-sandbox + +qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped +qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped +[1661:1661:0806/074307.502638:ERROR:nacl_fork_delegate_linux.cc(323)] Bad NaCl helper startup ack (0 bytes) +[1664:1664:0806/074307.504159:ERROR:nacl_fork_delegate_linux.cc(323)] Bad NaCl helper startup ack (0 bytes) +qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped +qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped +[1637:1678:0806/074308.337567:ERROR:file_path_watcher_linux.cc(315)] inotify_init() failed: Function not implemented (38) +Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank" +qemu: unknown option 'type=utility' +[1637:1680:0806/074313.598432:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye. +qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped +Trace/breakpoint trap + +Why? +And then I run firefox,it can be opened, but it can't load any web pages and HTML. +I really need help！ +Thank. \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1891 b/results/classifier/gemma3:12b/graphic/1891 new file mode 100644 index 00000000..267f09ea --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1891 @@ -0,0 +1,49 @@ + +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/gemma3:12b/graphic/1891749 b/results/classifier/gemma3:12b/graphic/1891749 new file mode 100644 index 00000000..eafc14a5 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1891749 @@ -0,0 +1,4 @@ + +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/gemma3:12b/graphic/1894071 b/results/classifier/gemma3:12b/graphic/1894071 new file mode 100644 index 00000000..0c87287b --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1894071 @@ -0,0 +1,20 @@ + +qemu-i386-static ioctl return -14 (Bad Address) + +I use qemu-i386-static on 64 bit ARM.But I don't know how to solve some problems. +First I added some ioctl operations. +Then I tried to do some DRM operations like test.c. +This is successful when I use qemu-x86_64-static,but it failed when I use qemu-i386-static. +I can get some strace info like this: + +403 openat(AT_FDCWD,"/dev/dri/card0",O_RDWR|O_LARGEFILE|O_CLOEXEC) = 4 +403 ioctl(4,DRM_IOCTL_GET_CAP,{1,0}) = 0 ({1,1}) +403 ioctl(4,DRM_IOCTL_MODE_GETRESOURCES,{0,0,0,0,0,0,0,0,0,0,0,0}) = 0 ({0,0,0,0,0,2,2,2,0,16384,0,16384}) +403 brk(NULL) = 0x40006000 +403 brk(0x40027000) = 0x40027000 +403 brk(0x40028000) = 0x40028000 +403 ioctl(4,DRM_IOCTL_MODE_GETRESOURCES,{0,1073766816,1073766832,1073766848,0,2,2,2,0,16384,0,16384}) = -1 errno=14 (Bad address) + +And there are similar errors in other self driven operations. +I want to know if it is QEMU's problem, so I hope to get some help. +Thank you! \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1896561 b/results/classifier/gemma3:12b/graphic/1896561 new file mode 100644 index 00000000..4da677fe --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1896561 @@ -0,0 +1,27 @@ + +EFI GOP Mode 1366x768 + +When using the EFI firmware from https://www.kraxel.org/repos/jenkins/edk2/ (https://www.kraxel.org/repos/jenkins/edk2/edk2.git-ovmf-x64-0-20200919.1453.g7faece6985.noarch.rpm) (OVMF-pure-efi.fd and OVMF_VARS-pure-efi.fd) then using the GOP, setting the mode to 1366x768, QEMU uses a width of 1360 instead. + +I am using QEMU for windows (https://qemu.weilnetz.de/) on a Windows 10 machine. + +To verify, while in the EFI firmware loaded code (within BOOTx64.EFI) and before ExitBootServices(), I choose the 1360x768 mode. I then took notice of where the host window was and how many pixels it occupied. I then reset the emulation (without quitting) and chose the 1366x768 mode. QEMU set the host window to the exact same width as the 1360 mode. i.e.: The same exact pixels where shown in the host background. The window did not expand the extra 6 pixels. + +I allowed the firmware to run its course to my test environment when using mode 1366x768, all pixels are 6 pixels off to the right. i.e.: 6 pixels down the Frame Buffer. If my test environment changes its HORZ WIDTH and PIXELS PER SCANLINE to 1360 while using this (1366x768) mode, the display is correct. + +This told me that it could be a few things. +1) Since most (I didn't check them all) of the other modes have the width value's bits 2:0 clear, mode 1366x768 is the only mode the EDK2 firmware has with a width where bits 2:0 are not zero. Could EDK2 or QEMU (which for the Windows version may use SDL2 so it must be considered here) be clearing these bits? The value of 1366 when clearing bits 2:0 is 1360. + +2) Could there be a typo in the code EDK2 where the width should have been 1366? +(I went looking at both QEMU (for Windows) and EDK2 and after looking at many lines of code, I could not find anywhere where this might happen. + +By the way, in /ui/sdl2-2d.c (QEMU Windows version only?), there is a typo in a comment, missing the second 'e': + +Line 156: * the native ones. Thes are the ones I have tested. + +3) Could EDK2 be sending 1360 instead of 1366? +4) Could QEMU (passing it on to SDL2 in SDL_SetWindowSize()?) be destroying the value (bottom three bits)? + +Anyway, using the latest version of the EDK2 from the URL listed above, choosing the 1366x768 mode, does not set QEMU (for Windows) to 1366 pixels in width. + +Ben \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1898215 b/results/classifier/gemma3:12b/graphic/1898215 new file mode 100644 index 00000000..ae31eccd --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1898215 @@ -0,0 +1,42 @@ + +[git][archlinux]Build process is busted in spice-display.c + +Linux distribution: Archlinux. Crash log added is based on a build from scratch. + +Gcc version: 10.2.0 + +Configure options used: + +configure \ + --prefix=/usr \ + --sysconfdir=/etc \ + --localstatedir=/var \ + --libexecdir=/usr/lib/qemu \ + --extra-ldflags="$LDFLAGS" \ + --smbd=/usr/bin/smbd \ + --enable-modules \ + --enable-sdl \ + --disable-werror \ + --enable-slirp=system \ + --enable-xfsctl \ + --audio-drv-list="pa alsa sdl" + +Crash log: + +../ui/spice-display.c: In function 'interface_client_monitors_config': +../ui/spice-display.c:682:25: error: 'VD_AGENT_CONFIG_MONITORS_FLAG_PHYSICAL_SIZE' undeclared (first use in this function); did you mean 'VD_AGENT_CONFIG_MONITORS_FLAG_USE_POS'? + 682 | if (mc->flags & VD_AGENT_CONFIG_MONITORS_FLAG_PHYSICAL_SIZE) { + | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + | VD_AGENT_CONFIG_MONITORS_FLAG_USE_POS +../ui/spice-display.c:682:25: note: each undeclared identifier is reported only once for each function it appears in +../ui/spice-display.c:683:13: error: unknown type name 'VDAgentMonitorMM' + 683 | VDAgentMonitorMM *mm = (void *)&mc->monitors[mc->num_of_monitors]; + | ^~~~~~~~~~~~~~~~ +../ui/spice-display.c:684:37: error: request for member 'width' in something not a structure or union + 684 | info.width_mm = mm[head].width; + | ^ +../ui/spice-display.c:685:38: error: request for member 'height' in something not a structure or union + 685 | info.height_mm = mm[head].height; + | ^ +make: *** [Makefile.ninja:2031: libcommon.fa.p/ui_spice-display.c.o] Error 1 +make: *** Waiting for unfinished jobs.... \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1898490 b/results/classifier/gemma3:12b/graphic/1898490 new file mode 100644 index 00000000..5cd43da8 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1898490 @@ -0,0 +1,16 @@ + +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/gemma3:12b/graphic/1899733 b/results/classifier/gemma3:12b/graphic/1899733 new file mode 100644 index 00000000..3adeb335 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1899733 @@ -0,0 +1,21 @@ + +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/gemma3:12b/graphic/1902 b/results/classifier/gemma3:12b/graphic/1902 new file mode 100644 index 00000000..5aa3272b --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1902 @@ -0,0 +1,66 @@ + +Crash on macOS when screen resolution changes when using SDL UI frontend +Description of problem: +In the above configuration, booting NetBSD works fine up to the point where the kernel sets the framebuffer resolution for the console, which results in a window size change. At this point, the OS terminates the qemu process with this error message: + +``` +*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'NSWindow geometry should only be modified on the main thread!' +*** First throw call stack: +( + 0 CoreFoundation 0x00000001849208c0 __exceptionPreprocess + 176 + 1 libobjc.A.dylib 0x0000000184419eb4 objc_exception_throw + 60 + 2 CoreFoundation 0x0000000184945bac _CFBundleGetValueForInfoKey + 0 + 3 AppKit 0x00000001880a6ab8 -[NSWindow(NSWindow_Theme) _postWindowNeedsToResetDragMarginsUnlessPostingDisabled] + 240 + 4 AppKit 0x00000001880b2a38 -[NSThemeFrame _tileTitlebarAndRedisplay:] + 88 + 5 AppKit 0x00000001880c18a0 -[NSTitledFrame _titleDidChange] + 116 + 6 AppKit 0x0000000188a92f04 -[NSTitledFrame setTitle:subtitle:] + 420 + 7 AppKit 0x00000001880c1570 -[NSThemeFrame setTitle:] + 52 + 8 AppKit 0x000000018866e0fc -[NSFrameView _updateTitleProperties:animated:] + 44 + 9 AppKit 0x0000000188a85e98 -[NSThemeFrame _updateTitleProperties:animated:] + 156 + 10 CoreFoundation 0x00000001848a0780 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 148 + 11 CoreFoundation 0x00000001849349a8 ___CFXRegistrationPost_block_invoke + 88 + 12 CoreFoundation 0x00000001849348f0 _CFXRegistrationPost + 440 + 13 CoreFoundation 0x000000018486f434 _CFXNotificationPost + 764 + 14 Foundation 0x0000000185960c74 -[NSNotificationCenter postNotificationName:object:userInfo:] + 88 + 15 AppKit 0x000000018881da88 -[NSWindowTitleController _propertiesChanged:] + 128 + 16 AppKit 0x00000001880c1388 -[NSWindow _dosetTitle:andDefeatWrap:] + 156 + 17 libSDL2-2.0.0.dylib 0x0000000106aa9abc Cocoa_SetWindowTitle + 104 + 18 qemu-system-aarch64 0x0000000105006628 sdl_update_caption + 256 + 19 qemu-system-aarch64 0x0000000105007838 sdl_mouse_mode_change + 168 + 20 qemu-system-aarch64 0x00000001054ab100 notifier_list_notify + 36 + 21 qemu-system-aarch64 0x0000000104d28124 qemu_input_check_mode_change + 96 + 22 qemu-system-aarch64 0x0000000104e13a74 hid_pointer_activate + 32 + 23 qemu-system-aarch64 0x0000000104f44c2c usb_process_one + 464 + 24 qemu-system-aarch64 0x0000000104f4491c usb_handle_packet + 120 + 25 qemu-system-aarch64 0x0000000104f58a94 xhci_kick_epctx + 1888 + 26 qemu-system-aarch64 0x00000001052d8f78 memory_region_write_accessor + 264 + 27 qemu-system-aarch64 0x00000001052d8db8 access_with_adjusted_size + 348 + 28 qemu-system-aarch64 0x00000001052d8c04 memory_region_dispatch_write + 428 + 29 qemu-system-aarch64 0x00000001052e6cfc flatview_write_continue + 344 + 30 qemu-system-aarch64 0x00000001052e4068 flatview_write + 156 + 31 qemu-system-aarch64 0x00000001052e9424 subpage_write + 124 + 32 qemu-system-aarch64 0x00000001052d8db8 access_with_adjusted_size + 348 + 33 qemu-system-aarch64 0x00000001052d8c04 memory_region_dispatch_write + 428 + 34 qemu-system-aarch64 0x000000010532ebf4 io_writex + 184 + 35 qemu-system-aarch64 0x000000010532ed44 do_st_mmio_leN + 104 + 36 qemu-system-aarch64 0x0000000105323e78 do_st4_mmu + 536 + 37 ??? 0x0000000108a91750 0x0 + 4440266576 + 38 qemu-system-aarch64 0x00000001053108f0 cpu_tb_exec + 164 + 39 qemu-system-aarch64 0x0000000105311754 cpu_exec_loop + 1084 + 40 qemu-system-aarch64 0x0000000105310edc cpu_exec_setjmp + 48 + 41 qemu-system-aarch64 0x0000000105310dcc cpu_exec + 560 + 42 qemu-system-aarch64 0x0000000105332650 tcg_cpus_exec + 44 + 43 qemu-system-aarch64 0x0000000105332c1c mttcg_cpu_thread_fn + 240 + 44 qemu-system-aarch64 0x00000001054a7494 qemu_thread_start + 128 + 45 libsystem_pthread.dylib 0x00000001847cf034 _pthread_start + 136 + 46 libsystem_pthread.dylib 0x00000001847c9e3c thread_start + 8 +) +libc++abi: terminating due to uncaught exception of type NSException +``` + +I think there have been other bugs of a similar nature in the past with the Cocoa UI. The regression may be because of stricter checks in the new macOS version. +Steps to reproduce: +1. Start qemu (the QEMU_EFI.fd is from Tianocore EDK2). +2. Wait for the NetBSD kernel to set framebuffer resolution and observe the crash. + +With `-nographic`, the problem does not occur. diff --git a/results/classifier/gemma3:12b/graphic/1904315 b/results/classifier/gemma3:12b/graphic/1904315 new file mode 100644 index 00000000..1d90f556 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1904315 @@ -0,0 +1,24 @@ + +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/gemma3:12b/graphic/1906185 b/results/classifier/gemma3:12b/graphic/1906185 new file mode 100644 index 00000000..219bee63 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1906185 @@ -0,0 +1,32 @@ + +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/gemma3:12b/graphic/1906948 b/results/classifier/gemma3:12b/graphic/1906948 new file mode 100644 index 00000000..2f49664f --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1906948 @@ -0,0 +1,29 @@ + +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/gemma3:12b/graphic/1907061 b/results/classifier/gemma3:12b/graphic/1907061 new file mode 100644 index 00000000..75ea4dc5 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1907061 @@ -0,0 +1,16 @@ + +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/gemma3:12b/graphic/1907952 b/results/classifier/gemma3:12b/graphic/1907952 new file mode 100644 index 00000000..9c39fdce --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1907952 @@ -0,0 +1,45 @@ + +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/gemma3:12b/graphic/1908266 b/results/classifier/gemma3:12b/graphic/1908266 new file mode 100644 index 00000000..31c420dd --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1908266 @@ -0,0 +1,4 @@ + +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/gemma3:12b/graphic/1910696 b/results/classifier/gemma3:12b/graphic/1910696 new file mode 100644 index 00000000..f937374b --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1910696 @@ -0,0 +1,10 @@ + +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/gemma3:12b/graphic/1914294 b/results/classifier/gemma3:12b/graphic/1914294 new file mode 100644 index 00000000..d3b47bd6 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1914294 @@ -0,0 +1,14 @@ + +Windows XP displays black screen when smp option is used + +When I use Windows XP with the -smp option, the screen goes black. The only thing I can see is a cursor. I have tried -smp 2, -smp cores=4, and -smp cores=2. + +My info: + +Host: +M1 Mac +Mac OS 11.1 +QEMU 5.2 at cf7ca7d5b9faca13f1f8e3ea92cfb2f741eb0c0e. + +Guest: +32-bit Windows XP SP3 build 2600. \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/1926952 b/results/classifier/gemma3:12b/graphic/1926952 new file mode 100644 index 00000000..ae55f6ba --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1926952 @@ -0,0 +1,37 @@ + +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/gemma3:12b/graphic/1932 b/results/classifier/gemma3:12b/graphic/1932 new file mode 100644 index 00000000..8fd6e95a --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1932 @@ -0,0 +1,13 @@ + +Broken grab on hover setting +Description of problem: +It seems that now qemu implements "static" grab on hover, i.e., it can only be disabled by + +1. setting `vmport=off` in `-M` (btw, `pc` or `q35`, doesn't matter) +2. emulating a usb mouse *and* blacklist/unload the `psmouse` driver on the guest side + +while grab on hover setting in the gtk display backend (or frontend?) is seemingly bogus now either way. + +Can this be fixed (again?) so that the setting (which can be toggled in the menu "dynamically") can be used to tell this "vmport" thing whether or not it should grab on hover? +Additional information: +NIL diff --git a/results/classifier/gemma3:12b/graphic/194 b/results/classifier/gemma3:12b/graphic/194 new file mode 100644 index 00000000..b6d4a48d --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/194 @@ -0,0 +1,2 @@ + +Qemu fails to start with error " There is no option group 'spice'" diff --git a/results/classifier/gemma3:12b/graphic/196 b/results/classifier/gemma3:12b/graphic/196 new file mode 100644 index 00000000..60968a45 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/196 @@ -0,0 +1,2 @@ + +Improve UX for macOS when launching from a fullscreen app diff --git a/results/classifier/gemma3:12b/graphic/1964 b/results/classifier/gemma3:12b/graphic/1964 new file mode 100644 index 00000000..1460569c --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1964 @@ -0,0 +1,8 @@ + +QEMU TCG faulted in RUNDLL32 at Windows 98SE Display Properties +Description of problem: +QEMU TCG faulted in RUNDLL32 at Windows 98SE Display Properties. 100% consistently reproducible across multiple host operating systems and CPU architectures and all types of QEMU emulated display controllers supported by Windows 98SE (`VGA, cirrus-vga and vmware-svga`). It is a user-mode fault so the OS simply terminated the faulting process, OS remains fully functional after the fault and the same fault can be repeated. Should be extremely helpful in debugging. Last known good QEMU version without this bug is 7.1.0. For x86_64, KVM and WHPX do not have the issue and can be used to gain access to Display Properties. On AArch64, last known good QEMU version is the only way to gain access to Display Properties. +Steps to reproduce: +See attached recorded video. + + diff --git a/results/classifier/gemma3:12b/graphic/1973 b/results/classifier/gemma3:12b/graphic/1973 new file mode 100644 index 00000000..be15218e --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1973 @@ -0,0 +1,2 @@ + +Issues with dmabuf use in dbus interface diff --git a/results/classifier/gemma3:12b/graphic/1994 b/results/classifier/gemma3:12b/graphic/1994 new file mode 100644 index 00000000..08a2309d --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/1994 @@ -0,0 +1,2 @@ + +MacOS window sizing bug diff --git a/results/classifier/gemma3:12b/graphic/2002 b/results/classifier/gemma3:12b/graphic/2002 new file mode 100644 index 00000000..9d524757 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2002 @@ -0,0 +1,4 @@ + +Need to be able to set WM_CLASS under X11 +Additional information: + diff --git a/results/classifier/gemma3:12b/graphic/2026 b/results/classifier/gemma3:12b/graphic/2026 new file mode 100644 index 00000000..7f4664a1 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2026 @@ -0,0 +1,9 @@ + +Virtio-vga-gl: If xres/yres is set, Qemu should not inherit the resolution of the window +Description of problem: +Despite setting xres=1920,yres-1080 when the VM the resolution the VM gets set to is inherited from the window. +Steps to reproduce: +1. Launch VM with xres/yres set +2. check display size +Additional information: + diff --git a/results/classifier/gemma3:12b/graphic/2048 b/results/classifier/gemma3:12b/graphic/2048 new file mode 100644 index 00000000..ebf8ce16 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2048 @@ -0,0 +1,2 @@ + +Host: Wayland sdl display problem diff --git a/results/classifier/gemma3:12b/graphic/2050 b/results/classifier/gemma3:12b/graphic/2050 new file mode 100644 index 00000000..4553916f --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2050 @@ -0,0 +1,8 @@ + +Graphical glitch on boot screen of ubuntu aarch64 +Description of problem: +Glitches on boot screen. +Additional information: + + +(The "TIANO Core" screen before this has similar issues) diff --git a/results/classifier/gemma3:12b/graphic/2051 b/results/classifier/gemma3:12b/graphic/2051 new file mode 100644 index 00000000..c46fbcec --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2051 @@ -0,0 +1,2 @@ + +virtio-gpu redraw issue diff --git a/results/classifier/gemma3:12b/graphic/2052 b/results/classifier/gemma3:12b/graphic/2052 new file mode 100644 index 00000000..8db3ec8d --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2052 @@ -0,0 +1,2 @@ + +sdl window partially catches mouse cursor diff --git a/results/classifier/gemma3:12b/graphic/2056 b/results/classifier/gemma3:12b/graphic/2056 new file mode 100644 index 00000000..b046d17f --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2056 @@ -0,0 +1,15 @@ + +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: + + +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/gemma3:12b/graphic/2067 b/results/classifier/gemma3:12b/graphic/2067 new file mode 100644 index 00000000..20cf71b2 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2067 @@ -0,0 +1,2 @@ + +screen unblanking issue with debian 12 gui diff --git a/results/classifier/gemma3:12b/graphic/2068 b/results/classifier/gemma3:12b/graphic/2068 new file mode 100644 index 00000000..61dd548c --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2068 @@ -0,0 +1,16 @@ + +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/gemma3:12b/graphic/2085 b/results/classifier/gemma3:12b/graphic/2085 new file mode 100644 index 00000000..b8e543e3 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2085 @@ -0,0 +1,23 @@ + +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/gemma3:12b/graphic/2099 b/results/classifier/gemma3:12b/graphic/2099 new file mode 100644 index 00000000..6e427092 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2099 @@ -0,0 +1,12 @@ + +Setting for initial GTK window size? +Description of problem: + +Steps to reproduce: +1. When starting QEMU on Windows, the GTK window size appears to be sized to approx 640x480, which is very hard to see on a 4k+ monitor. So interacting with the boot, reading BIOS messages, etc, isn't great. +2. It would be great to be able to specify the dimensions of the GTK window, say 2560x1600, and then just set "Zoom to Fit". +3. This way, the visible window area remains constant, and all stages of graphical interaction get scaled to a workable size. +4. The OS can be configured to say 2560x1600 once setup. +5. Perhaps I've overlook settings to accomplish this? + +Thank you. diff --git a/results/classifier/gemma3:12b/graphic/2100 b/results/classifier/gemma3:12b/graphic/2100 new file mode 100644 index 00000000..8269f475 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2100 @@ -0,0 +1,7 @@ + +Add option to skip quit confirmation with Cocoa display +Additional information: +This change was originally requested in back in 2016, but got lost in the issue tracker migration: https://bugs.launchpad.net/qemu/+bug/1556372 + +Patch in question: +https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg05031.html diff --git a/results/classifier/gemma3:12b/graphic/2116 b/results/classifier/gemma3:12b/graphic/2116 new file mode 100644 index 00000000..d04cf8a8 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2116 @@ -0,0 +1,29 @@ + +[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/gemma3:12b/graphic/2145 b/results/classifier/gemma3:12b/graphic/2145 new file mode 100644 index 00000000..c7bcf49d --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2145 @@ -0,0 +1,38 @@ + +Issue with Graphical Interface on RISC-V Emulation in QEMU +Description of problem: +I am facing an issue when attempting to run Ubuntu on RISC-V architecture in QEMU with a graphical interface. Specifically, when executing the following command without the -nographic option, the operating system fails to start: + +```bash +qemu-system-riscv64 -machine virt -m 2048 -smp 4 -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin -kernel /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf -drive file=ubuntu-22.04.3-preinstalled-server-riscv64+unmatched.img,format=raw,if=virtio +``` + +I have not found any examples online where QEMU is used with RISC-V architecture without the -nographic option, which raises uncertainty about the feasibility of running it with a graphical interface. + +Interestingly, when I run a similar command for x86_64 architecture, the operating system starts successfully with a graphical interface: + +```bash +qemu-system-x86_64 -enable-kvm -m 2G -drive file=ubuntu-22.04.3-desktop-amd64.iso,format=raw -boot c -cpu host -vga std -device virtio-net-pci -device virtio-rng-pci +``` +Steps to reproduce: +Execute QEMU with RISC-V architecture without the -nographic option. + +```bash +qemu-system-riscv64 -machine virt -m 2048 -smp 4 -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin -kernel /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf -drive file=ubuntu-22.04.3-preinstalled-server-riscv64+unmatched.img,format=raw,if=virtio +``` + +(The above command fails to start with a graphical interface) + +Execute QEMU with RISC-V architecture and the -nographic option. + +```bash +qemu-system-riscv64 -machine virt -nographic -m 2048 -smp 4 -bios /usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.bin -kernel /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf -drive file=ubuntu-22.04.3-preinstalled-server-riscv64+unmatched.img,format=raw,if=virtio +``` +(The above command works, but without a graphical interface) + +Execute QEMU with x86_64 architecture. + +```bash +qemu-system-x86_64 -enable-kvm -m 2G -drive file=ubuntu-22.04.3-desktop-amd64.iso,format=raw -boot c -cpu host -vga std -device virtio-net-pci -device virtio-rng-pci +``` +(The above command works and starts with a graphical interface) diff --git a/results/classifier/gemma3:12b/graphic/2158 b/results/classifier/gemma3:12b/graphic/2158 new file mode 100644 index 00000000..5fe6a98e --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2158 @@ -0,0 +1,10 @@ + +Qemu will not release mouse even after using the release mouse keybind +Description of problem: +There wasn't a crash but this is an annoying problem. The mouse does not release when the VM sizes the window larger because, as far as I know, qemu moves the window and relies on the user to click to release the mouse. +Steps to reproduce: +1. Open qemu +2. Try to release the mouse using the keybind shown. +3. It move the window and won't release. +Additional information: +In case it's really needed, I am using a custom QEMU VM Manager called "QEMU Manager". diff --git a/results/classifier/gemma3:12b/graphic/2172 b/results/classifier/gemma3:12b/graphic/2172 new file mode 100644 index 00000000..19b8d097 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2172 @@ -0,0 +1,2 @@ + +Error "cannot enable SPICE if pixman is not available" diff --git a/results/classifier/gemma3:12b/graphic/2188 b/results/classifier/gemma3:12b/graphic/2188 new file mode 100644 index 00000000..e2808bd0 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2188 @@ -0,0 +1,11 @@ + +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/gemma3:12b/graphic/2200 b/results/classifier/gemma3:12b/graphic/2200 new file mode 100644 index 00000000..3c1b876f --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2200 @@ -0,0 +1,10 @@ + +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/gemma3:12b/graphic/2201 b/results/classifier/gemma3:12b/graphic/2201 new file mode 100644 index 00000000..cbf21002 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2201 @@ -0,0 +1,12 @@ + +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/gemma3:12b/graphic/2217 b/results/classifier/gemma3:12b/graphic/2217 new file mode 100644 index 00000000..25ea4de5 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2217 @@ -0,0 +1,2 @@ + +Changing screen grab diff --git a/results/classifier/gemma3:12b/graphic/2225 b/results/classifier/gemma3:12b/graphic/2225 new file mode 100644 index 00000000..3043a4af --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2225 @@ -0,0 +1,12 @@ + +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/gemma3:12b/graphic/2231 b/results/classifier/gemma3:12b/graphic/2231 new file mode 100644 index 00000000..eeff02ae --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2231 @@ -0,0 +1,15 @@ + +GNOME/Mutter - Wayland Fractional Scaling Breaks VM Resolution +Description of problem: +VMs are rendered at a higher resolution than the pixel count of their window, seemingly because mutter is upscaling for fractional scaling. +Steps to reproduce: +1. Enable GNOME Mutter experimental fractional scaling +2. Launch VM +Additional information: +This only occurs when wayland fractional scaling is enabled, not when text is scaled. Since GNOME/mutter accomplishes fractional scaling by upscaling, I think the VM is being told its window has a higher resolution than it actually has, so it is rendering the VM at a higher resolution, which is then displayed at the display's real resolution. + +In the screenshot below, my resolution is 2256 x 1504 and I have set fractional scaling to 125%. It is worth noting (2256 / 1.25) / 3606 is approximately 0.5. + + + +I apologize if the report is unsatisfactory. I will provide more detail if instructed. I tried reporting to GNOME Boxes and Virt-manager, which both use QEMU, but it seems the problem is upstream. diff --git a/results/classifier/gemma3:12b/graphic/2234 b/results/classifier/gemma3:12b/graphic/2234 new file mode 100644 index 00000000..6cbbd624 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2234 @@ -0,0 +1,24 @@ + +upon pressing F2 failures in loading the edk2 bios interface app +Description of problem: +Cosmetic, low priority, but maybe easy to fix +Occasional failures to load the edk2 bios interface app +Workaround, retry until success +Steps to reproduce: +1. start qemu +2. press F2 when qemu guest display window pops up. When it works, it brings up the edk2 bios interface. + This bug concerns the case when it does not work + +For reasons not clear, sometimes, after pressing F2, and after qemu registered the key-stroke (F2) and responded by changing the window size, the bios interface loading process seems to abruptly stop at the following guest-display-screen with the following message. +```BdsDxe: Loading Boot0000 "UiApp" From Fv(7CB8BDC9-F8EB-F434-AAEA-3EE4AF6516A1)/FvFile(462CAA21-7614-4503-836E-8AB6F4662311)``` + + +When the bios interface loading process does succeed, it goes to the expected screen: + +Additional information: +Unsure if this sort of bug should go upstream to https://github.com/tianocore/edk2/issues +Herein notifying @kraxel + +Not a measured statistic, but on basis of feeling, I'd qualitatively say 4 out of 5 times it fails to bring up the bios interface. Its a bit frustrating because it feels like one has no control over it and a successful event is left to chance. + +This isn't a recent introduction/regression. I've noticed this since 8.0.0, so its been this way maybe longer. diff --git a/results/classifier/gemma3:12b/graphic/2244 b/results/classifier/gemma3:12b/graphic/2244 new file mode 100644 index 00000000..cedde6a0 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2244 @@ -0,0 +1,47 @@ + +Regression in 8.2.90: cpu_physical_memory_snapshot_get_dirty: assertion failed +Description of problem: +On executing the image from QEMU advent calendar 2014, door 12 the following error is shown and QEMU exists. + +On Debian (built on git-repo) +``` +$ qemu-system-i386 oberon/oberon.qcow2 +qemu-system-i386: ../system/physmem.c:948: cpu_physical_memory_snapshot_get_dirty: Zusicherung »start + length <= snap->end« nicht erfüllt. +Abgebrochen +``` +On Windows (built on qemu-9.0.0-rc0.tar.xz) +``` +$ qemu-system-i386 oberon/oberon.qcow2 +ERROR:../qemu-9.0.0-rc0/system/physmem.c:946:cpu_physical_memory_snapshot_get_dirty: assertion failed: (start + length <= snap->end) +Bail out! ERROR:../qemu-9.0.0-rc0/system/physmem.c:946:cpu_physical_memory_snapshot_get_dirty: assertion failed: (start + length <= snap->end) +``` +Steps to reproduce: +1. Retrieve oberon.tar.xz with `wget http://qemu-advent-calendar.org/2014/download/oberon.tar.xz` +2. Extract with `tar -xf oberon.tar.xz` +3. Execute with `qemu-system-i386 oberon/oberon.qcow2` +Additional information: +The same error is shown for QEMU advent calendar 2014, door 15 (Plan 9 from Bell Labs) soon after switch to graphical mode. + +git bisect result: +``` +973a724eb006f674301a0c45f34b3c08dee0fe49 is the first bad commit +commit 973a724eb006f674301a0c45f34b3c08dee0fe49 +Author: Paolo Bonzini <pbonzini@redhat.com> +Date: Mon Dec 29 14:48:14 2014 +0100 + + vga: implement horizontal pel panning in graphics modes + + This implements smooth scrolling, as used for example by Commander Keen + and Second Reality. + + Unfortunately, this is not enough to avoid tearing in Commander Keen, + because sometimes the wrong start address is used for a frame. + On real EGA, the panning register is sampled on every line, while + the display start is latched for the next frame at the start of the + vertical retrace. On real VGA, the panning register is also latched, + but at the end of the vertical retrace. It looks like Keen exploits + this by only waiting for horizontal retrace when setting the display + start, but implementing it breaks the 256-color Keen games... + + Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> +``` diff --git a/results/classifier/gemma3:12b/graphic/225 b/results/classifier/gemma3:12b/graphic/225 new file mode 100644 index 00000000..dc6d914c --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/225 @@ -0,0 +1,2 @@ + +Menu is not clickable on OSX Catalina diff --git a/results/classifier/gemma3:12b/graphic/2252 b/results/classifier/gemma3:12b/graphic/2252 new file mode 100644 index 00000000..f66519c0 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2252 @@ -0,0 +1,12 @@ + +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: + diff --git a/results/classifier/gemma3:12b/graphic/226 b/results/classifier/gemma3:12b/graphic/226 new file mode 100644 index 00000000..c93bd708 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/226 @@ -0,0 +1,2 @@ + +host window size does not change when guest video screen size changes while moving host window diff --git a/results/classifier/gemma3:12b/graphic/2261 b/results/classifier/gemma3:12b/graphic/2261 new file mode 100644 index 00000000..a77d0202 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2261 @@ -0,0 +1,88 @@ + +qemu-system-x86_64 crashs in cursor_put functions +Description of problem: +This problem cannot be stably reproduced，but we try enable --enable-sanitizers and catch the following information，why qemu_spice_cursor_refresh_bh be called twice at the same time？ + +==57296==ERROR: AddressSanitizer: heap-use-after-free on address 0x623000738110 at pc 0x55cec2ed06aa bp 0x7ffc54d1fea0 sp 0x7ffc54d1fe90 +READ of size 4 at 0x623000738110 thread T0 + #0 0x55cec2ed06a9 in cursor_put ../qemu-6.0.1/ui/cursor.c:112 + #1 0x55cec2f05d40 in vnc_dpy_cursor_define ../qemu-6.0.1/ui/vnc.c:1041 + #2 0x55cec2ec6352 in dpy_cursor_define ../qemu-6.0.1/ui/console.c:1841 + #3 0x55cec3ab176c in qemu_spice_cursor_refresh_bh ../qemu-6.0.1/ui/spice-display.c:469 + #4 0x55cec4abc6eb in aio_bh_call ../qemu-6.0.1/util/async.c:136 + #5 0x55cec4abce43 in aio_bh_poll ../qemu-6.0.1/util/async.c:164 + #6 0x55cec4a5f457 in aio_dispatch ../qemu-6.0.1/util/aio-posix.c:381 + #7 0x55cec4abe386 in aio_ctx_dispatch ../qemu-6.0.1/util/async.c:306 + #8 0x7fa4fadcdd3a in g_main_context_dispatch (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x55d3a) + #9 0x55cec4b0b5d6 in glib_pollfds_poll ../qemu-6.0.1/util/main-loop.c:231 + #10 0x55cec4b0b7c0 in os_host_main_loop_wait ../qemu-6.0.1/util/main-loop.c:254 + #11 0x55cec4b0bac5 in main_loop_wait ../qemu-6.0.1/util/main-loop.c:530 + #12 0x55cec3f49e70 in qemu_main_loop ../qemu-6.0.1/softmmu/runstate.c:786 + #13 0x55cec2e7f679 in main ../qemu-6.0.1/softmmu/main.c:50 + #14 0x7fa4f96f4d8f in __libc_start_call_main ../sysdeps/nptl/libc_start_call_main.h:58 + #15 0x7fa4f96f4e3f in __libc_start_main_impl ../csu/libc-start.c:392 + #16 0x55cec2e7f584 in _start (/usr/bin/qemu-system-x86_64+0x298a584) + +0x623000738110 is located 16 bytes inside of 6416-byte region [0x623000738100,0x623000739a10) +freed by thread T0 here: + #0 0x7fa4fb7d9537 in __interceptor_free ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:127 + #1 0x55cec2ed0769 in cursor_put ../qemu-6.0.1/ui/cursor.c:115 + #2 0x55cec3ab1818 in qemu_spice_cursor_refresh_bh ../qemu-6.0.1/ui/spice-display.c:471 + #3 0x55cec4abc6eb in aio_bh_call ../qemu-6.0.1/util/async.c:136 + #4 0x55cec4abce43 in aio_bh_poll ../qemu-6.0.1/util/async.c:164 + #5 0x55cec4a5f457 in aio_dispatch ../qemu-6.0.1/util/aio-posix.c:381 + #6 0x55cec4abe386 in aio_ctx_dispatch ../qemu-6.0.1/util/async.c:306 + #7 0x7fa4fadcdd3a in g_main_context_dispatch (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x55d3a) + +previously allocated by thread T14 here: + #0 0x7fa4fb7d9a57 in __interceptor_calloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:154 + #1 0x7fa4fadd6c50 in g_malloc0 (/lib/x86_64-linux-gnu/libglib-2.0.so.0+0x5ec50) + #2 0x55cec3b16918 in qxl_cursor ../qemu-6.0.1/hw/display/qxl-render.c:361 + #3 0x55cec3b18698 in qxl_render_cursor ../qemu-6.0.1/hw/display/qxl-render.c:448 + #4 0x55cec3af53a5 in interface_get_cursor_command ../qemu-6.0.1/hw/display/qxl.c:856 + #5 0x7fa4fb39ca1f in red_process_cursor ../../server/red-worker.c:152 + #6 0x7fa4fb39ca1f in red_process_cursor ../../server/red-worker.c:140 + +Thread T14 created by T0 here: + #0 0x7fa4fb77d685 in __interceptor_pthread_create ../../../../src/libsanitizer/asan/asan_interceptors.cpp:216 + #1 0x7fa4fb39ece5 in red_worker_run ../../server/red-worker.c:1588 + #2 0x62100002d94f (<unknown module>) + +SUMMARY: AddressSanitizer: heap-use-after-free ../qemu-6.0.1/ui/cursor.c:112 in cursor_put +Shadow bytes around the buggy address: + 0x0c46800defd0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0c46800defe0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0c46800deff0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0c46800df000: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa + 0x0c46800df010: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa +=>0x0c46800df020: fd fd[fd]fd fd fd fd fd fd fd fd fd fd fd fd fd + 0x0c46800df030: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd + 0x0c46800df040: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd + 0x0c46800df050: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd + 0x0c46800df060: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd + 0x0c46800df070: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd +Shadow byte legend (one shadow byte represents 8 application bytes): + Addressable: 00 + Partially addressable: 01 02 03 04 05 06 07 + Heap left redzone: fa + Freed heap region: fd + Stack left redzone: f1 + Stack mid redzone: f2 + Stack right redzone: f3 + Stack after return: f5 + Stack use after scope: f8 + Global redzone: f9 + Global init order: f6 + Poisoned by user: f7 + Container overflow: fc + Array cookie: ac + Intra object redzone: bb + ASan internal: fe + Left alloca redzone: ca + Right alloca redzone: cb + Shadow gap: cc +==57296==ABORTING +Steps to reproduce: +This problem cannot be stably reproduced +Additional information: +/label ~"kind::Bug" diff --git a/results/classifier/gemma3:12b/graphic/2282 b/results/classifier/gemma3:12b/graphic/2282 new file mode 100644 index 00000000..b66b3830 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2282 @@ -0,0 +1,2 @@ + +Corrupted output when using Intel Arc GPU with qemu+spice+virgl in headed mode diff --git a/results/classifier/gemma3:12b/graphic/2303 b/results/classifier/gemma3:12b/graphic/2303 new file mode 100644 index 00000000..4f56d44d --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2303 @@ -0,0 +1,72 @@ + +Multiple displays configuration supports +Additional information: +The following patch is a quick "hack" to make it work + +```patch + +From 18ad5058a18fa9f6db2c0c3058e25989908d95bb Mon Sep 17 00:00:00 2001 +From: Sergio Lopez <slp@redhat.com> +Date: Fri, 23 Jun 2023 13:15:15 +0200 +Subject: [PATCH 6/8] HACK: Set static resolutions for the VM + +--- + hw/display/virtio-gpu-base.c | 10 +++++++++- + ui/gtk.c | 6 ++++-- + 2 files changed, 13 insertions(+), 3 deletions(-) + +diff --git a/hw/display/virtio-gpu-base.c b/hw/display/virtio-gpu-base.c +index a29f191aa8..b1ccfa17b7 100644 +--- a/hw/display/virtio-gpu-base.c ++++ b/hw/display/virtio-gpu-base.c +@@ -47,6 +47,7 @@ virtio_gpu_base_fill_display_info(VirtIOGPUBase *g, + dpy_info->pmodes[i].enabled = 1; + dpy_info->pmodes[i].r.width = cpu_to_le32(g->req_state[i].width); + dpy_info->pmodes[i].r.height = cpu_to_le32(g->req_state[i].height); ++ fprintf(stderr, "display %d: %dx%d\n", i, dpy_info->pmodes[i].r.width, dpy_info->pmodes[i].r.height); + } + } + } +@@ -63,14 +64,17 @@ static void virtio_gpu_text_update(void *opaque, console_ch_t *chardata) + { + } + ++#if 0 + static void virtio_gpu_notify_event(VirtIOGPUBase *g, uint32_t event_type) + { + g->virtio_config.events_read |= event_type; + virtio_notify_config(&g->parent_obj); + } ++#endif + + static void virtio_gpu_ui_info(void *opaque, uint32_t idx, QemuUIInfo *info) + { ++#if 0 + VirtIOGPUBase *g = opaque; + + if (idx >= g->conf.max_outputs) { +@@ -94,6 +98,7 @@ static void virtio_gpu_ui_info(void *opaque, uint32_t idx, QemuUIInfo *info) + /* send event to guest */ + virtio_gpu_notify_event(g, VIRTIO_GPU_EVENT_DISPLAY); + return; ++#endif + } + + static void +@@ -186,11 +191,14 @@ virtio_gpu_base_device_realize(DeviceState *qdev, + virtio_add_queue(vdev, 16, cursor_cb); + } + +- g->enabled_output_bitmask = 1; ++ g->enabled_output_bitmask = 3; + + g->req_state[0].width = g->conf.xres; + g->req_state[0].height = g->conf.yres; + ++ g->req_state[1].width = 800; ++ g->req_state[1].height = 600; ++ + g->hw_ops = &virtio_gpu_ops; + for (i = 0; i < g->conf.max_outputs; i++) { + g->scanout[i].con = +``` diff --git a/results/classifier/gemma3:12b/graphic/2331 b/results/classifier/gemma3:12b/graphic/2331 new file mode 100644 index 00000000..dff95bed --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2331 @@ -0,0 +1,2 @@ + +(Question) There's a CLI option for the GUI option "Grab On Hover" ? diff --git a/results/classifier/gemma3:12b/graphic/2338 b/results/classifier/gemma3:12b/graphic/2338 new file mode 100644 index 00000000..04947790 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2338 @@ -0,0 +1,2 @@ + +(Feature request) Implement the "grab-on-hover=on" CLI option on the SDL frontend diff --git a/results/classifier/gemma3:12b/graphic/2348 b/results/classifier/gemma3:12b/graphic/2348 new file mode 100644 index 00000000..74034c7e --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2348 @@ -0,0 +1,8 @@ + +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/gemma3:12b/graphic/2387 b/results/classifier/gemma3:12b/graphic/2387 new file mode 100644 index 00000000..95bffe7e --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2387 @@ -0,0 +1,12 @@ + +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/gemma3:12b/graphic/2406 b/results/classifier/gemma3:12b/graphic/2406 new file mode 100644 index 00000000..a9f8d0bf --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2406 @@ -0,0 +1,8 @@ + +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/gemma3:12b/graphic/2407 b/results/classifier/gemma3:12b/graphic/2407 new file mode 100644 index 00000000..f6eaa887 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2407 @@ -0,0 +1,54 @@ + +"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/gemma3:12b/graphic/2418 b/results/classifier/gemma3:12b/graphic/2418 new file mode 100644 index 00000000..0a720593 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2418 @@ -0,0 +1,13 @@ + +[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" + +{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/gemma3:12b/graphic/2425 b/results/classifier/gemma3:12b/graphic/2425 new file mode 100644 index 00000000..889c0fb7 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2425 @@ -0,0 +1,8 @@ + +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/gemma3:12b/graphic/2447 b/results/classifier/gemma3:12b/graphic/2447 new file mode 100644 index 00000000..bbd8f351 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2447 @@ -0,0 +1,24 @@ + +With -display sdl,gl=on and 3D acceleration, the position of mouse does not show correctly +Description of problem: +Real mouse position is nearly 100 px on the left of drawn cursor. The closer the cursor to the lower right corner of the VM window, the worse (divergence becomes way bigger than 100 px). + +Split off from https://gitlab.com/qemu-project/qemu/-/issues/761 + +VM window is not necessary to be resized to reproduce this bug. If your VM desktop comes 1920x1080 originally, the bug can be reproduced from the very start. + +Smaller resolutions show this bug too, but it not so noticeable. +Steps to reproduce: +1. Download and install official QEMU 9.0 from https://qemu.weilnetz.de/w64/qemu-w64-setup-20240423.exe +2. Go to https://www.kali.org/get-kali/#kali-virtual-machines and click big QEMU 64 icon, and wait till kali-linux-2024.2-qemu-amd64.7z has been downloaded +3. Extract kali-linux-2024.2-qemu-amd64.qcow2 from kali-linux-2024.2-qemu-amd64.7z +4. Run it: `qemu-system-x86_64.exe -accel tcg -device virtio-vga-gl -display sdl,gl=on -hda C:\kali-linux-2024.2-qemu-amd64.qcow2 -usb -device usb-tablet -m 4096 -machine q35 -smp 2 -cpu Westmere` +5. Enter `kali` as user and `kali` as password when prompted +6. When the desktop is shown up, click the leftmost, upmost blue "Applications" button. Then click Settings -\> Display +7. Pick 1920x1080 as resolution and click Apply, then Keep this configuration. +8. Click Firefox Browser icon on the top panel. +9. When the browser starts working, experience how hard to use its interface, though it's fast. Real mouse position is nearly 100 px on the left of drawn cursor. The closer the cursor to the lower right corner of the VM window, the worse (divergence becomes way bigger than 100 px). +Additional information: +Run `qemu-system-x86_64.exe -accel tcg -device virtio-vga -display sdl -hda C:\kali-linux-2024.2-qemu-amd64.qcow2 -usb -device usb-tablet -m 4096 -machine q35 -smp 2 -cpu Westmere` and experience correct behavior. + +Mouse in Gtk mode works ok. OpenGL not available for Windows in GTK mode. diff --git a/results/classifier/gemma3:12b/graphic/2450 b/results/classifier/gemma3:12b/graphic/2450 new file mode 100644 index 00000000..57e62ec1 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2450 @@ -0,0 +1,18 @@ + +Intel GVT-g does not produce any output. +Description of problem: +I'm unable to see anything from screen: +{width=1201 height=956} + +By enabling VGA, I'm able to see the virtual monitor is presented in the guest OS: +{width=977 height=694} + +however it still cannot produce any output: + +{width=977 height=694} +Steps to reproduce: +1. echo "29d65a71-b9eb-45b2-aaaf-49e96f8cf753"> /sys/devices/pci0000:00/*/mdev_supported_types/i915-GVTg_V5_4/create +2. Download the romfile +3. Run the machine +Additional information: +CPU: i7-10700 diff --git a/results/classifier/gemma3:12b/graphic/2484 b/results/classifier/gemma3:12b/graphic/2484 new file mode 100644 index 00000000..c5691415 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2484 @@ -0,0 +1,2 @@ + +Confusing query-gic-capabilities output in --without-default-devices config diff --git a/results/classifier/gemma3:12b/graphic/251 b/results/classifier/gemma3:12b/graphic/251 new file mode 100644 index 00000000..66c666ad --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/251 @@ -0,0 +1,2 @@ + +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/gemma3:12b/graphic/2520 b/results/classifier/gemma3:12b/graphic/2520 new file mode 100644 index 00000000..e6ba6620 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2520 @@ -0,0 +1,12 @@ + +qemu-system-x86_64 : No Display when system wakeup from suspend +Description of problem: +Qemu display window is blank with message `Display output is not active.` +Steps to reproduce: +1. Use https://gitlab.com/berrange/tiny-vm-tools/-/blob/master/make-tiny-image.py to generate tiny-initrd.img +2. Run qemu and drop into shell +3. Put machine into S3 (echo mem > /sys/power/state) +4. Use socat to connect to QEMU monitor and wake up the machine (system_wakeup) +5. System resumes in shell, but no output in display +Additional information: +Same behavior, if I try standard ubuntu22.04.qcow2 image. Before suspend GUI is there and after wakeup from suspend blank display with message `Display output is not active.` diff --git a/results/classifier/gemma3:12b/graphic/253 b/results/classifier/gemma3:12b/graphic/253 new file mode 100644 index 00000000..1ecda77a --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/253 @@ -0,0 +1,2 @@ + +Qemu Win98 VM with KVM videocard passthrough DOS mode video is not working for most of games.. diff --git a/results/classifier/gemma3:12b/graphic/2533 b/results/classifier/gemma3:12b/graphic/2533 new file mode 100644 index 00000000..6574c04e --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2533 @@ -0,0 +1,2 @@ + +Black screen while I'm trying to emulate Android using "-machine raspi4b" diff --git a/results/classifier/gemma3:12b/graphic/2537 b/results/classifier/gemma3:12b/graphic/2537 new file mode 100644 index 00000000..63b7b88c --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2537 @@ -0,0 +1,2 @@ + +Hang in Cocoa_SetWindowSize() diff --git a/results/classifier/gemma3:12b/graphic/2539 b/results/classifier/gemma3:12b/graphic/2539 new file mode 100644 index 00000000..a494fb04 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2539 @@ -0,0 +1,2 @@ + +Crash in early_gtk_display_init() on macOS 14.6.1 diff --git a/results/classifier/gemma3:12b/graphic/254 b/results/classifier/gemma3:12b/graphic/254 new file mode 100644 index 00000000..28862521 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/254 @@ -0,0 +1,2 @@ + +Windows 98 videocard passthrough - unable to load higher resolution -Desktop, after some games crashes, without whole physical machine reset.. diff --git a/results/classifier/gemma3:12b/graphic/2559 b/results/classifier/gemma3:12b/graphic/2559 new file mode 100644 index 00000000..f0f83c79 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2559 @@ -0,0 +1,12 @@ + +macOS cocoa UI cursor position mismatch when running Windows XP under QEMU 9.1.0 +Description of problem: +QEMU 9.1.0 got hardware cursor support on macOS with the cocoa UI. When running a Windows XP guest, the windows's own cursor got a 13 pixel offset both in X and Y direction. When the "show-cursor" is off, the problem still exists, so the click target is not under the pointer of the cursor. I was using the "Red Hat QXL GPU" driver v6.1.0.10024 which was built in 2015. + +I also checked it with Linux (i have an x86-64 Alma Linux 8 installation too), this working fine when using the "-display cocoa,show-cursoor=off,zoom-to-fit=off -device virtio-vga" parameters. +Steps to reproduce: +1. Load a Windows XP with QXL drivers installed +Additional information: + + + diff --git a/results/classifier/gemma3:12b/graphic/2562 b/results/classifier/gemma3:12b/graphic/2562 new file mode 100644 index 00000000..f6e0a651 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2562 @@ -0,0 +1,53 @@ + +Booting EFI shell from GRUB using "chainloader" in Qemu with UEFI boot shows video artifacts if we have all_video, gfxterm +Steps to reproduce: +- Start Qemu in UEFI mode, i. e. `qemu-system-x86_64 -bios OVMF.fd ...` +- Qemu should load GRUB from the disk as the first thing after firmware +- GRUB should run commands `loadfont unicode; insmod all_video; terminal_output gfxterm` (note: this is perfectly ordinary sequence executed by Debian's default configuration) +- Then GRUB should execute EFI shell using `chainloader` command + +If we do all this, then instead of EFI shell we will see broken image. I. e. video output will be completely broken/mangled/damaged. But EFI shell will still respond to commands. If we type "exit", then we will exit from EFI shell back to GRUB. + +I will repeat: my configuration is not special at all. `loadfont unicode; insmod all_video; terminal_output gfxterm` are absolutely ordinary commands executed by Debian's GRUB default setup. So, essentially this bug means this: if I add EFI shell to GRUB menu in Debian, then this new menu entry will not work properly if I try to boot in Qemu in UEFI mode. + +Okay, now let me give you more detailed steps to reproduce. + +- Execute the following script on Linux x86_64 host: +```bash +#!/bin/bash +# This script was tested on Debian trixie (as on 2024-09-07) with the following packages installed: +# dosfstools grub-efi-amd64-bin qemu-system-x86 ovmf efi-shell-x64 +set -e +DIR="$(mktemp -d /tmp/qemu-bug-XXXXXX)" +truncate --size=100M "$DIR/disk" +echo ',+,' | sfdisk --label gpt "$DIR/disk" +LOOP="$(losetup --find --show --partscan --nooverlap "$DIR/disk")" +sleep 1 +mkfs.vfat "${LOOP}p1" +mkdir "$DIR/root" +mount "${LOOP}p1" "$DIR/root" +losetup --detach "$LOOP" +mkdir -p "$DIR/root/EFI/boot" "$DIR/root/boot/grub/fonts" +grub-mkimage --format=x86_64-efi --output="$DIR/root/EFI/boot/bootx64.efi" --prefix=/boot/grub part_gpt fat +cp -r /usr/lib/grub/x86_64-efi "$DIR/root/boot/grub" +cp /usr/share/efi-shell-x64/shellx64.efi "$DIR/root/boot" +cp /usr/share/grub/unicode.pf2 "$DIR/root/boot/grub/fonts" +cat << "EOF" > "$DIR/root/boot/grub/grub.cfg" +loadfont unicode +insmod all_video +terminal_output gfxterm +menuentry "EFI shell" { + chainloader /boot/shellx64.efi +} +EOF +umount "$DIR/root" +qemu-system-x86_64 -m 2048 -bios OVMF.fd -drive file="$DIR/disk",format=raw +``` +- When you see Qemu window, choose "EFI shell" menu entry in GRUB menu +- You will immediately see damaged video output instead of proper EFI shell + +This bug doesn't reproduce on real hardware, i. e. without Qemu!!! I. e. this is Qemu bug. Qemu task is to duplicate real hardware behaviour. On real hardware there is no this bug, so Qemu should not have it, either. + +Note: if I remove `loadfont unicode; insmod all_video; terminal_output gfxterm`, then the bug disappears. + +Also note: if I replace `all_video` with `efi_gop`, then the bug disappears, too. So, workaround is to use `efi_gop` instead of `all_video` in UEFI mode. But I still believe the bug is in Qemu, because `all_video` doesn't cause any problems on real hardware, so Qemu should work, too. diff --git a/results/classifier/gemma3:12b/graphic/2563 b/results/classifier/gemma3:12b/graphic/2563 new file mode 100644 index 00000000..4fe7bc74 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2563 @@ -0,0 +1,211 @@ + +W64 build referenced to by https://www.qemu.org/download/#windows fails to run with GTK and 3D but cross-build for W64 works ok with GTK and 3d +Description of problem: +Qemu W64 build referenced to by https://www.qemu.org/download/#windows (https://qemu.weilnetz.de/w64/qemu-w64-setup-20240903.exe) crashes with aforementioned command line, leaving 0xc0000005 exception in Windows event log. But a custom cross-compiled build at least boots into default qemu BIOS. See steps below to cross-compile qemu with GTK + OpenGL +VirGL support. +Steps to reproduce: +1. `wget https://qemu.weilnetz.de/w64/qemu-w64-setup-20240903.exe`, install it, run `qemu-system-x86_64.exe -display gtk,gl=on -device virtio-vga-gl` and watch immediate qemu crash. + 2. Prepare cross-compilation build of qemu 9.1.0 using following steps: + 3. Download official Fedora workstation 40 x86_64 ISO and install it to a virtual disk and boot that disk. + 4. `wget https://download.qemu.org/qemu-9.1.0.tar.xz`\ + `tar xvJf qemu-9.1.0.tar.xz`\ + `cd qemu-9.1.0` + 5. Run `sudo yum install git meson ninja-build python3-sphinx python3-sphinx_rtd_theme gcc mingw64-gcc mingw64-glib2 mingw64-pkg-config mingw64-pixman mingw64-gtk3 mingw64-SDL2 mingw64-libepoxy mingw64-librsvg2` in virtual Fedora. `mingw64-librsvg2` is optional, see step #14 + 6. `git clone https://gitlab.freedesktop.org/slirp/libslirp.git` (e61dbd45 as of 04 August 2024) `git clone https://gitlab.freedesktop.org/virgl/virglrenderer.git` (3d82ed86 as of 03 September 2024) + 7. create file x86_64-w64-mingw32.txt in qemu-9.1.0 directory with the content as follows:\ + `[binaries]`\ + `c = '/usr/bin/x86_64-w64-mingw32-gcc'`\ + `cpp = '/usr/bin/x86_64-w64-mingw32-g++'`\ + `ar = '/usr/bin/x86_64-w64-mingw32-ar'`\ + `strip = '/usr/bin/x86_64-w64-mingw32-strip'`\ + `pkg-config = '/usr/bin/x86_64-w64-mingw32-pkg-config'`\ + `exe_wrapper = 'wine'`\ + \ + `[host_machine]`\ + `system = 'windows'`\ + `cpu_family = 'x86_64'`\ + `cpu = 'i686'`\ + `endian = 'little'` + 8. Make a directory to which QEMU dependencies will be installed after compilation from git: `export CROSS_QEMU_DEPS="/home/cross-qemu-deps"`\ + `sudo mkdir -p $CROSS_QEMU_DEPS` + 9. Install libslirp so that future qemu binaries can have internet access via -netdev user\ + ` cd libslirp`\ + \ + ` meson setup --cross-file ../x86_64-w64-mingw32.txt --prefix "$CROSS_QEMU_DEPS" build-mingw/`\ + ` meson compile -C build-mingw`\ + ` cd build-mingw`\ + ` ninja install` +10. Install virgl to have 3D hardware acceleration\ + ` cd ../../`\ + ` cd virglrenderer`\ + \ + ` meson setup --cross-file ../x86_64-w64-mingw32.txt --prefix "$CROSS_QEMU_DEPS" build-mingw/`\ + ` meson compile -C build-mingw`\ + ` cd build-mingw`\ + ` ninja install` +11. Set three environment variables for cross-compilation: + + `sudo find / -type f -name '*.pc'` and make sure all mingw \*.pc files live in `/usr/x86_64-w64-mingw32/sys-root/mingw/share/pkgconfig/` and `/usr/x86_64-w64-mingw32/sys-root/mingw/lib/pkgconfig/`. Correct these paths in PKG_CONFIG_PATH if you see they were altered by mingw or package contributors.\ + \ + `export PKG_CONFIG_PATH="/usr/x86_64-w64-mingw32/sys-root/mingw/share/pkgconfig/:/usr/x86_64-w64-mingw32/sys-root/mingw/lib/pkgconfig/:$PKG_CONFIG_PATH"` + + \ + `export PKG_CONFIG_LIBDIR="${CROSS_QEMU_DEPS}/lib/pkgconfig/:$PKG_CONFIG_LIBDIR"` + + \ + `export PKG_CONFIG_SYSROOT_DIR=""` +12. <span dir="">Configure Qemu makefile:</span> + + `cd ../../` + + `./configure --cross-prefix=x86_64-w64-mingw32- --enable-gtk --enable-sdl --enable-opengl --enable-virglrenderer --enable-slirp --enable-debug` + + and make sure you see this in the output of configure: + + `Compilation`\ + `host CPU : x86_64`\ + `host endianness : little`\ + `C compiler : x86_64-w64-mingw32-gcc -m64`\ + `Host C compiler : cc` + + and this one: + + `Checking whether type "struct virgl_renderer_resource_info_ext" has member "d3d_tex2d" with dependency virglrenderer: YES` +13. Cross-compile qemu: `` make -j`nproc` `` +14. \[optional step to get rid of "**Gtk-WARNING \*\*: 19:22:02.461: Could not load a pixbuf**"\] + + **Copy gdk-pixbuf-query-loaders.exe** from `/usr/x86_64-w64-mingw32/sys-root/mingw/bin/`\ + to\ + `./qemu-9.1.0/build/qemu-bundle/qemu`**\ + \ + `mkdir -p ./qemu-9.1.0/build/qemu-bundle/qemu/lib`\ + \ + copy recursively /usr/x86_64-w64-mingw32/sys-root/mingw/lib/gdk-pixbuf-2.0** to `./qemu-9.1.0/build/qemu-bundle/qemu/lib` + + **`mkdir -p ./qemu-9.1.0/build/qemu-bundle/qemu/share`**\ + \ + **copy recursively /usr/x86_64-w64-mingw32/sys-root/mingw/share/icons** to `./qemu-9.1.0/build/qemu-bundle/qemu/share` + + **copy recursively /usr/x86_64-w64-mingw32/sys-root/mingw/share/themes** to `./qemu-9.1.0/build/qemu-bundle/qemu/share` + + Run `gdk-pixbuf-query-loaders.exe --update-cache` on host right before step 17. +15. Copy all dll files from + + `/usr/x86_64-w64-mingw32/sys-root/mingw/bin/`\ + to\ + `./qemu-9.1.0/build/qemu-bundle/`**`qemu`** + + Copy libvirglrenderer-1.dll and libslirp-0.dll from `$CROSS_QEMU_DEPS` directory exported above to + + `./qemu-9.1.0/build/qemu-bundle/`**`qemu`** +16. Copy this **`qemu`** folder from the previous step to Windows machine using ssh or whatever else\ + E.g. by doing\ + ` sudo yum install openssh-server`\ + ` sudo systemctl start sshd`\ + ` sudo systemctl status sshd`\ + on guest OS (provided you have launched guest Fedora qemu with `-nic user,hostfwd=tcp::8888-:22` command line parameter for ssh) + + and then + + `scp.exe -P 8888 -r virtual_machine_user@127.0.0.1:/home/virtual_machine_user/qemu-9.1.0/build/qemu-bundle/qemu C:\downloads\qemu`\ + on host OS +17. `cd` to that `qemu` folder and run `qemu-system-x86_64.exe -display gtk,gl=on -device virtio-vga-gl` and watch qemu booting into BIOS. + +<details> +<summary>Previous version</summary> + +1\. \`wget https://qemu.weilnetz.de/w64/qemu-w64-setup-20240903.exe\\\\\\\\\\\\\\\`, install it, run \`qemu-system-x86_64.exe -display gtk,gl=on -device virtio-vga-gl\` and watch immediate qemu crash. 2. Prepare cross-compilation build of qemu 9.1.0 using following steps: 3. Download official Fedora workstation 40 x86_64 ISO and install it to a virtual disk and boot that disk. 4. Run \`sudo yum install meson ninja-build python3-sphinx python3-sphinx_rtd_theme gcc mingw64-gcc mingw64-glib2 mingw64-pkg-config mingw64-pixman mingw64-gtk3 mingw64-SDL2 mingw64-libepoxy\` in virtual Fedora. 5. \`wget https://download.qemu.org/qemu-9.1.0.tar.xz\\\\\\\\\\\\\\\\\\\\\\\` + +``` +`tar xvJf qemu-9.1.0.tar.xz`\ +`cd qemu-9.1.0` +``` + + 6. `git clone https://gitlab.freedesktop.org/virgl/virglrenderer.git` (3d82ed86 as of 03 September 2024)\ + `cd virglrenderer` + 7. create file x86_64-w64-mingw32.txt in virglrenderer directory with the content as follows:\ + `[binaries]`\ + `c = '/usr/bin/x86_64-w64-mingw32-gcc'`\ + `cpp = '/usr/bin/x86_64-w64-mingw32-g++'`\ + `ar = '/usr/bin/x86_64-w64-mingw32-ar'`\ + `strip = '/usr/bin/x86_64-w64-mingw32-strip'`\ + `pkg-config = '/usr/bin/x86_64-w64-mingw32-pkg-config'`\ + `exe_wrapper = 'wine'`\ + \ + `[host_machine]`\ + `system = 'windows'`\ + `cpu_family = 'x86_64'`\ + `cpu = 'i686'`\ + `endian = 'little'` + 8. Run `meson setup --cross-file x86_64-w64-mingw32.txt build-mingw`\ + `meson compile -C build-mingw`\ + `cd build-mingw`\ + `ninja install` + 9. Set pkgconfig for virglrenderer: `export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/home/your_user/virglrenderer/build-mingw/meson-private`\ + (replace /home/your_user/virglrenderer/build-mingw/meson-private with path containing virglrenderer.pc file from output of `sudo find / -type f -name 'virglrenderer.pc'` command) +10. Run confugure: \ + `cd ../../`\ + `./configure --cross-prefix=x86_64-w64-mingw32- --enable-gtk --enable-sdl --enable-opengl --enable-virglrenderer --enable-debug`\ + \ + and make sure you see this in the output of configure:\ + `Compilation`\ + `host CPU : x86_64`\ + `host endianness : little`\ + `C compiler : x86_64-w64-mingw32-gcc -m64`\ + `Host C compiler : cc`\ + \ + run\ + `export PKG_CONFIG_PATH="/usr/local/lib/pkgconfig"` +11. Run this command to see where x86_64-w64-mingw32-pkg-config will look for virglrenderer.h: + + `/usr/bin/x86_64-w64-mingw32-pkg-config --cflags virglrenderer`\ + \> -I/usr/x86_64-w64-mingw32/sys-root/mingw/usr/local/include/virgl (possible result) +12. Copy folder containing virglrenderer.h to that one to satisfy mingw expectations: + + `sudo mkdir -p /usr/x86_64-w64-mingw32/sys-root/mingw/usr/local/include/`\ + `sudo cp -r /usr/local/include/virgl /usr/x86_64-w64-mingw32/sys-root/mingw/usr/local/include/` +13. Run search `sudo find / -type f -name 'libvirglrenderer.dll.a'` and satisfy mingw's expectation for libvirglrenderer.dll.a:\ + `sudo mkdir -p /usr/x86_64-w64-mingw32/sys-root/usr/local/lib/`\ + `sudo ln -s /usr/local/lib/libvirglrenderer.dll.a /usr/x86_64-w64-mingw32/sys-root/usr/local/lib/libvirglrenderer.dll.a` +14. Cross-compile qemu: \ + `make -j4`\ + \* if you see "/usr/lib/gcc/x86_64-w64-mingw32/14.1.1/../../../../x86_64-w64-mingw32/bin/ld: cannot find -lvirglrenderer: No such file or directory" then most likely Qemu's makefile was confused by libvirglrenderer.dll.a path; check `/usr/x86_64-w64-mingw32/bin/ld -lvirglrenderer --verbose` output to find out path of libvirglrenderer.dll.a file it cannot find +15. copy all dll files from \ + /usr/x86_64-w64-mingw32/sys-root/mingw/bin/\ + to\ + ./qemu-9.1.0-rc4/**build** +16. copy libvirglrenderer-1.dll from /usr/local/bin to\ + ./qemu-9.1.0-rc4/**build** +17. copy this **build** folder to Windows machine using ssh or whatever else +18. `cd` to that **build** folder and run `qemu-system-x86_64.exe -display gtk,gl=on -device virtio-vga-gl` and watch qemu booting into BIOS. + +</details> +Additional information: +P.S. Cross-compilation on Fedora build machine for Windows target usually requires installing pre-compiled binary packages along with libslirp and libvirglrenderer from git. Almost all of them include \*.pc files (pkg-config files) needed by mingw to find .h headers and .dll.a library files. Normally, it's not necessarry to add extra include paths using something like CFLAGS="-I/include_headers_path" or LDFLAGS="-L/path_to_dll_a_lib". The commands from above must produce a fully working windows build. But, just in case someone damages packages in Fedora repository or libslirp or virglrenderer in their git, here are some ideas how to fix broken links between files: + +- First, make sure you have enumerated all .pc folders from Fedora repository packages in PKG_CONFIG_PATH= and all .pc folders built from source in PKG_CONFIG_LIBDIR=, as it was shown at Step 11. If you see a message saying something like "virglrenderer.h not found", run this command to see where x86_64-w64-mingw32-pkg-config will look for virglrenderer.h: `/usr/bin/x86_64-w64-mingw32-pkg-config --cflags virglrenderer` + +> \-I/usr/x86_64-w64-mingw32/sys-root/mingw/usr/local/include/virgl (possible result) + +- Then copy folder containing virglrenderer.h (for example, /usr/local/include/virgl) to that one to satisfy mingw expectations: + + `sudo mkdir -p /usr/x86_64-w64-mingw32/sys-root/mingw/usr/local/include/` `sudo cp -r /usr/local/include/virgl /usr/x86_64-w64-mingw32/sys-root/mingw/usr/local/include/` +- If you see "/usr/lib/gcc/x86_64-w64-mingw32/14.1.1/../../../../x86_64-w64-mingw32/bin/ld: cannot find -lvirglrenderer: No such file or directory" then most likely Qemu's makefile was confused by libvirglrenderer.dll.a path; check `/usr/x86_64-w64-mingw32/bin/ld -lvirglrenderer --verbose` output to find out path of libvirglrenderer.dll.a file it cannot find +- For example, `/usr/x86_64-w64-mingw32/bin/ld -lvirglrenderer --verbose` shows that build script tries to find .dll.a file under /usr/x86_64-w64-mingw32/sys-root/usr/local/lib/libvirglrenderer.dll.a and `find / -type f -name 'libvirglrenderer.dll.a'` shows that file is in /usr/local/lib/libvirglrenderer.dll.a +- Then satisfy mingw's expectation for libvirglrenderer.dll.a: `sudo mkdir -p /usr/x86_64-w64-mingw32/sys-root/usr/local/lib/`\ + `sudo ln -s /usr/local/lib/libvirglrenderer.dll.a /usr/x86_64-w64-mingw32/sys-root/usr/local/lib/libvirglrenderer.dll.a` + +Upd: I was able to refine instructions on how to cross-compile Qemu's dependencies thanks to these references: + +https://gitlab.freedesktop.org/pkg-config/pkg-config/-/issues/52: + +> PKG_CONFIG_SYSROOT_DIR blindly prepend the sysroot to all paths. I made a MR that add PKG_CONFIG_SYSROOT_MAP to get smarter mapping from pcfiledir-\>sysroot. !7. I generally discontinued the use of PKG_CONFIG_SYSROOT_DIR and switched to merely using PKG_CONFIG_LIBDIR. That way I got absolute paths everyehere which at least was consistent and could be postprocessed if needed. + +https://forum.qt.io/topic/88946/qt5-10-1-cross-compile-configure-errors/9: + +> WARNING: Disabling pkg-config since PKG_CONFIG_LIBDIR is not set and the host's .pc files would be used (even if you set PKG_CONFIG_PATH). Set this variable to the directory that contains target .pc files for pkg-config to function correctly when cross-compiling or use -pkg-config to override this test. + +https://cmake.org/pipermail/cmake/2008-November/025050.html: + +> The situation is as follows: PKG_CONFIG_PATH is searched before PKG_CONFIG_LIBDIR for the desired \*.pc file. (The man page doesn't say which is searched first, but my tests reveal that is the order at least for the present version of pkg-config.) Cross-compiling users should avoid using native paths in PKG_CONFIG_PATH and PKG_CONFIG_LIBDIR. Furthermore, cross-compiling users should always specify PKG_CONFIG_LIBDIR (with or without PKG_CONFIG_PATH) since use of PKG_CONFIG_LIBDIR supresses appending default native paths to whatever is specified in PKG_CONFIG_PATH and PKG_CONFIG_LIBDIR. +> +> In sum, for cross-compilation purposes you should always use PKG_CONFIG_LIBDIR (with or without PKG_CONFIG_PATH) and make sure there are no native paths in it (or in PKG_CONFIG_PATH). If you follow those rules you should get a good cross-compilation result, otherwise not. diff --git a/results/classifier/gemma3:12b/graphic/2565 b/results/classifier/gemma3:12b/graphic/2565 new file mode 100644 index 00000000..d4032aed --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2565 @@ -0,0 +1,14 @@ + +Bisected: 176e3783f2ab14 results in a heavy performance regression with the SDL interface +Description of problem: +With the patch 176e3783f2ab14 a significant 3D performance regression was introduced when using the SDL gui and VirGL. Before the patch glxgears runs at about 4000 FPS on my machine, with the patch this drops to about 150 FPS, and if one moves the mouse the reported frame rate drops even more. +Steps to reproduce: +1. Run the qemu like given above with a current Debian-SID guest +2. Start glxgears from a terminal +3. Move the mouse continuously to see the extra drop in frame rate +Additional information: +* (Guest) OpenGL Renderer string: virgl (AMD Radeon RX 6700 XT (radeonsi, navi22, LLVM 18.1.8 ...) +* Reverting the commit 176e3783f2ab14 fixes the problem on SDL +* I don't think the host kernel version is an issue here (namely the KVM patches that are required to run Venus on discrete graphics cards) +* I've seen a similar issue when using GTK, but other that with SDL it's already present in version 7.2.11 (the one I used as a "good" base when I was bisecting the regression) - so I was not able to bisect yet. +* I've looked around in the code and I'm aware the that commit *shouldn't* have the impact it seems to have. I can only assume that there is some unexpected side effect when creating the otherwise unused renderer. diff --git a/results/classifier/gemma3:12b/graphic/2575 b/results/classifier/gemma3:12b/graphic/2575 new file mode 100644 index 00000000..f20512d4 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2575 @@ -0,0 +1,2 @@ + +cocoa: Remove deprecated CVDisplayLinkCreateWithCGDisplay() calls diff --git a/results/classifier/gemma3:12b/graphic/262 b/results/classifier/gemma3:12b/graphic/262 new file mode 100644 index 00000000..31479eeb --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/262 @@ -0,0 +1,2 @@ + +Broken scaling with gtk,gl=on on a hidpi display diff --git a/results/classifier/gemma3:12b/graphic/2637 b/results/classifier/gemma3:12b/graphic/2637 new file mode 100644 index 00000000..0cadaa5b --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2637 @@ -0,0 +1,54 @@ + +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: + +{width=764 height=467} +second time: + +{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/gemma3:12b/graphic/2640 b/results/classifier/gemma3:12b/graphic/2640 new file mode 100644 index 00000000..80ca2d23 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2640 @@ -0,0 +1,2 @@ + +QEMU twice logging when use SDL. diff --git a/results/classifier/gemma3:12b/graphic/2643 b/results/classifier/gemma3:12b/graphic/2643 new file mode 100644 index 00000000..afaeb93d --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2643 @@ -0,0 +1,53 @@ + +gtk initialization failed +Description of problem: +I compiled latest qemu version from sources with gtk enabled like below but still there is an issue of gtk initialization failed + ``` + ./configure --enable-gtk --enable-slirp + ``` +Steps to reproduce: +1. building qemu from sources or installing from packages results with gtk initialization failed message +Additional information: +``` + # virt-host-validate + QEMU: Checking for hardware virtualization : PASS + QEMU: Checking if device /dev/kvm exists : PASS + QEMU: Checking if device /dev/kvm is accessible : PASS + QEMU: Checking if device /dev/vhost-net exists : PASS + QEMU: Checking if device /dev/net/tun exists : PASS + QEMU: Checking for cgroup 'cpu' controller support : PASS + QEMU: Checking for cgroup 'cpuacct' controller support : PASS + QEMU: Checking for cgroup 'cpuset' controller support : PASS + QEMU: Checking for cgroup 'memory' controller support : PASS + QEMU: Checking for cgroup 'devices' controller support : PASS + QEMU: Checking for cgroup 'blkio' controller support : PASS + QEMU: Checking for device assignment IOMMU support : WARN (No ACPI IVRS table found, IOMMU either disabled in BIOS or not supported by this hardware platform) + QEMU: Checking for secure guest support : WARN (Unknown if this platform has Secure Guest support) + LXC: Checking for Linux >= 2.6.26 : PASS + LXC: Checking for namespace ipc : PASS + LXC: Checking for namespace mnt : PASS + LXC: Checking for namespace pid : PASS + LXC: Checking for namespace uts : PASS + LXC: Checking for namespace net : PASS + LXC: Checking for namespace user : PASS + LXC: Checking for cgroup 'cpu' controller support : PASS + LXC: Checking for cgroup 'cpuacct' controller support : PASS + LXC: Checking for cgroup 'cpuset' controller support : PASS + LXC: Checking for cgroup 'memory' controller support : PASS + LXC: Checking for cgroup 'devices' controller support : PASS + LXC: Checking for cgroup 'freezer' controller support : FAIL (Enable 'freezer' in kernel Kconfig file or mount/enable cgroup controller in your system) + LXC: Checking for cgroup 'blkio' controller support : PASS + LXC: Checking if device /sys/fs/fuse/connections exists : PASS + ``` + ``` +# apt list --installed | grep gtk +gir1.2-gtk-3.0/noble-updates,now 3.24.41-4ubuntu1.2 amd64 [installed,automatic] +gtk-update-icon-cache/noble-updates,now 3.24.41-4ubuntu1.2 amd64 [installed,automatic] +libavahi-ui-gtk3-0/noble,now 0.8-13ubuntu6 amd64 [installed,automatic] +libavahi-ui-gtk3-dev/noble,now 0.8-13ubuntu6 amd64 [installed] +libdecor-0-plugin-1-gtk/noble,now 0.2.2-1build2 amd64 [installed,automatic] +libgtk-3-0t64/noble-updates,now 3.24.41-4ubuntu1.2 amd64 [installed,automatic] +libgtk-3-bin/noble-updates,now 3.24.41-4ubuntu1.2 amd64 [installed,automatic] +libgtk-3-common/noble-updates,now 3.24.41-4ubuntu1.2 all [installed,automatic] +libgtk-3-dev/noble-updates,now 3.24.41-4ubuntu1.2 amd64 [installed,automatic] + ``` diff --git a/results/classifier/gemma3:12b/graphic/2667 b/results/classifier/gemma3:12b/graphic/2667 new file mode 100644 index 00000000..f678e984 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2667 @@ -0,0 +1,213 @@ + +Heavy graphic glitches when using Virtio with 3D acceleration +Description of problem: +Virtio with 3D acceleration enabled under "Video" and the corresponding OpenGL activated under "Display" with Spice leads to heavy artifacts in the graphical console. + +This error has been observed on Arch Linux with Intel Meteor Lake CPU (Intel Arc Graphics iGPU) as well as on OpenSuse Tumbleweed with Intel Kaby Lake CPU (Intel HD 630 iGPU) +Steps to reproduce: +1. Enable Virtio Graphics with 3D acceleration under "Video". +2. Activate the corresponding OpenGL under "Spice". +3. Start the VM and open the graphical console. +Additional information: + +(virtio without acceleration enabled) + + +(Same VM, same settings, but with 3D acceleration and OpenGL enabled) + + +(Same issue on a fresh install of OpenSuse Tumbleweed on a system that is in no way linked to the first one) + +``` +<domain type='kvm'> + <name>debian12</name> + <uuid>1d39d86a-b341-47bb-9847-4c78da9df863</uuid> + <metadata> + <libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0"> + <libosinfo:os id="http://debian.org/debian/12"/> + </libosinfo:libosinfo> + </metadata> + <memory unit='KiB'>4194304</memory> + <currentMemory unit='KiB'>4194304</currentMemory> + <vcpu placement='static'>4</vcpu> + <os firmware='efi'> + <type arch='x86_64' machine='pc-q35-9.1'>hvm</type> + <firmware> + <feature enabled='no' name='enrolled-keys'/> + <feature enabled='no' name='secure-boot'/> + </firmware> + <loader readonly='yes' type='pflash'>/usr/share/edk2/x64/OVMF_CODE.4m.fd</loader> + <nvram template='/usr/share/edk2/x64/OVMF_VARS.4m.fd'>/var/lib/libvirt/qemu/nvram/debian12_VARS.fd</nvram> + <boot dev='hd'/> + </os> + <features> + <acpi/> + <apic/> + <vmport state='off'/> + </features> + <cpu mode='host-passthrough' check='none' migratable='on'/> + <clock offset='utc'> + <timer name='rtc' tickpolicy='catchup'/> + <timer name='pit' tickpolicy='delay'/> + <timer name='hpet' present='no'/> + </clock> + <on_poweroff>destroy</on_poweroff> + <on_reboot>restart</on_reboot> + <on_crash>destroy</on_crash> + <pm> + <suspend-to-mem enabled='no'/> + <suspend-to-disk enabled='no'/> + </pm> + <devices> + <emulator>/usr/bin/qemu-system-x86_64</emulator> + <disk type='file' device='disk'> + <driver name='qemu' type='qcow2' discard='unmap'/> + <source file='/var/lib/libvirt/images/debian12.qcow2'/> + <target dev='vda' bus='virtio'/> + <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> + </disk> + <disk type='file' device='cdrom'> + <driver name='qemu' type='raw'/> + <target dev='sda' bus='sata'/> + <readonly/> + <address type='drive' controller='0' bus='0' target='0' unit='0'/> + </disk> + <controller type='usb' index='0' model='qemu-xhci' ports='15'> + <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> + </controller> + <controller type='pci' index='0' model='pcie-root'/> + <controller type='pci' index='1' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='1' port='0x10'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> + </controller> + <controller type='pci' index='2' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='2' port='0x11'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> + </controller> + <controller type='pci' index='3' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='3' port='0x12'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> + </controller> + <controller type='pci' index='4' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='4' port='0x13'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> + </controller> + <controller type='pci' index='5' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='5' port='0x14'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> + </controller> + <controller type='pci' index='6' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='6' port='0x15'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> + </controller> + <controller type='pci' index='7' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='7' port='0x16'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x6'/> + </controller> + <controller type='pci' index='8' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='8' port='0x17'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x7'/> + </controller> + <controller type='pci' index='9' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='9' port='0x18'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0' multifunction='on'/> + </controller> + <controller type='pci' index='10' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='10' port='0x19'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x1'/> + </controller> + <controller type='pci' index='11' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='11' port='0x1a'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x2'/> + </controller> + <controller type='pci' index='12' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='12' port='0x1b'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x3'/> + </controller> + <controller type='pci' index='13' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='13' port='0x1c'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x4'/> + </controller> + <controller type='pci' index='14' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='14' port='0x1d'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x5'/> + </controller> + <controller type='sata' index='0'> + <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> + </controller> + <controller type='virtio-serial' index='0'> + <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> + </controller> + <interface type='network'> + <mac address='52:54:00:d6:22:67'/> + <source network='default'/> + <model type='virtio'/> + <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> + </interface> + <serial type='pty'> + <target type='isa-serial' port='0'> + <model name='isa-serial'/> + </target> + </serial> + <console type='pty'> + <target type='serial' port='0'/> + </console> + <channel type='unix'> + <target type='virtio' name='org.qemu.guest_agent.0'/> + <address type='virtio-serial' controller='0' bus='0' port='1'/> + </channel> + <channel type='spicevmc'> + <target type='virtio' name='com.redhat.spice.0'/> + <address type='virtio-serial' controller='0' bus='0' port='2'/> + </channel> + <input type='tablet' bus='usb'> + <address type='usb' bus='0' port='1'/> + </input> + <input type='mouse' bus='ps2'/> + <input type='keyboard' bus='ps2'/> + <graphics type='spice'> + <listen type='none'/> + <image compression='off'/> + <gl enable='yes'/> + </graphics> + <sound model='ich9'> + <address type='pci' domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/> + </sound> + <audio id='1' type='spice'/> + <video> + <model type='virtio' heads='1' primary='yes'> + <acceleration accel3d='yes'/> + </model> + <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> + </video> + <redirdev bus='usb' type='spicevmc'> + <address type='usb' bus='0' port='2'/> + </redirdev> + <redirdev bus='usb' type='spicevmc'> + <address type='usb' bus='0' port='3'/> + </redirdev> + <watchdog model='itco' action='reset'/> + <memballoon model='virtio'> + <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> + </memballoon> + <rng model='virtio'> + <backend model='random'>/dev/urandom</backend> + <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> + </rng> + </devices> +</domain> +``` diff --git a/results/classifier/gemma3:12b/graphic/2670 b/results/classifier/gemma3:12b/graphic/2670 new file mode 100644 index 00000000..78e2c191 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2670 @@ -0,0 +1,45 @@ + +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/gemma3:12b/graphic/2674 b/results/classifier/gemma3:12b/graphic/2674 new file mode 100644 index 00000000..518ec9fe --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2674 @@ -0,0 +1,25 @@ + +NextSTEP 3.3 for Sparc graphical glitches +Description of problem: +It installs/boot by using complex boot syntax and taskset -c 0 under Linux + +see end of https://gitlab.com/qemu-project/qemu/-/issues/2620#note_2207999780 + +But after it installs I see some gfx corruption +Steps to reproduce: +1. install NEXTSTEP 3.3 for RISC computers +2. Boot to desktop (may need ctrl-c to skip some services at startup) +3. Select Info and watch for Workspace Manager info window to appear. +4. Move this window to the right - it corrupts! +Additional information: +Bug also exist if I boot qemu with -g 1024x768x24 + +Moving window vertically (up/down) does not corrupt it +Moving any window around corrupt it. + +Resizing and scrolling inside say Terminal emulators work. + +There was 86Box issue around one FPU instruction that looked a bit like this, +is there way to check fpu emulation? + + diff --git a/results/classifier/gemma3:12b/graphic/2676 b/results/classifier/gemma3:12b/graphic/2676 new file mode 100644 index 00000000..ab86f304 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2676 @@ -0,0 +1,8 @@ + +GTK+ UI has serious problems on macOS hosts +Description of problem: +The GTK+ UI simply does not work on macOS at this stage. One major reason is that there does not appear to be any regular polling of the (macOS) UI event loop. The Cocoa back-end for GTK [sets a custom event polling function in GLib's event handler](https://gitlab.gnome.org/GNOME/gtk/-/blob/main/gdk/macos/gdkmacoseventsource.c?ref_type=heads#L1089) but Qemu never actually calls GLib/GTK's event polling. + +Thanks to @bonzini for discovering this as part of a [discussion on a patch generalising runloop event handling on macOS](https://patchew.org/QEMU/20241113142343.40832-1-phil@philjordan.eu/20241113142343.40832-2-phil@philjordan.eu/#CABgObfat1JwiBFNKHK6wwMkW5kgaqZfKJa=rW._5F9VvEdMWJR75A@mail.gmail.com). + +There is also a reasonable chance that QEMU might not reliably call GTK+ functions from the main thread (thread 0), which causes problems when GTK then calls through to the native Cocoa APIs which must be called from thread 0. diff --git a/results/classifier/gemma3:12b/graphic/2679 b/results/classifier/gemma3:12b/graphic/2679 new file mode 100644 index 00000000..5e3fc7d9 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2679 @@ -0,0 +1,2 @@ + +TCX emulation missing 1152x900 mode diff --git a/results/classifier/gemma3:12b/graphic/2680 b/results/classifier/gemma3:12b/graphic/2680 new file mode 100644 index 00000000..21241fce --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2680 @@ -0,0 +1,15 @@ + +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/gemma3:12b/graphic/2706 b/results/classifier/gemma3:12b/graphic/2706 new file mode 100644 index 00000000..e5098048 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2706 @@ -0,0 +1,2 @@ + +MigrationCapability "dirty-bitmaps off" diff --git a/results/classifier/gemma3:12b/graphic/2724 b/results/classifier/gemma3:12b/graphic/2724 new file mode 100644 index 00000000..1ae5de4f --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2724 @@ -0,0 +1,9 @@ + +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/gemma3:12b/graphic/2728 b/results/classifier/gemma3:12b/graphic/2728 new file mode 100644 index 00000000..7d0d99ac --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2728 @@ -0,0 +1,16 @@ + +QEMU/Virt-Manager + QXL 4k Resolution + Win 10 and Win 11 Guest freeze +Description of problem: +I use two 4k displays in my VM with 150% display scaling. After a random amount of time the screen locks up. It can lock up before i can log in or it can wait a few minutes into using it before it stops responding. It still pings but is unresponsive via the display. I've tried several different builds of the guest drivers but that did not work, the only solution has been to revert to QEMU v9.0.2-1. +Steps to reproduce: +1.Create new x86 VM using QXl video, Install Windows 10 or Windows 11 and latest guest drivers from spice and fedora +2.Open with virt viewer and resize both screens to 3840 x 2160 or use autosize +3.Set display scaling to 150% +4.Lockup occurs at some point after that but not more than 5 minutes. +Additional information: +There seems to be a similar bug here:https://gitlab.com/qemu-project/qemu/-/issues/1628#note_214460662 +also a debian forum post here: https://forums.debian.net/viewtopic.php?t=160631 +QEMU v9.0.2-1 does not have this problem, eliminating the guest drivers as a culprit + + +/label ~"kind::Bug" diff --git a/results/classifier/gemma3:12b/graphic/2757 b/results/classifier/gemma3:12b/graphic/2757 new file mode 100644 index 00000000..1bde983b --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2757 @@ -0,0 +1,2 @@ + +EGL can't handle multi plane textures diff --git a/results/classifier/gemma3:12b/graphic/280 b/results/classifier/gemma3:12b/graphic/280 new file mode 100644 index 00000000..e4ffdd89 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/280 @@ -0,0 +1,2 @@ + +(ARM64) qemu-x86_64+schroot(Debian bullseye) can't run chrome and can't load HTML diff --git a/results/classifier/gemma3:12b/graphic/2875 b/results/classifier/gemma3:12b/graphic/2875 new file mode 100644 index 00000000..5b816bc2 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2875 @@ -0,0 +1,30 @@ + +[Virtio-GPU Venus] QEMU Virtio-GPU Venus with Lavapipe ICD shows corrupted graphical output along with error prints +Description of problem: +QEMU Virtio-GPU Venus with Lavapipe ICD shows corrupted graphical output (screenshots attached ahead) along with the following error prints, as guest_errors are enabled in QEMU command line `-d guest_errors`: +``` +VK_DRIVER_FILES=/usr/share/vulkan/icd.d/lvp_icd.x86_64.json ./qemu-system-x86_64 -enable-kvm -M q35 -smp 4 -m 4G -cpu host -net nic,model=virtio -net user,hostfwd=tcp::2222-:22 -d guest_errors -device virtio-vga-gl,hostmem=4G,blob=true,venus=true -vga none -display gtk,gl=on,show-cursor=on -usb -device usb-tablet -object memory-backend-memfd,id=mem1,size=4G -machine memory-backend=mem1 -hda ubuntu-2504.qcow2 +virtio_gpu_virgl_unmap_resource_blob: failed to unmap virgl resource: Invalid argument +virtio_gpu_virgl_process_cmd: ctrl 0x209, error 0x1200 +virtio_gpu_virgl_unmap_resource_blob: failed to unmap virgl resource: Invalid argument +virtio_gpu_virgl_process_cmd: ctrl 0x209, error 0x1200 +virtio_gpu_virgl_unmap_resource_blob: failed to unmap virgl resource: Invalid argument +virtio_gpu_virgl_process_cmd: ctrl 0x209, error 0x1200 +virtio_gpu_virgl_unmap_resource_blob: failed to unmap virgl resource: Invalid argument +virtio_gpu_virgl_process_cmd: ctrl 0x209, error 0x1200 +virtio_gpu_virgl_unmap_resource_blob: failed to unmap virgl resource: Invalid argument +virtio_gpu_virgl_process_cmd: ctrl 0x209, error 0x1200 +virtio_gpu_virgl_unmap_resource_blob: failed to unmap virgl resource: Invalid argument +virtio_gpu_virgl_process_cmd: ctrl 0x209, error 0x1200 +``` +Steps to reproduce: +1. Used steps mentioned here: https://gist.github.com/peppergrayxyz/fdc9042760273d137dddd3e97034385f, to build virglrenderer-1.1.0 with Venus support, and to build QEMU (latest: v10.0.0-rc1) with virglrenderer support. +2. Run QEMU with Lavapipe ICD using the command shared above. +3. When the QEMU guest is up, install required packages such as `sudo apt-get install -y mesa* vulkan* libvulkan* vkmark` and run vkcube / vkmark with VirtIO ICD: +``` +VK_DRIVER_FILES=/usr/share/vulkan/icd.d/virtio_icd.x86_64.json vkcube --wsi wayland +``` +Additional information: +Attaching screenshots for the error observed on guest side: +,  +Collected logs with tracing enabled (`meson setup -Dvenus=true -Dvenus-validate=true -Dvideo=true -Dtracing=stderr build`) in virglrenderer as well: [virgl-tracing-stderr.log](/uploads/202c698b7c265cde7c83b441a6a7abdb/virgl-tracing-stderr.log). Search for error in the log file. diff --git a/results/classifier/gemma3:12b/graphic/2883 b/results/classifier/gemma3:12b/graphic/2883 new file mode 100644 index 00000000..eab5846a --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2883 @@ -0,0 +1,2 @@ + +Advice regarding implementation of smooth scrolling diff --git a/results/classifier/gemma3:12b/graphic/2897 b/results/classifier/gemma3:12b/graphic/2897 new file mode 100644 index 00000000..109c15c5 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2897 @@ -0,0 +1,15 @@ + +Can't boot SeaBIOS based VM when using -display gtk, works fine with vnc or sdl +Description of problem: +When using -display gtk, SeaBIOS hangs nondeterministicly. Changing to -display sdl or -display vnc lets it boot. +Steps to reproduce: +1. Run `qemu-system-x86_64 -display gtk` and the VM will not complete BIOS POST. +2. Run `qemu-system-x86_64 -display sdl` and the VM will complete BIOS POST. +Additional information: +This ONLY happens with SeaBIOS. Using a UEFI BIOS to boot the VM does not cause this issue. + +I realise this is a crazy bug. I suspect that the only way it could have slipped through testing is because it *requires* human interaction. + +There is no difference with using --accel kvm or not, but I have provided the smallest possible command line to duplicate the issue, which is literally just `qemu-system-x86_64 -display gtk` + +# diff --git a/results/classifier/gemma3:12b/graphic/2905 b/results/classifier/gemma3:12b/graphic/2905 new file mode 100644 index 00000000..08acbe58 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2905 @@ -0,0 +1,25 @@ + +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/gemma3:12b/graphic/2959 b/results/classifier/gemma3:12b/graphic/2959 new file mode 100644 index 00000000..b938d75b --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2959 @@ -0,0 +1,78 @@ + +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/gemma3:12b/graphic/296 b/results/classifier/gemma3:12b/graphic/296 new file mode 100644 index 00000000..5e21e401 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/296 @@ -0,0 +1,2 @@ + +Enabling OpenGL for GUI doesn't work on old laptop diff --git a/results/classifier/gemma3:12b/graphic/2965 b/results/classifier/gemma3:12b/graphic/2965 new file mode 100644 index 00000000..79c1e61f --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2965 @@ -0,0 +1,15 @@ + +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/gemma3:12b/graphic/2967 b/results/classifier/gemma3:12b/graphic/2967 new file mode 100644 index 00000000..cca003b7 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2967 @@ -0,0 +1,215 @@ + +Heavy graphic glitches when using Virtio with 3D acceleration +Description of problem: +Virtio with 3D acceleration enabled under "Video" and the corresponding OpenGL activated under "Display" with Spice leads to heavy artifacts in the graphical console. + +This error has been observed on Arch Linux with Intel Meteor Lake CPU (Intel Arc Graphics iGPU) as well as on OpenSuse Tumbleweed with Intel Kaby Lake CPU (Intel HD 630 iGPU) + + +(virtio without acceleration enabled) + + +(Same VM, same settings, but with 3D acceleration and OpenGL enabled) + + +(Same issue on a fresh install of OpenSuse Tumbleweed on a system that is in no way linked to the first one) +Steps to reproduce: +1. Enable Virtio Graphics with 3D acceleration under "Video". +2. Activate the corresponding OpenGL under "Spice". +3. Start the VM and open the graphical console. +Additional information: +XML config: + +``` +<domain type='kvm'> + <name>debian12</name> + <uuid>1d39d86a-b341-47bb-9847-4c78da9df863</uuid> + <metadata> + <libosinfo:libosinfo xmlns:libosinfo="http://libosinfo.org/xmlns/libvirt/domain/1.0"> + <libosinfo:os id="http://debian.org/debian/12"/> + </libosinfo:libosinfo> + </metadata> + <memory unit='KiB'>4194304</memory> + <currentMemory unit='KiB'>4194304</currentMemory> + <vcpu placement='static'>4</vcpu> + <os firmware='efi'> + <type arch='x86_64' machine='pc-q35-9.1'>hvm</type> + <firmware> + <feature enabled='no' name='enrolled-keys'/> + <feature enabled='no' name='secure-boot'/> + </firmware> + <loader readonly='yes' type='pflash'>/usr/share/edk2/x64/OVMF_CODE.4m.fd</loader> + <nvram template='/usr/share/edk2/x64/OVMF_VARS.4m.fd'>/var/lib/libvirt/qemu/nvram/debian12_VARS.fd</nvram> + <boot dev='hd'/> + </os> + <features> + <acpi/> + <apic/> + <vmport state='off'/> + </features> + <cpu mode='host-passthrough' check='none' migratable='on'/> + <clock offset='utc'> + <timer name='rtc' tickpolicy='catchup'/> + <timer name='pit' tickpolicy='delay'/> + <timer name='hpet' present='no'/> + </clock> + <on_poweroff>destroy</on_poweroff> + <on_reboot>restart</on_reboot> + <on_crash>destroy</on_crash> + <pm> + <suspend-to-mem enabled='no'/> + <suspend-to-disk enabled='no'/> + </pm> + <devices> + <emulator>/usr/bin/qemu-system-x86_64</emulator> + <disk type='file' device='disk'> + <driver name='qemu' type='qcow2' discard='unmap'/> + <source file='/var/lib/libvirt/images/debian12.qcow2'/> + <target dev='vda' bus='virtio'/> + <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> + </disk> + <disk type='file' device='cdrom'> + <driver name='qemu' type='raw'/> + <target dev='sda' bus='sata'/> + <readonly/> + <address type='drive' controller='0' bus='0' target='0' unit='0'/> + </disk> + <controller type='usb' index='0' model='qemu-xhci' ports='15'> + <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> + </controller> + <controller type='pci' index='0' model='pcie-root'/> + <controller type='pci' index='1' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='1' port='0x10'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> + </controller> + <controller type='pci' index='2' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='2' port='0x11'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> + </controller> + <controller type='pci' index='3' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='3' port='0x12'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> + </controller> + <controller type='pci' index='4' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='4' port='0x13'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> + </controller> + <controller type='pci' index='5' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='5' port='0x14'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> + </controller> + <controller type='pci' index='6' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='6' port='0x15'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> + </controller> + <controller type='pci' index='7' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='7' port='0x16'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x6'/> + </controller> + <controller type='pci' index='8' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='8' port='0x17'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x7'/> + </controller> + <controller type='pci' index='9' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='9' port='0x18'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0' multifunction='on'/> + </controller> + <controller type='pci' index='10' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='10' port='0x19'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x1'/> + </controller> + <controller type='pci' index='11' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='11' port='0x1a'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x2'/> + </controller> + <controller type='pci' index='12' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='12' port='0x1b'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x3'/> + </controller> + <controller type='pci' index='13' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='13' port='0x1c'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x4'/> + </controller> + <controller type='pci' index='14' model='pcie-root-port'> + <model name='pcie-root-port'/> + <target chassis='14' port='0x1d'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x5'/> + </controller> + <controller type='sata' index='0'> + <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> + </controller> + <controller type='virtio-serial' index='0'> + <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> + </controller> + <interface type='network'> + <mac address='52:54:00:d6:22:67'/> + <source network='default'/> + <model type='virtio'/> + <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> + </interface> + <serial type='pty'> + <target type='isa-serial' port='0'> + <model name='isa-serial'/> + </target> + </serial> + <console type='pty'> + <target type='serial' port='0'/> + </console> + <channel type='unix'> + <target type='virtio' name='org.qemu.guest_agent.0'/> + <address type='virtio-serial' controller='0' bus='0' port='1'/> + </channel> + <channel type='spicevmc'> + <target type='virtio' name='com.redhat.spice.0'/> + <address type='virtio-serial' controller='0' bus='0' port='2'/> + </channel> + <input type='tablet' bus='usb'> + <address type='usb' bus='0' port='1'/> + </input> + <input type='mouse' bus='ps2'/> + <input type='keyboard' bus='ps2'/> + <graphics type='spice'> + <listen type='none'/> + <image compression='off'/> + <gl enable='yes'/> + </graphics> + <sound model='ich9'> + <address type='pci' domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/> + </sound> + <audio id='1' type='spice'/> + <video> + <model type='virtio' heads='1' primary='yes'> + <acceleration accel3d='yes'/> + </model> + <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> + </video> + <redirdev bus='usb' type='spicevmc'> + <address type='usb' bus='0' port='2'/> + </redirdev> + <redirdev bus='usb' type='spicevmc'> + <address type='usb' bus='0' port='3'/> + </redirdev> + <watchdog model='itco' action='reset'/> + <memballoon model='virtio'> + <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> + </memballoon> + <rng model='virtio'> + <backend model='random'>/dev/urandom</backend> + <address type='pci' domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> + </rng> + </devices> +</domain> +``` diff --git a/results/classifier/gemma3:12b/graphic/298 b/results/classifier/gemma3:12b/graphic/298 new file mode 100644 index 00000000..a4446af5 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/298 @@ -0,0 +1,2 @@ + +OpenGL, Virtio-VGA, Virtio-GPU-PCI, GTK diff --git a/results/classifier/gemma3:12b/graphic/2988 b/results/classifier/gemma3:12b/graphic/2988 new file mode 100644 index 00000000..bf5ebce5 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/2988 @@ -0,0 +1,8 @@ + +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/gemma3:12b/graphic/315 b/results/classifier/gemma3:12b/graphic/315 new file mode 100644 index 00000000..5b7c5201 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/315 @@ -0,0 +1,2 @@ + +3d accel does not take care of 1280x960 setting diff --git a/results/classifier/gemma3:12b/graphic/325 b/results/classifier/gemma3:12b/graphic/325 new file mode 100644 index 00000000..4128806e --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/325 @@ -0,0 +1,2 @@ + +Latest QEMU crashes when switching color depth of ReactOS diff --git a/results/classifier/gemma3:12b/graphic/397212 b/results/classifier/gemma3:12b/graphic/397212 new file mode 100644 index 00000000..fdf2a33c --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/397212 @@ -0,0 +1,10 @@ + +Scrolling artifacts on some guests + +Screen doesn't refresh properly when scrolling (see the attachment). + +The behavior is seen on RHEL 4.8 and SLES 11, but not on RHEL 5.3. However, on RHEL5.3, scrolling is very sluggish. It seems to be a trade-off between quick movement and frequent / accurate refreshing. + +Command line: + +qemu-system-x86_64 -m 2048 -drive file=/scratch/images/SLES-11-GMC-x86_64.raw -net nic,vlan=0,macaddr=DE:AD:BE:EF:88:95,model=rtl8139 -net tap -vnc :40 -boot cd -monitor stdio -smp 4 \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/434 b/results/classifier/gemma3:12b/graphic/434 new file mode 100644 index 00000000..39b537d1 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/434 @@ -0,0 +1,2 @@ + +Mouse pointer disappears when it is over console window diff --git a/results/classifier/gemma3:12b/graphic/471 b/results/classifier/gemma3:12b/graphic/471 new file mode 100644 index 00000000..33dea7ec --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/471 @@ -0,0 +1,65 @@ + +Clipboard sharing with `qemu_vdagent` does not work with SDL backend +Description of problem: +Clipboard sharing doesn't work: qemu does not send clipboard-grab messages when selecting on the host, nor does it respond to clipboard-grab messages from the guest. +Steps to reproduce: +1. Start QEMU with `qemu_vdagent` and `-display sdl` +2. Try to copy on the host or the guest +3. Observe that the clipboard is not shared +Additional information: +It appears as though `vdagent_clipboard_notify` function is not called. + +Logs: + +With SDL: +``` +vdagent_open +vdagent_recv_chunk size 28 +vdagent_recv_msg msg announce-capabilities, size 8 +vdagent_peer_cap cap mouse-state +vdagent_peer_cap cap monitors-config +vdagent_peer_cap cap reply +vdagent_peer_cap cap clipboard-by-demand +vdagent_peer_cap cap clipboard-selection +vdagent_peer_cap cap sparse-monitors-config +vdagent_peer_cap cap guest-lineend-lf +vdagent_peer_cap cap max-clipboard +vdagent_peer_cap cap audio-volume-sync +vdagent_send msg announce-capabilities +# tried to copy on host -- nothing happens here. +# trying to copy on guest: +vdagent_recv_chunk size 28 +vdagent_recv_msg msg clipboard-grab, size 8 +vdagent_cb_grab_selection selection clipboard +vdagent_cb_grab_type type text +# no response sent +``` +With GTK: +``` +vdagent_open +vdagent_recv_chunk size 28 +vdagent_recv_msg msg announce-capabilities, size 8 +vdagent_peer_cap cap mouse-state +vdagent_peer_cap cap monitors-config +vdagent_peer_cap cap reply +vdagent_peer_cap cap clipboard-by-demand +vdagent_peer_cap cap clipboard-selection +vdagent_peer_cap cap sparse-monitors-config +vdagent_peer_cap cap guest-lineend-lf +vdagent_peer_cap cap max-clipboard +vdagent_peer_cap cap audio-volume-sync +vdagent_send msg announce-capabilities +# trying to copy on host: +vdagent_send msg clipboard-grab +vdagent_recv_chunk size 28 +vdagent_recv_msg msg clipboard-request, size 8 +vdagent_send msg clipboard +vdagent_recv_chunk size 28 +# trying to copy on guest: +vdagent_recv_msg msg clipboard-grab, size 8 +vdagent_cb_grab_selection selection clipboard +vdagent_cb_grab_type type text +vdagent_send msg clipboard-request +vdagent_recv_chunk size 29 +vdagent_recv_msg msg clipboard, size 9 +``` diff --git a/results/classifier/gemma3:12b/graphic/476 b/results/classifier/gemma3:12b/graphic/476 new file mode 100644 index 00000000..d86c2206 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/476 @@ -0,0 +1,2 @@ + +QEMU with x86-64 EFI disk image and 'nographic' option crashes WSL2 window diff --git a/results/classifier/gemma3:12b/graphic/48 b/results/classifier/gemma3:12b/graphic/48 new file mode 100644 index 00000000..e353ab21 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/48 @@ -0,0 +1,2 @@ + +Hover effect color for "Full list of releases" button is low contrast diff --git a/results/classifier/gemma3:12b/graphic/488 b/results/classifier/gemma3:12b/graphic/488 new file mode 100644 index 00000000..30fb397c --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/488 @@ -0,0 +1,31 @@ + +[git]Virt-Manager cannot start any previously created virtual machine with Qemu commit bd306cfe: 'spicevmc' is not a valid char driver name +Description of problem: +With qemu built on commit bd306cfe, I'm unable to start a previously created VM. + +Because of both bug #463 and #474 I was blocked from building qemu from git for something like a week or so. My last built and working Qemu is based on commit 9bef7ea9d9. + +Doing a git bissect won't be an easy task :( +Steps to reproduce: +1. Build qemu using commit bd306cfe +2. Launch Virt-Manager +3. Try to launch a previously created VM or try to boot a new one. +Additional information: +Every single time I tried to launch a VM, I get a dialog box with this error message: + +``` +Error starting domain: internal error: qemu unexpectedly closed the monitor: 2021-07-18T07:56:50.116480Z qemu-system-x86_64: -chardev spicevmc,id=charchannel1,name=vdagent: 'spicevmc' is not a valid char driver name + +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/asyncjob.py", line 101, in tmpcb + callback(*args, **kwargs) + File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn + ret = fn(self, *args, **kwargs) + File "/usr/share/virt-manager/virtManager/object/domain.py", line 1329, in startup + self._backend.create() + File "/usr/lib/python3.9/site-packages/libvirt.py", line 1353, in create + raise libvirtError('virDomainCreate() failed') +libvirt.libvirtError: internal error: qemu unexpectedly closed the monitor: 2021-07-18T07:56:50.116480Z qemu-system-x86_64: -chardev spicevmc,id=charchannel1,name=vdagent: 'spicevmc' is not a valid char driver name +``` diff --git a/results/classifier/gemma3:12b/graphic/497 b/results/classifier/gemma3:12b/graphic/497 new file mode 100644 index 00000000..1abcdaac --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/497 @@ -0,0 +1,20 @@ + +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/gemma3:12b/graphic/498 b/results/classifier/gemma3:12b/graphic/498 new file mode 100644 index 00000000..0aaffc41 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/498 @@ -0,0 +1,43 @@ + +Cannot focus QEMU window on macOS Big Sur (11.4) +Description of problem: +I'm not sure when the problem has been started, but I recently noticed that key inputs to QEMU window are not processed and the input goes other focused windows (e.g. terminal). QEMU window itself is shown but it looks like they are not focused. Also, the Dock icon for QEMU is also disappeared (it was displayed before). +Steps to reproduce: +1. build & install the latest qemu with `./configure --target-list=x86_64-softmmu` + - (`a146af86c8247f41b641783428b95ee71eb0e43f` was the revision I used) +2. run `qemu-system-x86_64` from terminal +3. click the QEMU window. + - Expected behavior: menu bar title will be switched to "QEMU", key inputs are handled by QEMU, Dock icon will be shown. + - Actual behavior: menu bar shows different app name that were focused before clicking the qemu, key inputs went to other app that was focused, dock icon is not showing up. +Additional information: +I tried to see if the events are delivered to QemuCocoaView by putting `NSLog(@"handleEventLocked: %@\n", event);` at the beginning of `handleEventLocked` @ `ui/cocoa.m`. It looks like the mouse events are delivered but not NSEventTypeKeyDown. + +(logs after clicked the QEMU window and type some 'a') +``` +$ qemu-system-x86_64 +2021-07-24 16:58:00.767 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=Kitdefined loc=(0,428) time=682409.7 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 subtype=4 data1=1144258560 data2=1138098176 +2021-07-24 16:58:00.768 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=Kitdefined loc=(0,228) time=682409.7 flags=0 win=0x7fe2b5fb0ee0 winNum=10356 ctxt=0x0 subtype=4 data1=1137180672 data2=1130627072 +2021-07-24 16:58:06.462 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=Kitdefined loc=(0,428) time=682415.4 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 subtype=9 data1=1129 data2=0 +2021-07-24 16:58:06.462 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=LMouseDown loc=(591.031,166.896) time=682415.4 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=6096 click=1 buttonNumber=0 pressure=1 deviceID:0x0 subtype=0 +2021-07-24 16:58:06.462 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=Kitdefined loc=(0,0) time=0.0 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 subtype=1 data1=1129 data2=0 +2021-07-24 16:58:06.487 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=Kitdefined loc=(0,428) time=682415.4 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 subtype=22 data1=0 data2=0 +2021-07-24 16:58:06.487 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=Kitdefined loc=(0,428) time=682415.4 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 subtype=23 data1=0 data2=0 +2021-07-24 16:58:06.565 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=LMouseUp loc=(591.031,166.896) time=682415.5 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=6096 click=1 buttonNumber=0 pressure=0 deviceID:0x0 subtype=0 +2021-07-24 16:58:12.997 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=MouseEntered loc=(174.184,408.859) time=682421.9 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=0 trackNum=7fe2b5e81d60 userData=0x0 +2021-07-24 16:58:13.013 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=MouseExited loc=(152.704,428.804) time=682422.0 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=0 trackNum=7fe2b5e81d60 userData=0x0 +2021-07-24 16:58:24.181 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=Kitdefined loc=(0,428) time=682433.1 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 subtype=9 data1=1131 data2=0 +2021-07-24 16:58:24.181 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=LMouseDown loc=(268.333,208.222) time=682433.1 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=6098 click=1 buttonNumber=0 pressure=1 deviceID:0x0 subtype=0 +2021-07-24 16:58:24.262 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=LMouseUp loc=(268.333,208.222) time=682433.2 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=6098 click=1 buttonNumber=0 pressure=0 deviceID:0x0 subtype=0 +2021-07-24 16:58:24.877 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=MouseEntered loc=(3.83252,400.359) time=682433.8 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=0 trackNum=7fe2b5e81d60 userData=0x0 +2021-07-24 16:58:25.053 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=MouseEntered loc=(7.08813,408.091) time=682434.0 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=0 trackNum=7fe295c0f090 userData=0x1 +2021-07-24 16:58:25.054 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=MouseEntered loc=(7.08813,408.091) time=682434.0 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=0 trackNum=7fe2b5e80e30 userData=0x0 +2021-07-24 16:58:25.302 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=LMouseDown loc=(10.917,420.558) time=682434.2 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=6099 click=1 buttonNumber=0 pressure=1 deviceID:0x0 subtype=0 +2021-07-24 16:58:25.365 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=LMouseUp loc=(10.917,420.558) time=682434.3 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=6099 click=1 buttonNumber=0 pressure=0 deviceID:0x0 subtype=0 +2021-07-24 16:58:25.845 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=MouseExited loc=(11.9221,422.759) time=682434.8 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=0 trackNum=7fe295c0f090 userData=0x1 +2021-07-24 16:58:25.846 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=MouseExited loc=(11.9221,422.759) time=682434.8 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=0 trackNum=7fe2b5e80e30 userData=0x0 +2021-07-24 16:58:25.855 qemu-system-x86_64[3752:7837649] handleEventLocked: NSEvent: type=MouseExited loc=(14.2417,428.558) time=682434.8 flags=0 win=0x7fe2b5e48960 winNum=10355 ctxt=0x0 evNum=0 trackNum=7fe2b5e81d60 userData=0x0 + +``` + +Possibly related discussion on Apple Developer Forums: +- https://developer.apple.com/forums/thread/667004 diff --git a/results/classifier/gemma3:12b/graphic/498421 b/results/classifier/gemma3:12b/graphic/498421 new file mode 100644 index 00000000..cf4b0bec --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/498421 @@ -0,0 +1,4 @@ + +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/gemma3:12b/graphic/504368 b/results/classifier/gemma3:12b/graphic/504368 new file mode 100644 index 00000000..7af9f56c --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/504368 @@ -0,0 +1,44 @@ + +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/gemma3:12b/graphic/558 b/results/classifier/gemma3:12b/graphic/558 new file mode 100644 index 00000000..79515e78 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/558 @@ -0,0 +1,58 @@ + +gtk UI interprets double/triple click as button release +Description of problem: +When using the GTK interface clicking rapidly in a down-up-down pattern, the final "down" event is erroneously followed by an immediate "up" event and the mouse device in the guest reports the pressed button as no longer being held. +Steps to reproduce: +1. Start a VM using the GTK interface. +2. Open a tool to examine guest mouse input events, such as `xev` or `yutani-test` +3. Click twice with any button, without releasing on the second click. +4. Observe erroneous 'up' event in guest. +5. Move the mouse while keeping the button pressed. +6. Observe the guest reports the button is not held. +Additional information: +GTK 3 sends an additional `GDK_2BUTTON_PRESS` event after the initial `GDK_BUTTON_PRESS` event, which QEMU is misinterpreting as a release event. I confirmed this with the addition of some logging of `button->type` in `gd_button_event`: + +``` +button = 1, type = 4 +button = 1, type = 7 +button = 1, type = 4 +button = 1, type = 7 +button = 1, type = 4 # = PRESS +button = 1, type = 5 # = 2BUTTON_PRESS +button = 1, type = 7 +button = 1, type = 4 +button = 1, type = 7 +button = 1, type = 4 +button = 1, type = 5 +button = 1, type = 7 +button = 1, type = 4 +button = 1, type = 7 +button = 1, type = 4 +button = 1, type = 7 +button = 1, type = 4 +button = 1, type = 7 +button = 1, type = 4 +button = 1, type = 5 +button = 1, type = 7 +``` + +```diff +diff --git a/ui/gtk.c b/ui/gtk.c +index cfb0728d1f..b9979f0e11 100644 +--- a/ui/gtk.c ++++ b/ui/gtk.c +@@ -925,6 +925,13 @@ static gboolean gd_button_event(GtkWidget *widget, GdkEventButton *button, + return TRUE; + } + ++ /* ignore additional events for double- and triple- press, as they are ++ * sent to us after a regular press event; otherwise we will misinterpret ++ * these as release events and eat the button! */ ++ if (button->type == GDK_2BUTTON_PRESS || button->type == GDK_3BUTTON_PRESS) { ++ return TRUE; ++ } ++ + qemu_input_queue_btn(vc->gfx.dcl.con, btn, + button->type == GDK_BUTTON_PRESS); + qemu_input_event_sync(); +``` diff --git a/results/classifier/gemma3:12b/graphic/564 b/results/classifier/gemma3:12b/graphic/564 new file mode 100644 index 00000000..05f981aa --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/564 @@ -0,0 +1,14 @@ + +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/gemma3:12b/graphic/568614 b/results/classifier/gemma3:12b/graphic/568614 new file mode 100644 index 00000000..a15060b1 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/568614 @@ -0,0 +1,17 @@ + +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/gemma3:12b/graphic/574 b/results/classifier/gemma3:12b/graphic/574 new file mode 100644 index 00000000..c35b9c02 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/574 @@ -0,0 +1,2 @@ + +ui/sdl2: warning: redundant redeclaration of 'direct_waitqueue_init' diff --git a/results/classifier/gemma3:12b/graphic/58 b/results/classifier/gemma3:12b/graphic/58 new file mode 100644 index 00000000..529b2390 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/58 @@ -0,0 +1,2 @@ + +Bitmaps with Extra Data cannot be removed diff --git a/results/classifier/gemma3:12b/graphic/606 b/results/classifier/gemma3:12b/graphic/606 new file mode 100644 index 00000000..0bf4c8d3 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/606 @@ -0,0 +1,2 @@ + +Gtk: gtk_clipboard_set_with_data: assertion 'targets != NULL' failed diff --git a/results/classifier/gemma3:12b/graphic/610 b/results/classifier/gemma3:12b/graphic/610 new file mode 100644 index 00000000..0280697a --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/610 @@ -0,0 +1,32 @@ + +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/gemma3:12b/graphic/612677 b/results/classifier/gemma3:12b/graphic/612677 new file mode 100644 index 00000000..7bc38605 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/612677 @@ -0,0 +1,19 @@ + +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/gemma3:12b/graphic/614958 b/results/classifier/gemma3:12b/graphic/614958 new file mode 100644 index 00000000..265303b8 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/614958 @@ -0,0 +1,38 @@ + +copy-paste between client and host + +Hi, + +I propose that copy/paste between VMs be implemented somehow directly in QEMU. +This has been discussed repeatedly elsewhere; various solutions are proposed. See below. + +As it is, each user has to do their own research and testing if they are to find a solution. This makes the product frustratingly unattractive for many. + +Most solutions involve either running vnc and using a vnc client that supports copy/paste (this can be tricky to find itself), or running some other tcp-based copy-paste application. + +For many users, the networking in a client VM is unimportant--they just want to run some application there, and setting up netoworking in a VM itself can be an issue. Most of these solutions rely on un-maintained software, and some require that other software be installed to make them work (Basic interpreter, Java, etc). Any of these solutions take some work to set up. + +I can tell you, the absence of a copy/paste mechanism makes the project an immediate no-go for many users. I work with a guy who spent a lot of time trying, gave up, and switched to VirtualBox for this exact reason. + +It would be much better if copy/paste worked out of the box. Ideally, it should work independently of networking. + +Cheers! + +Some discussions and proposed solutions: +----------------------------------------------------- +http://qemu-forum.ipi.fi/viewtopic.php?f=4&t=161 + Somebody suggests VNC into the virtual host, and use vncviewer + Somebody else suggests TCP/IP Clipboard (text editor with tcp/ip) + +http://qemu-forum.ipi.fi/viewtopic.php?f=4&t=2626 + primitive app for sharing text across machines (in Basic) + http://homepage.mac.com/bnej/shareclip/ + +http://borderworlds.dk/blog/20070217-00.html + Says doesn't know a good solution but points to unmaintained package + Qemu Guest Tools + http://wolfpackally.wo.funpic.de/qemu/qgt/ + +http://bonzoli.com/docs/How_to_setup_Qemu_on_Fedora_8.html + proposes Java remoteclip running on client and server + http://www.cs.cmu.edu/afs/cs/user/rcm/WWW/RemoteClip/ \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/631 b/results/classifier/gemma3:12b/graphic/631 new file mode 100644 index 00000000..57a8782a --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/631 @@ -0,0 +1,26 @@ + +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 + + + + + diff --git a/results/classifier/gemma3:12b/graphic/660 b/results/classifier/gemma3:12b/graphic/660 new file mode 100644 index 00000000..5450e69d --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/660 @@ -0,0 +1,10 @@ + +User emulation does not use host GPU +Description of problem: + +Steps to reproduce: +1. Make a Arch Linux chroot (though any Linux system should work) on Linux +2. run `glxinfo | grep OpenGL +3. It's using llvmpipe, not whatever GPU/driver that the hosts use +Additional information: + diff --git a/results/classifier/gemma3:12b/graphic/665743 b/results/classifier/gemma3:12b/graphic/665743 new file mode 100644 index 00000000..05c2768c --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/665743 @@ -0,0 +1,4 @@ + +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/gemma3:12b/graphic/671 b/results/classifier/gemma3:12b/graphic/671 new file mode 100644 index 00000000..0af78f2b --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/671 @@ -0,0 +1,19 @@ + +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/gemma3:12b/graphic/691424 b/results/classifier/gemma3:12b/graphic/691424 new file mode 100644 index 00000000..dc4af5fa --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/691424 @@ -0,0 +1,51 @@ + +qemu/kvm SDL over ssh -X broken + +qemu/kvm by default uses SDL to render the output of its emulated VGA graphics. +This is broken over ssh -X since quite a while. +The only workaround I know, is to use qemu -vnc :0 +and connect using vncviewer + + +How To Reproduce: +1. zypper in qemu +2. ssh -X localhost qemu -cdrom ANYISOFILE + +Actual Results: +qemu hangs in an endless loop on the BIOS display screen + +Expected Results: +should boot up the iso as 0.10 versions did + +Reproducible: Always + + +this is what broke it: +$ git bisect bad +c18a2c360e3100bbd71162cf922dcd8c429a8b71 is first bad commit +commit c18a2c360e3100bbd71162cf922dcd8c429a8b71 +Author: Stefano Stabellini <email address hidden> +Date: Wed Jun 24 11:58:25 2009 +0100 + + sdl zooming + + Hi all, + this patch implements zooming capabilities for the sdl interface. + A new sdl_zoom_blit function is added that is able to scale and blit a + portion of a surface into another. + This way we can enable SDL_RESIZABLE and have a real_screen surface with + a different size than the guest surface and let sdl_zoom_blit take care + of the problem. + + Signed-off-by: Stefano Stabellini <email address hidden> + Signed-off-by: Anthony Liguori <email address hidden> + +:100644 100644 a06c9bfc22cc6de1c6e5e9068d6bf59d89613767 f8dc5065dd27010bfdbb6bcfb0c6e3af25024cdb M Makefile +:100644 100644 417217582363a87ee67e746ba798e285a64b6cdc 35183399f65de6f50f3baa4767ab7d4d11d45bca M console.h +:100644 100644 178b5532b8d9dd2194a8662fbfdcd49b4bc04222 d81399e51276e1c97fa1f7272ef16ea4c312b51b M sdl.c +:000000 100644 0000000000000000000000000000000000000000 56d3604fc3d79e4cc4622be8437c78bf70075da3 A sdl_zoom.c +:000000 100644 0000000000000000000000000000000000000000 33dc63408b43a37fd6b1acde3fa62b1a51315e75 A sdl_zoom.h +:000000 100644 0000000000000000000000000000000000000000 64bbca849bd3af678c2259b4d8cc0e48c6a6b43c A sdl_zoom_template.h + + +This problem occurs on both Debian and openSUSE. \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/696 b/results/classifier/gemma3:12b/graphic/696 new file mode 100644 index 00000000..c398ab92 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/696 @@ -0,0 +1,10 @@ + +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/gemma3:12b/graphic/700 b/results/classifier/gemma3:12b/graphic/700 new file mode 100644 index 00000000..ee9ed8bc --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/700 @@ -0,0 +1,2 @@ + +GTK display refresh rate is throttled diff --git a/results/classifier/gemma3:12b/graphic/705931 b/results/classifier/gemma3:12b/graphic/705931 new file mode 100644 index 00000000..4768ada0 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/705931 @@ -0,0 +1,30 @@ + +make ui sdl error 1 on git devel + +after clone git devel, try compile on slackware 13.1 32 bit machine got error: + +ui/sdl.c:809:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before '{' token +ui/sdl.c:815:36: error: expected ')' before '*' token +/usr/include/X11/Xlib.h:3575:14: error: old-style parameter declarations in prototyped function definition +/usr/include/X11/Xlib.h:3576:5: error: parameter name omitted +ui/sdl.c:883:1: error: expected '{' at end of input +ui/sdl.c:883:1: error: control reaches end of non-void function +make: *** [ui/sdl.o] Error 1 + + +root@darkstar:/usr/src/qemu/qemu# gcc -v +Reading specs from /usr/lib/gcc/i486-slackware-linux/4.5.1/specs +COLLECT_GCC=gcc +COLLECT_LTO_WRAPPER=/usr/libexec/gcc/i486-slackware-linux/4.5.1/lto-wrapper +Target: i486-slackware-linux +Configured with: ../gcc-4.5.1/configure --prefix=/usr --libdir=/usr/lib --mandir=/usr/man --infodir=/usr/info --enable-shared --enable-bootstrap --enable-languages=ada,c,c++,fortran,java,objc,lto --enable-threads=posix --enable-checking=release --with-system-zlib --with-python-dir=/lib/python2.6/site-packages --disable-libunwind-exceptions --enable-__cxa_atexit --enable-libssp --enable-lto --with-gnu-ld --verbose --with-arch=i486 --target=i486-slackware-linux --build=i486-slackware-linux --host=i486-slackware-linux +Thread model: posix +gcc version 4.5.1 (GCC) + + +root@darkstar:/usr/src/qemu/qemu# uname -a +Linux darkstar 2.6.35.7-smp #2 SMP Mon Oct 11 14:52:09 CDT 2010 i686 Intel(R) Core(TM)2 Duo CPU T7100 @ 1.80GHz GenuineIntel GNU/Linux +root@darkstar:/usr/src/qemu/qemu# cat /etc/slackware-version +Slackware 13.1.0 + +thanks \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/709584 b/results/classifier/gemma3:12b/graphic/709584 new file mode 100644 index 00000000..7df31991 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/709584 @@ -0,0 +1,20 @@ + +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/gemma3:12b/graphic/718 b/results/classifier/gemma3:12b/graphic/718 new file mode 100644 index 00000000..ccd898f9 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/718 @@ -0,0 +1,7 @@ + +option to take screenshot with screendump as PNG +Additional information: +Libvirt already have preparation for PNG MIME type: https://github.com/libvirt/libvirt/blob/master/tools/virsh-domain.c#L5526 + + +Thanks diff --git a/results/classifier/gemma3:12b/graphic/723 b/results/classifier/gemma3:12b/graphic/723 new file mode 100644 index 00000000..b3f87156 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/723 @@ -0,0 +1,32 @@ + +multiple displays VGA + qxl forces Spice mouse-mode=server and breaks usb-tablet/seamless mode +Description of problem: +qxl causes a totally unexpected mouse conflict with the default VGA in OSX Catalina and newer guests using AppleVirtualGraphics.kext + +usb-tablet is unusable - only clicks are received +usb-mouse works but grabs focus +Steps to reproduce: +1. install and run OSX guest +2. connect to Spice port +3. can't move mouse if usb-tablet is used. usb-mouse pointer but is grabbed +4. removing qxl fixed the issue for me. Mouse is seamless/not grabbed now +5. added -spice agent-mouse=on just in case +Additional information: +qmp from broken shows mouse-mode server. Working guests show mouse-mode client + +``` +{ "execute": "query-spice" } +... "mouse-mode": "server"}} +``` +- spice works with multiple displays in OSX if both are VGA but I had the same focus problem, will need to recheck because Qemu 6.1 seems stuck on mouse-mode=server. + + +Working VGA +``` +/usr/bin/qemu-system-x86_64 -name macos-big-sur,process=macos-big-sur -pidfile macos-big-sur/macos-big-sur.pid -enable-kvm -machine q35,smm=off,vmport=off -device isa-applesmc,osk=ourhardworkbythesewordsguardedpleasedontsteal\(c\)AppleComputerInc -no-hpet -global kvm-pit.lost_tick_policy=discard -cpu host,kvm=on,vendor=GenuineIntel,+hypervisor,+invtsc,+kvm_pv_eoi,+kvm_pv_unhalt -smp cores=2,threads=1,sockets=1 -m 8G -device virtio-balloon -smbios type=2,manufacturer="Wimpys World",product=Quickemu,version=2.3.1,serial=jvzclfjbeyq.pbz,location=wimpysworld.com,asset=macos-big-sur -device VGA,vgamem_mb=128 -display none -device usb-ehci,id=input -device usb-kbd,bus=input.0 -device usb-tablet,bus=input.0 -rtc base=localtime,clock=host,driftfix=slew -spice disable-ticketing=on,agent-mouse=on,port=5930 -device virtio-serial-pci -chardev socket,id=agent0,path=macos-big-sur/macos-big-sur-agent.sock,server=on,wait=off -device virtserialport,chardev=agent0,name=org.qemu.guest_agent.0 -device virtio-rng-pci,rng=rng0 -object rng-random,id=rng0,filename=/dev/urandom -chardev socket,id=monitor0,path=macos-big-sur/macos-big-sur-monitor.sock,server=on,wait=off -mon chardev=monitor0,id=monitor,mode=control -monitor none -serial mon:stdio -audiodev spice,id=audio0 -device ich9-intel-hda -device hda-duplex,audiodev=audio0 -device virtio-net,netdev=nic -netdev user,hostname=macos-big-sur,hostfwd=tcp::22220-:22,id=nic -global driver=cfi.pflash01,property=secure,value=on -drive if=pflash,format=raw,unit=0,file=macos-big-sur/OVMF_CODE.fd,readonly=on -drive if=pflash,format=raw,unit=1,file=macos-big-sur/OVMF_VARS-1024x768.fd -device ahci,id=ahci -device ide-hd,bus=ahci.0,drive=BootLoader,bootindex=0 -drive id=BootLoader,if=none,format=qcow2,file=macos-big-sur/OpenCore.qcow2 -device virtio-blk-pci,drive=SystemDisk -drive id=SystemDisk,if=none,format=qcow2,file=macos-big-sur/disk.qcow2 -device qemu-xhci,id=spicepass -chardev spicevmc,id=usbredirchardev1,name=usbredir -device usb-redir,chardev=usbredirchardev1,id=usbredirdev1 -chardev spicevmc,id=usbredirchardev2,name=usbredir -device usb-redir,chardev=usbredirchardev2,id=usbredirdev2 -chardev spicevmc,id=usbredirchardev3,name=usbredir -device usb-redir,chardev=usbredirchardev3,id=usbredirdev3 -device usb-ccid -chardev spicevmc,id=ccid,name=smartcard -device ccid-card-passthru,chardev=ccid -device virtio-serial-pci -chardev spiceport,id=webdav0,name=org.spice-space.webdav.0 -device virtserialport,chardev=webdav0,name=org.spice-space.webdav.0 -fsdev local,id=fsdev0,path=/home/jmorrison/Public,security_model=mapped-xattr -device virtio-9p-pci,fsdev=fsdev0,mount_tag=Public-jmorrison +``` + +Broken usb-tablet qxl +``` +/usr/bin/qemu-system-x86_64 -name macos-big-sur,process=macos-big-sur -pidfile macos-big-sur/macos-big-sur.pid -enable-kvm -machine q35,smm=off,vmport=off -device isa-applesmc,osk=ourhardworkbythesewordsguardedpleasedontsteal\(c\)AppleComputerInc -no-hpet -global kvm-pit.lost_tick_policy=discard -cpu host,kvm=on,vendor=GenuineIntel,+hypervisor,+invtsc,+kvm_pv_eoi,+kvm_pv_unhalt -smp cores=2,threads=1,sockets=1 -m 8G -device virtio-balloon -smbios type=2,manufacturer="Wimpys World",product=Quickemu,version=2.3.1,serial=jvzclfjbeyq.pbz,location=wimpysworld.com,asset=macos-big-sur -device qxl -display none -device usb-ehci,id=input -device usb-kbd,bus=input.0 -device usb-tablet,bus=input.0 -rtc base=localtime,clock=host,driftfix=slew -spice disable-ticketing=on,port=5930 -device virtio-serial-pci -chardev socket,id=agent0,path=macos-big-sur/macos-big-sur-agent.sock,server=on,wait=off -device virtserialport,chardev=agent0,name=org.qemu.guest_agent.0 -device virtio-rng-pci,rng=rng0 -object rng-random,id=rng0,filename=/dev/urandom -chardev socket,id=monitor0,path=macos-big-sur/macos-big-sur-monitor.sock,server=on,wait=off -mon chardev=monitor0,id=monitor,mode=control -monitor none -serial mon:stdio -audiodev spice,id=audio0 -device ich9-intel-hda -device hda-duplex,audiodev=audio0 -device virtio-net,netdev=nic -netdev user,hostname=macos-big-sur,hostfwd=tcp::22220-:22,id=nic -global driver=cfi.pflash01,property=secure,value=on -drive if=pflash,format=raw,unit=0,file=macos-big-sur/OVMF_CODE.fd,readonly=on -drive if=pflash,format=raw,unit=1,file=macos-big-sur/OVMF_VARS-1024x768.fd -device ahci,id=ahci -device ide-hd,bus=ahci.0,drive=BootLoader,bootindex=0 -drive id=BootLoader,if=none,format=qcow2,file=macos-big-sur/OpenCore.qcow2 -device virtio-blk-pci,drive=SystemDisk -drive id=SystemDisk,if=none,format=qcow2,file=macos-big-sur/disk.qcow2 -device qemu-xhci,id=spicepass -chardev spicevmc,id=usbredirchardev1,name=usbredir -device usb-redir,chardev=usbredirchardev1,id=usbredirdev1 -chardev spicevmc,id=usbredirchardev2,name=usbredir -device usb-redir,chardev=usbredirchardev2,id=usbredirdev2 -chardev spicevmc,id=usbredirchardev3,name=usbredir -device usb-redir,chardev=usbredirchardev3,id=usbredirdev3 -device usb-ccid -chardev spicevmc,id=ccid,name=smartcard -device ccid-card-passthru,chardev=ccid -device virtio-serial-pci -chardev spiceport,id=webdav0,name=org.spice-space.webdav.0 -device virtserialport,chardev=webdav0,name=org.spice-space.webdav.0 -fsdev local,id=fsdev0,path=/home/jmorrison/Public,security_model=mapped-xattr -device virtio-9p-pci,fsdev=fsdev0,mount_tag=Public-jmorrison +``` diff --git a/results/classifier/gemma3:12b/graphic/731 b/results/classifier/gemma3:12b/graphic/731 new file mode 100644 index 00000000..2eaf7fe1 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/731 @@ -0,0 +1,22 @@ + +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: + + + +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/gemma3:12b/graphic/75 b/results/classifier/gemma3:12b/graphic/75 new file mode 100644 index 00000000..2777fa1a --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/75 @@ -0,0 +1,2 @@ + +Add -display SDL grab-on-hover option diff --git a/results/classifier/gemma3:12b/graphic/76 b/results/classifier/gemma3:12b/graphic/76 new file mode 100644 index 00000000..0c2f5b49 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/76 @@ -0,0 +1,2 @@ + +Mouse cursor sometimes can't pass the invisible border on the right side of the screen diff --git a/results/classifier/gemma3:12b/graphic/761 b/results/classifier/gemma3:12b/graphic/761 new file mode 100644 index 00000000..3b4be93f --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/761 @@ -0,0 +1,13 @@ + +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/gemma3:12b/graphic/768 b/results/classifier/gemma3:12b/graphic/768 new file mode 100644 index 00000000..9315f3a8 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/768 @@ -0,0 +1,13 @@ + +Mouse cursor disappears in RHEL guest when using "-device virtio-vga-gl -display gtk,gl=on" option +Description of problem: +Mouse cursor disappears in RHEL guest when using -device virtio-vga-gl -display gtk,gl=on +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. The mouse cursor disappears once it moves into the VM. +Additional information: + diff --git a/results/classifier/gemma3:12b/graphic/769 b/results/classifier/gemma3:12b/graphic/769 new file mode 100644 index 00000000..c5c3ba53 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/769 @@ -0,0 +1,17 @@ + +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: + + + diff --git a/results/classifier/gemma3:12b/graphic/775604 b/results/classifier/gemma3:12b/graphic/775604 new file mode 100644 index 00000000..bc64f620 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/775604 @@ -0,0 +1,12 @@ + +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/gemma3:12b/graphic/776 b/results/classifier/gemma3:12b/graphic/776 new file mode 100644 index 00000000..bd3ab7f1 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/776 @@ -0,0 +1,26 @@ + +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/gemma3:12b/graphic/784 b/results/classifier/gemma3:12b/graphic/784 new file mode 100644 index 00000000..c3c8abd8 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/784 @@ -0,0 +1,14 @@ + +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: + diff --git a/results/classifier/gemma3:12b/graphic/821 b/results/classifier/gemma3:12b/graphic/821 new file mode 100644 index 00000000..89d0aef3 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/821 @@ -0,0 +1,2 @@ + +[SOLVED] ReactOS video problems... diff --git a/results/classifier/gemma3:12b/graphic/839 b/results/classifier/gemma3:12b/graphic/839 new file mode 100644 index 00000000..d49afea7 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/839 @@ -0,0 +1,51 @@ + +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/gemma3:12b/graphic/840 b/results/classifier/gemma3:12b/graphic/840 new file mode 100644 index 00000000..fe22d57e --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/840 @@ -0,0 +1,11 @@ + +When O2 level is enabled raspi3b board crash randomly when creating abuffer of a differnt size +Description of problem: +Sometimes when running the code creating a framebuffer different from the default size ej:1024x768 qemu hangs and crash with a SIGV, making a weird screen that's painted with the original size and the background of the current window merged onto a large window. This happens when you resize a window without updating it's contents, so qemu is crashing before the first frame after reising the window. +Steps to reproduce: +1. Create a producedure similar to the one descrived below +2. Run qemu with O2 enabled(debuggind disabled) +3. You may need to run it multiple times to see the bug(like two or three times) +Additional information: +Here is the example procedure implemented on rust, the mailbox interface is test and it's sure that the procedure it's well implemented: +[code.rs](/uploads/a28fe33a856fb843d80ffeb078bc6729/code.rs) diff --git a/results/classifier/gemma3:12b/graphic/855630 b/results/classifier/gemma3:12b/graphic/855630 new file mode 100644 index 00000000..87dac503 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/855630 @@ -0,0 +1,10 @@ + +Cant Run Wine (posix not nptl) past 0.14.1 + +when trying to build qemu I can build with ./configure --static --enable-sdl --target-list=i386-linux-user just fine with 0.12.5 + +But when I try to go on 0.13.0 or higher (tested on 0.15.0) it will say it cant find libSDL. + +Tried with arm and x86 versions of Ubuntu 9.10 and 11.04. Same on all 4 tests. + +I found I could run posix wine on 12.5 but I cant go higher for posix wine because of that libSDL. \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/865 b/results/classifier/gemma3:12b/graphic/865 new file mode 100644 index 00000000..a6793e3a --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/865 @@ -0,0 +1,46 @@ + +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: + + +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/gemma3:12b/graphic/868 b/results/classifier/gemma3:12b/graphic/868 new file mode 100644 index 00000000..9c3847b9 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/868 @@ -0,0 +1,16 @@ + +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/gemma3:12b/graphic/90 b/results/classifier/gemma3:12b/graphic/90 new file mode 100644 index 00000000..d593a15a --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/90 @@ -0,0 +1,2 @@ + +vga/std lacks few wide screen modes. diff --git a/results/classifier/gemma3:12b/graphic/901 b/results/classifier/gemma3:12b/graphic/901 new file mode 100644 index 00000000..565d7d62 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/901 @@ -0,0 +1,11 @@ + +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/gemma3:12b/graphic/910 b/results/classifier/gemma3:12b/graphic/910 new file mode 100644 index 00000000..f8d97be7 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/910 @@ -0,0 +1,2 @@ + +Black screen in qemu 6.2 with wayland, weston, gtk, virgl, ivi shell, Aarch64 diff --git a/results/classifier/gemma3:12b/graphic/922076 b/results/classifier/gemma3:12b/graphic/922076 new file mode 100644 index 00000000..57f5433c --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/922076 @@ -0,0 +1,14 @@ + +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/gemma3:12b/graphic/926 b/results/classifier/gemma3:12b/graphic/926 new file mode 100644 index 00000000..bda9d38a --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/926 @@ -0,0 +1,2 @@ + +block-backend assertion with Cocoa UI diff --git a/results/classifier/gemma3:12b/graphic/939443 b/results/classifier/gemma3:12b/graphic/939443 new file mode 100644 index 00000000..2d4d6096 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/939443 @@ -0,0 +1,7 @@ + +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/gemma3:12b/graphic/962 b/results/classifier/gemma3:12b/graphic/962 new file mode 100644 index 00000000..897b0e87 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/962 @@ -0,0 +1,20 @@ + +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/gemma3:12b/graphic/984516 b/results/classifier/gemma3:12b/graphic/984516 new file mode 100644 index 00000000..9c5e80b3 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/984516 @@ -0,0 +1,24 @@ + +should use sdl-config for static build not pkg-config + +In the configure script when a user wants to compile a static QEMU and enable SDL support (i.e. ./configure --static --enable-sdl): + +pkg-config does not have an option "--static-libs". For correct results (to find the static archive libSDL.a) you need to use sdl-config --static-libs. + + +This is how I get it to work for me anyway: + + +diff --git a/configure b/configure +index 2d62d12..3de4c9b 100755 +--- a/configure ++++ b/configure +@@ -1548,7 +1548,7 @@ int main( void ) { return SDL_Init (SDL_INIT_VIDEO); } + EOF + sdl_cflags=`$sdlconfig --cflags 2> /dev/null` + if test "$static" = "yes" ; then +- sdl_libs=`$sdlconfig --static-libs 2>/dev/null` ++ sdl_libs=`${SDL_CONFIG-${cross_prefix}sdl-config} --static-libs` + else + sdl_libs=`$sdlconfig --libs 2> /dev/null` + fi \ No newline at end of file diff --git a/results/classifier/gemma3:12b/graphic/986318 b/results/classifier/gemma3:12b/graphic/986318 new file mode 100644 index 00000000..328b0617 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/986318 @@ -0,0 +1,6 @@ + +[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/gemma3:12b/graphic/988 b/results/classifier/gemma3:12b/graphic/988 new file mode 100644 index 00000000..a3c04e1b --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/988 @@ -0,0 +1,2 @@ + +Cirrus video, graphical corruption, bad fonts diff --git a/results/classifier/gemma3:12b/graphic/996 b/results/classifier/gemma3:12b/graphic/996 new file mode 100644 index 00000000..489b75c7 --- /dev/null +++ b/results/classifier/gemma3:12b/graphic/996 @@ -0,0 +1,27 @@ + +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). |