Informatika & Komputer    
   
Daftar Isi ☛
(Sebelumnya) HyperTransportHyphen (Berikutnya)

Hyper-V

Hyper-V
Developer(s)Microsoft
Initial releaseJuly 26, 2008 (2008-07-26) (KB950050)[1][2]
Stable releaseR2 Service Pack 1 (KB976932) (standalone)[3][4] / March 15, 2011; 2 years ago (2011-03-15)
Operating systemWindows 8, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008
TypeNative hypervisor
LicenseProprietary
Websitemicrosoft.com/hyper-v

Hyper-V, codenamed Viridian[5] and formerly known as Windows Server Virtualization, is a native hypervisor that enables platform virtualization on x86-64 systems.[6] A beta version of Hyper-V was shipped with certain x86-64 editions of Windows Server 2008, and a finalized version (automatically updated through Windows Update) was released on June 26, 2008.[7] Hyper-V has since been released in a free stand-alone version, and has been upgraded to Release 2 (R2) status.[8][9] It was updated in Windows Server 2012.[10]

Contents

Versions and variants

Hyper-V exists in two variants: as a stand-alone product called Microsoft Hyper-V Server 2012 (containing the current release of Hyper-V) and Microsoft Hyper-V Server 2008 (Hyper-V Server 2008 R2 for the second release), and as an installable role in Windows Server 2012, Windows Server 2008 R2, and Windows Server 2008 (the former containing the current release of Hyper-V).

The stand-alone versions of Hyper-V are free. Hyper-V Server 2008 was released on October 1, 2008. It is a variant of the core installation of Windows Server 2008 that includes full Hyper-V functionality; other Windows Server 2008 roles are disabled, and there are limited Windows Services.[11] The free Hyper-V Server 2008 variant is limited to a command line interface (CLI), where configuration of the "Host" or "Parent" (Hyper-V Server 2008) OS, physical hardware and software is done using shell commands. A new menu driven CLI interface does simplify initial configuration considerably, and some freely downloadable script files extend this concept. Administration and configuration of the "Host" (Hyper-V Server 2008 OS) and the "guest" or virtual OSes is generally done by downloading extended Microsoft Management Consoles that are installed onto a Windows 7 PC or Windows 2008 Server (32 or 64 bit) or System Center Virtual Machine.

Alternatively, another Windows Server 2008 or 2012 computer, with the Hyper-V role installed, can be used to manage Hyper-V Server 2008 by redirecting the management console. Other administration and configuration of Hyper-V Server 2008 can be done using a Remote Desktop RDP session (though still CLI) or redirected standard management consoles (MMC) such as "Computer Management" and "Group Policy (Local)" from a Windows Vista PC or a full installation of Windows Server 2008. This allows much easier "point and click" configuration, and monitoring of the Hyper-V Server 2008. Hyper-V Server Release 2 (R2) was made available in September 2009, its main feature being the inclusion of Windows Powershell v2 for greater CLI control, and the updated Windows Server 2008 R2 code base.

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. A hypervisor instance has to have at least one parent partition, running a supported version of Windows Server (2008, 2008 R2, or 2012). The virtualization stack runs in the parent partition and has direct access to the hardware devices. The parent partition then creates the 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.[12]

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 specialized virtualization-aware implementation of high level communication protocols like SCSI to take advantage of VMBus directly, that allows bypassing any device emulation layer. This makes the communication more efficient, but requires the guest OS to support Enlightened I/O. Windows Server 2008 R2, Windows Server 2008, Windows 7, Windows Vista, Red Hat Enterprise Linux, and SUSE Linux are currently the only operating systems that 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 and specifications

See also: Windows Server 2008#System requirements
  • Host operating system:
    • To install the Hyper-V role, Windows Server 2008 (64-bit only) or 2008 R2 Standard, Enterprise or Datacenter edition or Windows Server 2012 Standard or Datacenter is required. Installation on the Web, Essentials, and/or Foundation editions is not possible; neither is it possible on 32-bit (x86-32) versions of Windows Server 2008 nor IA64 editions.
    • It can be installed regardless of whether the installation is a full or core installation.
  • Processor:
    • An x86-64 processor
    • Hardware-assisted virtualization must be enabled. This is available in processors that include a virtualization option; specifically, Intel VT or AMD Virtualization (AMD-V, formerly code-named "Pacifica").
    • A NX bit-compatible CPU must be available and Hardware Data Execution Prevention (DEP) must be enabled.
    • Although this is not an official requirement, Windows Server 2008 R2 and a CPU with second-level address translation support are recommended for workstations.[13]
      • Second-level address translation is a mandatory requirement for Hyper-V in Windows 8.[14]
  • Memory
    • Minimum 2 GB. (Each virtual machine requires its own memory, and so realistically much more.)
    • Windows Server 2008 Standard (x64) Hyper-V full GUI or Core supports up to 31 GB of memory for running VMs, plus 1 GB for the Hyper-V parent OS.[15]
    • Maximum total memory per system for Windows Server 2008 R2 hosts: 32 GB (Standard) or 2 TB (Enterprise, Datacenter) [16]
    • Maximum total memory per system for Windows Server 2012 hosts: 4 TB
  • Guest operating systems
    • Hyper-V in Windows Server 2008 and 2008 R2 supports virtual machines with up to 4 processors each (1, 2, or 4 processors depending on guest OS-see below )
    • Hyper-V in Windows Server 2012 supports virtual machines with up to 64 processors each.
    • Hyper-V in Windows Server 2008 and 2008 R2 supports up to 384 VMs per system[17]
    • Hyper-V in Windows Server 2012 supports up to 1024 active virtual machines per system.
    • Hyper-V supports both 32-bit (x86) and 64-bit (x64) guest VMs.

Microsoft Hyper-V Server

The stand-alone Hyper-V Server variant does not require an existing installation of Windows Server 2008 nor Windows Server 2008 R2. The standalone installation is called Microsoft Hyper-V Server for the non-R2 version and Microsoft Hyper-V Server 2008 R2. Microsoft Hyper-V server is built with components of Windows and has a Windows Server Core user experience. None of the other roles of Windows Server are available in Microsoft Hyper-V Server. This version supports up to 64 VMs per system.[18] System requirements of Microsoft Hyper-V server are the same for supported guest operating systems and processor, but differ in the following :[19]

  • RAM: Minimum: 1 GB RAM; Recommended: 2 GB RAM or greater; Maximum 1 TB.
  • Available disk space: Minimum: 8 GB; Recommended: 20 GB or greater.

Supported guests

The following table lists supported guest operating systems for versions earlier than Windows Server 2012.[20] Other guest operating systems such as Ubuntu Linux 6.06/6.10/7.10 or Fedora 8/9 are unsupported; however, they have been reported to run.[20][21][22][23]

Guest OSVirtual processorsEdition(s)
Windows 71,2,3 or 4Both x86-32 and x86-64, all editions except home editions (the home editions are Home Premium, Home Basic, and Starter)
Windows Server 2008 R21,2,3 or 4x64, Web, Standard, Enterprise, Datacenter
Windows Server 20081,2,3 or 4Both x86 and x64, Web, HPC, Standard, Enterprise, Datacenter, with or without Hyper-V
Linux (only including SUSE Linux Enterprise Server 10 with SP3 or version 11, Red Hat Enterprise Linux versions 5.2-6.1 and CentOS 5.2-6.2)1,2 or 4Both x86 and x64
Unix ( FreeBSD version 9 )1,2 or 4x64
Windows Server 20031 or 2Both x86 and x64, Standard, Enterprise, Datacenter, SP2 required
Windows Server 2003 R21 or 2Web, Standard, Enterprise, Datacenter, both x86 and x64 except for Web whose 64-bit version is not supported
Windows 2000 Server1Server, Advanced Server, SP4 required
Windows Vista1 or 2Both x86 and x64, all editions except home editions
Windows XP1 or 2x86, Professional edition only, SP3 required (SP2 only supports 1 virtual CPU)
Windows XP x64 Edition1 or 2x64, Professional edition only, SP2 required
Windows Small Business Server 20111, 2 or 4Essentials, Standard (Essentials supports only 2 virtual CPUs)
Windows Home Server 20111, 2 or 4Standard
Windows Storage Server 2008 R2 Essentials1, 2 or 4Essentials
Others (any officially unsupported operating system)1N/A

Desktop virtualization (VDI) products from third-party companies (such as Quest Software vWorkspace, Citrix XenDesktop, Systancia AppliDis Fusion[24] 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.[25] Non-"enlightened" operating systems will run with emulated I/O;[26] however, integration components (which include the VSC drivers) are available for Windows Server 2003 SP2, Windows Vista SP1 and Linux to achieve better performance. Xen-enabled Linux guest distributions can also be paravirtualized in Hyper-V. As of 2013[update] Microsoft officially supports only SUSE Linux Enterprise Server 10 SP1/SP2 x86 and x64 Editions in this way,[27] 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.[28]

Linux support

In July 2009, Microsoft submitted Hyper-V drivers to the kernel, which improve the performance of virtual Linux guest systems in a Windows hosted environment. Microsoft was forced to submit the code when it was discovered that Microsoft had incorporated a Hyper-V network driver with GPL-licensed components statically linked to closed-source binaries.[29] Hyper-V provides basic virtualization support for Linux guests out of the box. Paravirtualization support is, however, available by installing the Linux Integration Components or Satori InputVSC drivers. On July 20, 2009, Microsoft submitted these drivers for inclusion in the Linux kernel under the terms of the GPL,[30] so that kernels from 2.6.32 may include inbuilt Hyper-V paravirtualization support.

Windows Server 2012

Hyper-V in Windows Server 2012 supports the same guest operating systems as the above, with the addition of Windows Server 2012 itself, except that the required version of CentOS is from 6.0 to 6.3 and the required version of Red Hat Enterprise Linux is from 6.0 to 6.3. In addition, Windows XP 32-bit requires SP3 and Windows Vista requires SP2.[31]

VHD compatibility with Virtual Server 2005 and Virtual PC 2004/2007

Hyper-V, like Microsoft Virtual Server and Windows Virtual PC, saves each guest OS to a single virtual hard disk file with the extension .VHD, except in Windows 8 and Windows Server 2012 where it can be the newer .vhdx. This file contains the entire guest OS, though other files can also be configured to allow "undo information" etc.

Older .vhd files from Virtual Server 2005 and Virtual PC 2004/2007 can be copied and used by Hyper-V, but any old virtual machine integration software (equivalents of Hyper-V Integration Services for other virtualization software) 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. Consequently, Windows guests may require re-activation.

Limitations

USB passthrough

Hyper-V does not support virtualized USB ports or COM ports. This fact makes it very inconvenient to run software protected by dongles in the guest. A workaround to access USB drives in Windows guest VMs involves using the Microsoft Remote Desktop Client to "share" host drives with guests over a Remote Desktop Connection.[32][33]

Audio

Audio hardware is not virtualized by Hyper-V although the above Remote Desktop workaround may be used.

Optical drives pass-through

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

Graphics issues on the host

On CPUs without Second Level Address Translation, 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.[36]

In Windows Server 2008, Microsoft officially supported Hyper-V only with the default VGA drivers,[37] 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.[38] Some NVidia graphics drivers did not experience problems so long as Windows Aero was turned off and no 3D applications were running.[36]

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,[39] 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.[40]

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

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 supports live migration in the form of "shared nothing live migration". With adequate Windows permissions present, it is possible to migrate a running virtual machine from one Hyper-V host to another Hyper-V host without shutting down the VM, or without losing network connectivity to the VM.[42][43]

Degraded performance for Windows XP VMs

32-bit Windows XP guests running on Hyper-V experience degraded CPU and I/O performance because the Windows XP kernel frequently accesses the CPU APIC's Task Priority Register (TPR) which Hyper-V intercepts putting more overhead on the hypervisor.[44] While there is no resolution for this issue, some Intel CPUs include a technology called vTPR which works around this issue. AMD CPUs have a software workaround. 32-bit and 64-bit editions of Windows Server 2003, Windows XP x64 Edition and Windows Vista and later Windows versions are not affected.

NIC teaming

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

No support for home editions of Windows

The management tools for Hyper-V are not compatible with Windows Vista Home Basic or Windows Vista Home Premium.[47][48] This is also the case for Windows 7 home editions (Home Premium, Home Basic, and Starter).

Windows Server 2012

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

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

See also

References

  1. ^ "Comprehensive Daftar/Tabel -- Hyper-V Updates". Technet.microsoft.com. Retrieved 2010-03-02. 
  2. ^ "Description of the update for the release version of the Hyper-V technology for Windows Server 2008". Support.microsoft.com. 2010-11-22. Retrieved 2012-10-07. 
  3. ^ "Hyper-V Update List for Windows Server 2008 R2". Technet.microsoft.com. Retrieved 2012-10-07. 
  4. ^ "Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2". Support.microsoft.com. 2012-10-02. Retrieved 2012-10-07. 
  5. ^ "Microsoft to ship Windows Server 2008, over time, in eight flavors". Retrieved 2007-11-13. 
  6. ^ Paul Thurrott. "Windows Server Virtualization Preview". Retrieved 2007-09-25. 
  7. ^ "Announcement available from the Microsoft download centre". Retrieved 2008-06-26. 
  8. ^ "Microsoft Hyper-V Server". Microsoft. p. 1. Retrieved January 12, 2012. Text " Virtualization " ignored (help); Text " Virtual " ignored (help)
  9. ^ "Download: Microsoft® Hyper-V™ Server 2008 R2 SP1 - Microsoft Download Center - Download Details". Microsoft.com. 2011-12-04. Retrieved 2012-10-07. 
  10. ^ a b "Server Virtualization Features". Microsoft. Retrieved October 05, 2012. 
  11. ^ "Microsoft Helps Customers Overcome Barriers to Virtualization and Get Virtual Now". PressPass (Press release). Microsoft. October 1, 2008 2. Retrieved 2008-10-02. 
  12. ^ "Benchmarking Hyper-V on Windows Server 2008 R2 x64". Retrieved 2010-01-28. 
  13. ^ "Understanding High-End Video Performance Issues with Hyper-V - Ben Armstrong - Site Home - MSDN Blogs". Blogs.msdn.com. 2009-11-17. Retrieved 2012-10-07. 
  14. ^ Thurott, Paul. "Q: Will Windows Server 2012 require the processor to support SLAT?". 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. ^ "Microsoft Hyper-V Server:Frequently asked questions". Microsoft.com. Retrieved 2012-10-07. 
  19. ^ "Microsoft Hyper-V Server: System Requirements". Microsoft.com. Retrieved 2010-03-16. 
  20. ^ a b "About Virtual Machines and Guest Operating Systems for Hyper-V". Microsoft.com. Retrieved 2012-10-07. 
  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. Retrieved 2012-10-07. 
  23. ^ "Install Ubuntu 7.10 on Hyper-V". Haiders.net. 2008-04-04. Retrieved 2012-10-07. 
  24. ^ "Systancia offers application and desktop virtualization in a single product". DataMonitor. 
  25. ^ "Microsoft Windows Server 2008 – Hyper-V solution overview - Gabe Knuth". BrianMadden.com. Retrieved 2012-10-07. 
  26. ^ Stevens, Alan (2008-02-27). "Microsoft's Hyper-V: why all the fuss? | ZDNet". Reviews.zdnet.co.uk. Retrieved 2012-10-07. 
  27. ^ Babcock, Charles (2008-04-24). "Microsoft Hyper-V To Flaunt Advanced Virtualization Features". Informationweek.com. Retrieved 2012-10-07. 
  28. ^ Foley, Mary Jo (2009-02-16). "Microsoft and Red Hat sign virtualization pact | ZDNet". Blogs.zdnet.com. Retrieved 2012-10-07. 
  29. ^ Mary Jo Foley (2009-07-22). "Pigs are flying low: Why Microsoft open-sourced its Linux drivers". ZDNet. 
  30. ^ "Microsoft Contributes Linux Drivers to Linux Community: Roundtable Q&A: Sam Ramji, senior director of Platform Strategy at Microsoft, and Tom Hanrahan, director of Microsoft’s Open Source Technology Center, discuss the company’s release of Linux device driver code under General Public License v2". Microsoft.com. 2009-07-20. Retrieved 2010-03-02. 
  31. ^ "Hyper-V Overview". Microsoft. Retrieved October 05, 2012. 
  32. ^ "Hyper-V FAQ [general]". Microsoft TechNet. Microsoft. Retrieved 2012-10-07. 
  33. ^ "Known Issues with Running Windows Small Business Server 2008 in a Hyper-V Environment". Microsoft TechNet. Microsoft. Retrieved 2012-10-07. 
  34. ^ "DVD writer on Hyper-V server". Social.technet.microsoft.com. Retrieved 2012-10-07. 
  35. ^ "Using Full DVD/CD Writing Capabilities in a Hyper-V VM | Mark Gilbert's Blog". Mark-gilbert.co.uk. 2012-09-05. Retrieved 2012-10-07. 
  36. ^ a b Armstrong, Ben. "Understanding High-End Video Performance Issues with Hyper-V". 
  37. ^ "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. 
  38. ^ Armstrong, Ben. "Hyper-V versus Desktop Computing". 
  39. ^ Finn, Aidan. "Windows Server 2012 Hyper-V DOES NOT Require SLAT (EPT/NPT) Capable Processors". 
  40. ^ Brodkin, Jon. "Hyper-V coming to Windows 8—with new hardware virtualization requirement". 
  41. ^ "Hyper-V Live Migration vs. Quick Migration". Virtualization Team. 2008-09-29. Retrieved 2012-10-07. 
  42. ^ Conger, Jason (18 September 2012). "Video: Microsoft Hyper-V Shared Nothing Live Migration". Jason Conger Blog. Retrieved 11 November 2012. 
  43. ^ Waggoner, Rob (23 July 2012). "Shared Nothing Live Migration on Windows Server 2012". TechNet Blogs. Microsoft. Retrieved 11 November 2012. 
  44. ^ "Degraded I/O Performance using a Windows XP Virtual Machine with Windows Server 2008 Hyper-V". Technet.microsoft.com. Retrieved 2012-10-07. 
  45. ^ "Microsoft Support Policy for NIC Teaming with Hyper-V". Support.microsoft.com. 2012-01-17. Retrieved 2012-10-07. 
  46. ^ "NIC Teaming Overview". Microsoft. February 29, 2012. Retrieved October 07, 2012. 
  47. ^ "Install and Configure Hyper-V Tools for Remote Administration". Technet.microsoft.com. Retrieved 2012-10-07. 
  48. ^ "Install and Configure Hyper-V Tools for Remote Administration". Technet.microsoft.com. Retrieved 2012-10-07. 
  49. ^ a b "A deep dive into Hyper-V Networking (Video and Slides)". 
  50. ^ "Extending the Hyper-V switch (Video and Slides)". 
  51. ^ "Hyper-V Virtual Hard Disk Format Overview". Technet.microsoft.com. Retrieved August 25, 2012. 
  52. ^ "Microsoft announces "RemoteFX," the Calista-based Hyper-V-requiring PC-over-IP competitor". Brianmadden.com. Retrieved 2012-10-07. 

Further reading

External links

(Sebelumnya) HyperTransportHyphen (Berikutnya)