Hyper-V's VM in Workstation 8

[kketbb]

I need some help here. I have followed the exact same method from this "http://www.vladan.fr/vmware-workstation-8-how-to-run-hyper-v/#ixzz1kF7sBHay", Enabled  the Virtualize Intel VT-x/EPT, edited the .vmx file and tried different  combination of 2-1 / 1-2 CPU core, have sufficient RAM of 3GB and 60GB  of HDD space on my HyperV Windows 2008 R2 server.

Using VMware Workstation 8
Have Compatible hardware CPU Intel Core i2500 not the K one and a motherboard MSI z68A-G43 (G3).

Have enabled Intel Virtualisation Technology and Intel VT- D tech in BIOS.

For some reason I just cannot get the VM to start up on the hyper-v server.

‘New Virtual Machine’ could not initialize.
‘New Virtual Machine’ could not initialize. (Virtual machine ID 7DF06815-6A2C-424E-8E83-046264ACC541)

[jmtella]

http://communities.vmware.com/docs/DOC-8970

[continuum]

Hi
it would help if you post a vmware.log from that VM so that we can check your config

[kketbb]

Thanks for the link dude, but I have done that "as mentioned Intel VT enabled setting for the VM in CPU section".

Log file has been attached.

Thanks

[continuum]

that run of the VM was started from a suspended state.
Do you get the same problem if you do a fresh start ?

why do you use
monitor.virtual_exec = "automatic"
and not
monitor.virtual_exec = "hardware"

[kketbb]

Thanks for speedy reply.

Yes I have tried to fully switch on and off the server test start the VM, but results are same.

Have tried to change hyper-v VM's RAM setting to 128mb and 10GB HDD, also have tried remove each interface to see if they make any different but no

Not sure why monitor.virtual_exec = "automatic" lol, but I have changed to hardware and re-tested, again same result.

I have setup another hyper-V server Windows 2008 R2 server in Workstation, again... VM cannot initialize *wack myself*

On the other note this command seems " hypervisor.cpuid.v0 = “FALSE” " not valid, got a pop up message when VM booting up.

I have modify the file again and took them quatation marks off hypervisor.cpuid.v0 = FALSE, now VM start up fine no warning message.

http://dl.dropbox.com/u/4251080/vm.png

Source: http://www.veeam.com/blog/nesting-hyper-v-with-vmware-workstation-8-and-esxi-5.html

[continuum]

are all the Hyper-V servcies running ?
can you run
net start vmms ?

[kketbb]

Cmd said the requested service has already been started.

Wondering if Windows 2008 R2 "Enterprise" version make any difference?

[admin]

Some versions of Hyper-V don't like Sandy Bridge CPUs.  Try disabling XSAVE:

cpuid.1.ecx="----:-0--:----:----:----:----:--h-:----"

(Don't use smart-quotes.)

[continuum]

here I use
hypervisor.cpuid.v0 = "FALSE"
without complaints

make sure you type that line yourself - do NOT copy it from a post here - then often the quotes are invalid.

I am running a 2008 R2 Enterprise here and HyperV VM work nice.

I attach my vmx so that you can compare values

[kketbb]

I have added this cpuid.1.ecx="----:-0--:----:----:----:----:--h-:----" to .vmx file and tried to type those commands by hands, still getting the same error.

I have compared the .vmx file and I cannot find much differenc with mine.

[admin]

Your configuration file is missing:

hypervisor.cpuid.v0 = "FALSE"

[kketbb]

sorry uploaded the wrong one, I was messing with the command.

if the configuration file without the command the error I will get is "unable to allocate partition" and "VM could not initalize" but with the command inserted in the configuration file, the error only prompt "VM could not initalize".

[admin]

Have you installed Service Pack 1?  http://www.microsoft.com/download/en/details.aspx?id=5842.

[kketbb]

Good point! Cheers for the link!

My server has the latest updates but not SP1, for some reason Windows Updater did not receive Service Pack 1 from Microsoft?

I never know you have to manually download and install Service Pack for server.

This might be the problem! LETS HOPE :smileygrin:

Will report back soon

[admin · Accepted solution]

Without SP1, I believe you also have to hide AVX:

cpuid.1.ecx="---0:-0--:----:----:----:----:--h-:----"

[kketbb]

The Virtualception WORKED!!!

Just curioes where did you get those information from?

Will definilty share this info on the web!

Massive Thanks Jim!

[admin]

kketbb wrote:

Just curioes where did you get those information from?

I ran into the same problem about a year ago.  I just couldn't remember the specifics.  I was able to dig up the information from our internal bug database, but it took a few searches to uncover what I wanted.

[admin]

Here is a blog posting from the Microsoft Windows Virtualization Product Group that discusses the issue:

http://blogs.technet.com/b/virtualization/archive/2011/04/30/hyper-v-r2-sandy-bridge-and-avx.aspx

[rickyelqasem]

I noticed you posted this too on the original Veeam site. I think the answer to you problem is you have the Sandy Bridge chipset and in the Veeam thread Chris Dearden suggested a hotfix from Microsoft. Please let me know if this helps?