Hyper-V

Last updated
Hyper-V
Developer(s) Microsoft
Initial releaseJune 28, 2008;15 years ago (June 28, 2008)
Operating system Windows Server
Windows 8, Windows 8.1, Windows 10, Windows 11 (x64; Pro, Enterprise and Education)
Predecessor Windows Virtual PC
Type Native hypervisor
Website learn.microsoft.com/en-us/virtualization/hyper-v-on-windows/about/

Microsoft Hyper-V, codenamed Viridian, [1] and briefly known before its release 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 has a command-line interface only. The last version of free Hyper-V Server is Hyper-V Server 2019, which is based on Windows Server 2019.

Contents

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, Windows 10 and Windows 11.
  2. Hyper-V Server: It is a freeware edition of Windows Server with limited functionality and Hyper-V component. [7]

Hyper-V Server

Microsoft Hyper-V Server wordmark (2012-2016).png

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.

Microsoft ended mainstream support of the free version of Hyper-V Server 2019 on January 9, 2024 and extended support will end on January 9, 2029. [9] Hyper-V Server 2019 will be the last version of the free, standalone product. Hyper-V is still available as a role in Windows Server 2022 and will be supported as long as that operating system is, currently scheduled for end of extended support on October 14, 2031. [10]

Architecture

Hyper-V architecture Hyper-V.png
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. The parent partition creates child partitions which host the guest OSs. The Virtualization Service Provider and Virtual Machine Management Service runs in the parent partition and provide support for child partition. A parent partition creates child partitions using the hypercall API, which is the application programming interface exposed by Hyper-V. [11]

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[ when? ] 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. [14] Either way, the host computer needs the following. [15]

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

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

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

Supported guests

Windows Server 2008 R2

The following table lists supported guest operating systems on Windows Server 2008 R2 SP1. [22]

Guest operating systemVirtual CPUs
OSEditionsNumberArchitecture
Windows Server 2012 [lower-alpha 1] Hyper-V, Standard, Datacenter1–4 x86-64
Windows Home Server 2011 Standard1–4 x86-64
Windows Server 2008 R2 SP1Web, Standard, Enterprise, Datacenter1–4 x86-64
Windows Server 2008 SP2Web, Standard, Enterprise, Datacenter1–4 IA-32, x86-64
Windows Server 2003 R2 SP2Web, [lower-alpha 2] Standard, Enterprise, Datacenter1 or 2 IA-32, x86-64
Windows 2000 SP4Professional, Server, Advanced Server1 IA-32
Windows 7 Professional, Enterprise, Ultimate1–4 IA-32, x86-64
Windows Vista Business, Enterprise, Ultimate1–4 IA-32, x86-64
Windows XP SP3Professional1 or 2 IA-32
Windows XP SP2Professional, Professional x64 Edition1 IA-32, x86-64
SUSE Linux Enterprise Server 10 SP4 or 11 SP1–SP3—1–4 IA-32, x86-64
Red Hat Enterprise Linux 5.5–7.0Red Hat Compatible Kernel1–4 IA-32, x86-64
CentOS 5.5–7.5—1–4 IA-32, x86-64
Ubuntu 12.04–20.04Debian Compatible Kernel1–4 IA-32, x86-64
Debian 7.0Debian Compatible Kernel1–4 IA-32, x86-64
Oracle Linux 6.4Red Hat Compatible Kernel1–4 IA-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. [22] [23] [24] [25]

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

Desktop virtualization (VDI) products from third-party companies (such as Quest Software vWorkspace, Citrix XenDesktop, Systancia AppliDis Fusion [28] 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. [29] Non-"enlightened" operating systems will run with emulated I/O; [30] 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. [31] 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. [32] 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, [33] 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. [34]

Windows Server 2012

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

  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.

Windows Server 2012 R2

Hyper-V on Windows Server 2012 R2 added the Generation 2 VM. [36]

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. [37] [38] Windows 8.1 and Windows Server 2012 R2 add the enhanced session mode which provides redirection without a network connection. [39]

Optical drives pass-through

Optical drives virtualized in the guest VM are read-only. [40] 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. [41]

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. [42]

Client operating systems

x64 SKUs of Windows 8, 8.1, 10 Pro, Enterprise, Education, come with a special version Hyper-V called Client Hyper-V. [43]

Features added per version

Windows Server 2012

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

Windows Server 2012 R2

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

Windows Server 2016

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

Windows Server 2019

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

See also

Web interface for Hyper-V

Related Research Articles

<span class="mw-page-title-main">Xen</span> Type-1 hypervisor

Xen is a free and open-source type-1 hypervisor, providing services that allow multiple computer operating systems to execute on the same computer hardware concurrently. It was originally developed by the University of Cambridge Computer Laboratory and is now being developed by the Linux Foundation with support from Intel, Citrix, Arm Ltd, Huawei, AWS, Alibaba Cloud, AMD, Bitdefender and epam.

Remote Desktop Protocol (RDP) is a proprietary protocol developed by Microsoft Corporation which provides a user with a graphical interface to connect to another computer over a network connection. The user employs RDP client software for this purpose, while the other computer must run RDP server software.

<span class="mw-page-title-main">UEFI</span> Operating system and firmware specification

Unified Extensible Firmware Interface is a specification that defines the architecture of the platform firmware used for booting the computer hardware and its interface for interaction with the operating system. Examples of firmware that implement the specification are AMI Aptio, Phoenix SecureCore, TianoCore EDK II, InsydeH2O. UEFI replaces the BIOS which was present in the boot ROM of all personal computers that are IBM PC compatible, although it can provide backwards compatibility with the BIOS using CSM booting. Intel developed the original Extensible Firmware Interface (EFI) specification. Some of the EFI's practices and data formats mirror those of Microsoft Windows. In 2005, UEFI deprecated EFI 1.10.

A hypervisor, also known as a virtual machine monitor (VMM) or virtualizer, is a type of computer software, firmware or hardware that creates and runs virtual machines. A computer on which a hypervisor runs one or more virtual machines is called a host machine, and each virtual machine is called a guest machine. The hypervisor presents the guest operating systems with a virtual operating platform and manages the execution of the guest operating systems. Unlike an emulator, the guest executes most instructions on the native hardware. Multiple instances of a variety of operating systems may share the virtualized hardware resources: for example, Linux, Windows, and macOS instances can all run on a single physical x86 machine. This contrasts with operating-system–level virtualization, where all instances must share a single kernel, though the guest operating systems can differ in user space, such as different Linux distributions with the same kernel.

In computing, paravirtualization or para-virtualization is a virtualization technique that presents a software interface to the virtual machines which is similar, yet not identical, to the underlying hardware–software interface.

<span class="mw-page-title-main">QEMU</span> Free virtualization and emulation software

QEMU is a free and open-source emulator. It emulates a computer's processor through dynamic binary translation and provides a set of different hardware and device models for the machine, enabling it to run a variety of guest operating systems. It can interoperate with Kernel-based Virtual Machine (KVM) to run virtual machines at near-native speed. QEMU can also do emulation for user-level processes, allowing applications compiled for one architecture to run on another.

Platform virtualization software, specifically emulators and hypervisors, are software packages that emulate the whole physical computer machine, often providing multiple virtual machines on one physical platform. The table below compares basic information about platform virtualization hypervisors.

Parallels Workstation is the first commercial software product released by Parallels, Inc., a developer of desktop and server virtualization software. The Workstation software comprises a virtual machine suite for Intel x86-compatible computers which allows the simultaneous creation and execution of multiple x86 virtual computers. They distributed the product as a download package. Parallels Workstation has been discontinued for Windows and Linux as of 2013.

<span class="mw-page-title-main">Windows Server 2008</span> Fourth version of Windows Server, released in 2008

Windows Server 2008, codenamed "Longhorn Server", is the fourth release of the Windows Server operating system produced by Microsoft as part of the Windows NT family of the operating systems. It was released to manufacturing on February 4, 2008, and generally to retail on February 27, 2008. Derived from Windows Vista, Windows Server 2008 is the successor of Windows Server 2003 and the predecessor to Windows Server 2008 R2.

Microsoft Virtual Server was a virtualization solution that facilitated the creation of virtual machines on the Windows XP, Windows Vista and Windows Server 2003 operating systems. Originally developed by Connectix, it was acquired by Microsoft prior to release. Virtual PC is Microsoft's related desktop virtualization software package.

The following is a timeline of virtualization development. In computing, virtualization is the use of a computer to simulate another computer. Through virtualization, a host simulates a guest by exposing virtual hardware devices, which may be done through software or by allowing access to a physical device connected to the machine.

<span class="mw-page-title-main">VMware ESXi</span> Enterprise-class, type-1 hypervisor for deploying and serving virtual computers

VMware ESXi is an enterprise-class, type-1 hypervisor developed by VMware, a subsidiary of Broadcom, for deploying and serving virtual computers. As a type-1 hypervisor, ESXi is not a software application that is installed on an operating system (OS); instead, it includes and integrates vital OS components, such as a kernel.

<span class="mw-page-title-main">Parallels Desktop for Mac</span> Virtual machine software

Parallels Desktop for Mac is software providing hardware virtualization for Macintosh computers with Intel processors, and since version 16.5 also for Apple silicon-based Macintosh computers. It is developed by Parallels, since 2018 a subsidiary of Corel.

<span class="mw-page-title-main">VirtualBox</span> Open-source x86 virtualization application

Oracle VM VirtualBox is a hosted hypervisor for x86 virtualization developed by Oracle Corporation. VirtualBox was originally created by InnoTek Systemberatung GmbH, which was acquired by Sun Microsystems in 2008, which was in turn acquired by Oracle in 2010.

VHD and its successor VHDX are file formats representing a virtual hard disk drive (HDD). They may contain what is found on a physical HDD, such as disk partitions and a file system, which in turn can contain files and folders. They are typically used as the hard disk of a virtual machine, are built into modern versions of Windows, and are the native file format for Microsoft's hypervisor, Hyper-V.

Oracle VM Server for x86 is the server virtualization offering from Oracle Corporation. Oracle VM Server for x86 incorporates the free and open-source Xen hypervisor technology, supports Windows, Linux, and Solaris guests and includes an integrated Web based management console. Oracle VM Server for x86 features fully tested and certified Oracle Applications stack in an enterprise virtualization environment.

Second Level Address Translation (SLAT), also known as nested paging, is a hardware-assisted virtualization technology which makes it possible to avoid the overhead associated with software-managed shadow page tables.

<span class="mw-page-title-main">Windows Server 2012</span> Sixth version of Windows Server, released in 2012

Windows Server 2012, codenamed "Windows Server 8", is the sixth version of the Windows Server operating system by Microsoft, as part of the Windows NT family of operating systems. It is the server version of Windows based on Windows 8 and succeeds Windows Server 2008 R2, which is derived from the Windows 7 codebase, released nearly three years earlier. Two pre-release versions, a developer preview and a beta version, were released during development. The software was officially launched on September 4, 2012, which was the month before the release of Windows 8. It was succeeded by Windows Server 2012 R2 in 2013. Mainstream support for Windows Server 2012 ended on October 9, 2018, and extended support ended on October 10, 2023. Windows Server 2012 is eligible for the paid Extended Security Updates (ESU) program, which offers continued security updates until October 13, 2026.

<span class="mw-page-title-main">Windows Server 2012 R2</span> Seventh version of Windows Server, released in 2013

Windows Server 2012 R2, codenamed "Windows Server Blue", is the seventh version of the Windows Server operating system by Microsoft, as part of the Windows NT family of operating systems. It was unveiled on June 3, 2013, at TechEd North America, and released on October 18 of the same year. It is the successor to Windows Server 2012, and is based on the Windows 8.1 codebase.

<span class="mw-page-title-main">Windows Server 2016</span> Eighth version of Windows Server, released in 2016

Windows Server 2016 is the eighth release of the Windows Server operating system developed by Microsoft as part of the Windows NT family of operating systems. It was developed alongside Windows 10 and is the successor to the Windows 8.1-based Windows Server 2012 R2. The first early preview version became available on October 1, 2014 together with the first technical preview of System Center. Windows Server 2016 was released on September 26, 2016 at Microsoft's Ignite conference and broadly released for retail sale on October 12, 2016. It was succeeded by Windows Server 2019 and the Windows Server Semi-Annual Channel.

References

  1. ↑ "Microsoft to ship Windows Server 2008, over time, in eight flavors". ZDNet . Archived from the original on 2010-09-24. 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". Archived from the original on 2008-06-29. Retrieved 2008-06-26.
  4. ↑ "Microsoft Hyper-V Server". Microsoft. p. 1. Archived from the original on October 5, 2013. Retrieved January 12, 2012.
  5. ↑ "Download: Microsoft® Hyper-V™ Server 2008 R2 SP1 - Microsoft Download Center - Download Details". Microsoft.com. 2011-12-04. Archived from the original on 2012-04-19. Retrieved 2012-10-07.
  6. 1 2 "Server Virtualization Features". Microsoft. Archived from the original on October 14, 2012. Retrieved October 5, 2012.
  7. ↑ "Try Hyper-V Server 2012 R2". Evaluation Center. Microsoft. Archived from the original on 11 July 2020. Retrieved 16 February 2015.
  8. ↑ "Microsoft Helps Customers Overcome Barriers to Virtualization and Get Virtual Now". PressPass (Press release). Microsoft. October 1, 2008. Archived from the original on 2010-01-18. Retrieved 2008-10-02.
  9. ↑ "Microsoft Lifecycle". Hyper-V Server 2019 - Microsoft Lifecycle. Microsoft.
  10. ↑ "Windows Server 2022 - Microsoft Lifecycle". learn.microsoft.com. Microsoft. Retrieved 2024-03-21.
  11. ↑ "Hyper-V Architecture". Microsoft. 26 April 2022. Retrieved 2023-10-25.
  12. ↑ "Staging: hv: storvsc: Move the storage driver out of the staging area" . Retrieved 28 December 2015.
  13. ↑ "FreeBSD and Microsoft Windows Server Hyper-V support". Archived from the original on 24 January 2015. Retrieved 10 February 2015.
  14. 1 2 3 "Microsoft Hyper-V Server 2008 R2: Frequently Asked Questions". Microsoft.com. Microsoft. Archived from the original on 14 August 2011.
  15. 1 2 "Microsoft Hyper-V Server: System Requirements". Microsoft.com. Microsoft. Archived from the original on 14 March 2010.
  16. ↑ 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.
  17. ↑ "Memory Limits for Windows Releases (Windows)". Msdn.microsoft.com. Archived from the original on 2009-06-20. Retrieved 2010-03-02.
  18. ↑ "Microsoft Windows Server 2008 System Requirements". Microsoft.com. Archived from the original on 2011-06-12. Retrieved 2012-10-07.
  19. ↑ "Microsoft Hyper-V Server: Overview". Microsoft.com. Archived from the original on 2012-03-22. Retrieved 2010-03-02.
  20. ↑ "Hyper-V Server whitepaper" (PDF). Archived (PDF) from the original on 2013-11-07. Retrieved 2013-12-21.
  21. ↑ "Plan for Hyper-V scalability in Windows Server 2016". Microsoft.com. Retrieved 2017-06-22.
  22. 1 2 "About Virtual Machines and Guest Operating Systems". TechNet . Microsoft. 16 July 2014. Archived from the original on 2016-05-06. Retrieved 2016-05-09.
  23. ↑ "Installing Fedora Core 8 on Hyper-V - Ben Armstrong - Site Home - MSDN Blogs". Blogs.msdn.com. 2008-01-03. Archived from the original on 2010-02-10. Retrieved 2012-10-07.
  24. ↑ 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.
  25. ↑ "Install Ubuntu 7.10 on Hyper-V". Haiders.net. 2008-04-04. Archived from the original on 2009-02-24. Retrieved 2012-10-07.
  26. ↑ "Available Today: FreeBSD Support for Windows Server Hyper-V". Openness@Microsoft. 2012-08-09. Archived from the original on 2014-05-25. Retrieved 2014-05-25.
  27. ↑ "HyperV - FreeBSD Wiki". Freebsd.org. Archived from the original on 2014-07-18. Retrieved 2014-05-25.
  28. ↑ "Systancia offers application and desktop virtualization in a single product". DataMonitor.
  29. ↑ "Microsoft Windows Server 2008 – Hyper-V solution overview - Gabe Knuth". BrianMadden.com. Archived from the original on 2008-07-04. Retrieved 2012-10-07.
  30. ↑ Stevens, Alan (2008-02-27). "Microsoft's Hyper-V: why all the fuss?". ZDNet . CBS Interactive. Archived from the original on 2009-05-15. Retrieved 2012-10-07.
  31. ↑ Ramji, Sam; Hanrahan, Tom (2009-07-20). "Microsoft Contributes Linux Drivers to Linux Community". News Center. Microsoft. Archived from the original on 2012-04-18. Retrieved 2010-03-02.
  32. ↑ Foley, Mary Jo (2009-07-22). "Pigs are flying low: Why Microsoft open-sourced its Linux drivers". ZDNet . CBS Interactive. Archived from the original on 2012-10-12. Retrieved 2012-08-07.
  33. ↑ Babcock, Charles (2008-04-24). "Microsoft Hyper-V To Flaunt Advanced Virtualization Features". Informationweek.com. Archived from the original on 2014-09-03. Retrieved 2012-10-07.
  34. ↑ Foley, Mary Jo (2009-02-16). "Microsoft and Red Hat sign virtualization pact". ZDNet . CBS Interactive. Archived from the original on 2016-02-08. Retrieved 2012-10-07.
  35. ↑ "Hyper-V Overview". TechNet . Microsoft. Archived from the original on September 15, 2012. Retrieved October 5, 2012.
  36. ↑ Archiveddocs (25 October 2016). "Generation 2 Virtual Machine Overview". docs.microsoft.com. Archived from the original on 2021-01-26. Retrieved 2021-01-19.
  37. ↑ Otey, Michael (24 June 2008). "Guest VM Audio Support under Hyper-V". Windows IT Pro. Penton Media. Archived from the original on 21 October 2014. Retrieved 21 September 2014.
  38. ↑ "Enable Audio in Windows 2008 guest machines running on HyperV". Akshat's Blog. Microsoft. 7 April 2011. Archived from the original on 21 October 2014. Retrieved 21 September 2014.
  39. ↑ Gear, Gavin (5 December 2013). "Overview: Client Hyper-V Enhanced Session Mode in Windows 8.1". Blogging Windows. Microsoft. Archived from the original on 15 October 2014. Retrieved 21 September 2014.
  40. ↑ Cook, John Paul. "DVD writer on Hyper-V server". TechNet Forums. Microsoft. Archived from the original on 2012-03-23. Retrieved 2012-10-07.
  41. ↑ "Using Full DVD/CD Writing Capabilities in a Hyper-V VM | Mark Gilbert's Blog". Mark-gilbert.co.uk. 2012-09-05. Archived from the original on 2016-05-09. Retrieved 2015-01-18.
  42. ↑ 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.
  43. ↑ "Fix Hyper-V Has Not Been Installed on Computer 'localhost'". Techdracula.com. Archived from the original on 2015-10-14. Retrieved 2013-06-06.
  44. 1 2 "A deep dive into Hyper-V Networking (Video and Slides)". Archived from the original on 2012-03-10. Retrieved 2011-09-22.
  45. ↑ "Extending the Hyper-V switch (Video and Slides)". Archived from the original on 2012-05-23. Retrieved 2012-05-10.
  46. ↑ "Hyper-V Virtual Hard Disk Format Overview". TechNet . Microsoft. Archived from the original on August 27, 2012. Retrieved August 25, 2012.
  47. ↑ Reseller, Mike. "Hyper-V Replica in depth". Veeam Software. Archived from the original on 2014-11-29. Retrieved 2014-11-14.
  48. ↑ "What's New in Hyper-V for Windows Server 2012 R2". Technet.microsoft.com. Archived from the original on 2016-06-03. Retrieved 2016-04-26.
  49. ↑ "What's New in Hyper-V for Windows Server 2012 R2". Technet.microsoft.com. Archived from the original on 2016-06-03. Retrieved 2016-04-26.
  50. ↑ "What's New in Hyper-V for Windows Server 2012 R2". Technet.microsoft.com. Archived from the original on 2016-06-03. Retrieved 2016-04-26.
  51. ↑ "What's New in Hyper-V for Windows Server 2012 R2". Technet.microsoft.com. Archived from the original on 2016-06-03. Retrieved 2016-04-26.
  52. ↑ "What's New in Hyper-V for Windows Server 2012 R2". Technet.microsoft.com. Archived from the original on 2016-06-03. Retrieved 2016-04-26.
  53. ↑ "What's New in Hyper-V for Windows Server 2012 R2". Technet.microsoft.com. Archived from the original on 2016-06-03. Retrieved 2016-04-26.
  54. ↑ "What's new in Hyper-V on Windows Server 2016". Docs.microsoft.com. Archived from the original on 2017-10-28. Retrieved 2017-10-27.
  55. ↑ "Run Hyper-V in a Virtual Machine with Nested Virtualization". Docs.microsoft.com. Archived from the original on 2017-10-28. Retrieved 2017-10-27.
  56. ↑ "What's new in Hyper-V on Windows Server 2016". Docs.microsoft.com. Archived from the original on 2019-01-13. Retrieved 2019-02-21.
  57. ↑ "What's new in Windows Server 2019". Docs.microsoft.com. Archived from the original on 2019-03-27. Retrieved 2019-02-21.

Further reading

  1. "Hypervisor Top Level Functional Specification". Microsoft. 2016. Archived from the original on 2017-04-05. Retrieved 2017-04-04.
  2. Koens, Dimitri (2013). "Hyper-V Quick Reference" (PDF). Dimension IT TV. Archived (PDF) from the original on 2016-03-26. Retrieved 2017-04-04.
  3. Howard, John (2006). "WinHEC 2006 Presentation slides". Virtualization Blog. Microsoft. Archived from the original on 2015-12-20. Retrieved 2017-04-04.
  4. Radzikowski, Przemek (2009). "Benchmarking Hyper-V on Windows Server 2008 R2 x64". Archived from the original on 2017-04-23. 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 page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.