1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
|
<think>
Alright, let's try to figure out the category for this bug report. The user mentioned that QEMU freezes on startup and uses 100% CPU. They noticed this started happening from version 0.13.0 onwards, while 0.12.5 works fine.
Looking at their test cases, they're trying different options like specifying the machine type (pc-0.12), various audio cards, and even a recent seabios build, but nothing works. The freeze occurs with both Windows and OpenBSD images, so it's not specific to any OS.
The symptoms point towards an issue during the startup process where QEMU isn't initializing properly, leading to 100% CPU usage. This suggests that something is causing an infinite loop or a deadlock in the initialization phase. Since they tried different configurations without success, it's likely a deeper issue within QEMU's core components.
The possible categories include things like mistranslation, assembly lowering, performance issues, hypervisor problems, etc. Given that it's freezing at startup and using all CPU, it doesn't seem to be an issue with device emulation or graphics because those would typically manifest later once the VM is running. Similarly, network or socket issues might cause hangs but usually not immediately on startup.
The fact that specifying a specific machine type (pc-0.12) didn't help indicates that it's more about how QEMU initializes its components. Mistranslation errors could cause incorrect mappings leading to hangs, especially if there's an issue in the way instructions are translated or hardware is emulated. However, without more details on the exact behavior during startup, it's a bit tricky.
Alternatively, performance issues might not directly cause a freeze but would affect responsiveness. Kernel or hypervisor problems could also lead to such freezes, as those components are critical for VM management. The high CPU usage suggests that QEMU is stuck in a loop waiting for something, possibly related to how the hypervisor interacts with the host OS.
Considering all this, the most fitting category seems to be 'hypervisor' because it's likely an issue within QEMU's core management of virtual machines, causing it to freeze during startup due to a problem in how it handles the VM initialization process.
</think>
hypervisor
|