VM VirtualBox Manager has stop working

Discussions related to using VirtualBox on Windows hosts.
Post Reply
pieterselmec
Posts: 3
Joined: 14. Aug 2012, 15:42

VM VirtualBox Manager has stop working

Post by pieterselmec »

I am running windows server 2008 R2 Standard, with VirtualBox 4.1.18 with 2 Windows XP clients.

VirtualBox keeps on crushing. Even after rebooting the server.

Here are the log of one off the VirtualBox clients.

Windows event log.
Faulting application name: VirtualBox.exe, version: 4.1.18.0, time stamp: 0x4fce11de
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc0000374
Fault offset: 0x00000000000c40f2
Faulting process id: 0x18ac
Faulting application start time: 0x01cd7a1eaae087cc
Faulting application path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: fa8095f6-e614-11e1-ac75-68b599520114
Attachments
Pastel-2012-08-14-15-22-46.7z
(8.08 KiB) Downloaded 15 times
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: VM VirtualBox Manager has stop working

Post by Perryg »

Code: Select all

HWACCM: No VT-x or AMD-V CPU extension found. Reason VERR_VMX_MSR_LOCKED_OR_DISABLED
This usually means that you either do not have hardware-v enabled in your bios, or something is preventing it from being used.
Do you have hyper-v installed?
pieterselmec
Posts: 3
Joined: 14. Aug 2012, 15:42

Re: VM VirtualBox Manager has stop working

Post by pieterselmec »

There was actually two settings I had to change in the Bios. It seems to work now. Thank You.
michaln
Oracle Corporation
Posts: 2973
Joined: 19. Dec 2007, 15:45
Primary OS: MS Windows 7
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Any and all
Contact:

Re: VM VirtualBox Manager has stop working

Post by michaln »

Perryg wrote:

Code: Select all

HWACCM: No VT-x or AMD-V CPU extension found. Reason VERR_VMX_MSR_LOCKED_OR_DISABLED
This usually means that you either do not have hardware-v enabled in your bios, or something is preventing it from being used.
Do you have hyper-v installed?
But why would that make the VM manager crash? If it does, someone needs to open a ticket and supply a crash dump...
Post Reply