See more Hardware virtualization articles on AOD.

Powered by
TTSReader
Share this page on
Article provided by Wikipedia


Main article: "Full virtualization
""
""
Logical diagram of full virtualization.

In full virtualization, the virtual machine simulates enough hardware to allow an unmodified "guest" OS (one designed for the same "instruction set) to be run in isolation. This approach was pioneered in 1966 with the IBM "CP-40 and "CP-67, predecessors of the "VM family.

Examples outside the mainframe field include "Parallels Workstation, "Parallels Desktop for Mac, "VirtualBox, "Virtual Iron, "Oracle VM, "Virtual PC, "Virtual Server, "Hyper-V, "VMware Workstation, "VMware Server (discontinued, formerly called GSX Server), "VMware ESXi, "QEMU, "Adeos, "Mac-on-Linux, Win4BSD, "Win4Lin Pro, and "Egenera vBlade technology.

Hardware-assisted virtualization[edit]

Hardware-assisted virtualization

In hardware-assisted virtualization, the hardware provides architectural support that facilitates building a virtual machine monitor and allows guest OSes to be run in isolation.[7] Hardware-assisted virtualization was first introduced on the IBM System/370 in 1972, for use with VM/370, the first virtual machine operating system.

In 2005 and 2006, "Intel and "AMD provided additional hardware to support virtualization. Sun Microsystems (now "Oracle Corporation) added similar features in their "UltraSPARC T-Series processors in 2005. Examples of virtualization platforms adapted to such hardware include "KVM, "VMware Workstation, "VMware Fusion, "Hyper-V, "Windows Virtual PC, "Xen, "Parallels Desktop for Mac, "Oracle VM Server for SPARC, "VirtualBox and "Parallels Workstation.

In 2006, first-generation 32- and 64-bit x86 hardware support was found to rarely offer performance advantages over software virtualization.[8]

Paravirtualization[edit]

Paravirtualization

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["clarification needed] 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 "hypervisor is called a "hypercall" in "TRANGO and "Xen; it is implemented via a DIAG ("diagnose") hardware instruction in IBM's "CMS under "VM["clarification needed] (which was the origin of the term hypervisor). Examples include IBM's "LPARs,[9] "Win4Lin 9x, Sun's "Logical Domains, "z/VM,["citation needed] and "TRANGO.

Operating-system-level virtualization[edit]

Operating-system-level virtualization

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 "operating system kernel is also used to implement the "guest" environments, and applications running in a given "guest" environment view it as a stand-alone system. The pioneer implementation was "FreeBSD jails; other examples include "Docker, "Solaris Containers, "OpenVZ, "Linux-VServer, "LXC, AIX "Workload Partitions, Parallels Virtuozzo Containers, and "iCore Virtual Accounts.

Hardware virtualization disaster recovery[edit]

A "disaster recovery (DR) plan is good business practice for a hardware virtualization platform solution. DR of a virtualization environment can ensure high rate of availability during a wide range of situations that disrupt normal business operations. Continued operations of VMs is mission critical and a DR can compensate for concerns of hardware performance and maintenance requirements. A hardware virtualization DR environment involves hardware and software protection solutions based on business continuity needs, which include the methods described below.[10][11]

Tape backup for software data long-term archival needs
This common method can be used to store data offsite but can be a difficult and lengthy process to recover your data. 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
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.[12]

See also[edit]

References[edit]

  1. ^ Turban, E; King, D.; Lee, J.; Viehland, D. (2008). "19". Electronic Commerce A Managerial Perspective (PDF) (5th ed.). Prentice-Hall. p. 27. 
  2. ^ "Virtualization in education" (PDF). "IBM. October 2007. Retrieved 6 July 2010. 
  3. ^ Creasy, R.J. (1981). "The Origin of the VM/370 Time-sharing System" (PDF). "IBM. Retrieved 26 February 2013. 
  4. ^ [1] Profiling Energy Usage for Efficient Consumption; Rajesh Chheda, Dan Shookowsky, Steve Stefanovich, and Joe Toscano
  5. ^ VMware server consolidation overview
  6. ^ Examining VMware Dr. Dobb’s Journal August 2000 By "Jason Nieh and Ozgur Can Leonard
  7. ^ Uhlig, R. et al.; "Intel virtualization technology," Computer , vol.38, no.5, pp. 48-56, May 2005
  8. ^ A Comparison of Software and Hardware Techniques for x86 Virtualization, Keith Adams and Ole Agesen, VMWare, ASPLOS’06 21–25 October 2006, San Jose, California, USA "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."
  9. ^ Borden, T.L. et al.; Multiple Operating Systems on One Processor Complex. IBM Systems Journal, vol.28, no.1, pp. 104-123, 1989
  10. ^ "The One Essential Guide to Disaster Recovery: How to Ensure IT and Business Continuity" (PDF). Vision Solutions, Inc. 2010. 
  11. ^ Wold, G (2008). "Disaster Recovery Planning Process". 
  12. ^ "Disaster Recovery Virtualization Protecting Production Systems Using VMware Virtual Infrastructure and Double-Take" (PDF). VMWare. 2010. 

External links[edit]

) )