VM Crashing almost instantly! Please help!

Discussions related to using VirtualBox on Windows hosts.
Post Reply
NICG_Tech
Posts: 1
Joined: 5. Oct 2012, 01:59

VM Crashing almost instantly! Please help!

Post by NICG_Tech »

Greetings!!

I've attached the log file.....

I am attempting to install a Windows Server 2008 R2 VM on a similar OS Host.

I ran into an issue with Hyper-V as the processors are not Data Execution Prevention capable.
I have confirmed that that they are Virtualization capable and have enabled the same in BIOS. (Performed a full shutdown afterwards and power on via the DRAC)

After removing the Hyper-V Role, and rebooting.....I've installed VirtualBox.
Attempting various settings in regards to the Processor, I get 2 results.
The first result is a message stating that Virtualization technology is not enabled. This message is received immediately.
The 2nd result is a bit different. The machine will boot and start the loading from the Windows installation media. It will get as far as selecting to "Install Windows" and then crash.

The processors are Intel Xeon E5310 models

If anyone can assist, I would be incredibly appreciative!!!
Thank you in advance!!

David
Attachments
VBox_10042012.zip
(43.71 KiB) Downloaded 4 times
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: VM Crashing almost instantly! Please help!

Post by mpack »

VBox.log wrote: 00:01:28.711 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:01:28.711 !!
00:01:28.711 !! Guru Meditation -4010 (VERR_VMX_VMXON_FAILED)
00:01:28.711 !!
00:01:28.711 !!
00:01:28.711 !! {mappings, <NULL>}
00:01:28.711 !!
00:01:28.711
I would reduce the VM memory below 8GB. In fact I would make it 4GB.

Of course, VirtualBox can't use VT-x if some other app (Hyper-v?) is already using it, or if it is disabled in the host BIOS. The wording of the error message is new to me but it clearly was not able to get VT-x going.

Crashing when the VM accesses the virtual hdd may be a result of using the wrong disk controller. I would try IDE.

ps. I would also convert the disk files from VHD to the more reliable VDI, asap.
Post Reply