1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Alright, let me try to figure out how to classify this bug report. The user mentioned an issue with QEMU using HAXM (Intel Haxm) on Windows 10 as a host and a Windows 7 guest. They're saving a VM state with savevm, but when they load it again, the guest crashes or freezes.
The key details here are that the registers saved and loaded aren't matching. The user looked into the code and found that hax_arch_get_registers reads the registers from HAXM and is called during synchronization. They noticed this function was hit only once during the guest OS boot, which seems off because if it's only called once, maybe the state isn't being properly managed after resuming.
So, looking at the categories provided: mistranslation, assembly lowering, device, graphic, socket, network, KVM, boot, vnc, debug, files, permissions, performance, kernel, peripherals, hypervisor.
The issue seems to be related to how QEMU interacts with HAXM, specifically when saving and loading VM states. Since HAXM is a hypervisor, the problem likely stems from incorrect handling of register states during these operations. The registers aren't being read properly when resuming, which points towards an issue in the hypervisor's interaction.
Therefore, the most fitting category would be "hypervisor" because it relates to how QEMU and HAXM handle VM state management.
</think>
hypervisor
|