Hyper-V

Microsoft Hyper-V, codenamed Viridian,[1] formerly known as Windows Server Virtualization, is a native hypervisor; it can create virtual machines on x86-64 systems running Windows.[2] Starting with Windows 8, Hyper-V superseded Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V was first released with Windows Server 2008, and has been available without additional charge since Windows Server 2012 and Windows 8. A standalone Windows Hyper-V Server is free, but with command line interface only.

Hyper-V
Developer(s)Microsoft
Initial release2008
Operating systemWindows Server
PredecessorWindows Virtual PC
TypeNative hypervisor
Websitewww.microsoft.com/hyper-v 

History

A beta version of Hyper-V was shipped with certain x86-64 editions of Windows Server 2008. The finalized version was released on June 26, 2008 and was delivered through Windows Update.[3] Hyper-V has since been released with every version of Windows Server.[4][5][6]

Microsoft provides Hyper-V through two channels:

  1. Part of Windows: Hyper-V is an optional component of Windows Server 2008 and later. It is also available in x64 SKUs of Pro and Enterprise editions of Windows 8, Windows 8.1 and Windows 10.
  2. Hyper-V Server: It is a freeware edition of Windows Server with limited functionality and Hyper-V component.[7]

Hyper-V Server

Hyper-V Server 2008 was released on October 1, 2008. It consists of Windows Server 2008 Server Core and Hyper-V role; other Windows Server 2008 roles are disabled, and there are limited Windows services.[8] Hyper-V Server 2008 is limited to a command-line interface used to configure the host OS, physical hardware, and software. A menu driven CLI interface and some freely downloadable script files simplify configuration. In addition, Hyper-V Server supports remote access via Remote Desktop Connection. However, administration and configuration of the host OS and the guest virtual machines is generally done over the network, using either Microsoft Management Consoles on another Windows computer or System Center Virtual Machine Manager. This allows much easier "point and click" configuration, and monitoring of the Hyper-V Server.

Hyper-V Server 2008 R2 (an edition of Windows Server 2008 R2) was made available in September 2009 and includes Windows PowerShell v2 for greater CLI control. Remote access to Hyper-V Server requires CLI configuration of network interfaces and Windows Firewall. Also using a Windows Vista PC to administer Hyper-V Server 2008 R2 is not fully supported.

Architecture
Hyper-V architecture

Hyper-V implements isolation of virtual machines in terms of a partition. A partition is a logical unit of isolation, supported by the hypervisor, in which each guest operating system executes. There must be at least one parent partition in a hypervisor instance, running a supported version of Windows Server (2008 and later). The virtualization software runs in the parent partition and has direct access to the hardware devices. The parent partition creates child partitions which host the guest OSs. A parent partition creates child partitions using the hypercall API, which is the application programming interface exposed by Hyper-V.[9]

A child partition does not have access to the physical processor, nor does it handle its real interrupts. Instead, it has a virtual view of the processor and runs in Guest Virtual Address, which, depending on the configuration of the hypervisor, might not necessarily be the entire virtual address space. Depending on VM configuration, Hyper-V may expose only a subset of the processors to each partition. The hypervisor handles the interrupts to the processor, and redirects them to the respective partition using a logical Synthetic Interrupt Controller (SynIC). Hyper-V can hardware accelerate the address translation of Guest Virtual Address-spaces by using second level address translation provided by the CPU, referred to as EPT on Intel and RVI (formerly NPT) on AMD.

Child partitions do not have direct access to hardware resources, but instead have a virtual view of the resources, in terms of virtual devices. Any request to the virtual devices is redirected via the VMBus to the devices in the parent partition, which will manage the requests. The VMBus is a logical channel which enables inter-partition communication. The response is also redirected via the VMBus. If the devices in the parent partition are also virtual devices, it will be redirected further until it reaches the parent partition, where it will gain access to the physical devices. Parent partitions run a Virtualization Service Provider (VSP), which connects to the VMBus and handles device access requests from child partitions. Child partition virtual devices internally run a Virtualization Service Client (VSC), which redirect the request to VSPs in the parent partition via the VMBus. This entire process is transparent to the guest OS.

Virtual devices can also take advantage of a Windows Server Virtualization feature, named Enlightened I/O, for storage, networking and graphics subsystems, among others. Enlightened I/O is a specialized virtualization-aware implementation of high level communication protocols, like SCSI, that allows bypassing any device emulation layer and takes advantage of VMBus directly. This makes the communication more efficient, but requires the guest OS to support Enlightened I/O.

Currently only the following operating systems support Enlightened I/O, allowing them therefore to run faster as guest operating systems under Hyper-V than other operating systems that need to use slower emulated hardware:

System requirements

The Hyper-V role is only available in the x86-64 variants of Standard, Enterprise and Datacenter editions of Windows Server 2008 and later, as well as the Pro, Enterprise and Education editions of Windows 8 and later. On Windows Server, it can be installed regardless of whether the installation is a full or core installation. In addition, Hyper-V can be made available as part of the Hyper-V Server operating system, which is a freeware edition of Windows Server.[12] Either way, the host computer needs the following.[13]

The amount of memory assigned to virtual machines depends on the operating system:

  • Windows Server 2008 Standard supports up to 31 GB of memory for running VMs, plus 1 GB for the host OS.[15]
  • Windows Server 2008 R2 Standard supports up to 32 GB, but the Enterprise and Datacenter editions support up to 2 TB.[16] Hyper-V Server 2008 R2 supports up to 1 TB.[13]
  • Windows Server 2012 supports up to 4 TB.

The number of CPUs assigned to each virtual machine also depends on the OS:

  • Windows Server 2008 and 2008 R2 support 1, 2, or 4 CPUs per VM; the same applies to Hyper-V Server 2008 R2[12]
  • Windows Server 2012 supports up to 64 CPUs per VM

There is also a maximum for the number of concurrently active virtual machines.

  • Windows Server 2008 and 2008 R2 support 384 per server;[17] Hyper-V Server 2008 supports the same[12]
  • Windows Server 2012 supports 1024 per server; the same applies to Hyper-V Server 2012[18]
  • Windows Server 2016 supports 8000 per cluster and per node[19]

Supported guests

Windows 10

The following table lists supported guest operating systems on Windows 10 Pro RS5, and Windows Server 2019.[20]

Guest operating system Virtual CPUs
OSEditionsNumberArchitecture
Windows Server 2012[lower-alpha 1]Hyper-V, Standard, Datacenter1–4x86-64
Windows Home Server 2011Standard1–4x86-64
Windows Server 2008 R2 SP1Web, Standard, Enterprise, Datacenter1–4x86-64
Windows Server 2008 SP2Web, Standard, Enterprise, Datacenter1–4IA-32, x86-64
Windows Server 2003 R2 SP2Web,[lower-alpha 2] Standard, Enterprise, Datacenter1 or 2IA-32, x86-64
Windows 2000 SP4Professional, Server, Advanced Server1IA-32
Windows 7Professional, Enterprise, Ultimate1–4IA-32, x86-64
Windows VistaBusiness, Enterprise, Ultimate1–4IA-32, x86-64
Windows XP SP3Professional1 or 2IA-32, x86-64
Windows XP SP2Professional, Professional x64 Edition1IA-32, x86-64
SUSE Linux Enterprise Server 10 SP4 or 11 SP1–SP3N/A1–4IA-32, x86-64
Red Hat Enterprise Linux 5.5–7.0Red Hat Compatible Kernel1–4 IA-32, x86-64
CentOS 5.5–7.5N/A1–4IA-32, x86-64
Ubuntu 12.04–20.04Debian Compatible Kernel1–4IA-32, x86-64
Debian 7.0Debian Compatible Kernel1–4 IA-32, x86-64
Oracle Linux 6.4Red Hat Compatible Kernel1–4IA-32, x86-64
  1. Windows Server 2012 is supported and runs only on a host system Windows Server 2008 R2 RTM or SP1, with a hotfix applied.
  2. Web edition does not have an x64 version.

Fedora 8 or 9 are unsupported; however, they have been reported to run.[20][21][22][23]

Third-party support for FreeBSD 8.2 and later guests is provided by a partnership between NetApp and Citrix.[24] This includes both emulated and paravirtualized modes of operation, as well as several HyperV integration services.[25]

Windows 10 Home does not support Hyper-V.[26]

Desktop virtualization (VDI) products from third-party companies (such as Quest Software vWorkspace, Citrix XenDesktop, Systancia AppliDis Fusion[27] and Ericom PowerTerm WebConnect) provide the ability to host and centrally manage desktop virtual machines in the data center while giving end users a full PC desktop experience.

Guest operating systems with Enlightened I/O and a hypervisor-aware kernel such as Windows Server 2008 and later server versions, Windows Vista SP1 and later clients and offerings from Citrix XenServer and Novell will be able to use the host resources better since VSC drivers in these guests communicate with the VSPs directly over VMBus.[28] Non-"enlightened" operating systems will run with emulated I/O;[29] however, integration components (which include the VSC drivers) are available for Windows Server 2003 SP2, Windows Vista SP1 and Linux to achieve better performance.

Linux support

On July 20, 2009, Microsoft submitted Hyper-V drivers for inclusion in the Linux kernel under the terms of the GPL.[30] Microsoft was required to submit the code when it was discovered that they had incorporated a Hyper-V network driver with GPL-licensed components statically linked to closed-source binaries.[31] Kernels beginning with 2.6.32 may include inbuilt Hyper-V paravirtualization support which improves the performance of virtual Linux guest systems in a Windows host environment. Hyper-V provides basic virtualization support for Linux guests out of the box. Paravirtualization support requires installing the Linux Integration Components or Satori InputVSC drivers. Xen-enabled Linux guest distributions may also be paravirtualized in Hyper-V. As of 2013 Microsoft officially supported only SUSE Linux Enterprise Server 10 SP1/SP2 (x86 and x64) in this manner,[32] though any Xen-enabled Linux should be able to run. In February 2008, Red Hat and Microsoft signed a virtualization pact for hypervisor interoperability with their respective server operating systems, to enable Red Hat Enterprise Linux 5 to be officially supported on Hyper-V.[33]

Windows Server 2012

Hyper-V in Windows Server 2012 and Windows Server 2012 R2 changes the support list above as follows:[34]

  1. Hyper-V in Windows Server 2012 adds support for Windows 8.1 (up to 32 CPUs) and Windows Server 2012 R2 (64 CPUs); Hyper-V in Windows Server 2012 R2 adds support for Windows 10 (32 CPUs) and Windows Server 2016 (64 CPUs).
  2. Minimum supported version of CentOS is 6.0.
  3. Minimum supported version of Red Hat Enterprise Linux is 5.7.
  4. Maximum number of supported CPUs for Windows Server and Linux operating systems is increased from four to 64.

Backward compatibility

Hyper-V, like Microsoft Virtual Server and Windows Virtual PC, saves each guest OS to a single virtual hard disk file. It supports the older .vhd format, as well as the newer .vhdx. Older .vhd files from Virtual Server 2005, Virtual PC 2004 and Virtual PC 2007 can be copied and used in Hyper-V, but any old virtual machine integration software (equivalents of Hyper-V Integration Services) must be removed from the virtual machine. After the migrated guest OS is configured and started using Hyper-V, the guest OS will detect changes to the (virtual) hardware. Installing "Hyper-V Integration Services" installs five services to improve performance, at the same time adding the new guest video and network card drivers.

Limitations

Audio

Hyper-V does not virtualize audio hardware. Before Windows 8.1 and Windows Server 2012 R2, it was possible to work around this issue by connecting to the virtual machine with Remote Desktop Connection over a network connection and use its audio redirection feature.[35][36] Windows 8.1 and Windows Server 2012 R2 add the enhanced session mode which provides redirection without a network connection.[37]

Optical drives pass-through

Optical drives virtualized in the guest VM are read-only.[38] Officially Hyper-V does not support the host/root operating system's optical drives to pass-through in guest VMs. As a result, burning to discs, audio CDs, video CD/DVD-Video playback are not supported; however, a workaround exists using the iSCSI protocol. Setting up an iSCSI target on the host machine with the optical drive can then be talked to by the standard Microsoft iSCSI initiator. Microsoft produces their own iSCSI Target software or alternative third party products can be used.[39]

Graphics issues on the host

On CPUs without Second Level Address Translation (SLAT), installation of most WDDM accelerated graphics drivers on the primary OS will cause a dramatic drop in graphic performance. This occurs because the graphics drivers access memory in a pattern that causes the translation lookaside buffer to be flushed frequently (cache thrashing).[40]

In Windows Server 2008, Microsoft officially supported Hyper-V only with the default VGA drivers,[41] which do not support Windows Aero, higher resolutions, rotation, or multi-monitor display. However, unofficial workarounds were available in certain cases. Older non-WDDM graphics drivers sometimes did not cause performance issues, though these drivers did not always install smoothly on Windows Server. Intel integrated graphics cards did not cause TLB flushing even with WDDM drivers.[42] Some NVidia graphics drivers did not experience problems so long as Windows Aero was turned off and no 3D applications were running.[40]

In Windows Server 2008 R2, Microsoft added support for Second Level Address Translation to Hyper-V. Since SLAT is not required to run Hyper-V with Windows Server,[43] the problem will continue to occur if a non-SLAT CPU is used with accelerated graphics drivers. However, SLAT is required to run Hyper-V on client versions of Windows 8.[44]

Live migration

Hyper-V in Windows Server 2008 does not support "live migration" of guest VMs (where "live migration" is defined as maintaining network connections and uninterrupted services during VM migration between physical hosts). Instead, Hyper-V on Server 2008 Enterprise and Datacenter Editions supports "quick migration", where a guest VM is suspended on one host and resumed on another host. This operation happens in the time it takes to transfer the active memory of the guest VM over the network from the first host to the second host.[45]

However, with the release of Windows Server 2008 R2, live migration is supported with the use of Cluster Shared Volumes (CSVs). This allows for failover of an individual VM as opposed to the entire host having to failover (it seems that when a node (Hyper-V server, not a VM) fails then each "VM running on the failed node" may migrate to other live nodes independently of "other VMs on the same LUN running on other nodes that share the LUN with the failed node". In Hyper-V we are clustering the Hyper-V nodes not the VMs.). See also Cluster Shared Volumes.

Windows Server 2012's implementation of Hyper-V (Version 3.0) introduced many new features to increase VM mobility, including the ability to execute simultaneous live migrations (Windows Server 2008 R2 only supported live migrating a single VM at a time, significantly increasing the time required to carry administrative tasks, such as draining a node for scheduled maintenance). The only real limiting factor here is hardware and network bandwidth available. Windows Server 2012 also supports a new "shared nothing live migration" option, where no traditional shared storage is required in order to complete a migration. Also referred to as “Live System Migration”, a shared nothing live migration will move a running VM and its storage from one Hyper-V host to another without any perceived downtime. Live Migration between different host OS versions is not possible, although this is soon to be addressed in Windows Server 2012 R2.

Windows Server 2012 also introduced the ability to use simple SMB shares as a shared storage option (in conjunction with the new Scale out File Services role in Server 2012 for highly available environments), alleviating the need for expensive SANs. This is particularly useful for low budget environments, without the need to sacrifice performance due to the many new improvements to the SMB3 stack. Windows Server 2012 will fully support the live migration of VMs running on SMB shares, whether it be a live or live system migration.

Hyper-V under Windows Server 2012 also supports the ability to migrate a running VM's storage, whereby an active Virtual Machines storage can be moved from one infrastructure to another without the VM's workload being affected, further reducing the limitations associated with VM mobility.

With the introduction of Windows Server 2012 R2, SMB 3.0 was introduced as a transport option for Live Migration, either between clustered or non-clustered virtualization hosts. This enables Hyper-V Live Migration to leverage the additional benefits that SMB 3.0 brings, such as SMB Multichannel and SMB Direct (in conjunction with RDMA NICs) for increased Live Migration performance.

Degraded performance for Windows XP VMs

Windows XP frequently accesses CPU's APIC task-priority register (TPR) when interrupt request level changes, causing a performance degradation when running as guests on Hyper-V.[46] Microsoft has fixed this problem in Windows Server 2003 and later.[46]

Intel adds TPR virtualization (FlexPriority) to VT-x on Intel Core 2 stepping E onwards to alleviate this problem.[47] AMD has a similar feature on AMD-V but uses a new register for the purpose. This however means that the guest has to use different instructions to access this new register. AMD provides a driver called "AMD-V Optimization Driver" that has to be installed on the guest to do that.[48]

NIC teaming

Network card teaming or link aggregation is not supported if the NIC manufacturer supplied drivers support NIC teaming.[49] However, Windows Server 2012 and thus the version of Hyper-V included with it supports software NIC teaming.[50]

NIC Teaming is a software based option in Windows Server 2012. It offers redundancy and fault tolerance in a network.

Administration tools

Hyper-V management tools are not compatible with Windows Vista Home Basic or Home Premium[51][51] or Windows 7 Home Premium, Home Basic or Starter.

Hyper-V 2012 can only be managed by Windows 8, Windows Server 2012 or their successors.

VT-x/AMD-V handling

Hyper-V uses the VT-x on Intel or AMD-V on AMD x86 virtualization. Since Hyper-V is a native hypervisor, as long as it is installed, third-party software cannot use VT-x or AMD-V. For instance, the Intel HAXM Android device emulator (used by Android Studio or Microsoft Visual Studio) cannot run while Hyper-V is installed.[52]

Client operating systems

64-bit SKUs of Windows 8 Pro or Enterprise, or later, come with a special version Hyper-V called Client Hyper-V.[53]

Features added per version

Windows Server 2012

Windows Server 2012 introduced many new features in Hyper-V.[6]

  • Hyper-V Extensible Virtual Switch[54][55]
  • Network virtualization[54]
  • Multi-tenancy
  • Storage Resource Pools
  • .vhdx disk format supporting virtual hard disks as large as 64 TB[56] with power failure resiliency
  • Virtual Fibre Channel
  • Offloaded data transfer
  • Hyper-V replica[57]
  • Cross-premises connectivity
  • Cloud backup

Windows Server 2012 R2

With Windows Server 2012 R2 Microsoft introduced another set of new features.[58]

  • Shared virtual hard disk[59]
  • Storage quality of service[60]
  • Virtual machine generation[61]
  • Enhanced session mode[62]
  • Automatic virtual machine activation[63]

Windows Server 2016

Hyper-V in Windows Server 2016 and Windows 10 1607 adds[64]

  • Nested virtualization[65] (Intel processors only, both the host and guest instances of Hyper-V must be Windows Server 2016 or Windows 10 or later)
  • Discrete Device Assignment (DDA), allowing direct pass-through of compatible PCI Express devices to guest Virtual Machines[66]
  • Windows containers (to achieve isolation at the app level rather than the OS level)
  • Shielded VMs using remote attestation servers
  • Monitoring of host CPU resource utilization by guests and protection (limiting CPU usage by guests)

Windows Server 2019

Hyper-V in Windows Server 2019 and Windows 10 1809 adds[67]

  • Shielded Virtual Machines improvements including Linux compatibility
  • Virtual Machine Encrypted Networks
  • vSwitch Receive Segment Coalescing
  • Dynamic Virtual Machine Multi-Queue (d.VMMQ)
  • Persistent Memory support
  • Significant feature and performance improvements to Storage Spaces Direct and Failover Clustering

See also

References
  1. "Microsoft to ship Windows Server 2008, over time, in eight flavors". Retrieved 2007-11-13.
  2. Paul Thurrott. "Windows Server Virtualization Preview". Archived from the original on 2007-10-11. Retrieved 2007-09-25.
  3. "Announcement available from the Microsoft download centre". Retrieved 2008-06-26.
  4. "Microsoft Hyper-V Server". Microsoft. p. 1. Retrieved January 12, 2012.
  5. "Download: Microsoft® Hyper-V™ Server 2008 R2 SP1 - Microsoft Download Center - Download Details". Microsoft.com. 2011-12-04. Retrieved 2012-10-07.
  6. "Server Virtualization Features". Microsoft. Retrieved October 5, 2012.
  7. "Try Hyper-V Server 2012 R2". Evaluation Center. Microsoft. Retrieved 16 February 2015.
  8. "Microsoft Helps Customers Overcome Barriers to Virtualization and Get Virtual Now". PressPass (Press release). Microsoft. October 1, 2008. Retrieved 2008-10-02.
  9. "Hyper-V Architecture". Msdn.microsoft.com. Retrieved 2017-04-04.
  10. "Staging: hv: storvsc: Move the storage driver out of the staging area". Retrieved 28 December 2015.
  11. "FreeBSD and Microsoft Windows Server Hyper-V support". Retrieved 10 February 2015.
  12. "Microsoft Hyper-V Server 2008 R2: Frequently Asked Questions". Microsoft.com. Microsoft. Archived from the original on 14 August 2011.
  13. "Microsoft Hyper-V Server: System Requirements". Microsoft.com. Microsoft. Archived from the original on 14 March 2010.
  14. Thurott, Paul. "Q: Will Windows Server 2012 require the processor to support SLAT?". Archived from the original on August 9, 2017. Retrieved November 5, 2011.
  15. "Memory Limits for Windows Releases (Windows)". Msdn.microsoft.com. Retrieved 2010-03-02.
  16. "Microsoft Windows Server 2008 System Requirements". Microsoft.com. Retrieved 2012-10-07.
  17. "Microsoft Hyper-V Server: Overview". Microsoft.com. Retrieved 2010-03-02.
  18. "Hyper-V Server whitepaper" (PDF).
  19. "Plan for Hyper-V scalability in Windows Server 2016". Microsoft.com. Retrieved 2017-06-22.
  20. "About Virtual Machines and Guest Operating Systems". TechNet. Microsoft. Retrieved 2016-05-09.
  21. "Installing Fedora Core 8 on Hyper-V - Ben Armstrong - Site Home - MSDN Blogs". Blogs.msdn.com. 2008-01-03. Retrieved 2012-10-07.
  22. Sheinberg, Brian (2008-02-08). "First Look: Fedora 9 Alpha, Running in Hyper-V Beta". Crn.com. Archived from the original on 2010-07-23. Retrieved 2012-10-07.
  23. "Install Ubuntu 7.10 on Hyper-V". Haiders.net. 2008-04-04. Archived from the original on 2009-02-24. Retrieved 2012-10-07.
  24. "Available Today: FreeBSD Support for Windows Server Hyper-V". Openness@Microsoft. 2012-08-09. Retrieved 2014-05-25.
  25. "HyperV - FreeBSD Wiki". Freebsd.org. Retrieved 2014-05-25.
  26. "Windows 10 Hyper-V System Requirements". Docs.microsoft.com. Retrieved 31 May 2019.
  27. "Systancia offers application and desktop virtualization in a single product". DataMonitor.
  28. "Microsoft Windows Server 2008 – Hyper-V solution overview - Gabe Knuth". BrianMadden.com. Retrieved 2012-10-07.
  29. Stevens, Alan (2008-02-27). "Microsoft's Hyper-V: why all the fuss?". ZDNet. CBS Interactive. Retrieved 2012-10-07.
  30. Ramji, Sam; Hanrahan, Tom (2009-07-20). "Microsoft Contributes Linux Drivers to Linux Community". News Center. Microsoft. Retrieved 2010-03-02.
  31. Foley, Mary Jo (2009-07-22). "Pigs are flying low: Why Microsoft open-sourced its Linux drivers". ZDNet. CBS Interactive.
  32. Babcock, Charles (2008-04-24). "Microsoft Hyper-V To Flaunt Advanced Virtualization Features". Informationweek.com. Retrieved 2012-10-07.
  33. Foley, Mary Jo (2009-02-16). "Microsoft and Red Hat sign virtualization pact". ZDNet. CBS Interactive. Retrieved 2012-10-07.
  34. "Hyper-V Overview". TechNet. Microsoft. Retrieved October 5, 2012.
  35. Otey, Michael (24 June 2008). "Guest VM Audio Support under Hyper-V". Windows IT Pro. Penton Media. Retrieved 21 September 2014.
  36. "Enable Audio in Windows 2008 guest machines running on HyperV". Akshat's Blog. Microsoft. 7 April 2011. Retrieved 21 September 2014.
  37. Gear, Gavin (5 December 2013). "Overview: Client Hyper-V Enhanced Session Mode in Windows 8.1". Blogging Windows. Microsoft. Retrieved 21 September 2014.
  38. Cook, John Paul. "DVD writer on Hyper-V server". TechNet Forums. Microsoft. Retrieved 2012-10-07.
  39. "Using Full DVD/CD Writing Capabilities in a Hyper-V VM | Mark Gilbert's Blog". Mark-gilbert.co.uk. 2012-09-05. Retrieved 2015-01-18.
  40. Armstrong, Ben. "Understanding High-End Video Performance Issues with Hyper-V".
  41. "Video performance may decrease when a Windows Server 2008 or Windows Server 2008 R2 based computer has the Hyper-V role enabled and an accelerated display adapter installed". Support.microsoft.com. 2010-11-22. Retrieved 2012-10-07.
  42. Armstrong, Ben. "Hyper-V versus Desktop Computing".
  43. Finn, Aidan. "Windows Server 2012 Hyper-V DOES NOT Require SLAT (EPT/NPT) Capable Processors".
  44. Brodkin, Jon (2011-09-07). "Hyper-V coming to Windows 8—with new hardware virtualization requirement". Ars Technica.
  45. "Hyper-V Live Migration vs. Quick Migration". Virtualization Team. 2008-09-29. Retrieved 2012-10-07.
  46. "Degraded I/O Performance using a Windows XP Virtual Machine with Windows Server 2008 Hyper-V". Microsoft TechNet. Microsoft. 5 March 2010. Retrieved 28 August 2013.
  47. "Enabling Intel Virtualization Technology Features and Benefits" (PDF). Intel. 2010.
  48. "AmdvOpt". Processor Drivers. AMD. 1 July 2011. Readme.rtf. Retrieved 28 August 2013.
  49. "Microsoft Support Policy for NIC Teaming with Hyper-V". Support.microsoft.com. 2012-01-17. Retrieved 2012-10-07.
  50. "NIC Teaming Overview". Microsoft. February 29, 2012. Retrieved October 7, 2012.
  51. "Install and Configure Hyper-V Tools for Remote Administration". TechNet. Microsoft. Retrieved 2012-10-07.
  52. Syrewicze, Andy (October 2, 2013). "VMware vs. Hyper-V: Architectural Differences". Syrewiczeit.com. Self-published. Archived from the original on February 25, 2018. Retrieved 2019-01-18.
  53. "Fix Hyper-V Has Not Been Installed on Computer 'localhost'". Techdracula.com. Retrieved 2013-06-06.
  54. "A deep dive into Hyper-V Networking (Video and Slides)".
  55. "Extending the Hyper-V switch (Video and Slides)".
  56. "Hyper-V Virtual Hard Disk Format Overview". TechNet. Microsoft. Retrieved August 25, 2012.
  57. Reseller, Mike. "Hyper-V Replica in depth". Veeam Software.
  58. "What's New in Hyper-V for Windows Server 2012 R2". Technet.microsoft.com. Retrieved 2016-04-26.
  59. "What's New in Hyper-V for Windows Server 2012 R2". Technet.microsoft.com. Retrieved 2016-04-26.
  60. "What's New in Hyper-V for Windows Server 2012 R2". Technet.microsoft.com. Retrieved 2016-04-26.
  61. "What's New in Hyper-V for Windows Server 2012 R2". Technet.microsoft.com. Retrieved 2016-04-26.
  62. "What's New in Hyper-V for Windows Server 2012 R2". Technet.microsoft.com. Retrieved 2016-04-26.
  63. "What's New in Hyper-V for Windows Server 2012 R2". Technet.microsoft.com. Retrieved 2016-04-26.
  64. "What's new in Hyper-V on Windows Server 2016". Docs.microsoft.com. Retrieved 2017-10-27.
  65. "Run Hyper-V in a Virtual Machine with Nested Virtualization". Docs.microsoft.com. Retrieved 2017-10-27.
  66. "What's new in Hyper-V on Windows Server 2016". Docs.microsoft.com. Retrieved 2019-02-21.
  67. "What's new in Windows Server 2019". Docs.microsoft.com. Retrieved 2019-02-21.

Further reading
  1. "Hypervisor Top Level Functional Specification". Microsoft. 2016. Retrieved 2017-04-04.
  2. Koens, Dimitri (2013). "Hyper-V Quick Reference" (PDF). Dimension IT TV. Retrieved 2017-04-04.
  3. Howard, John (2006). "WinHEC 2006 Presentation slides". Virtualization Blog. Microsoft. Retrieved 2017-04-04.
  4. Radzikowski, Przemek (2009). "Benchmarking Hyper-V on Windows Server 2008 R2 x64". Retrieved 2017-04-04.
  5. Posey, Brien; Zerger, Pete; Henley, Chris (2013). The Hands-on Guide: Understanding Hyper-V in Windows Server 2012. Veeam Software. Archived from the original on 2014-04-13. Retrieved 2017-04-04.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.