VirtualBox

Ticket #12240 (closed defect: fixed)

Opened 22 months ago

Last modified 15 months ago

Windows ME BlueScreen during boot after update -- again as of VBox 4.3.8 [FIXED IN SVN]

Reported by: S.Seide Owned by:
Priority: major Component: other
Version: VirtualBox 4.3.8 Keywords:
Cc: Guest type: Windows
Host type: Linux

Description

After updating VirtualBox from version 4.2.18 to 4.3.0 my Windows ME VM does not start anymore. During boot it crashes with an blue screen:

While initializing device NTKERN Windows protection error. You need to restart your computer. System angehalten.

Switching back to VirtualBox 4.2.18 the same VM starts again without any problem.

VirtualBox 4.3.0-89960~Ubuntu~quantal, deb-Package from Oracle

Host: Linux 3.5.0-42 (x86_64), Xubuntu 64Bit

Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz

Guest: Windows Millenium Edition, all patches installed

512MB RAM, 1 CPU, VT-x, Nested Paging, PAE/NX, no IO-APIC

Attachments

VBox.log Download (90.7 KB) - added by S.Seide 22 months ago.
VirtualBox Logfile
BOOTLOG-VBOX430-Crash.txt Download (7.8 KB) - added by S.Seide 22 months ago.
WinME BOOTLOG.TXT - Crash with VBOX 4.3.0
BOOTLOG-VBOX4218-OK.txt Download (59.2 KB) - added by S.Seide 22 months ago.
WinME BOOTLOG.TXT - normal start after downgrade to VBox 4.2.18
VBox.2.log Download (68.9 KB) - added by hqngl 21 months ago.
VBox.log of BSOD in Windows ME on Xubuntu 13.10 x64 Host
Windows ME-2014-04-06-10-15-18.log Download (83.5 KB) - added by scop 16 months ago.
VirtualBox 4.3.10 Windows ME BSOD log from a Fedora 20 x86_64 host
VBox.3.log Download (79.6 KB) - added by Andreu 16 months ago.
Blue screen installing Windows 8.1 Pro (64) on VirtualBox 4.3.10. Host is Ubuntu 13.10 (64 bits)

Change History

Changed 22 months ago by S.Seide

VirtualBox Logfile

Changed 22 months ago by S.Seide

WinME BOOTLOG.TXT - Crash with VBOX 4.3.0

Changed 22 months ago by S.Seide

WinME BOOTLOG.TXT - normal start after downgrade to VBox 4.2.18

comment:1 Changed 21 months ago by Petr Vones

See #12227

comment:2 Changed 21 months ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

Should be fixed in VBox 4.3.2.

comment:3 Changed 21 months ago by hqngl

Persists in 4.3.2

comment:4 Changed 21 months ago by hqngl

  • Status changed from closed to reopened
  • Resolution fixed deleted

comment:5 follow-up: ↓ 6 Changed 21 months ago by frank

hqngl, please attach a VBox.log file from such a VM session running on VBox 4.3.2.

Changed 21 months ago by hqngl

VBox.log of BSOD in Windows ME on Xubuntu 13.10 x64 Host

comment:6 in reply to: ↑ 5 Changed 21 months ago by hqngl

Replying to frank:

hqngl, please attach a VBox.log file from such a VM session running on VBox 4.3.2.

Attached log from Xubuntu 13.10 x64 host.

Some additional info on the bug:

  • Same error with Windows 7 x64 Host
  • Only occurs if hardware virtualization is enabled
  • VirtualBox until 4.2.8 works fine
  • Bug occurs first in 4.3.0 Beta 1

Thanks for looking into this issue.

comment:7 Changed 21 months ago by klaus

That line explains it all...

00:00:05.034819 IEM: rdmsr(0x1b) -> GP(0)

The guest OS accesses accessing IA32_APIC_BASE_MSR, and VirtualBox 4.3 doesn't let it. So this is one of the issues where the new checks are too restrictive.

comment:8 Changed 21 months ago by bird

  • Status changed from reopened to closed
  • Resolution set to fixed
  • Summary changed from Windows ME BlueScreen during boot after update from 4.2.18 to 4.3.0 to Windows ME BlueScreen during boot after update from 4.2.18 to 4.3.0 - FIXED IN SVN

Bug in the apic device emulation. Fixed will be shipped in 4.3.4.

comment:9 Changed 16 months ago by scop

  • Status changed from closed to reopened
  • Resolution fixed deleted

I'm seeing the exact same issue with VirtualBox 4.3.10 on a couple of Fedora 20 hosts, one 32-bit and another 64-bit. Disabling hardware virtualization works around it.

Changed 16 months ago by scop

VirtualBox 4.3.10 Windows ME BSOD log from a Fedora 20 x86_64 host

comment:10 Changed 16 months ago by kjonca

I can confirm this issue in 4.3.10. I *think* than in 4.3.6 worked properly.

comment:11 Changed 16 months ago by frank

  • Version changed from VirtualBox 4.3.0 to VirtualBox 4.3.8
  • Summary changed from Windows ME BlueScreen during boot after update from 4.2.18 to 4.3.0 - FIXED IN SVN to Windows ME BlueScreen during boot after update -- again as of VBox 4.3.8

comment:12 Changed 16 months ago by Andreu

I also have this issue with VirtualBox 4.3.10 on Ubuntu 13.10 (64 bits). Guest OS is Windows 7 Prof (32 bits). Disabling VT-x solves the problem.

comment:13 Changed 16 months ago by foulsoft

Well done Andreu,

Disabling VT-x solves the problem also for me Windows7 Prof (64 bits)). Thank you :)

comment:14 Changed 16 months ago by foulsoft

Well done Andreu,

Disabling VT-x solves the problem also for me Windows7 Prof (64 bits)). Thank you :)

Just I forgot one thing to say : it was for Windows7 Prof (64 bits) Guest OS is WindowsME (Windows Millenium Edition) where I usually faced NTKERN error... :)

comment:15 follow-up: ↓ 16 Changed 16 months ago by frank

Disabling VT-x is only a workaround. This has to be properly fixed.

comment:16 in reply to: ↑ 15 Changed 16 months ago by Andreu

Replying to frank:

Disabling VT-x is only a workaround. This has to be properly fixed.

I agree this must be properly fixed. The problem also occurs with guest Windows 8.1 (64 bits) and I can't disable VT-X for this OS.

comment:17 Changed 16 months ago by frank

Please attach a VBox.log file for your Windows 8.1 guest. I think this problem is different from the Windows ME problem.

Changed 16 months ago by Andreu

Blue screen installing Windows 8.1 Pro (64) on VirtualBox 4.3.10. Host is Ubuntu 13.10 (64 bits)

comment:18 Changed 16 months ago by Andreu

Doing a little search, I found that maybe my issue is related to #12876.

comment:19 Changed 15 months ago by bird

  • Status changed from reopened to closed
  • Resolution set to fixed
  • Summary changed from Windows ME BlueScreen during boot after update -- again as of VBox 4.3.8 to Windows ME BlueScreen during boot after update -- again as of VBox 4.3.8 [FIXED IN SVN]

Next release contains a workaround both issues reported here.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use