Hyper-V Program Manager
With the availability of the Windows Server 2012 Release Candidate – we have a bunch of information available online right now.
Over on the Microsoft Server and Cloud Platform site we have:
Meanwhile – on our TechNet Library we have:
If feedback still has any effect on Microsoft, I just want to be loud and clear that I want Windows Virtual PC to be available for Windows 8 because Hyper-V does not do many things it did. So please make sure VPC 2007 is compatible with Windows 8 and update the WVPC MSU for Windows 8, including the RemoteApp integration so can use our own XP-mode like client OS.
I'll try here, too:
I understand the emphasis on the latest-and-greatest, and the answer to the following question may certainly be "yes": after all, this is your blog, so your rules:
Is your blog now exclusively Windows 8 related? I see the subtitle still reads "Talking about core virtualization at Microsoft (Hyper-V, Virtual PC and Virtual Server)," but it seems it's been a while since there was any discussion regarding (say) Virtual PC.
Again, if that's intentional, that's fine, I just need to know because my organization currently has no plans to migrate (heck, we're only just now finalizing on Windows 7) so it's not a good use of my time to pore over Windows 8 right now.
Thanks for a reply either way,
I cannot comment on Virtual PC + Windows 8 until people higher than me make a formal statement first.
I talk about what I am using, which tends to be the latest and greatest, though every now and then I will use older software for personal interest. Out of curiosity - what information are you looking for that I have not yet blogged about?
Is there a document on remotely managing Hyper-V with the Windows Server 2012 Hyper-V RC download?
Ben: With regard to Client Hyper-V and Windows 8, I'd be happy if it worked on CPUs with hardware virtualization, but without requiring SLAT. I realize that RemoteFX is a goal, to get desktop composition to work for hosted VMs, but the number of mobile CPUs supporting SLAT is pretty low. If the goal is for Windows 8 to run on *any* hardware that ran Windows 7, there will be a lot of Core 2 machines out in the cold.
This is similar to the original decision for Windows Virtual PC 7 to require hardware virtualization, which was (thankfully) reversed in time for Windows 7 RTM, or perhaps a little later?
All versions of Hyper-V so far have required 64-bit and hardware virtualization; the situation now is a bit different from that of Windows 7 three years ago and you probably can assume everyone who cares is running 64-bit and has hardware virtualization. Please do check the telemetry for the Windows 8 previews.
Our use case: We need to support old development environments like VB6 or eMbedded Visual C++ for extended support. While the tools do work on Windows 7 when installed in the correct order, oldest to newest, it's a major pain for developers who didn't install those tools to begin with, and now would have to uninstall VS2010, 2008 and 2005 to then install eVC, then required CE SDKs, then all the newer IDEs. There are also some older development tools that aren't compatible with Windows 7 at all, or are 16-bit and therefore won't run on a 64-bit OS.
Supposedly you can use PowerShell or DISM to add Hyper-V and it doesn't check for SLAT, only the GUI installation option checks for SLAT.
I haven't tried this myself though.
What about hibernation & sleep capabilities in Hyper-V of Windows Server 2012?
I've read the beta supports this, but I cannot find information how to use that in Windows Server 2012. Please help.
@smjain: "Supposedly you can use PowerShell or DISM to add Hyper-V and it doesn't check for SLAT, only the GUI installation option checks for SLAT.
I haven't tried this myself though."
It did not work! Hyper-V-Services refuses to work on a non-SLAT-CPU - I have tested it . You can run Hyper-V-Manager and create a VM - but Hyper-V-Platform required to virtualize your guest won't run.