This article is rated B-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||
|
Why does this article contain ONLY architecture info? No general info on supported guest OSes? —Preceding unsigned comment added by 221.128.147.224 ( talk) 06:46, 3 April 2008 (UTC)
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)
Now that Microsoft is giving away Win2008 Core Hyper-V, I think this article needs to focus more on this aspect - "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.
Can someone who knows this stuff clean up the grammar/usage and clarify the first paragraph? —Preceding unsigned comment added by 66.97.114.26 ( talk) 21:04, 15 October 2008 (UTC)
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 204.15.87.226 ( talk) 18:50, 9 January 2009 (UTC)
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 79.121.186.28 ( talk) 08:12, 19 May 2009 (UTC)
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)
From the article:
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)
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)
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 .
For Full installation size: Definitely not 11GB .
( both these links are for R1 , R2 has a differnt specification here : [7] Melnakeeb ( talk) 18:08, 19 March 2010 (UTC)
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 ( talk • contribs) 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:
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.
Best, -- Macrakis ( talk) 23:33, 13 February 2015 (UTC)
Features in "Windows Server 2012" paragraph like "Multi-tenancy", "Network virtualization" and probably others refer to SCVMM, not Hyper-V. 92.50.219.161 ( talk) 00:00, 3 July 2015 (UTC)
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)
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: https://msdn.microsoft.com/en-us/library/mt228280.aspx - is this section now out of date ? — Preceding unsigned comment added by Khmayfin ( talk • contribs) 22:42, 21 February 2017 (UTC)
Hello fellow Wikipedians,
I have just modified 2 external links on Hyper-V. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
This message was posted before February 2018.
After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than
regular verification using the archive tool instructions below. Editors
have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the
RfC before doing mass systematic removals. This message is updated dynamically through the template {{
source check}}
(last update: 18 January 2022).
Cheers.— InternetArchiveBot ( Report bug) 13:26, 9 November 2017 (UTC)
Which leads to confusion like "What does installing Win10 Hyper-V do?" (It installs hypervisor management software), "Why does WSL work without Hyper-V? (The hypervisor is a core component of Win10), and "What is the difference between Hyper-V on Win Server and Hyper-V on Win Pro? (The hypervisor, which is a core component, is the same, but the management software contains different features on Server versions)
The Win10 Virtual Machine feature enables integration with Explorer (same as Win7 Virtual Machine),
The Win10 Windows Hypervisor platform is a management API, for when you want to run DOSbox or Vmware on the MS hypervisor instead of Hyper-V on the MS hypervisor.
This article is rated B-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||
|
Why does this article contain ONLY architecture info? No general info on supported guest OSes? —Preceding unsigned comment added by 221.128.147.224 ( talk) 06:46, 3 April 2008 (UTC)
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)
Now that Microsoft is giving away Win2008 Core Hyper-V, I think this article needs to focus more on this aspect - "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.
Can someone who knows this stuff clean up the grammar/usage and clarify the first paragraph? —Preceding unsigned comment added by 66.97.114.26 ( talk) 21:04, 15 October 2008 (UTC)
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 204.15.87.226 ( talk) 18:50, 9 January 2009 (UTC)
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 79.121.186.28 ( talk) 08:12, 19 May 2009 (UTC)
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)
From the article:
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)
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)
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 .
For Full installation size: Definitely not 11GB .
( both these links are for R1 , R2 has a differnt specification here : [7] Melnakeeb ( talk) 18:08, 19 March 2010 (UTC)
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 ( talk • contribs) 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:
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.
Best, -- Macrakis ( talk) 23:33, 13 February 2015 (UTC)
Features in "Windows Server 2012" paragraph like "Multi-tenancy", "Network virtualization" and probably others refer to SCVMM, not Hyper-V. 92.50.219.161 ( talk) 00:00, 3 July 2015 (UTC)
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)
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: https://msdn.microsoft.com/en-us/library/mt228280.aspx - is this section now out of date ? — Preceding unsigned comment added by Khmayfin ( talk • contribs) 22:42, 21 February 2017 (UTC)
Hello fellow Wikipedians,
I have just modified 2 external links on Hyper-V. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
This message was posted before February 2018.
After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than
regular verification using the archive tool instructions below. Editors
have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the
RfC before doing mass systematic removals. This message is updated dynamically through the template {{
source check}}
(last update: 18 January 2022).
Cheers.— InternetArchiveBot ( Report bug) 13:26, 9 November 2017 (UTC)
Which leads to confusion like "What does installing Win10 Hyper-V do?" (It installs hypervisor management software), "Why does WSL work without Hyper-V? (The hypervisor is a core component of Win10), and "What is the difference between Hyper-V on Win Server and Hyper-V on Win Pro? (The hypervisor, which is a core component, is the same, but the management software contains different features on Server versions)
The Win10 Virtual Machine feature enables integration with Explorer (same as Win7 Virtual Machine),
The Win10 Windows Hypervisor platform is a management API, for when you want to run DOSbox or Vmware on the MS hypervisor instead of Hyper-V on the MS hypervisor.