-->
Applies To: Windows Server 2016, Windows Server 2019
Hyper-V supports several versions of Windows Server, Windows, and Linux distributions to run in virtual machines, as guest operating systems. This article covers supported Windows Server and Windows guest operating systems. For Linux and FreeBSD distributions, see Supported Linux and FreeBSD virtual machines for Hyper-V on Windows. Turn this software off to use Windows 10 in Boot Camp. Microsoft Hyper-V must be off for Windows 10 to start up on a Mac using Boot Camp. If you try to boot into Windows 10 with Hyper-V turned on, you see only a black screen and Windows doesn't start.
Hyper-V supports several versions of Windows Server, Windows, and Linux distributions to run in virtual machines, as guest operating systems. This article covers supported Windows Server and Windows guest operating systems. For Linux and FreeBSD distributions, see Supported Linux and FreeBSD virtual machines for Hyper-V on Windows.
Some operating systems have the integration services built-in. Others require that you install or upgrade integration services as a separate step after you set up the operating system in the virtual machine. For more information, see the sections below and Integration Services.
Supported Windows Server guest operating systems
Following are the versions of Windows Server that are supported as guest operating systems for Hyper-V in Windows Server 2016 and Windows Server 2019.
Guest operating system (server) | Maximum number of virtual processors | Integration Services | Notes |
---|---|---|---|
Windows Server, version 1909 | 240 for generation 2; 64 for generation 1 | Built-in | Greater than 240 virtual processor support requires Windows Server, version 1903 or later guest operating systems. |
Windows Server, version 1903 | 240 for generation 2; 64 for generation 1 | Built-in | |
Windows Server, version 1809 | 240 for generation 2; 64 for generation 1 | Built-in | |
Windows Server 2019 | 240 for generation 2; 64 for generation 1 | Built-in | |
Windows Server, version 1803 | 240 for generation 2; 64 for generation 1 | Built-in | |
Windows Server 2016 | 240 for generation 2; 64 for generation 1 | Built-in | |
Windows Server 2012 R2 | 64 | Built-in | |
Windows Server 2012 | 64 | Built-in | |
Windows Server 2008 R2 with Service Pack 1 (SP 1) | 64 | Install all critical Windows updates after you set up the guest operating system. | Datacenter, Enterprise, Standard and Web editions. |
Windows Server 2008 with Service Pack 2 (SP2) | 8 | Install all critical Windows updates after you set up the guest operating system. | Datacenter, Enterprise, Standard and Web editions (32-bit and 64-bit). |
Supported Windows client guest operating systems
Following are the versions of Windows client that are supported as guest operating systems for Hyper-V in Windows Server 2016 and Windows Server 2019.
Guest operating system (client) | Maximum number of virtual processors | Integration Services | Notes |
---|---|---|---|
Windows 10 | 32 | Built-in | |
Windows 8.1 | 32 | Built-in | |
Windows 7 with Service Pack 1 (SP 1) | 4 | Upgrade the integration services after you set up the guest operating system. | Ultimate, Enterprise, and Professional editions (32-bit and 64-bit). |
Guest operating system support on other versions of Windows
The following table gives links to information about guest operating systems supported for Hyper-V on other versions of Windows.
Host operating system | Topic |
---|---|
Windows 10 | Supported Guest Operating Systems for Client Hyper-V in Windows 10 |
Windows Server 2012 R2 and Windows 8.1 | - Supported Windows Guest Operating Systems for Hyper-V in Windows Server 2012 R2 and Windows 8.1 - Linux and FreeBSD Virtual Machines on Hyper-V |
Windows Server 2012 and Windows 8 | Supported Windows Guest Operating Systems for Hyper-V in Windows Server 2012 and Windows 8 |
Windows Server 2008 and Windows Server 2008 R2 | About Virtual Machines and Guest Operating Systems |
How Microsoft provides support for guest operating systems
Microsoft provides support for guest operating systems in the following manner:
- Issues found in Microsoft operating systems and in integration services are supported by Microsoft support.
- For issues found in other operating systems that have been certified by the operating system vendor to run on Hyper-V, support is provided by the vendor.
- For issues found in other operating systems, Microsoft submits the issue to the multi-vendor support community, TSANet.
See also
With the release of Windows Server 2012 (yes, I'm aware this is the Macintosh Thread, thankyou), comes Microsoft's new Hyper-V implementation, an Ars Front Page article explains: http://arstechnica.com/information-technology/2012/09/first-look-hyper-v-2012-targets-vmwares-air-supply/
My current Windows box is from November 2009, based on the Ars Hotrod October 2009 build, with SSD for the operating system, Windows 7 Pro, and 8GB memory.
With Hyper-V offering many virtual machines on the one box, I can have my existing Windows 7 implementation - AS IS - hosted in a Windows 8 Hyper-V Virtual Machine, without any software changes, which would be very magical if it worked.
Additionally, on the same box, I could host a Hackintosh VM setup, and get my toes wet in the completely different world of the Apple Mac 'closed garden'. I'm already part-way embroiled in the Apple world, with my iPad and my iPhone, so having a Mac makes some modicum of sense; my investment in PC software over the years, and my library of games, greatly-deters me from doing a full on 'switch' to the Mac side fo the fence.
Hardware wise, I'm thinking:
I7 CPU of some kind (must support SLAT whatever that is)
16GB-32GB Ram
.5TB SSD.
3-5TB storage.
Some variant of Windows 8 with Client Hyper-V
I've read the Hackintosh thread, with all the caveats about hardware, 'installed' RAM, and what do-dads are required to get a stable current-release Macintosh OS install running on 'non-official' hardware. It looks plenty annoying to do this with a physical box.
But with a virtual machine, it should be just another generic lump of hardware?
What's the hiccough in having a 'Macintosh' for the cost of a licensed copy of the software, running on Windows 8 and Client Hyper-V.
Here's the Microsoft blurb : Survival Guide for Client-Hyper-V, where the client Hyper-V software itself is a free download (you must cover licensing for any VM hosted O/S's)
Please discuss, I'd like to see some positive outcome from this, rather than some semi-legalese BS discussion about 'hackintosh', thanks.
If there are more appropriate areas of the web where this is already being discussed, links would be appreciated.
My current Windows box is from November 2009, based on the Ars Hotrod October 2009 build, with SSD for the operating system, Windows 7 Pro, and 8GB memory.
With Hyper-V offering many virtual machines on the one box, I can have my existing Windows 7 implementation - AS IS - hosted in a Windows 8 Hyper-V Virtual Machine, without any software changes, which would be very magical if it worked.
Additionally, on the same box, I could host a Hackintosh VM setup, and get my toes wet in the completely different world of the Apple Mac 'closed garden'. I'm already part-way embroiled in the Apple world, with my iPad and my iPhone, so having a Mac makes some modicum of sense; my investment in PC software over the years, and my library of games, greatly-deters me from doing a full on 'switch' to the Mac side fo the fence.
Hardware wise, I'm thinking:
I7 CPU of some kind (must support SLAT whatever that is)
16GB-32GB Ram
.5TB SSD.
3-5TB storage.
Some variant of Windows 8 with Client Hyper-V
I've read the Hackintosh thread, with all the caveats about hardware, 'installed' RAM, and what do-dads are required to get a stable current-release Macintosh OS install running on 'non-official' hardware. It looks plenty annoying to do this with a physical box.
But with a virtual machine, it should be just another generic lump of hardware?
What's the hiccough in having a 'Macintosh' for the cost of a licensed copy of the software, running on Windows 8 and Client Hyper-V.
Here's the Microsoft blurb : Survival Guide for Client-Hyper-V, where the client Hyper-V software itself is a free download (you must cover licensing for any VM hosted O/S's)
Please discuss, I'd like to see some positive outcome from this, rather than some semi-legalese BS discussion about 'hackintosh', thanks.
If there are more appropriate areas of the web where this is already being discussed, links would be appreciated.