virtualbox.org

VirtualBox-4.3.18-96516-Win.exe
vm is sysresccd from sysresccd.org running as bootable ISO.

Failed to open a session for the virtual machine sysrescueccd.

VT-x is being used by another hypervisor. (VERR_VMX_IN_VMX_ROOT_MODE).

VirtualBox can't operate in VMX root mode. Please close all other virtualization programs. (VERR_VMX_IN_VMX_ROOT_MODE).

Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

so... why is this? I had thought with a windows box I could run as many VM protgrams as I wanted. virtual pc running XP Mode is running alongside virtualbox, and after error about audio, vbox come up with the above error. please fix so I can run both for productivity's sake I have 12 threads and 64GB ram, this is like working in the stone age.

jmichae3 wrote: so... why is this? I had thought with a windows box I could run as many VM protgrams as I wanted. virtual pc running XP Mode is running alongside virtualbox, and after error about audio, vbox come up with the above error. please fix so I can run both for productivity's sake I have 12 threads and 64GB ram, this is like working in the stone age.

Then you thought incorrectly. There is nothing to "fix". Generally on any platform you can only run one virtualization program at a time. If you want to install and run guests in VirtualBox, you need to disable Hyper-V.

Most hypervisors can play well with each other these days but not Hyper-V. Microsoft locks VMX for explicit use and does not share or play well with others. If you need a fix you need to get Microsoft to stop using the lock and start playing well with others.

I should have limited my statement to the Windows platform. However, it's only been relatively recently on the Mac platform that hypervisors such as Parallels Desktop and VirtualBox played nice.

Not sure what happens in Linuxland.