Understanding of Virtualization

First, virtualization Hypervisor Meta-system

Hypervisoris an intermediate software layer running between the physical server and the operating system, allows multiple operating systems and applications to share a set of basic physical hardware , and therefore can also be viewed as a virtual environment "Yuan"Operating System, it can coordinate access to all physical devices and virtual machines on the server, also called virtual machine monitors (Virtual Machine Monitor). Hypervisoris at the heart of all virtualization technologies. The ability to support multi-workload migrations non-disruptively isHypervisorthe basic functionality. When the server starts andLineHypervisor, it allocates the appropriate amount of memory to each virtual machine,CPU, network, and disk, and load the guest operating system for all virtual machines.

Hyper-V is very comprehensive (although not the same technique, but the principle of implementation is the same)

Hardware -hyper-v- Virtual Machines ( hardware -vsphere- virtual machines )

Systems that can be installed and run on bare metal independently. Do not depend on the host.

650) this.width=650; "title=" 1.png "src=" Http://s5.51cto.com/wyfs02/M01/85/E0/wKiom1etP8KQOpGDAAAmf3XAW20171.png " alt= "Wkiom1etp8kqopgdaaamf3xaw20171.png"/>

VMM ( virtual machine monitor ) , primarily used to isolate and manage multiple virtual machines running on the upper level, to arbitrate their access to the underlying hardware ,

Second, understand the core of virtualization technology and virtualization architecture

Hypervisor is at the heart of all virtualization technologies. the ability to support multi-workload migrations non-disruptively is the basic function of Hypervisor

currently on the market various x86 (hypervisor)

(1) Type: Virtual Machines run directly on the system hardware, create a hardware full emulation instance, known as " Bare Metal " type .

bare-metal type in virtualization Hypervisor directly manages calls to hardware resources, does not require the underlying operating system, or can Hypervisor See

To make a very thin operating system. The performance of this scenario is between host virtualization and operating system virtualization.

(2) Type: Virtual Machines run in a traditional Operating System is also a hardware full emulation instance, called " Hosting (hosting) " type.

managed Type / Host Type Hypervisor run on the underlying operating system to build a complete set of virtual hardware platforms

( Cpu/memory/storage/adapter ), the user installs the new operating system and application software as needed, and the underlying and upper

the operating system can be completely irrelevant, such as Windows Run Linux operating system. the application of the VM in host virtualization needs to go through when calling hardware resources : VM kernel ->hypervisor-> Hardware Resources, the host core, so the performance

Is the worst of three virtualization technologies.

Note: We use the vmwareworkstation Workstation Edition is this

(3) running in legacy operating system on , Create a standalone instance of virtualization (container), pointing to the underlying managed operating system, called Span style= "FONT-FAMILY:CALIBRI;" > " operating system virtualization " operating system virtualization is an operating system that simulates the container , There is a virtual machine shared kernel space , ( best performance, resource-intensive

Less. However, the disadvantage is that the underlying and upper layers must use the same operating system , such as

the underlying operating system is running Windows System, you vps/ve it must be running Windows .

Iii. differences between managed and bare-metal types

managed Type: The common is VMware the workstation version and VirtualBox.

Bare-Metal type: The common is Vmware VSphere and the Hyper-V and XenServer

The working mode of the workstation edition switch is very different from the operating mode of the server edition.

Virtual Switch:

VMware workStation The Virtual Switch configuration is configured on the Virtual network editor

Bridge mode: Directly bridged on the local network card, the virtual machine can communicate with the native direct access to the same network segment address as the host.

Nat and host-only It is not possible to communicate with a local network card, creating a connection to the NAT Virtual network adapter for the switch

such as: VMware Network Adapter VMnet1 ( the last word indicates that the virtual NIC is connected to the VMnet1 switch )

Vmwarenetwork Adapter VMnet8 ( the last word indicates that the virtual NIC is connected to the VMnet8 switch )

Standard Virtual Switch:

  VM (VM VM )

  Kernel vcenter exsi esxi virtual machines under host management host

Explanation: By logging into VCenter, centrally managing the exsi host , through Exsi hosts centrally manage virtual machines.

the port groups on which the virtual machines reside(Pvid)need one and it in the sameVLanof theKernelportto be managed, different port groups can be refined(specifically whichVLAN), then the virtual machine'sKernelportcan also be refined to manage it(He's going to have the same thing.VLAN). It will only be used when ———— centralized management

in and other VMS and external communication, directly out of the host network card (host network card is not the gateway of the virtual machine).

At this time do not tangle the VM data directly from the host network card out, do not control the IP network card

Host network card can also be virtual a lot of Kernelport , it is like a workstation version of the bridge adapter, can communicate with the outside world.

2. Other features: such as migration of management traffic is specifically used as a copy, more like the transfer of the past through host sharing

This article is from the "Sleep" blog, please be sure to keep this source http://jinkaiye.blog.51cto.com/7619715/1837224

Understanding of Virtualization