I am using Win Server 2012 R2 DC Edition, courtesy of DreamSpark. I went for this as it meant I can create and delete VMs constantly for experimentation without worrying about keys or Guest OS activation.
AVMA greatly simplifies this. Used to have a Technet membership and that was required given the number of XP VMs I used to create and then break/delete constantly in VMware, but that obviously wasn't an option anymore. I was done with XP, nevermind that Generation 2 VM's require Win 8 or Win Server 2012 as the Gust OS anyway. I know XP was favored for it's light footprint, but Gen 2 VMs seem to make up for this.
I've found this list of the differences between Hyper-V Client and HyperV in Windows Server in a few places, but it predates the R2 release.
http://devonenote.com/2012/06/differenc ... r-hyper-v/Regarding RemoteFX... that's a little surprising if Win 8 Pro's Client Hyper-V doesn't get this feature. All that is required for RemoteFX GPU support is DirectX11 and WDDM 1.2 support for the graphics driver, so even my old GTX 480 does work with this feature. I'm just hoping they will add the RemoteFX functionality to Gen 2 based VMs, I would imagine it's next on the list of features to be added?
So far Gen 2 VMs appear to be all-around better than virtualizing an entire ~486 based computer then sticking an OS ontop of it. I need to make a Gen 1 VM just to get a better feel for the comparison, but with Gen 2 Win 2012 VMs shutdown and boot literally take ~3 seconds tops, it's incredible. Linked clone Disk usage (or to use HyperV's terminology, differential disks) is also significantly more efficient, I can keep all the VM playing confined to a single SSD.
Yes, SR-IOV is a subset of VT-d if I recall. Per Ryu's
link:SR-IOV networking requires:
--A host system which supports SR-IOV (for example, Intel VT-d), including chipset support for interrupt and DMA remapping, and proper firmware support to enable and describe the platform’s SR-IOV capabilities to the operating system.
--An SR-IOV–capable network adapter and driver in both the management operating system (which runs the Hyper-V role) and each virtual machine where a virtual function is assigned.
Support for SR-IOV networking devices – Single Root I/O Virtualization (SR-IOV) is a standard introduced by the PCI-SIG. SR-IOV works in conjunction with system chipset support for virtualization technologies. This provides remapping of interrupts and DMA and allows SR-IOV capable devices to be assigned directly to a virtual machine. Hyper-V in Windows Server 2012 enables support for SR-IOV–capable network devices and allows an SR-IOV virtual function of a physical network adapter to be assigned directly to a virtual machine. This increases network throughput and reduces network latency, while also reducing the host CPU overhead required for processing network traffic.
That said I'd guess no that Z87's Intel-based Gbit LAN supports this. Figured out that Z87 uses
this ethernet controller. And this list of SR-IOV compliant controllers seems to confirm it, oh well.
http://www.intel.com/support/network/ad ... 031492.htmHz so good wrote:
Thanks for the link! I'll have to try out one of two of those and see what they can do!
Toby wrote:Hi guys!
I've written a few articles on how to get RemoteFX going (on 2012 in my case); in this guide I use a consumer NV 650 and it works great. I now use the RemoteFX VM as my main work machine either local or remote (over an RD Gateway). Kougar note you can setup a Gen1 or Gen2 machine with the newest Hyper-V, so that shouldn't be that big a deal. HyperV does use VT-D as well as a couple other techs.
Thanks for the links! I'll have to watch your site
I've already been using Gen 2 VMs, I'm just surprised you can't (yet) combine a Gen 2 VM with a RemoteFX vGPU. I'd think all the hard parts had already been done, unless there's some in-between interface driver they still need to write for this! Only Gen 1 VMs can use RemoteFX so far.