1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
|
<think>
Alright, let me try to figure out the category of this bug report. The user mentioned an issue with QEMU where saving a VM (savevm) fails when a CD is inserted. The error message says, "Device '%s' is writable but does not support snapshots."
First, I need to understand what's happening here. It looks like when they try to save the VM state, QEMU is encountering an issue with a device that's supposed to be writeable but doesn't support snapshots. They tried setting "-drive ...,readonly=on,snapshot=off" but it didn't help.
Looking at their hint from blockdev.c, there's a patch where dinfo->bdrv->read_only is set to 1 for certain interfaces. This suggests that the problem might be related to how devices are marked as read-only or writable, and whether they support snapshots.
The error message specifically mentions that the device is writable but doesn't support snapshots. So it seems like there's a misconfiguration where the device is being treated as writable when it shouldn't be, or the snapshot functionality isn't properly handling certain devices.
Now, considering the possible categories: mistranslation relates to incorrect semantic mapping in user-mode, which might not fit here. Assembly lowering (assembly) is about code generation, which doesn't seem relevant. Other is a catch-all, but perhaps there's a more specific category.
Device seems like a strong candidate because it's directly related to hardware emulation and device handling. The issue is about how the CD-ROM device is being treated by QEMU—whether it's writable and supporting snapshots.
Looking at other categories: graphic would be for display issues, network for connectivity, KVM for hypervisor issues, etc. This seems more about device configuration and behavior.
Therefore, the most appropriate category here is "device" since the problem revolves around how a specific device (the CD-ROM) is handled in terms of read-only status and snapshot support.
</think>
device
|