VB-2.1.0 crashed on starting 2nd guest while 1st is being installed with VT-x and AMD-V enabled (Mac OS X)

[synack]

Host: Mac OS X 10.5.6 with 2gb RAM

1. Started installation of Ubuntu-8.04.1 (64-bit) with VT-x and AMD-V enabled in options.
2. Half-way the installation decided to try PXE boot and get connected to my LTSP server.

Complain/error: An active VM already uses Intel VT-x hw accel. it is not allowed to simultaneously use software virtualization.

Settings of the 2nd guest:

• Base_memory = 128mb
• os type = gentoo
• video memory = default value
• boot order = network
• acpi = enabled
• io acpi = enabled
• vt-x/amd-v = disabled
• pae/nx = enabled
• 3D accel. = disabled

From the crash log:

Process:         VBoxSVC [8165]
Path:            /Applications/VirtualBox.app/Contents/MacOS/VBoxSVC
Identifier:      VBoxSVC
Version:         ??? (???)
Code Type:       X86 (Native)
Parent Process:  launchd [1]

Date/Time:       2008-12-18 09:57:44.103 +0800
OS Version:      Mac OS X 10.5.6 (9G55)
Report Version:  6

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000c01de1cf
Crashed Thread:  9


Thread 9 Crashed:
0   VBoxXPCOM.dylib                     0x005e3fbc pt_PostNotifyToCvar + 14
1   VBoxXPCOM.dylib                     0x005e4600 PR_NotifyAll + 22
2   VBoxXPCOMIPCC.dylib                 0x01130a02 DConnectWorker::Run() + 134
3   VBoxXPCOM.dylib                     0x005d02e3 nsThread::Main(void*) + 45
4   VBoxXPCOM.dylib                     0x006038dd _pt_iprt_root + 141
5   VBoxRT.dylib                        0x005114c0 rtThreadMain + 64
6   VBoxRT.dylib                        0x0053b334 rtThreadNativeMain(void*) + 132
7   libSystem.B.dylib                   0x91992095 _pthread_start + 321
8   libSystem.B.dylib                   0x91991f52 thread_start + 34

PS: If I enable "VT-x and AMD-V", I can start that guest (tried with another 32-bit guest installed earlier)

[Frank Mehnert]

Indeed it should not crash but it is not possible to run two concurrent VMs, one with VT-x enabled and another one with VT-x disabled.

[Frank Mehnert]

Please check the latest release 2.2.2 and reopen this ticket if the problem persits. Starting with VBox 2.2.0 we allow to run VT-x and non-VT-x VM sessions in parallel.