Unable to run multiple VMs with AMD-V properly -> fixed in SVN/1.6.6

[concord]

Originally posted on forum. I have tried to remove guest additions but nothing changes. Once a Windows VM starts when another presents already, the VM will hangup/BSOD. (VBOX GUI still alives)

===== Just updated to 1.6.2. With AMD-V turned on, I can run any one of the VMs I have smoothly. However if I tried to open another Windows VM, all Windows VMs (new and current) will freeze or BSOD. If starting ubuntu VM and Windows VM simutaneously (with AMD-V), it's highly possible to have some error message during ubuntu initialization.

All the VMs I have can run properly without AMD-V. It seems that the current AMD-V support still have some problems dealing with multiple instances.

OS: Vista x64 HW: Phenom 9550, 790FX, 8G DDR2.

[concord]

Two Win2K VMs start simutaneously and BSOD while initializing

[Frank Mehnert]

Please check if VirtualBox 1.6.4 fixed the problem for you (there were several fixes regarding VT-x and AMD-V in 1.6.4).

[Marko]

Hi guys,

I have the same problem running VBox 1.6.4 x64 ver on XP Pro x64. Single VM with AMD-V enabled runs smoothly, but immediately after another starts to boot... BSODs and blackouts on both guests. No impact on host. Every other well-know software reports that host system IS AMD-V capable and operational.

BR,

Marko

[virtualboy]

Hi,

I got exactly the same problem, except that i dont run the same OSs
Host is Vista X86 (32bits) and the 2 Vms are XP sp3
hardware is Turion X2, 2Go DDR2
i was using VirtualBox 1.6.2,
so when 1.6.4 came, i was glade to see the spec about improved amd-v support,
but 1.6.4 hang like 1.6.2 did ;(

keep up the good work, guys.

[Sander van Leeuwen]

I've just fixed another issue that would show up when running multiple VMs. Please try again with 1.6.6 (due out soon hopefully).