The full content of this no-can-do error message is shown here:
Here are the basics about my Mac:
I do also run the Parallels Desktop for Mac VM, with a Win XP guest OS.
This fatal error occurs regardless of whether the Parallels VM is running or not. The same is true whether I am running the 32-bit imported appliance (as shown above) or the 64-bit one. This appliance has Ubuntu running as the guest OS on VirtualBox's VM.
Both VirtualBox and the imported appliance are configured with their default preferences and settings, respectively.
Does anybody have any insight as to what is going on, and how to resolve it?
Thank you and best regards,
Bob
VirtualBox can't operate in VMX root mode.
-
Bob Newby
- Posts: 2
- Joined: 5. Dec 2011, 00:14
- Primary OS: Mac OS X other
- VBox Version: OSE Debian
- Guest OSses: Ubuntu
VirtualBox can't operate in VMX root mode.
Last edited by Bob Newby on 5. Dec 2011, 01:02, edited 1 time in total.
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: VirtualBox can't operate in VMX root mode.
From what I read here you need to run the Repair Disk Permissions using DIsk Utility on your MAC host then it should work.
-
Bob Newby
- Posts: 2
- Joined: 5. Dec 2011, 00:14
- Primary OS: Mac OS X other
- VBox Version: OSE Debian
- Guest OSses: Ubuntu
Re: VirtualBox can't operate in VMX root mode.
Hi Perry,Perryg wrote:From what I read here you need to run the Repair Disk Permissions using DIsk Utility on your MAC host then it should work.
Repair Disk Permissions makes no difference. The error remains in play.
Bob
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: VirtualBox can't operate in VMX root mode.
Then you actually do have something using the VT-x/AMD-v feature such as another virtualizer. This can not happen as it would trash the contents on the HDD.
Make sure that the other virtualizer is not active.
Make sure that the other virtualizer is not active.