VMs crashing with Win7 64 bit and Xeon E3-1245v3 (Haswell)

[SeniorSpielbergo]

i'm quite desperate because no vm is running on my new hardware, always going to meditation mode straight at the beginning. no difference if starting a new vm or using an existing one.
the new small workstation i build is as follows:

cpu: 1x intel xeon e3-1245v3 (haswell-architecture, p4600 graphics)
ram: kingston, 2x8 GB, 1600 MHz
mobo: asus p9d ws (c226 chipset)
hdd: Sata 1TB

host-os: win7 pro 64 bit (not activated yet)
guest-os: the same
vbox: 4.3.4r91027

for me it looks like hardware-problems but i have no idea. so far i tried several things: changing all kinds of vbox settings; checking bios settings; exchanging the mobo with an asus z87-a (z87 chipset); testing the cpu with the intel processor diagnostic tool; tried debian 7 64 bit and centos 6.4 as host-os; installed radeon 7750 graphics card; checked the cpu socket pins -> but no difference.

does anyone know, whether the cpu is the problem? or must win7 be activated? any idea or help would be great! thanks.

[mpack]

00:00:00.514762 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:00.514764 !!
00:00:00.514764 !! Guru Meditation -4000 (VERR_VMX_VMXON_FAILED)

Make sure you don't have any other VM platform running, in particular Hyper-v.

[SeniorSpielbergo]

the host os i installed from scratch and no further virtualization software was put on. hyper-v? i think it is not installed on win 7 by default.

[mpack]

I edited my previous message - I forgot to quote the error from the log. You can see that it's having trouble enabling VT-x. I believe this particular message happens when something else is using VT-x without fully locking it down. Look for the Hyper-v service being loaded at boot time (I agree that I don't think this is a default for Win7-64, unlike Win8-64), ditto system level debuggers, anything of that nature.

Problem with Haswell? That's always possible, but I'd want to see a few more reports - yours is the first I know of.

[gwardell]

Hi,

You have almost the exact same setup i have, except I'm using an AMD processor.

In my case I had set the guest to use two processors and it crashed when loading the OS. When I set it to use one processor it came up. Don't know if that will help you. See [ viewtopic.php?f=6&t=58992 ] for details.

Gary

[SeniorSpielbergo]

@gwardell: to change the number of cpus doesn't change anything.

@mpack: on other host os' the situation was the same so i don't think it's a problem with my host win7. but i will check tomorroww if i can find something.

[ManofGod]

Yes, I have Windows 8.1 x64 and recently upgraded to an AMD R9 290. I also have an FX8350 on an Asrock 990FX. It seems that setting it to one processor helped some as now Vista X64 and Win 7 X64 does not appear to crash. However, I also had to at least remove the experimental direct 3d stuff and disable 3d acceleration. (I am also using the Catalyse 13.11 Beta 11 ver 9.2.)

XP virtualized works fine though. This is kind of frustrating since I did not know if my system was unstable or what.

[SeniorSpielbergo]

after wasting too much time on this issue i changed the hardware. using a xeon e3-1245v2 (ivy bridge) plus gigabyte Z77-D3H mobo (Z77 chipset) now everything works. i have no idea what the problem was, hardware incompatibility or a cpu fault?

i do not recommend combining a xeon e3-1245v3 wih an asus z87-a or asus p9d ws board if using virtualbox!
regards.

[andersonas25]

Interesting I have a Win 7 64bit VM on a FC17 host. Asrock 990FX Extreme3 MB with AMD FX-8120 Eight-Core Processor. VM configured for two CPU's. This has been running for over a year no issues. Shortly after updating to 4.3.4 r91027 the VM would not boot, due to a fatal errors, after several attempts eventually it let me boot far enough to do a windows do a self repair it would boot. The next day same issue. After reading the above post I disabled one CPU in the VM and it came right up, after a self repair. In a few days I'll know if disabling the cpu helps. I do not have 3D video enabled.