1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Okay, so I have to classify this bug report into one of the given categories for QEMU. Let me read through the problem again. The user mentions that after live migration using virt-manager or virsh, when they shut down the guest VM from the OS, the guest becomes undefined on the host and the XML config is lost.
First, I need to understand what each category means. The options are mistranslation, assembly, other, device, graphic, socket, network, KVM, boot, vnc, debug, files, permissions, performance, kernel, peripherals, hypervisor.
The bug seems related to how the VM is handled after migration. Live migration usually involves moving a running VM from one host to another without downtime. If after shutdown the guest becomes undefined and XML config lost, it's likely an issue with how the hypervisor (QEMU/KVM in this case) manages the VMs.
Looking at the symptoms: no errors during migration except losing a packet, but upon shutdown, the VM disappears. This could be related to how the hypervisor cleans up resources or if there's a misconfiguration causing it not to properly handle the state post-migration and shutdown.
Possible categories: The issue isn't about translation (mistranslation) or assembly lowering (assembly). It doesn't seem like a network issue because the packet loss is minimal. The problem occurs with virsh and virt-manager, which are tools for managing KVM/QEMU VMs, so it's likely under the hypervisor category since that's the component responsible for running and managing VMs.
I don't see it fitting into other categories like files or permissions; it's more about the state management of the VM. So the most appropriate category is hypervisor.
</think>
hypervisor
|