From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Microsoft / Windows (Rated B-class, Low-importance)
WikiProject icon This article is within the scope of WikiProject Microsoft, a collaborative effort to improve the coverage of articles relating to Microsoft on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
B-Class article B  This article has been rated as B-Class on the project's quality scale.
 Low  This article has been rated as Low-importance on the project's importance scale.
Taskforce icon
This article is supported by WikiProject Microsoft Windows (marked as Mid-importance).

a little help[edit]

Only architecture info[edit]

Why does this article contain ONLY architecture info? No general info on supported guest OSes? —Preceding unsigned comment added by (talk) 06:46, 3 April 2008 (UTC)

Direct Hardware Access[edit]

Unfortunately, this article does not answer the questions I have at the moment. I understand that Hyper-V does not have an USB or sound support. By the look of the diagram, it looks like the Root partition has not got any more direct hardware access than the Child partitions. Does this mean that even the host Root partition OS (Windows 2008) does not have USB or sound support? If it does, does it also have direct graphics card access? ie. Can the host (Root) OS (Windows 2008) use the physical hardware graphics card directly, with 3D acceleration? Jason404 (talk) 15:11, 1 August 2008 (UTC)

Yes, the root partition has full access to all of the hardware, including hardware video. The performance for video hardware is not ideal (depending on drivers and the specific cards used) because they currently tend to do operations that are expensive when running under a hypervisor. —Preceding unsigned comment added by (talk) 09:59, 24 October 2008 (UTC)

Memory requirements / usage Hyper-V Core[edit]

Now that Microsoft is giving away Win2008 Core Hyper-V, I think this article needs to focus more on this aspect - "free software".

Microsoft Hyper-V server is a freeware not a free software

Hyper-V is somewhat hyped (no pun intended!) considering it's limitations, and features. It does not have much over Windows 2003 and Virtual Server 2005, other than the fact that Microsoft now give away the whole O/S and Hypervisor for free! Few will needlessly pay for a full blown version of Windows 2008 if they wan to run virtualised servers.

Please can someone clarify the memory requirements / usage aspect, especially for the free Hyper-V Core.

  • Stating the 2 GB memory minimum completely looses the point, as the server needs loads of memory for the virtualised "guest" O/S's.
It requires minimum 1GB , recommended 2GB for the host , you have to add your memory needed for guest operating system to your requiremnts .Melnakeeb (talk) 14:38, 16 March 2010 (UTC)
  • What is the maximum amount of memory that the free Core product can access, is there a 4 GB type limitation as the older "Standard" Windows versions.
Of course not, as it only runs on a 64 bit arch. -- (talk) 12:48, 13 June 2009 (UTC)
For Microsoft Hyper-V R2 it supports up to 1 TB . Microsoft Hyper-V server support less memory - but also a number that is very hard to reach :) , but I don't know how much exactly . Melnakeeb (talk) 14:38, 16 March 2010 (UTC)

Unclear english[edit]

Can someone who knows this stuff clean up the grammar/usage and clarify the first paragraph? —Preceding unsigned comment added by (talk) 21:04, 15 October 2008 (UTC)

I removed the poorly written information on hypervisors in general, as it does not belong in an article about a specific hypervisor. - Josh (talk | contribs) 21:17, 15 October 2008 (UTC)

Limitations of Hyper-V[edit]

It would be useful to detail the limitations of Hyper-V as a Virtualization platform, since Wikipedia is often used to get a "bird's-eye" view of a subject or technology. —Preceding unsigned comment added by (talk) 18:50, 9 January 2009 (UTC)

Opening Paragraph[edit]

Can the reference to beta be removed from the opening paragraph, Windows Update takes care of this, so the opening seems rather dated and may cause unnecessary confusion. Now that Hyper-V release 2 is close to fruition, now is a good time to move on! —Preceding unsigned comment added by (talk) 08:12, 19 May 2009 (UTC)

Disambig needed[edit]

The first para links to virtualization, but gives no clue which of the options listed there applies to Hyper-V. --Tom Edwards (talk) 16:32, 21 July 2009 (UTC)

  • For some strange reason people like to link to disambiguation articles when they should directly link to the article relative to the subject. Its either lazy editing or a complete lack of knowledge of the subject at hand. (talk) 14:47, 21 April 2010 (UTC)

Completely missing the point[edit]

From the article:

“[...] which makes it pointless to use Hyper-V on workstations.”

Um, yes. The OS is called Windows Server 2008 (R2) for a reason. Hyper-V is not intended for use on workstations. That's like complaining about Windows XP/Vista/7 only allowing one interactive session. --MushroomCloud (talk) 14:13, 16 December 2009 (UTC)

Nobody says that hyper-v is intended for workstations; however, the impossibility to use it on a workstation is a major drawback, which, imho, should be mentioned in "Limitations". In common case, without WDDM drivers, with default VGA driver shipped with the OS, users are unable to use any resolution except for default 640*480, 800*600 etc or dual-monitor configurations, so it seems that hyper-v should be used only on headless servers. The OS is called Windows Server 2008, but, with hyper-v, there is nearly no possibility to use windows except for by connecting to server by Remote Desktop Protocol.
Because it is impossible to use hyper-v on workstations, it is also impossible to set up e.g. a demo laptop with hyper-v -- how can you show anybody a real live demo if just switching between windows makes system hung for 10-20 seconds? Also, if someone will try to play with hyper-v on their desktop/laptop before making a decision of using hyper-v over other hypervisors, they will face the same problem, and, of course, will immediately make a decision against hyper-v (when they will see such worse performance on the host, they will not even try guests). If you will read that thread on technet, you will see that issue in subject possibly have significantly lowered hyper-v adoption on the market.
MS gives us a technology which cannot be tested on the workstation; however, MS makes all to seem that hyper-v could be used on workstation (with all this graphic installation, common Windows interface etc -- in contrast with competitors). There is no any warnings like "Do not install Windows Server / Hyper-V on your workstation, it will result in a degraded graphic performance".
I'm sorry for such a large post with such a terrible English.
Penartur (talk) 17:56, 16 December 2009 (UTC)
I've fixed some errors in the corresponding section. According to link given by, there is no solution exists for WS 2008 SP2, only for R2. Also, the issue was not solved; it is just the issue roots are not appearing on R2 if EPT is available; from what i've understood, there was no "fix" for the issue. R2 does support EPT feature of CPU and there is no loss of performance when using EPT, that's all. Also, it seems that the problem will never be resolved on older systems, as now there is no need in these. Penartur (talk) 23:24, 15 January 2010 (UTC)

Rename article to "Microsoft Hyper-V"[edit]

May I suggest that this article be renamed to "Microsoft Hyper-V". That's what it's called in the opening sentence, and the text above the info box. --RenniePet (talk) 00:02, 20 February 2010 (UTC)

Just to mention that I've changed my mind, having queried the rules involved and being informed that WP:COMMONNAME applies. --RenniePet (talk) 19:22, 24 February 2010 (UTC)


Core: Micosoft Hyper-V server installation size ==Windows server 2008 core installation size && [1]:Available disk space: Minimum: 8 GB; Recommended: 20 GB or greater (additional disk space needed for each guest operating system).

Full: Contradiction between: [2] and [3] but both higher than values mentioned in article . Melnakeeb (talk) 09:12, 19 March 2010 (UTC)

For Core Installation: Core installation is never 3 GB of Size for sure .

  • How much exactly ? no reference.
  • From a personal experience it was 11 GB , including memory paging file , for 4GB RAM)
  • as Microsoft Hyper-V server is a window server 2008 with hyper-v role installed and all other roles disabled , core installation size should equate with size of Microsoft hyper-v server , Microsoft in[[4]] specifies minimum requirements of Microsoft Hyper-V server R2 as 8GB hard disk and recommended as 20GB hard disk space . Microsoft removed any trace from its website for system requirements for Microsoft Hyper-V server ( noted by users as R1 as contrast to R2)

For Full installation size: Definitely not 11GB .

  • How much exactly ? no reference.
  • Microsoft specify 2 contradicting system requirements in its website : see these two links:

( both these links are for R1 , R2 has a differnt specification here : [7] Melnakeeb (talk) 18:08, 19 March 2010 (UTC)

Linux support[edit]

The same information is presented in the first and last sentence of this section of the article. Please revise and edit to include the most information with the most efficacious presentation. — Preceding unsigned comment added by Techpriest (talkcontribs) 16:28, 12 July 2013 (UTC)


The introductory paragraph is still extremely confusing. Could someone more knowledgable scrap it and rewrite it?


Current lead reads:

Hyper-V, codenamed Viridian and formerly known as Windows Server Virtualization, is a native hypervisor; it can create virtual machines on x86-64 systems. Starting with Windows 8, Hyper-V supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT.
A host server running Hyper-V could be accessed remotely by multiple guest computers. Each guest computer could perform as if they are using the host server directly. Users on the guest computers could run applications in the host server remotely, even though that application is not available on the guest computer.
A beta version of Hyper-V was shipped with certain x86-64 editions of Windows Server 2008, and a finalized version (delivered through Windows Update) was released on June 26, 2008. Hyper-V has since been released in a free stand-alone version, and has been upgraded to Release 2 (R2) status. It was updated in Windows Server 2012.

I am confused by the use of various verb tenses in this. Why does it say that a host server "could" be accessed remotely? Can it no longer be accessed remotely? Why does it say that Hyper-V "supersedes" Virtual PC; didn't it "supercede" it? I also don't understand why the Viridian codename is mentioned in the lead, when it is not mentioned at all in the body of the article. I don't understand what "guest" and "remote" are supposed to mean, and what the difference is. I don't understand why the detailed version history (including the beta) belong in the lead. Do server versions have a different hardware virtualization component, or no hardware virtualization component? Here is a proposed rewrite, where I've probably gotten some things wrong. Please correct before I change it in the article.

Hyper-V, formerly known as Windows Server Virtualization, is a native hypervisor which runs multiple virtual machines on x86-64 hardware. Each virtual machines acts as though it is running directly on the native hardware.
Hyper-V was released in 2008. As of Windows 8, it is the standard hardware virtualization component of the client editions of Windows NT, replacing Windows Virtual PC. Hyper-V has also been released in a free stand-alone version.

Best, --Macrakis (talk) 23:33, 13 February 2015 (UTC)

Hello, Macrakis
I'll go over your proposals one by one:
  1. "Could" isn't always the past tense for "can"; it is a modal verb that is sometimes used for denoting subjunctive mood. The full verb here is "could be accessed" which is subjunctive passive simple present. The subjunctive simple present equivalent is "could access". (Also, when someone says "I could use a glass of water", he is not asserting that he no longer needs one; rather, he is saying that he needs one right now!) Please consult a grammar book.
  2. Per WP:BOLDTITLE, the lead may mention any important alternative names. Also please apply common sense: banishing an important piece of info from the article is wrong. Even if WP:BOLDTITLE wasn't in effect, the solution was to include the codename in the body text.
  3. The rest of the lead is a summary of § Versions and variants and § Architecture. Per WP:LEAD, the lead must be a standalone summary.
The current lead could use some tweaks but your proposal is, I am afraid, out of the question.
Best regards,
Codename Lisa (talk) 02:43, 14 February 2015 (UTC)
Thanks for your response.
Yes, "could" can be a modal. Why do you think a modal is appropriate here? A simple present seems perfectly adequate, like this:
A host server running Hyper-V can be accessed remotely by multiple guest computers.
Anyway, I find this sentence hard to understand in other ways. Is it supposed to mean that host functions can be accessed by guest VMs? Does that belong in the lead?
As for the name Viridian, I agree that important alternative names belong in the lead. It just seems strange that, if it is so noteworthy, it is not mentioned again in the article.
I agree that the lead should be a standalone summary of the content of the article. The version history of a piece of software is not generally necessary in that standalone summary. --Macrakis (talk) 20:54, 14 February 2015 (UTC)
  1. The purpose was to use subjunctive mood because the client–server model is not mandatory. The only other mood that could be used was the declarative mood but that gives wrong info. The declarative form of "could be accessed" is "is accessed", which changes the meaning and makes the non-mandatory nature mandatory.
  2. Good find! I changed the article. The writer had clearly mistakenly used "host" for "server" and "guest" for "client". Guest is a virtual machine running inside the host. Host is Hyper-V (in this article). But a server is a computer running the host while client is a computer (be it actual or virtual) that connects over the network.
  3. Again, you are right. The article needs a history section, where the conception of codename Viridian can be explained with date. This error should be fixed by writing said section. Maybe sometimes later, when I had some times to investigate...
  4. Again, same as #3. I think we can leave them there for while.
Best regards,
Codename Lisa (talk) 03:18, 15 February 2015 (UTC)

"Windows Server 2012" is not about Hyper-V[edit]

Features in "Windows Server 2012" paragraph like "Multi-tenancy", "Network virtualization" and probably others refer to SCVMM, not Hyper-V. (talk) 00:00, 3 July 2015 (UTC)

"USB Passthrough" section reads oddly[edit]

I don't know enough about the subject to make any changes, but I was reading this article and found that the USB passthrough section seems really, really strange. "Hyper-V supports USB devices in Hyper-V guest VMs with a new feature called Virtual Machine Connection- Enhanced Session Mode.[34] This fact makes it very inconvenient to run software protected by dongles in the guest."? Why would supporting USB devices make it inconvenient to use dongles? Was the first sentence in this section changed and the second half left untouched? It is a mystery. Hopefully someone with more knowledge about the subject or the article's history can help out here. ✨Nivomi👀👌💯 (talk) 08:35, 19 April 2016 (UTC)

vt-x handling ?[edit]

The section on vt-x handling states that Hyper-V needs to be disabled if the user wishes to use (say) the Microsoft Android emulator, however that appears to directly contradict the following from Microsoft: - is this section now out of date ? — Preceding unsigned comment added by Khmayfin (talkcontribs) 22:42, 21 February 2017 (UTC)