blob: f959b4c598e10874bb65c81fdbc7d43a617dacbf (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Alright, let's try to figure out which category this bug report falls into. The user is experiencing a blue screen when installing Windows XP using QEMU with avirtioblk device. They mention that changing the machine type from `q35` to `pc-q35-2.10` fixes it, but newer versions like 2.11 cause issues again.
First, looking at the categories: mistranslation is about incorrect semantic mapping in user-mode assembly. Assembly lowering is related to how code is translated into assembly. Other includes things not covered elsewhere. Then there are specific areas like device, graphic, socket, network, etc.
The blue screen occurs during the installation, suggesting a hardware or driver issue from the guest OS's perspective. Since they're using a SATA drivers slipstreamed in the ISO and virtioblk (which is a virtual block device), it might be related to how QEMU emulates the hardware.
They fixed it by changing the machine type, which implies it's a configuration or emulation issue. The warning about `pc-q35-2.10` being deprecated suggests that newer machine types might not support certain features needed for XP installation, possibly pointing towards compatibility in the hypervisor layer.
The problem seems to be related to how QEMU emulates hardware (like SATA controllers) when using virtioblk. Since this affects the installer's ability to load drivers properly, it's likely a device-related issue within the hypervisor or emulator setup.
</think>
device
|