1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
|
<think>
Okay, so I'm trying to figure out what category this bug report falls into for QEMU. Let me read through the details again.
The user is experiencing a continuous screen refresh when using QXL and enabling VDA Agent in their Windows 10 VM. They mention that as soon as they start up VDA-Agent, the screen flickers so much it's hard to use. When VDA-Agent isn't installed or when they disable it, the same issue happens. However, if they don't install the QXL driver on the guest side, the flicker doesn't occur.
The workaround involves turning off "Resize Guest to Match Window Size" and enabling scaling in Spice-GTK. They also note that their QXL driver shows 8GB of video memory, which seems unusual.
Looking at the possible categories: mistranslation, assembly lowering, device, graphic, socket, network, KVM, boot, vnc, debug, files, permissions, performance, kernel, peripherals, hypervisor, and other.
The issue is related to screen flickering, which sounds like a graphics problem. The QXL driver is involved, so that points towards the graphics category. Additionally, VDA-Agent is part of Spice's graphical remote access tools, which further ties it to graphics handling.
I don't think this is a translation error because it's not about source-to-target mapping in user-mode. It's more about how the display is being handled, especially since the QXL driver and VDA-Agent are both related to spice graphical features.
So, putting it all together, the bug report seems to fall under the 'graphic' category.
</think>
The issue involves screen flickering when using the QXL driver with VDA-Agent, pointing towards a graphics-related problem. Therefore, the category is:
**graphic**
|