windows 8 hyper-v

Sorry spoke too soon.

After ticking Hyper-V and restarting, Hyper-V is still not installed and when I am back in Add Windows Features Hyper-V is unticked as if nothing happeneed.

Still and ongoing issue. I know my hardware supports it though.

Hyper V requires these CPU extensions/flags vmx (virtualization), nx (data execution prevention), ept (second level address translation), and vmm (VM Monitor Mode). I don't see ept or vmm listed in your list at all, with or without *. In linux, I have a pile of flags that include all of these except vmm.

Have you seen this article?

I can't tell you why Hyper V needs vmm, but I regularly use VirtualBox on OS X, and qemu-kvm on Linux with CPUs that do not have vmm, and they virtualize fine.

Thanks Christopher

My Macbook Pro is the October 2013 release of the retina type so very recent hardware on 16GB. I would go nuts if I didnt have it. This was one the main intentions of buying this powerhouse. To run labs like I did in my SQL Server 2012 course in Hyper-V hosted by Windows 8.

http://www.zdnet.com/blog/bott/does-your-pc-have-what-it-takes-to-run-windows-8s -hyper-v/4254

Upon reading article above, ran the tool with the -v option and like expected, I am supported:

C:\Users\Guest\Downloads\Coreinfo>coreinfo -v

Coreinfo v3.21 - Dump information on system CPU and memory topology

Copyright (C) 2008-2013 Mark Russinovich

Sysinternals - www.sysinternals.com

Intel(R) Core(TM) i7-4850HQ CPU @ 2.30GHz

Intel64 Family 6 Model 70 Stepping 1, GenuineIntel

HYPERVISOR - Hypervisor is present

VMX * Supports Intel hardware-assisted virtualization

EPT * Supports Intel extended page tables (SLAT)

Then in this article flags the issue I have.

http://superuser.com/questions/530379/hyper-v-wont-enable-in-windows-8-pro-virtu alization-support-is-disabled-in-th

It was mentioned earlier in this thread that running Windows 8 in Bootcamp robs the machine of VM mode being enabled in the bios/EFI and thats my problem.

So I have heard that installing Windows 8 Pro outright (not using bootcamp) can remedy this but involves backing up everything and blanking it all while somehow booting to install Windows 8 Pro without bootcamp, which is terrible and maybe not even possible.

This ***** because its because my Macbook doesnt have a BIOS, that is partly the culprit due to incomplete support from the Windows/Apple side. I could had bought an Dell XPS 15 and not had trouble, which was my Plan B.

I have used Bootcamp on generations of macbook pro's over the years. In this last round Apple has not treated me well with Bootcamp. I've spent days trying to get Windows 8.1 to install, then trying for days to get an EFI based Windows 8.1 to install, then trying for days to find a way to boot with or without GPU support (for battery life - but apple blocks the ability to use the internal integrated intel graphics under Bootcamp if you have an nVidia chip), and now Apple is arbitrarily blocking Hyper-V because their BIOS settings aren't changeable.

Aargh.

Apple, I understand that resources are always tight for the Bootcamp team, but we're talking about flipping a bit in a BIOS setting. These roadblocks become frustrating after a while.

Please count this as yet another vote to fix the issue.

Apple doesn't support EFI booting anything other than OS X. If you're using Boot Camp Assistant, the only way to boot Windows is with the CSM-BIOS. So you need to undo that first. I suggest using gdisk to remove the bootcamp partition, and create a new protective MBR. Then see if you can boot the Windows installer in EFI mode - if it's on a DVD then boot with the option key and make sure you don't select the Windows icon. Choose the DVD icon with the EFI title instead.

Also, Apple aren't even using an EFI that meets the minimum requirements for Windows 8, which is UEFI 2.3.1. Apple is still using Intel EFI 1.10 (plus some parts of UEFI 2.x). But as others have gotten it to work with some caveats, it might be possible to use Hyper-V in that mode, rather than when booted via the CSM-BIOS mode that Boot Camp Assistant depends on.

You need to call Apple to complain. Or at the least use the feedback form.They don't read these forums, so your vote isn't being counted at all here. And calling counts more than the feedback form, so I would do both. Actually, I would also go to the Apple store and try to return the computer. It'll almost certainly fail if it's more than 30 days old, but it's worth making them aware of the problem at yet another level.

Thanks both for your input.

I will try booting in native EFI mode.

Accordng to various sources including Disk Adimistrator and System Information, I am apparently already booting Windows 8.1 Pro in EFI mode, which I dont beleive because I could had swore installing it using Bootcamp Assistant.

I seem to pass all the tests laid out below:

http://www.eightforums.com/tutorials/29504-bios-mode-see-if-windows-boot-uefi-le gacy-mode.html

Now that Ive just spent even more money on this and got myself a big backup drive, I can safetly store all my work and blitz partitions without sweating when trying out Re-installs.

I may re-install for no reason but really want Hyper-V to work since its one of my main reasons for getting a powerful machine.

I too have the same problem on a new Macbook Pro Retina...

I seem to pass that tests in the link on AbandonmentIssues post above.

Can anyone please confirm if reinstalling windows without boot camp assistance did the trick?

And if it did please confirm the steps you took. If you just booted with a Windows USB and format the old Widnows partition and just install the new one or if you took any extra steps

thanks in advance!

Well it seems to me that whatever test for Hyper-V you're doing within Windows should clearly indicate what hardware feature is needed that the hardware doesn't have (or isn't offered by the BIOS). It might be worth checking out this massive MacRumors thread (viewed over 1/4 million times) where some of the work getting Macs to EFI boot is discussed. Beg forgiveness for hijacking the thread, and ask if EFI booting a Mac enables Hyper-V to work.

I think some of the problems with EFI booting is that dual video Macs have both GPUs enabled, so it requires special drivers that can switch between them. Apple's drivers via Bootcamp.exe are predicated on CSM-BIOS booting, which disables integrated Intel graphics so this isn't a concern. So chances are it's not going to be a dirt simple step by step.

thanks for the reply Christopher Murphy!

I was wondering if you heard about the rEFInd Boot Manager project? What's your toughts on this? do you tink that it could do the trick?

@Christopher Murphy : Thanks again. I am yet to try to set up Windows from Scratch like fornat everything quite yet. I could imagine there will be some interesting driver hurdles. That's almost a seperate issue to the VT enable, EFI thing I am on.

I just want to know if anyone has actually managed to pull this off successfully. If it is possbile. I heard yes frrom various forums but no definitive how-to.

@rickrvo : Good suggestion although having tried installing rEFind and followed the instructions for placing the scripts and running off the commands to enable VT, ran into the legendary error message that rEFind was only for 32-bit systems and mine is 64-bit, being new etc etc. So an error doing this prevents me from gong further on this angle

rEFInd is the currently maintained fork of rEFIt, current version is 0.7.7. It's an EFI boot manager application, and presents a nice interface and some intelligence for locating bootable systems on multiple disks, then presenting them in the UI for the user. It should find OS X and Windows EFI OS Loaders out of the box. All it really is in your case is a replacement for the option+chime boot manager that's built into the Mac's EFI. Both of them still must use the same OS Loaders for OS X and Windows. And after the OS Loader is executed, there's no difference between using and not using rEFInd.

I think you installed the wrong package or you ran into a bug that should be reported. The package refind-bin-0.7.7.zip at sourceforge contains both 32-bit and 64-bit drivers and the firmware should run the proper arch.

Most of the world is using 64-bit EFI firmware. 32-bit EFI is restricted to some newer tablets (not made by Apple), and at this point rather old Apple Macs - the first round of Intel Macs which had 64-bit CPUs but 32-bit EFI.

Installed trial copy of Parallels in Mac OSX and then rebooted machine into Windows through Bootcamp. Hyper V options now enabled completed the installation all working fine.

I found this solution and it works to me: http://pfonseca.com/hyper-v-emulation-on-parallels-mac-os-x/

My configuration:

• MacBook Pro
• Parallels 8
• Mac OS X 10.9.4

Hello everyone. I also have a Macbook Pro 13" with Retina DispIay (October 2014) and ran into all of the same issues with regard to trying to run Hyper-V in Windows 8.1 Pro via Boot Camp. I tried everything mentioned in this thread, all to no avail. I eventually tried VMWare Workstation 10.0.4 and it runs VM's without issue (Windows Server 2012 R2 and Windows 7 Pro, so far). I realize it's not Hyper-V but it solves the problem of needing to run VM's on otherwise excellent Apple hardware for development and testing purposes, at least for me. Best of luck.