1 | <?xml version='1.0' encoding='UTF-8'?>
|
---|
2 | <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
|
---|
3 | <topic xml:lang="en-us" id="ts_win-guest-bluescreen">
|
---|
4 | <title>Windows Bluescreens After Changing VM Configuration</title>
|
---|
5 |
|
---|
6 | <body>
|
---|
7 | <p>
|
---|
8 | Changing certain virtual machine settings can cause Windows
|
---|
9 | guests to fail during start up with a bluescreen. This may
|
---|
10 | happen if you change VM settings after installing Windows, or if
|
---|
11 | you copy a disk image with an already installed Windows to a
|
---|
12 | newly created VM which has settings that differ from the
|
---|
13 | original machine.
|
---|
14 | </p>
|
---|
15 | <p>
|
---|
16 | This applies in particular to the following settings:
|
---|
17 | </p>
|
---|
18 | <ul>
|
---|
19 | <li>
|
---|
20 | <p>
|
---|
21 | The ACPI and I/O APIC settings should never be changed after
|
---|
22 | installing Windows. Depending on the presence of these
|
---|
23 | hardware features, the Windows installation program chooses
|
---|
24 | special kernel and device driver versions and will fail to
|
---|
25 | startup should these hardware features be removed. Enabling
|
---|
26 | them for a Windows VM which was installed without them does
|
---|
27 | not cause any harm. However, Windows will not use these
|
---|
28 | features in this case.
|
---|
29 | </p>
|
---|
30 | </li>
|
---|
31 | <li>
|
---|
32 | <p>
|
---|
33 | Changing the storage controller hardware will cause bootup
|
---|
34 | failures as well. This might also apply to you if you copy a
|
---|
35 | disk image from an older version of Oracle VM VirtualBox to a new
|
---|
36 | virtual machine. The default subtype of IDE controller
|
---|
37 | hardware used by Oracle VM VirtualBox is PIIX4. Make sure that the
|
---|
38 | storage controller settings are identical.
|
---|
39 | </p>
|
---|
40 | </li>
|
---|
41 | </ul>
|
---|
42 | </body>
|
---|
43 |
|
---|
44 | </topic>
|
---|