1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Okay, so I'm looking at this bug report about QEMU not booting Windows 8 properly on Core2Duo machines with certain kernels. The user mentioned that when using KVM with QEMU versions 1.7.0, 2.0.0, or 2.1.0 on a Core2Duo with kernel 3.4.67 or 3.10.12, the guest OS freezes during boot. However, it works fine when using an older kernel (2.6.32.12) or when running on an i3/i5 CPU.
The user tried disabling networking and USB, which didn't help, so it's not a peripheral issue. They also changed the graphics card without success. The report suggests that the problem might be related to KVM/progressor incompatibility.
Now, looking at the categories provided: mistranslation, assembly, device, graphic, socket, network, KVM, boot, vnc, debug, files, permissions, performance, kernel, peripherals, hypervisor.
The issue is specifically with KVM and the host's CPU architecture (Core2Duo vs i3/i5). Since KVM is involved and the problem seems related to how the hypervisor interacts with the hardware under different kernels, it points towards a KVM-related bug. The fact that it works on newer CPUs but not Core2 Duo suggests an issue in how KVM handles certain processor features or virtualization extensions.
Therefore, the most fitting category here is "KVM."
</think>
The bug report describes an issue where QEMU with KVM fails to boot Windows 8 guests on Core2Duo machines running specific kernels (3.x), but works fine on i3/i5 CPUs or older kernels. The problem is suspected to be related to KVM/progressor incompatibility, which points directly to the hypervisor component.
**KVM**
|