I've created a detailed step-by-step instructions (with screenshots and video) using all GA level code over here:
http://tinkertry.com/esxi-5-1-running-hyper-v-server-2012
using the "Core" version of the new Hyper-V, using tips and ideas from these forums and other sites about previous beta tests.
Here's the gist:
mce.enable = TRUE
hypervisor.cpuid.v0 = FALSE
featMask.vm.hv.capable = “Min:1″
vhv.enable = TRUE
I'm eager for any suggestions or alternative methods, but for now, this was the only way I could get it working in my own lab, figured others might want to try to replicate this excercise.
"Windows Hyper-V (unsupported)" is a guest OS selection available through the UI in Workstation 9. It sets the guestOS to "winhyperv". Though the Hyper-V OS selection is not available through the ESXi 5.1 UI, I happen to know that the support for it is still there.
pbraren wrote:
- tweak the VMX, adding these 4 lines:
mce.enable = TRUE
hypervisor.cpuid.v0 = FALSE
featMask.vm.hv.capable = “Min:1″
vhv.enable = TRUE
Alternatively, it should suffice to change the guestOS line to
guestOS = "winhyperv"
Very nice, that seems to work fine as well, and is even simpler than my method.
Here's what I did:
Cloned the VM.
Edited the cloned VM's vmx file, removing the 4 entries:
mce.enable = TRUE
hypervisor.cpuid.v0 = FALSE
featMask.vm.hv.capable = "Min:1";
vhv.enable = TRUE
then changed this line:
guestOS = "windows8srv-64"
to
guestOS = "winhyperv"
and the Hyper-V VM booted up and ran VMs without incident.
Thank you so much!
This "winyhyperv" parameter doesn't seem to be well documented anywhere. May I ask how you figured this out, and/or what are your sources, so I can give proper credit to you and others for this even simpler method of success?
"Windows Hyper-V (unsupported)" is a guest OS selection available through the UI in Workstation 9. It sets the guestOS to "winhyperv". Though the Hyper-V OS selection is not available through the ESXi 5.1 UI, I happen to know that the support for it is still there.
Thank you, VMware employee "jmattson", so nice to meet you in this wonderful way. I'm sure glad I posted in this forum (as are my blog's readers)!
And of course, I've now clicked on the Answered button for this post, crediting you for helping confirm the now-definitive (simpler) method of tweaking the vmx file (no vSphere Web Client UI required, and no VMware Workstation 9 UI required, just enable SSH and use WinSCP (or PuTTY and VI).
I realize VMware might not exactly publish sort of thing widely for any implied sort (I'm assuming there is none). But many of us are already used to being on entirely unsupported, that's kind of what my blog is all about anyway, so you could say that we're used it.
It's amazing what you can do using commodity/affordable hardware, instead of server-class gear, in the home-lab, saving a lot of $ and electricity. Admittedly, such projects don't necessarily save time. But it's getting easier and easier, a good thing for busy, self-training virtualization enthusiasts/IT professionals like me, who enjoy talking about such projects at user group meetings. So many others share this enthusiasm for pushing the boundaries of what's possible with virtualization.
Of these 2 methods (4 lines added, versus one line changed), does one method have a speed or capability advantage over the other?
I'm glad that you find this capability useful.
There is one line in the long version that isn't subsumed by guestOS type. That's featMask.vm.hv.capable = "Min:1". With this setting, VC knows that the VM requires virtualized HV, and it won't let you try to power on the VM on a host that isn't capable of virtualized HV support. VC doesn't know that guestOS="winhyperv" implies the same constraint. Without this line, you'll get a more unfriendly failure if you try to power on the VM on a host that can't handle it.
By the way, your post uses "smart-quotes" around "Min:1". Smart-quotes are not parsed by the configuration file reader, so that line will be ignored. You should always use "straight quotes" in configuration file settings.
Fixed that pesky wordpress/smartquotes issue, thanks for the sharp eye (and everything else).
I've also revamped/cleaned up my blog post about this:
http://tinkertry.com/esxi-5-1-running-hyper-v-server-2012
it's done (stick a fork in it)!
Sure wish I had run into you at VMworld...
I hate to say this, but it looks like there are still some angled quotes in step 8 on your blog.
They are gone from my site: all instances of vmx tweaks with quotes are now normal quotes.
But, as far as this site's forum, it won't let me go back and edit the earliest/first post I made when I started this thread, filled with angled quotes (the edit button only appears for very recent posts).
Oh well, at least I fixed up what I could on this site.
Now back to my site, mastered quotes, but didn't master constant disconnects (and autosave bugs), so fed up, upgrading my host to dedicated IP tonight (so tinkertry.com may be offline for a few hours)...
This did the trick for me.
Thank you very much!