October 7, 2024, Monday, 280

X86 Virtualization

From NeoWiki

(Difference between revisions)
Jump to: navigation, search
m
m (→See also)
 
(3 intermediate revisions by one user not shown)
Line 1: Line 1:
−
'''x86 virtualization''' is the method by which [[x86]]-based "guest" operating systems are run under another "host" x86 operating system, with little or no modification of the guest OS. The x86 processor architecture did not originally meet the [[Popek and Goldberg virtualization requirements]]. As a result, it was very difficult to implement a general [[virtual machine]] on an x86 processor. In 2005 and 2006, extensions to their respective x86 architectures by [[Intel]] and [[AMD]] resolved this and other virtualization difficulties.
+
'''x86 virtualization''' is the method by which x86-based "guest" operating systems are run under another "host" x86 operating system, with little or no modification of the guest OS. The x86 processor architecture did not originally meet the Popek and Goldberg virtualization requirements. As a result, it was very difficult to implement a general virtual machine on an x86 processor. In 2005 and 2006, extensions to their respective x86 architectures by Intel and AMD resolved this and other virtualization difficulties.
  
 
==Software techniques==
 
==Software techniques==
−
On [[February 8]], [[1999]], [[VMware]] introduced the first x86 virtualization product, "VMware Virtual Platform", based on earlier research by its founders at [[Stanford University]]. VMware filed for a patent on their techniques in October 1998, which was granted as {{US patent|6,397,242}} on [[May 28]], [[2002]]. VMware and similar virtualization software for the x86 must employ very sophisticated techniques to trap and virtualize the execution of certain instructions. These techniques incur some performance overhead as compared to a VM running on a natively virtualizable architecture such as the IBM System/370 or Motorola MC68020.
+
On February 8, 1999, VMware introduced the first x86 virtualization product, "VMware Virtual Platform", based on earlier research by its founders at Stanford University. VMware filed for a patent on their techniques in October 1998, which was granted as US patent 6,397,242 on May 28, 2002. VMware and similar virtualization software for the x86 must employ very sophisticated techniques to trap and virtualize the execution of certain instructions. These techniques incur some performance overhead as compared to a VM running on a natively virtualizable architecture such as the IBM System/370 or Motorola MC68020.
  
−
Kevin Lawton started the [[Plex86]] project (originally called "freemware") to create [[Free software]] for x86 virtualization. The focus of this project has since changed to support only Linux as a guest operating system, but prior to that Mr. Lawton published the paper [http://www.floobydust.com/virtualization/lawton_1999.txt Running multiple operating systems concurrently on an IA32 PC using virtualization techniques], which gives an analysis of what aspects of the x86 architecture are hard to virtualize and some techniques to overcome these difficulties.
+
Kevin Lawton started the Plex86 project (originally called "freemware") to create Free software for x86 virtualization. The focus of this project has since changed to support only Linux as a guest operating system, but prior to that Mr. Lawton published the paper [http://www.floobydust.com/virtualization/lawton_1999.txt Running multiple operating systems concurrently on an IA32 PC using virtualization techniques], which gives an analysis of what aspects of the x86 architecture are hard to virtualize and some techniques to overcome these difficulties.
  
−
[[Microsoft]] offers two Windows-based x86 virtualization products, [[Microsoft Virtual PC]] and [[Microsoft Virtual Server]], based on technology they acquired from [[Connectix]].
+
Microsoft offers two Windows-based x86 virtualization products, Microsoft Virtual PC and Microsoft Virtual Server, based on technology they acquired from Connectix.
  
−
[[Open source]] alternatives include [[QEMU]] and [[VirtualBox]].
+
Open source alternatives include QEMU and VirtualBox.
  
−
The research systems [[Denali (operating system)|Denali]], [[L4 microkernel family|L4]], and [[Xen (virtual machine monitor)|Xen]] explored ways to provide high performance virtualization of x86 by implementing a virtual machine that differs from the raw hardware. Operating systems are [[ported]] to run on the resulting virtual machine, which does not implement the hard-to-virtualize parts of the actual x86 instruction set. This technique is known as [[paravirtualization]].
+
The research systems Denali, L4, and Xen explored ways to provide high performance virtualization of x86 by implementing a virtual machine that differs from the raw hardware. Operating systems are ported to run on the resulting virtual machine, which does not implement the hard-to-virtualize parts of the actual x86 instruction set. This technique is known as paravirtualization.
  
 
==Hardware support==
 
==Hardware support==
−
Intel and AMD have independently developed virtualization extensions to the x86 architecture. They are not directly compatible with each other, but serve largely the same functions. Either will allow a virtual machine [[hypervisor]] to run an unmodified guest operating system without incurring significant [[emulation]] performance penalties.
+
Intel and AMD have independently developed virtualization extensions to the x86 architecture. They are not directly compatible with each other, but serve largely the same functions. Either will allow a virtual machine hypervisor to run an unmodified guest operating system without incurring significant emulation performance penalties.
  
 
===Intel VT (IVT)===
 
===Intel VT (IVT)===
−
Intel's virtualization extension for 32-bit and 64-bit x86 architecture is named ''IVT'' (short for ''Intel Virtualization Technology''), and is sometimes referred to by the development code name "Vanderpool". The 32-bit or [[IA-32]] IVT extensions are referred to as ''VT-x'' <ref name="IVT-vtx-vti">{{cite web|url=http://www.intel.com/technology/itj/2006/v10i3/1-hardware/5-architecture.htm|title=Intel Virtualization Technology|publisher=Intel}}</ref>. Intel has also published specifications for IVT for the [[IA-64]] ([[Itanium 2|Itanium]]) processors which are referred to as ''VT-i'' <ref name="IVT-vtx-vti" />; formerly the IA-64 virtualization was code-named "Silvervale". However, since 2005, new Itanium processors no longer implement the x86 instructions in hardware, so x86 virtualization on IA-64, if implemented, will be via emulation.
+
Intel's virtualization extension for 32-bit and 64-bit x86 architecture is named ''IVT'' (short for ''Intel Virtualization Technology''), and is sometimes referred to by the development code name "Vanderpool". The 32-bit or IA-32 IVT extensions are referred to as ''VT-x''[http://www.intel.com/technology/itj/2006/v10i3/1-hardware/5-architecture.htm]. Intel has also published specifications for IVT for the IA-64 (Itanium) processors which are referred to as ''VT-i'' <ref name="IVT-vtx-vti" />; formerly the IA-64 virtualization was code-named "Silvervale". However, since 2005, new Itanium processors no longer implement the x86 instructions in hardware, so x86 virtualization on IA-64, if implemented, will be via emulation.
  
−
Intel VT was officially launched at the Intel Developer Forum Spring 2005. It is available on most [[Pentium 4]] 6x2 and 6x1, [[Pentium D]] 9x0, [[Xeon]] 3xxx/5xxx/7xxx [http://www.intel.com/products/processor/xeon/specs.htm], [[Intel Core|Core Duo]] (excluding T2300E) and [[Intel Core 2|Core 2 Duo]] processors (excluding the T5200, T5500, E4x00). On some implementations, IVT support may be switched off in the [[BIOS]]/[[Extensible Firmware Interface|EFI]]. This can be determined by checking if the VMX flag is enabled by the Feature Control MSR.
+
Intel VT was officially launched at the Intel Developer Forum Spring 2005. It is available on most Pentium 4 6x2 and 6x1, Pentium D 9x0, Xeon 3xxx/5xxx/7xxx [http://www.intel.com/products/processor/xeon/specs.htm], Core Duo (excluding T2300E) and Core 2 Duo processors (excluding the T5200, T5500, E4x00). On some implementations, IVT support may be switched off in the BIOS/EFI. This can be determined by checking if the VMX flag is enabled by the Feature Control MSR.
  
−
Documentation on the Intel website have stated that VT requires not only support from the processor, but also support from the [[chipset]], [[BIOS]], and perhaps software <ref name="xen-wiki">{{cite web|url=http://wiki.xensource.com/xenwiki/IntelVT|title=Intel Processors Supporting VT|publisher=Xen Source}}</ref><ref name="intel">{{cite web|url=http://www.intel.com/design/pentium4/datashts/306382.htm|title=Intel Pentium 4 Processor 6xx Sequence and Intel Pentium 4 Processor Extreme Edition Datasheet|publisher=Intel}}</ref>.
+
Documentation on the Intel website have stated that VT requires not only support from the processor, but also support from the chipset, BIOS, and perhaps software[http://wiki.xensource.com/xenwiki/IntelVT][http://www.intel.com/design/pentium4/datashts/306382.htm].
  
−
Intel plans to add a technology named [[Virtualization for Directed I/O]] to VT. It will provide what AMD provides with [[IOMMU]].
+
Intel plans to add a technology named Virtualization for Directed I/O to VT. It will provide what AMD provides with IOMMU.
  
 
===AMD virtualization (AMD-V)===
 
===AMD virtualization (AMD-V)===
Line 31: Line 31:
 
===Software utilizing VT===
 
===Software utilizing VT===
 
The following software is known to conditionally make use of virtualization technology features:
 
The following software is known to conditionally make use of virtualization technology features:
−
* [[Blue Pill (malware)]] uses AMD Pacifica
+
* Blue Pill (malware) uses AMD Pacifica
−
* [[Kernel-based Virtual Machine]] (KVM)
+
* Kernel-based Virtual Machine (KVM)
−
* [[Microsoft Virtual PC]] — As of Virtual PC 2007 supports both Intel VT-x and AMD AMD-V. VPC 2007 was released on 19 February 2007
+
* Microsoft Virtual PC — As of Virtual PC 2007 supports both Intel VT-x and AMD AMD-V. VPC 2007 was released on 19 February 2007
−
* [[Microsoft Virtual Server]] — a future version (Virtual Server 2005 R2 SP1, to be released in Q1 2007<ref name="vs2005r2sp1">{{cite web|url=http://blogs.technet.com/jhoward/archive/2006/04/28/426703.aspx|title=Virtual Server 2005 R2 SP1 Beta 1 download link and availability details|date=[[2006-04-28]]|publisher=technet.com}}</ref><ref>{{cite web|url=http://www.microsoft.com/windowsserversystem/virtualserver/downloads/servicepack.mspx|title=Virtual Server 2005 R2 SP1 - beta 2 feature listing|publisher=Microsoft}}</ref>) will support Intel VT and AMD Pacifica extensions.
+
* Microsoft Virtual Server — a future version (Virtual Server 2005 R2 SP1, to be released in Q1 2007http://blogs.technet.com/jhoward/archive/2006/04/28/426703.aspx][http://www.microsoft.com/windowsserversystem/virtualserver/downloads/servicepack.mspx]) will support Intel VT and AMD Pacifica extensions.
−
* [[Parallels Workstation]] — lightweight hypervisor with Intel VT-x and AMD AMD-V support (AMD support on Macs is nonexistent as Macs do not use AMD processors)
+
* Parallels Workstation — lightweight hypervisor with Intel VT-x and AMD AMD-V support (AMD support on Macs is nonexistent as Macs do not use AMD processors)
 
* TRANGO real-time embedded hypervisor
 
* TRANGO real-time embedded hypervisor
−
* [[VirtualBox]] supports VT, but does not enable it by default. As with VMware, the developers state that it slows down virtualization, at least for those guest operating systems for which their software virtualization has been optimized.<ref>{{cite web|url=http://www.virtualbox.org/wiki/VirtualBox%20architecture|title=VirtualBox architecture|publisher=[[InnoTek]]}}</ref>
+
* VirtualBox supports VT, but does not enable it by default. As with VMware, the developers state that it slows down virtualization, at least for those guest operating systems for which their software virtualization has been optimized.[http://www.virtualbox.org/wiki/VirtualBox%20architecture]
−
* [[VMware]] — on Intel processors, VMware Workstation 5.5 requires Intel VT to execute 64-bit guests.<ref>{{cite web|url=http://www.vmware.com/support/kb/enduser/std_adp.php?p_faqid=1901|title=Hardware Requirements for 64-Bit Guest Operating Systems|publisher=[[VMWare]]}}</ref> For 32-bit guests, use of VT is possible but not enabled by default because for normal workloads it's slower.<ref name="adams-compare">{{cite web|url=http://www.vmware.com/pdf/asplos235_adams.pdf|last=Adams|first=Keith|coauthors=Agesen, Ole|title=A Comparison of Software and Hardware Techniques for x86 Virtualization|date=2006|publisher=[[VMWare]]}}</ref><ref>{{cite web|url=http://www.vmware.com/community/thread.jspa?threadID=34853&start=0&tstart=0|title=How to check if Vanderpool usage is enabled?|date=March 2006|publisher=[[VMware]]}} Article suggests adding <code>monitor_control.vt32 = "TRUE"</code> to the *.vmx file will enable use of hardware VT.</ref>
+
* VMware — on Intel processors, VMware Workstation 5.5 requires Intel VT to execute 64-bit guests.[http://www.vmware.com/support/kb/enduser/std_adp.php?p_faqid=1901] For 32-bit guests, use of VT is possible but not enabled by default because for normal workloads it's slower.[http://www.vmware.com/pdf/asplos235_adams.pdf][http://www.vmware.com/community/thread.jspa?threadID=34853&start=0&tstart=0]
−
* [[Virtual Iron]] - Virtual Iron 3.1 is the first virtualization software that fully supports hardware-assisted virtualization (Intel-VT and AMD-V) to execute unmodified 32 and 64-bit guest operating systems (Windows, RedHat and Suse) with near native performance. Intel and AMD both have contributed support for their extensions to the Virtual Iron open source virtualization, allowing it to execute unmodified guest operating systems. Virtual Iron refers to this architecture as "[[native virtualization]]".
+
* Virtual Iron - Virtual Iron 3.1 is the first virtualization software that fully supports hardware-assisted virtualization (Intel-VT and AMD-V) to execute unmodified 32 and 64-bit guest operating systems (Windows, RedHat and Suse) with near native performance. Intel and AMD both have contributed support for their extensions to the Virtual Iron open source virtualization, allowing it to execute unmodified guest operating systems. Virtual Iron refers to this architecture as "native virtualization".
 
* [http://www.virtuallogix.com VirtualLogix] VLX uses hardware assised virtualization (VT) to run unmodified guest OSs including Linux and Real-Time operating systems.
 
* [http://www.virtuallogix.com VirtualLogix] VLX uses hardware assised virtualization (VT) to run unmodified guest OSs including Linux and Real-Time operating systems.
−
* [[Xen]] — Xen 3.0, open source ([[GPL]]) virtualization, uses Intel VT to execute unmodified guest operating systems. Both Intel and AMD have contributed support for their virtualization extensions to the [[Xen]] virtual machine monitor, allowing it to execute unmodified guest operating systems.
+
* Xen — Xen 3.0, open source (GPL) virtualization, uses Intel VT to execute unmodified guest operating systems. Both Intel and AMD have contributed support for their virtualization extensions to the Xen virtual machine monitor, allowing it to execute unmodified guest operating systems.
  
 
===Performance===
 
===Performance===
−
[[Standard Performance Evaluation Corporation]] (SPEC) has created a working group to address the development of a set of industry standard methods to compare performance of virtualization technologies.  Current members of the working group include AMD, [[Dell]], [[Fujitsu Siemens]], [[Hewlett-Packard]], Intel, [[IBM]], [[Sun Microsystems]], and [[VMWare]].  SPEC is currently seeking information from the IT community to better understand the types of information that would provide the best industry [[benchmark]]s.
+
Standard Performance Evaluation Corporation (SPEC) has created a working group to address the development of a set of industry standard methods to compare performance of virtualization technologies.  Current members of the working group include AMD, Dell, Fujitsu Siemens, Hewlett-Packard, Intel, IBM, Sun Microsystems, and VMWare.  SPEC is currently seeking information from the IT community to better understand the types of information that would provide the best industry benchmarks.
  
 
==See also==
 
==See also==
 
* [[Virtualization]]
 
* [[Virtualization]]
 
* [[Virtualization Development]]
 
* [[Virtualization Development]]
−
* [[Virtual machine]]
+
* Virtual machine
−
* [[Comparison of virtual machines]]
+
* [[Virtualization Comparison]]
 
* [[Comparison of Application Virtual Machines]]
 
* [[Comparison of Application Virtual Machines]]
−
* [[Emulation]]
+
* Emulation
−
* [[Native virtualization]]
+
* Native virtualization
−
* [[Paravirtualization]]
+
* Paravirtualization
−
* [[Operating system-level virtualization]]
+
* Operating system-level virtualization
  
 
==External links==
 
==External links==
Line 70: Line 70:
 
* [http://www.bugcheck.org/toolz/vrdtsc/ Timing attack to detect presence of hardware assisted VMM]
 
* [http://www.bugcheck.org/toolz/vrdtsc/ Timing attack to detect presence of hardware assisted VMM]
 
* [http://x86virtualization.com/ General current information about x86 Virtualization]
 
* [http://x86virtualization.com/ General current information about x86 Virtualization]
−
;Hardware virtualization ''VT'' from [[Intel]]
+
;Hardware virtualization ''VT'' from Intel
 
* [http://developer.intel.com/technology/virtualization/index.htm Official Intel Virtualization Technology website with PowerPoint/PDF documents on the specifications]
 
* [http://developer.intel.com/technology/virtualization/index.htm Official Intel Virtualization Technology website with PowerPoint/PDF documents on the specifications]
 
* [http://www.hardwaresecrets.com/printpage/263 Intel Virtualization Technology (VT) Explained]
 
* [http://www.hardwaresecrets.com/printpage/263 Intel Virtualization Technology (VT) Explained]
Line 78: Line 78:
 
* [http://x86vmm.blogspot.com/2005/11/vt-coverage-predictable-and-complete_21.html Keith Adams. VT Coverage: Predictable and Complete Confusion.]
 
* [http://x86vmm.blogspot.com/2005/11/vt-coverage-predictable-and-complete_21.html Keith Adams. VT Coverage: Predictable and Complete Confusion.]
 
* [http://www.virtualiron.com/fusetalk/blog/blogpost.cfm?threadid=66&catid=22 Alex Vasilevsky. New Approach to Virtualizing x86s.]
 
* [http://www.virtualiron.com/fusetalk/blog/blogpost.cfm?threadid=66&catid=22 Alex Vasilevsky. New Approach to Virtualizing x86s.]
−
;Hardware virtualization ''Pacifica'' from [[AMD]]
+
;Hardware virtualization ''Pacifica'' from AMD
 
* [http://www.eweek.com/article2/0,1759,1780606,00.asp AMD Previews 'Pacifica' Virtualization Technology]
 
* [http://www.eweek.com/article2/0,1759,1780606,00.asp AMD Previews 'Pacifica' Virtualization Technology]
 
* [http://www.eweek.com/article2/0,1895,1644414,00.asp AMD Preps 'Pacifica' Virtualization Technology]
 
* [http://www.eweek.com/article2/0,1895,1644414,00.asp AMD Preps 'Pacifica' Virtualization Technology]
Line 85: Line 85:
 
*[http://www.devx.com/amd/Article/30186 Coming Soon to VMware, Microsoft, and Xen: AMD Virtualization Technology Solves Virtualization Challenges]. A very concise, intuitive introduction.
 
*[http://www.devx.com/amd/Article/30186 Coming Soon to VMware, Microsoft, and Xen: AMD Virtualization Technology Solves Virtualization Challenges]. A very concise, intuitive introduction.
 
*[http://developer.amd.com/articles.aspx?id=14&num=1 Processor-Based Virtualization, AMD64 Style]
 
*[http://developer.amd.com/articles.aspx?id=14&num=1 Processor-Based Virtualization, AMD64 Style]
−
;(non-x86) Hardware virtualization from [[IBM]]
+
;(non-x86) Hardware virtualization from IBM
 
*[http://www-03.ibm.com/systems/p/apv/ Advanced POWER Virtualization]
 
*[http://www-03.ibm.com/systems/p/apv/ Advanced POWER Virtualization]
 
*[http://www-03.ibm.com/servers/eserver/iseries/lpar/ IBM Dynamic Logical Partitioning]
 
*[http://www-03.ibm.com/servers/eserver/iseries/lpar/ IBM Dynamic Logical Partitioning]
−
;(non-x86) Hardware virtualization for [[SPARC]]
+
;(non-x86) Hardware virtualization for SPARC
 
* [http://opensparc-t1.sunsource.net/specs/Hypervisor-api-current-draft.pdf UltraSPARC T1 Hypervisor API Specification]
 
* [http://opensparc-t1.sunsource.net/specs/Hypervisor-api-current-draft.pdf UltraSPARC T1 Hypervisor API Specification]
 
* [http://x86vmm.blogspot.com/2006/01/opensparc-hypervisor-specification.html OpenSparc Hypervisor Specification]
 
* [http://x86vmm.blogspot.com/2006/01/opensparc-hypervisor-specification.html OpenSparc Hypervisor Specification]

Latest revision as of 16:35, 5 March 2007

x86 virtualization is the method by which x86-based "guest" operating systems are run under another "host" x86 operating system, with little or no modification of the guest OS. The x86 processor architecture did not originally meet the Popek and Goldberg virtualization requirements. As a result, it was very difficult to implement a general virtual machine on an x86 processor. In 2005 and 2006, extensions to their respective x86 architectures by Intel and AMD resolved this and other virtualization difficulties.

Contents

Software techniques

On February 8, 1999, VMware introduced the first x86 virtualization product, "VMware Virtual Platform", based on earlier research by its founders at Stanford University. VMware filed for a patent on their techniques in October 1998, which was granted as US patent 6,397,242 on May 28, 2002. VMware and similar virtualization software for the x86 must employ very sophisticated techniques to trap and virtualize the execution of certain instructions. These techniques incur some performance overhead as compared to a VM running on a natively virtualizable architecture such as the IBM System/370 or Motorola MC68020.

Kevin Lawton started the Plex86 project (originally called "freemware") to create Free software for x86 virtualization. The focus of this project has since changed to support only Linux as a guest operating system, but prior to that Mr. Lawton published the paper Running multiple operating systems concurrently on an IA32 PC using virtualization techniques, which gives an analysis of what aspects of the x86 architecture are hard to virtualize and some techniques to overcome these difficulties.

Microsoft offers two Windows-based x86 virtualization products, Microsoft Virtual PC and Microsoft Virtual Server, based on technology they acquired from Connectix.

Open source alternatives include QEMU and VirtualBox.

The research systems Denali, L4, and Xen explored ways to provide high performance virtualization of x86 by implementing a virtual machine that differs from the raw hardware. Operating systems are ported to run on the resulting virtual machine, which does not implement the hard-to-virtualize parts of the actual x86 instruction set. This technique is known as paravirtualization.

Hardware support

Intel and AMD have independently developed virtualization extensions to the x86 architecture. They are not directly compatible with each other, but serve largely the same functions. Either will allow a virtual machine hypervisor to run an unmodified guest operating system without incurring significant emulation performance penalties.

Intel VT (IVT)

Intel's virtualization extension for 32-bit and 64-bit x86 architecture is named IVT (short for Intel Virtualization Technology), and is sometimes referred to by the development code name "Vanderpool". The 32-bit or IA-32 IVT extensions are referred to as VT-x[1]. Intel has also published specifications for IVT for the IA-64 (Itanium) processors which are referred to as VT-i [1]; formerly the IA-64 virtualization was code-named "Silvervale". However, since 2005, new Itanium processors no longer implement the x86 instructions in hardware, so x86 virtualization on IA-64, if implemented, will be via emulation.

Intel VT was officially launched at the Intel Developer Forum Spring 2005. It is available on most Pentium 4 6x2 and 6x1, Pentium D 9x0, Xeon 3xxx/5xxx/7xxx [2], Core Duo (excluding T2300E) and Core 2 Duo processors (excluding the T5200, T5500, E4x00). On some implementations, IVT support may be switched off in the BIOS/EFI. This can be determined by checking if the VMX flag is enabled by the Feature Control MSR.

Documentation on the Intel website have stated that VT requires not only support from the processor, but also support from the chipset, BIOS, and perhaps software[3][4].

Intel plans to add a technology named Virtualization for Directed I/O to VT. It will provide what AMD provides with IOMMU.

AMD virtualization (AMD-V)

AMD's virtualization extensions to the 64-bit x86 architecture is named AMD Virtualization, abbreviated AMD-V. It is still referred to as "Pacifica", the AMD internal project code name.

AMD-V is present in K8 AMD processors from stepping "F" onwards.

Software utilizing VT

The following software is known to conditionally make use of virtualization technology features:

  • Blue Pill (malware) uses AMD Pacifica
  • Kernel-based Virtual Machine (KVM)
  • Microsoft Virtual PC — As of Virtual PC 2007 supports both Intel VT-x and AMD AMD-V. VPC 2007 was released on 19 February 2007
  • Microsoft Virtual Server — a future version (Virtual Server 2005 R2 SP1, to be released in Q1 2007http://blogs.technet.com/jhoward/archive/2006/04/28/426703.aspx][5]) will support Intel VT and AMD Pacifica extensions.
  • Parallels Workstation — lightweight hypervisor with Intel VT-x and AMD AMD-V support (AMD support on Macs is nonexistent as Macs do not use AMD processors)
  • TRANGO real-time embedded hypervisor
  • VirtualBox supports VT, but does not enable it by default. As with VMware, the developers state that it slows down virtualization, at least for those guest operating systems for which their software virtualization has been optimized.[6]
  • VMware — on Intel processors, VMware Workstation 5.5 requires Intel VT to execute 64-bit guests.[7] For 32-bit guests, use of VT is possible but not enabled by default because for normal workloads it's slower.[8][9]
  • Virtual Iron - Virtual Iron 3.1 is the first virtualization software that fully supports hardware-assisted virtualization (Intel-VT and AMD-V) to execute unmodified 32 and 64-bit guest operating systems (Windows, RedHat and Suse) with near native performance. Intel and AMD both have contributed support for their extensions to the Virtual Iron open source virtualization, allowing it to execute unmodified guest operating systems. Virtual Iron refers to this architecture as "native virtualization".
  • VirtualLogix VLX uses hardware assised virtualization (VT) to run unmodified guest OSs including Linux and Real-Time operating systems.
  • Xen — Xen 3.0, open source (GPL) virtualization, uses Intel VT to execute unmodified guest operating systems. Both Intel and AMD have contributed support for their virtualization extensions to the Xen virtual machine monitor, allowing it to execute unmodified guest operating systems.

Performance

Standard Performance Evaluation Corporation (SPEC) has created a working group to address the development of a set of industry standard methods to compare performance of virtualization technologies. Current members of the working group include AMD, Dell, Fujitsu Siemens, Hewlett-Packard, Intel, IBM, Sun Microsystems, and VMWare. SPEC is currently seeking information from the IT community to better understand the types of information that would provide the best industry benchmarks.

See also

External links

General links
Hardware virtualization VT from Intel
Hardware virtualization Pacifica from AMD
(non-x86) Hardware virtualization from IBM
(non-x86) Hardware virtualization for SPARC
Blogs discussing virtualization technologies

Cite error: <ref> tags exist, but no <references/> tag was found
Retrieved from "http://7thgen.info/wiki/X86_Virtualization"