blob: 9099e130b47513d791e9068526d4bb22c70b14da (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
|
<think>
Okay, I need to classify this bug report into one of the given categories. Let me start by reading through the problem description carefully.
The issue is that QEMU crashes during a warm reboot when using the virtio-gpu device with vga=775 on the Linux command line. The first boot works fine, but after a warm reboot, it crashes during boot. This happens when the VM is accessed remotely via virt-manager and VNC.
Looking at the provided code patch, it seems related to the virtio-gpu driver in QEMU. The commit message says: "virtio-gpu: disable scanout when backing resource is destroyed." The changes involve adding a loop that disables scanouts for each affected output when a resource is destroyed. This suggests the problem lies within how resources are managed, particularly regarding display outputs.
The categories I can consider are:
- **device**: Since it's related to virtio-gpu, which is a device in QEMU.
- **graphic**: The issue occurs during display-related operations, specifically with scanouts and image handling.
- **other**: If none of the specific categories fit.
I think "graphic" is the most appropriate category because the bug involves display resources and scanout functionality. The problem arises when managing the graphics output after a reboot, pointing to issues in how QEMU handles the graphical devices during their lifecycle (like destruction of resources).
The patch modifies how resources are cleaned up by disabling scanouts when they're destroyed. This directly impacts the graphical output handling, so it's not just a device issue but specifically about graphic operations.
</think>
graphic
|
