blob: ff6b34d3efcfc340f60e44cd3fc005b85880c899 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
|
<think>
Okay, I need to classify this bug report into one of the given categories for QEMU. Let me read through the problem carefully.
The issue is about virtual monitors not being connected until viewed in a front-end like the GUI. The user attached a virtio GPU and observed that the guest's DRM nodes (like card0-Virtual-1 to 4) are disabled by default. They only become enabled when the user switches to view them using the GUI.
The problem affects Weston, which doesn't initialize displays without monitors, causing system failures. The user tried command-line options but found none to force monitor attachment immediately. They also attempted using screengrab, which didn't work.
Looking at the steps to reproduce, it's clear that without user interaction through the GUI, the virtual displays remain disabled, leading to issues in automated environments like CI with egl-headless.
Now, considering the categories: Mistranslation relates to incorrect mappings but this is more about hardware setup. Assembly lowering isn't relevant here. Other could be a possibility, but I need to check specific categories.
The bug involves virtual GPUs and display handling, so 'graphic' seems appropriate since it's related to graphical output and display management in QEMU.
</think>
The issue pertains to how virtual displays are managed and connected within the guest OS when using a GPU. Since it's about the interaction between the virtual GPU and the DRM subsystem affecting display availability, the most fitting category is:
graphic
|