blob: 1d571a23411a73a1dbfdd9854b7d1d7433701c79 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
|
graphic: 0.968
device: 0.914
semantic: 0.838
architecture: 0.778
performance: 0.751
PID: 0.670
register: 0.604
user-level: 0.540
ppc: 0.528
peripherals: 0.526
boot: 0.512
debug: 0.506
permissions: 0.469
mistranslation: 0.408
network: 0.401
vnc: 0.398
assembly: 0.377
hypervisor: 0.376
socket: 0.373
VMM: 0.366
kernel: 0.349
risc-v: 0.344
arm: 0.331
x86: 0.316
TCG: 0.307
i386: 0.304
files: 0.288
virtual: 0.211
KVM: 0.066
Blue screen in Windows XP
Description of problem:
When starting the installation of Windows XP when using a virtioblk device you immediately get a bluescreen: `STOP: 0x000000A5 (0x00000002, 0x8A1A6008, 0xE1018808, 0x8A1B7F00)`. I think this happens even before it loads the SATA drivers that are slipstreamed in the ISO.
After a lot of Googling about this error 0x000000A5 I found some posts suggesting that changing the machine type from `q35` to `pc-q35-2.10` solves the issue. And it worked. Anything above 2.10 (for example 2.11) and the bluescreens return.
So I always used this solution, but in QEMU 9.1.0 it warns that `pc-q35-2.10` will be removed soon. This would mean there is no way anymore to install XP to a SATA disk unattendly.
Steps to reproduce:
1. Use a virtioblk disk and SATA drivers
2. Start the Windows XP installer
3. Bluescreen will appear
|