1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
|
<think>
Okay, so I need to classify this bug report for QEMU. The user mentioned that QEMU 2.10.0 can't boot Windows 10 and Windows Server 2016; it hangs during the boot process. Downgrading to version 2.9 fixes the issue.
Looking at the setup details, they're using various QEMU options like accel=kvm, pc-q35-2.8 machine type, and multiple devices such as VirtIO network, USB, VGA, etc. The problem seems related to booting a specific OS version.
The categories provided include things like mistranslation, assembly lowering, device, graphic, socket, network, KVM, boot, VNC, debug, files, permissions, performance, kernel, peripherals, hypervisor.
Since the issue occurs during boot and is resolved by downgrading QEMU, it's likely a problem with how QEMU handles the boot process for newer Windows versions. It could be related to KVM acceleration or the machine configuration (like pc-q35-2.8). Alternatively, perhaps there's an issue with device emulation.
The mention of KVM in the setup suggests that the hypervisor is involved, but since it's hanging during boot, maybe it's a problem with the initialization process. Alternatively, it could be related to network or display settings, but I'm not sure.
Another thought: The pc-q35-2.8 machine type might not fully support newer Windows versions in QEMU 2.10.0. Or perhaps there's a regression in how certain devices are handled. Since the user is using VirtIO and other modern device models, maybe that's where the issue lies.
Wait, the category "boot" seems relevant here because the problem occurs during the boot process of the guest OS. So this would fall under the "boot" category.
</think>
boot
|