Hardware virtualization

<h2 id="concept">Concept</h2>
The term "virtualization" was coined in the 1960s to refer to a <a href="/facts/Virtual_machine/BLevU3sx">virtual machine</a> (sometimes called "pseudo machine"), a term which itself dates from the experimental <a href="/facts/IBM_M44%2f44X/z3I31hrs">IBM M44/44X</a> system.<a class="footnote-ref" id="fnref:2" href="#fn:2">2</a> The creation and management of virtual machines has also been called "platform virtualization", or "server virtualization", more recently.<a class="footnote-ref" id="fnref:3" href="#fn:3">3</a><a class="footnote-ref" id="fnref:4" href="#fn:4">4</a>
Platform virtualization is performed on a given hardware platform by host software (a control program), which creates a simulated computer environment, a virtual machine (VM), for its guest software. The guest software is not limited to user applications; many hosts allow the execution of complete operating systems. The guest software executes as if it were running directly on the physical hardware, with several notable caveats. Access to physical system resources (such as the <a href="/facts/Network_interface_card/wyf5FR29">network access</a>, display, keyboard, and <a href="/facts/Hard_disk_drive/kekLSGSE">disk storage</a>) is generally managed at a more restrictive level than the host processor and system-memory. Guests are often restricted from accessing specific <a href="/facts/Peripheral_device/3lEBPE14">peripheral devices</a>, or may be limited to a subset of the device's native capabilities, depending on the hardware access policy implemented by the virtualization host.<a class="footnote-ref" id="fnref:5" href="#fn:5">5</a>: 5,13 
Virtualization often exacts performance penalties, both in resources required to run the hypervisor, as well as in reduced performance on the virtual machine compared to running native on the physical machine.<a class="footnote-ref" id="fnref:6" href="#fn:6">6</a>: 35,67-68 

<h2 id="reasons-for-hardware-virtualization">Reasons for Hardware virtualization</h2>
<ul><li>In the case of <a href="/facts/Server_(computing)/dEaYFD7r">server</a> consolidation, many small physical servers can be replaced by one larger physical server to decrease the need for more (costly) hardware resources such as CPUs, and hard drives. Although hardware is consolidated in virtual environments, typically OSs are not. Instead, each OS running on a physical server is converted to a distinct OS running inside a virtual machine. Thereby, the large server can "host" many such "guest" virtual machines. This is known as <a href="/facts/Physical-to-Virtual/W0kPwwtW">Physical-to-Virtual</a> (P2V) transformation. The average utilization of a server in the early 2000s was 5 to 15%, but with the adoption of virtualization this figure started to increase to reduce the number of servers needed.<a class="footnote-ref" id="fnref:7" href="#fn:7">7</a></li>
<li>In addition to reducing equipment and labor costs associated with equipment maintenance, consolidating servers can also have the added benefit of reducing energy consumption and the global footprint in environmental-ecological sectors of technology. For example, a typical server runs at 425 W<a class="footnote-ref" id="fnref:8" href="#fn:8">8</a> and VMware estimates a hardware reduction ratio of up to 15:1.<a class="footnote-ref" id="fnref:9" href="#fn:9">9</a></li>
<li>A virtual machine (VM) can be more easily controlled and inspected from a remote site than a physical machine, and the configuration of a VM is more flexible. This is very useful in kernel development and for teaching operating system courses, including running legacy operating systems that do not support modern hardware.<a class="footnote-ref" id="fnref:10" href="#fn:10">10</a></li>
<li>A new virtual machine can be provisioned as required without the need for an up-front hardware purchase.</li>
<li>A virtual machine can easily be relocated from one physical machine to another as needed. For example, a salesperson going to a customer can copy a virtual machine with the demonstration software to their laptop, without the need to transport the physical computer. Likewise, an error inside a virtual machine does not harm the host system, so there is no risk of the OS crashing on the laptop.</li>
<li>Because of this ease of relocation, virtual machines can be readily used in <a href="/facts/IT_disaster_recovery/gDARyxfl">disaster recovery</a> scenarios without concerns with impact of refurbished and faulty energy sources.</li></ul>
However, when multiple VMs are concurrently running on the same physical host, each VM may exhibit varying and unstable performance which highly depends on the workload imposed on the system by other VMs. This issue can be addressed by appropriate installation techniques for <a href="/facts/Temporal_isolation_among_virtual_machines/CR6cPwd8">temporal isolation among virtual machines</a>.
There are several approaches to platform virtualization.
Examples of virtualization use cases:

<ul><li>Running one or more applications that are not supported by the host OS: A virtual machine running the required guest OS could permit the desired applications to run, without altering the host OS.</li>
<li>Evaluating an alternate operating system: The new OS could be run within a VM, without altering the host OS.</li>
<li>Server virtualization: Multiple virtual servers could be run on a single physical server, in order to more fully utilize the hardware resources of the physical server.</li>
<li>Duplicating specific environments: A virtual machine could, depending on the virtualization software used, be duplicated and installed on multiple hosts, or restored to a previously backed-up system state.</li>
<li>Creating a protected environment: If a guest OS running on a VM becomes damaged in a way that is not cost-effective to repair, such as may occur when studying <a href="/facts/Malware/5ee7TLFR">malware</a> or installing badly behaved software, the VM may simply be discarded without harm to the host system, and a clean copy used upon rebooting the guest .</li></ul>
<h2 id="full-virtualization">Full virtualization</h2>
Main article: <a href="/facts/Full_virtualization/5Hakw6k7">Full virtualization</a>

In full virtualization, the virtual machine simulates enough hardware to allow an unmodified "guest" OS designed for the same <a href="/facts/Instruction_set/8p8vwUeE">instruction set</a> to be run in isolation. This approach was pioneered in 1966 with the IBM <a href="/facts/CP-40/QMTqp93G">CP-40</a> and <a href="/facts/CP-67/IbFRIhLw">CP-67</a>, predecessors of the <a href="/facts/VM_(Operating_system)/Ymu9SRtX">VM</a> family.

<h2 id="paravirtualization">Paravirtualization</h2>
Main article: <a href="/facts/Paravirtualization/5MMXo72C">Paravirtualization</a>
In paravirtualization, the virtual machine does not necessarily simulate hardware, but instead (or in addition) offers a special API that can only be used by modifying the "guest" OS. For this to be possible, the "guest" OS's source code must be available. If the source code is available, it is sufficient to replace sensitive instructions with calls to VMM APIs (e.g.: "cli" with "vm_handle_cli()"), then re-compile the OS and use the new binaries. This system call to the <a href="/facts/Hypervisor/3gX9fKlH">hypervisor</a> is called a "hypercall" in <a href="/facts/Trango_Virtual_Processors/4S0hqrqA">TRANGO</a> and <a href="/facts/Xen/U5fq6ESl">Xen</a>; it is implemented via a DIAG ("diagnose") hardware instruction in IBM's <a href="/facts/Conversational_Monitor_System/qmWXRkQT">CMS</a> under <a href="/facts/VM_(operating_system)/Ymu9SRtX">VM</a> (which was the origin of the term hypervisor)..

<h2 id="hardware-assisted-virtualization">Hardware-assisted virtualization</h2>
Main article: <a href="/facts/Hardware-assisted_virtualization/n4kjJLqA">Hardware-assisted virtualization</a>
In hardware-assisted virtualization, the hardware provides architectural support that facilitates building a virtual machine monitor and allows guest OSs to be run in isolation.<a class="footnote-ref" id="fnref:11" href="#fn:11">11</a> This can be used to assist either full virtualization or paravirtualization. Hardware-assisted virtualization was first introduced on the <a href="/facts/IBM_308X/sxWguzcN">IBM 308X</a> processors in 1980, with the Start Interpretive Execution (SIE) instruction.<a class="footnote-ref" id="fnref:12" href="#fn:12">12</a>
In 2005 and 2006, <a href="/facts/Intel/SMF0gJJX">Intel</a> and <a href="/facts/AMD/CB1G7QTb">AMD</a> developed additional hardware to support virtualization ran on their platforms. Sun Microsystems (now <a href="/facts/Oracle_Corporation/0z14FygH">Oracle Corporation</a>) added similar features in their <a href="/facts/SPARC_T3/DWJgEvyL">UltraSPARC T-Series</a> processors in 2005.
In 2006, first-generation 32- and 64-bit x86 hardware support was found to rarely offer performance advantages over software virtualization.<a class="footnote-ref" id="fnref:13" href="#fn:13">13</a>

<h2 id="operating-system-level-virtualization">Operating-system-level virtualization</h2>
Main article: <a href="/facts/OS-level_virtualization/gkLoCrgN">OS-level virtualization</a>
In operating-system-level virtualization, a physical server is virtualized at the operating system level, enabling multiple isolated and secure virtualized servers to run on a single physical server. The "guest" operating system environments share the same running instance of the operating system as the host system. Thus, the same <a href="/facts/Operating_system_kernel/uEj4U3Rz">operating system kernel</a> is also used to implement the "guest" environments, and applications running in a given "guest" environment view it as a stand-alone system.

<h2 id="hardware-virtualization-disaster-recovery">Hardware virtualization disaster recovery</h2>
A <a href="/facts/IT_disaster_recovery/gDARyxfl">disaster recovery</a> (DR) plan is often considered good practice for a hardware virtualization platform. DR of a virtualization environment can ensure high rate of availability during a wide range of situations that disrupt normal business operations. In situations where continued operations of hardware virtualization platforms is important, a disaster recovery plan can ensure hardware performance and maintenance requirements are met. A hardware virtualization disaster recovery plan involves both hardware and software protection by various methods, including those described below.<a class="footnote-ref" id="fnref:14" href="#fn:14">14</a><a class="footnote-ref" id="fnref:15" href="#fn:15">15</a>

Tape backup for software data long-term archival needs
This common method can be used to store data offsite, but data recovery can be a difficult and lengthy process. Tape backup data is only as good as the latest copy stored. Tape backup methods will require a backup device and ongoing storage material.
Whole-file and application replication
The implementation of this method will require control software and storage capacity for application and data file storage replication typically on the same site. The data is replicated on a different disk partition or separate disk device and can be a scheduled activity for most servers and is implemented more for database-type applications.
Hardware and software redundancy
This method ensures the highest level of disaster recovery protection for a hardware virtualization solution, by providing duplicate hardware and software replication in two distinct geographic areas.<a class="footnote-ref" id="fnref:16" href="#fn:16">16</a>
<h2 id="see-also">See also</h2>

<ul><li><a href="/facts/Application_virtualization/Wdgbbrun">Application virtualization</a></li>
<li><a href="/facts/Comparison_of_platform_virtualization_software/46DLmx6H">Comparison of platform virtualization software</a></li>
<li><a href="/facts/Desktop_virtualization/mCcGm6hL">Desktop virtualization</a></li>
<li><a href="/facts/Dynamic_infrastructure/MBhMK8rr">Dynamic infrastructure</a></li>
<li><a href="/facts/Hardware_emulation/EhDA3xRG">Hardware emulation</a></li>
<li><a href="/facts/Hyperjacking/1y2htQvI">Hyperjacking</a></li>
<li><a href="/facts/Instruction_set_simulator/kz2WRgjb">Instruction set simulator</a></li>
<li><a href="/facts/Popek_and_Goldberg_virtualization_requirements/5PWkIVpH">Popek and Goldberg virtualization requirements</a></li>
<li><a href="/facts/Physicalization/83oT8SDj">Physicalization</a></li>
<li><a href="/facts/Thin_provisioning/WBmC1chV">Thin provisioning</a></li>
<li><a href="/facts/Virtual_appliance/CDgMshNf">Virtual appliance</a></li>
<li><a href="/facts/Virtualization_for_aggregation/B0CRfQNP">Virtualization for aggregation</a></li>
<li><a href="/facts/Workspace_virtualization/HHfEXP5f">Workspace virtualization</a></li></ul>

<h2 id="external-links">External links</h2>
<ul><li><a href="https://webx.ubi.pt/~hgil/utils/Virtualization_Introduction.html">An Introduction to Virtualization</a> <a href="https://web.archive.org/web/20201022004035/https://webx.ubi.pt/~hgil/utils/Virtualization_Introduction.html">Archived</a> 22 October 2020 at the <a href="/facts/Wayback_Machine/nmQ3a6JC">Wayback Machine</a>, by Amit Singh</li>
<li><a href="http://www.cl.cam.ac.uk/research/srg/netos/papers/2003-xensosp.pdf">Xen and the Art of Virtualization</a>, ACM, 2003, by a group of authors</li>
<li><a href="https://web.archive.org/web/20070209020711/http://www-128.ibm.com/developerworks/library/l-linuxvirt/index.html">Linux Virtualization Software</a></li>
<li>Zoppis, Bruno (27 August 2007) [1st pub. LinuxDevices:2007]. <a href="https://web.archive.org/web/20131224184029/http://archive.linuxgizmos.com/using-a-hypervisor-to-reconcile-gpl-and-proprietary-embedded-code/">"Using a hypervisor to reconcile GPL and proprietary embedded code"</a>. Linux Gizmos. Archived from <a href="http://archive.linuxgizmos.com/using-a-hypervisor-to-reconcile-gpl-and-proprietary-embedded-code/">the original</a> on 24 December 2013.</li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1">Creasy, R.J. (1981). "The Origin of the VM/370 Time-sharing System" (PDF). IBM. Retrieved 26 February 2013. <a href="http://pages.cs.wisc.edu/~stjones/proj/vm_reading/ibmrd2505M.pdf" target="_blank">http://pages.cs.wisc.edu/~stjones/proj/vm_reading/ibmrd2505M.pdf</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></li>
<li id="fn:2">Creasy, R.J. (1981). "The Origin of the VM/370 Time-sharing System" (PDF). IBM. Retrieved 26 February 2013. <a href="http://pages.cs.wisc.edu/~stjones/proj/vm_reading/ibmrd2505M.pdf" target="_blank">http://pages.cs.wisc.edu/~stjones/proj/vm_reading/ibmrd2505M.pdf</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></li>
<li id="fn:3">Thomson, Julian (23 May 2018). "Virtual Machines: An Introduction to Platform Virtualization". Performance Software. Retrieved 8 July 2023. <a href="https://www.psware.com/virtual-machines-an-introduction-to-platform-virtualization/" target="_blank">https://www.psware.com/virtual-machines-an-introduction-to-platform-virtualization/</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></li>
<li id="fn:4">"What is Server Virtualization?". <a href="https://www.vmware.com/topics/glossary/content/server-virtualization.html" target="_blank">https://www.vmware.com/topics/glossary/content/server-virtualization.html</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></li>
<li id="fn:5">Bugnion, Edouard; Nieh, Jason; Tsafrir, Dan (2017). Hardware and software support for virtualization. San Rafael, CA: Morgan & Claypool Publishers. ISBN 9781627056939. <a href="9781627056939" target="_blank">9781627056939</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></li>
<li id="fn:6">Bugnion, Edouard; Nieh, Jason; Tsafrir, Dan (2017). Hardware and software support for virtualization. San Rafael, CA: Morgan & Claypool Publishers. ISBN 9781627056939. <a href="9781627056939" target="_blank">9781627056939</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></li>
<li id="fn:7">"Chip Aging Accelerates". 14 February 2018. <a href="https://semiengineering.com/chip-aging-accelerates/" target="_blank">https://semiengineering.com/chip-aging-accelerates/</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></li>
<li id="fn:8">Rajesh Chheda; Dan Shookowsky; Steve Stefanovich; Joe Toscano (14 January 2009). "Profiling Energy Usage for Efficient Consumption". <a href="https://learn.microsoft.com/en-us/previous-versions/dd393312(v=msdn.10)" target="_blank">https://learn.microsoft.com/en-us/previous-versions/dd393312(v=msdn.10)</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></li>
<li id="fn:9">"VMware server consolidation overview". Archived from the original on 8 January 2022. <a href="https://web.archive.org/web/20220108130221/https://www.vmware.com/solutions/consolidation.html" target="_blank">https://web.archive.org/web/20220108130221/https://www.vmware.com/solutions/consolidation.html</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></li>
<li id="fn:10">Jason Nieh; Ozgur Can Leonard (August 2000). "Examining VMware". Dr. Dobb's Journal. Archived from the original on 22 November 2019. <a href="/wiki/Jason_Nieh" target="_blank">/wiki/Jason_Nieh</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></li>
<li id="fn:11">Smith, L.; Kägi, A.; Martins, F. M.; Neiger, G.; Leung, F. H.; Rodgers, D.; Santoni, A. L.; Bennett, S. M.; Uhlig, R.; Anderson, A. V. (May 2005). "Intel virtualization technology". Computer. 38 (5): 48–56. doi:10.1109/MC.2005.163. <a href="https://www.computer.org/csdl/magazine/co/2005/05/r5048/13rRUzpQPGB" target="_blank">https://www.computer.org/csdl/magazine/co/2005/05/r5048/13rRUzpQPGB</a> <a href="#fnref:11" class="footnote-back-ref">↩</a></li>
<li id="fn:12">IBM System/370 Extended Architecture Interpretive Execution (PDF) (First ed.). IBM. January 1984. SA22-7095-0. Retrieved 27 October 2022. <a href="http://bitsavers.org/pdf/ibm/370/MVS_XA/SA22-7095-0_370-XA_Interpretive_Execution_Jan84.pdf" target="_blank">http://bitsavers.org/pdf/ibm/370/MVS_XA/SA22-7095-0_370-XA_Interpretive_Execution_Jan84.pdf</a> <a href="#fnref:12" class="footnote-back-ref">↩</a></li>
<li id="fn:13">Keith Adams; Ole Agesen (21–25 October 2006). A Comparison of Software and Hardware Techniques for x86 Virtualization (PDF). ASPLOS’06. San Jose, California, USA. Archived from the original (PDF) on 8 January 2022. Surprisingly, we find that the first-generation hardware support rarely offers performance advantages over existing software techniques. We ascribe this situation to high VMM/guest transition costs and a rigid programming model that leaves little room for software flexibility in managing either the frequency or cost of these transitions. <a href="https://web.archive.org/web/20220108130207/https://www.vmware.com/pdf/asplos235_adams.pdf" target="_blank">https://web.archive.org/web/20220108130207/https://www.vmware.com/pdf/asplos235_adams.pdf</a> <a href="#fnref:13" class="footnote-back-ref">↩</a></li>
<li id="fn:14">"The One Essential Guide to Disaster Recovery: How to Ensure IT and Business Continuity" (PDF). Vision Solutions, Inc. 2010. Archived from the original (PDF) on 16 May 2011. <a href="https://web.archive.org/web/20110516030950/http://www.visionsolutions.com/downloads/whitepapers/EssentialDR.pdf" target="_blank">https://web.archive.org/web/20110516030950/http://www.visionsolutions.com/downloads/whitepapers/EssentialDR.pdf</a> <a href="#fnref:14" class="footnote-back-ref">↩</a></li>
<li id="fn:15">Wold, G (2008). "Disaster Recovery Planning Process". Archived from the original on 15 August 2012. <a href="https://web.archive.org/web/20120815054111/http://www.drj.com/new2dr/w2_002.htm" target="_blank">https://web.archive.org/web/20120815054111/http://www.drj.com/new2dr/w2_002.htm</a> <a href="#fnref:15" class="footnote-back-ref">↩</a></li>
<li id="fn:16">"Disaster Recovery Virtualization Protecting Production Systems Using VMware Virtual Infrastructure and Double-Take" (PDF). VMware. 2010. Archived from the original (PDF) on 23 September 2010. <a href="https://web.archive.org/web/20100923021435/http://www.vmware.com/files/pdf/DR_VMware_DoubleTake.pdf" target="_blank">https://web.archive.org/web/20100923021435/http://www.vmware.com/files/pdf/DR_VMware_DoubleTake.pdf</a> <a href="#fnref:16" class="footnote-back-ref">↩</a></li>
</ol>

Hardware virtualization open-in-new

Hardware virtualization