I have not seen this done or heard of anyone doing it... given that Hyper-V is a server role in Server 2008/R2, I'd be relatively surprised to hear it happening. If you do happen to see someone doing it, I'd love to hear how they accomplished it.
I was too looking forward to this. I finally installed Win8 to start playing with Hyper-V v3.
Unfortunately I got dissapointed immediatly. Windows 8 Hyper-V need SLAT support from CPU. I have a Q6600 so I dont have that support :(.
The Server OS 2012 with the same Hyper-V 3.0 does not need SLAT so this seems odd I think (I have read why, but cant I choose if I like to run RemoteFX or not on the Client OS in the same way as on the Server OS).
Have anyone been able to solve this? Example: - Copying the right DLLs from the server OS to the Client OS to be able to run Hyper-V on the Client OS? - Editing something to bypass this?
The role can easily be installed from the CMD line with this command (to bypass the check): Dism /online /enable-feature /featurename:Microsoft-Hyper-V But the Hyper-V server wont start...
Anyone with ideas?
//Ase
< Message edited by Ase -- 11.Aug.2012 9:42:50 AM >
I understand why MS requires SLAT support in Windows 8, but also feel that they should provide some kind of workaround. It's a bit limiting otherwise, especially when the same requirement doesn't hold for WS2012 (unless you intend to use RemoteFX, of course).
Have you considered just using another hypervisor on Windows 8, such as the free VirtualBox?
I use VMWare at the moment, but have read 2 books on Hyper-V and wanted to put that into practice. Server OS is not an option for me, otherwise I could have used 2008R2, even tested that but too many other programs I use cannot run on Server OS. That is why I was happy that Windows 8 would finally come with Hyper-V.
Please anyone if you find a solution, please post it in this thread.
Hi Guys, Here is some interesting info from discussions in TechNet Forums regarding a workaround. This workaround is not ideal, but this may trigger some ideas how to solve this...(I have not been able to test this myself). If You got ideas for me to test, please advice :) //Ase
"Hyper-V, on a Windows 8 client, can't be installed without the computer providing SLAT support. However, I've installed the Hyper-V feature on a Windows To Go install while the disk was connected to a laptop with SLAT support, moved the disk to a laptop that did not have SLAT support and Hyper-V continues to work. The blocking is done at install time. Once you've got the feature installed, it will continue to work even if the new system doesn't support SLAT."
Interesting... I wouldn't have considered using Windows To Go quite like this, but it does make sense that it would work if the blocking is done at install time.
I wish I had a way to test Windows To Go at my fingertips!