blob: ae3b92214f4453bb4de450691af3cf3c1533e03a (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
|
<think>
Alright, let me try to figure out how to classify this bug report. The user mentioned they're using macOS with QEMU and the HVF accelerator. They set up a simple configuration but when they enable HVF, their WinXP VM hangs during boot. Without HVF (using TCG), it works fine.
Looking at their analysis, they pointed out two commits: b7394c8394 which replaced explicit VMCS checks with hflags/hflags2, and 92d5f1a414 which changed the behavior of these flags. They believe that this second commit broke HVF's interrupt handling, causing WinXP to fail.
They also noted that KVM and HAXM weren't affected because they still do explicit checks, but HVF relies on the new approach which is now flawed.
So, the issue seems related to how QEMU handles virtualization flags when using HVF. Since it's about interrupt handling and hflags, which are part of the hypervisor's management, I think this falls under the 'hypervisor' category.
</think>
hypervisor
|