XP x64 guest (on XP x64 host) fails if more than 1 virtual CPU enabled -> retry with 3.1.4

[Kurt Frank]

Exact same install media with exact same VM settings except:

If only one virtual processor is enabled the system installs and (as far as I can tell) runs flawlessly.

If two virtual processors are enabled the system still installs up to the second reboot (after the GUI install section).

However after that the system either simply fails to start (the white progress bar freezes or just a blank screen) or crashes with seemingly random BSODs (the one I remember was System Service Exception).

[Kurt Frank]

It would appear that the problem is not restricted to XP x64 guests.

The same problem is apparent with Windows 2000 guests.

[Jason Elwell]

I see random BSODs with a Windows Server 2008 x64 guest running on a Windows Server 2008 x64 host when virtual CPUs are set to "2". Setting to "1" makes the BSODs disappear.

[Kurt Frank]

Problem remains with version 3.0.4

[stevensm]

Same problem with Windows 7 64 Bit and windows guests (XP, 2003, 2008, Windows 7) with more than 1 vCPU. During the installation of the windows guest there are random BSODs.

[Gibraltar]

Also experiencing this problem (host Win7 Ultimare RTM x64 and guest Win SBS 2008). Didn't try to limit to only one CPU (will try at home), but did try disabling the network config - no more BSOD, but also no network (kinda defeats the purpose of installing a Windows Server :)

[Gibraltar]

I've just confirmed that the same VM (Windows SBS 2008) is now stable with only one core enabled. Seems to be a problem related - 64bit host and SMP, hope it gets fixed soon :)

[Maik van der Gaag]

I'm having kind of the same problem. My host OS is Windows 7 x64 and the guest OS is windows server 2008 R2 x64.

When I assign two cpu to the virtual is sometimes hangs (Screen goes completly black. When I look in the task manager virtualbox is using 100% of the cpu) when I try to install something like SQL Server 2008. When using 1 cpu everything goes fine.

Is this something that can be fixed?

[Gibraltar]

Possible solution - new test build available: ​http://www.virtualbox.org/ticket/4947

Will test tonight and post results when done, fingers crossed ;)

[Gibraltar]

Sorry to report the test build didn't help with my problem. So reverted to using only one core. Will keep waiting for a version that works with my setup :)

[Burns Boaz]

I'm also having this problem; host is Vista x64, guest is Windows7 x64. Please fix as soon as possible. Thanks.

[Blake Blackshear]

I am experiencing the same issue Win7RTM x64 host Server 2008 x64 guest. Mine works fine for a short time, and then VirtualBox.exe on the host goes up to 99% cpu usage and the vm is black. This is a feature of virtualbox that sets it apart from other virtualization, and it would be great if it could be fixed.

[Blake Blackshear]

This is in 3.0.8 as well.

[Kurt Frank]

It would seem that version 3.0.10 has licked this problem, at least for me.

[Sander van Leeuwen]

Thanks for the feedback.

[Maik van der Gaag]

I also thought it was fixed but when I tryed to install the Visual Studio Beta 2010 on my virtual of Windows Server 2008 R2 the screen went black again :s (2 cpu's enabled).

Can I provide you guys with information so that the ticket can be fixed?

[Technologov]

Since Windows XP x64 and Windows Server 2003 x64 are based on the same kernel (NT 5.2), this bug may be related bug #5385

-Technologov

[Sander van Leeuwen]

Retry with 3.1.4. That version will include an important stability fix for SMP guests.

[Sander van Leeuwen]

Please check if 3.1.4 beta 1 solves the problem: ​http://forums.virtualbox.org/viewtopic.php?f=15&t=27300

[Sander van Leeuwen]

Please reopen if it still occurs with 3.1.4.

[Kurt Frank]

Same old problem with version 3.1.4, log attached, reverting to 3.0.12

[Kurt Frank]

3.1.6 appears to have fixed the problem (touch wood).

[Sander van Leeuwen]

Thanks for the feedback.