Explore topic-wise InterviewSolutions in .

virt-viewer -C QEMU:///SYSTEM <VMName>

virt-viewer -c qemu:///system <VMName>

Use XM COMMAND :

# xm SHUTDOWN [domain-id]

# xm REBOOT [domain-id]

# xm START [domain-id]

Use xm command :

# xm shutdown [domain-id]

# xm reboot [domain-id]

# xm start [domain-id]

XM CONSOLE &LT;domain-id&GT;

xm console <domain-id>

A VM can have different states like

R – Running

b – Blocked

C – crashed

s – Shutdown

p – Paused

A VM can have different states like

r – Running

b – Blocked

c – crashed

s – Shutdown

p – Paused

‘VIRSH MIGRATE –live machine_name qemu+ssh://destination_server/system’

‘virsh migrate –live machine_name qemu+ssh://destination_server/system’

virsh is the interface or command for managing the virtual machines based on KVM &AMP; Xen hypervisor. On virsh interface virtual machines are identified by their domain names , so virsh is generally USED to list current domains , to CREATE , PAUSE & shutdown domains.

virsh is the interface or command for managing the virtual machines based on KVM & Xen hypervisor. On virsh interface virtual machines are identified by their domain names , so virsh is generally used to list current domains , to create , pause & shutdown domains.

GREP -E ‘SVM|VMX’ /proc/cpuinfo

vmx is for Intel PROCESSORS

svm is for AMD processors

grep -E ‘svm|vmx’ /proc/cpuinfo

vmx is for Intel processors

svm is for AMD processors

Dom0 or Domain0 is the initial domain started by xen HYPERVISOR. It has the special rights LIKE to START NEW domain and access the hardware directly. Dom0 is RESPONSIBLE for running all of the device drivers for the hardware. 

Dom0 or Domain0 is the initial domain started by xen hypervisor. It has the special rights like to start new domain and access the hardware directly. Dom0 is responsible for running all of the device drivers for the hardware. 

Type-1 hypervisor is bare metal hypervisor RUNS on bare metal of hardware. Hyper-V and ESXI Server are the examples of type-1 hypervisor. Type-2 hypervisor is HOSTED by OPERATING system. Examples of type-2 hypervisor are Microsoft Virtual Server &AMP; VMware Server.

Type-1 hypervisor is bare metal hypervisor runs on bare metal of hardware. Hyper-V and ESXI Server are the examples of type-1 hypervisor. Type-2 hypervisor is hosted by operating system. Examples of type-2 hypervisor are Microsoft Virtual Server & VMware Server.

For XEN hypervisor first we have to install Xen kernel and have to BOOT the machine with Xen kernel where as KVM is kernel based Virtualization , we don’t need any EXTRA kernel for KVM. KVM is a module in Kernel. Xen hypervisor by default does not support full virtualization whereas KVM SUPPORTS Full virtualization.

For Xen hypervisor first we have to install Xen kernel and have to boot the machine with Xen kernel where as KVM is kernel based Virtualization , we don’t need any extra kernel for KVM. KVM is a module in Kernel. Xen hypervisor by default does not support full virtualization whereas KVM supports Full virtualization.

XEN & KVM are TWO hypervisor available in LINUX.

Xen & KVM are two hypervisor available in linux.

Hypervisor is a piece of a software that is being INSTALL on the physical machine , which then further creates and run virtual MACHINES. Virtual machine are known as GUEST machines and host machine is the hypervisor on which DIFFERENT virtual machines are created.

Hypervisor is a piece of a software that is being install on the physical machine , which then further creates and run virtual machines. Virtual machine are known as guest machines and host machine is the hypervisor on which different virtual machines are created.

Full virtualization & para virtualization both comes under the Hardware virtualization.

Some of the difference between them are listed below :

Full Virtualization : It is a virtualization in which guest MACHINE(virtual machines) is unaware that it is in virtualized environment therefore hardware is virtualized by the HOST operating system so that the guest can ISSUE commands to what it thinks is actual hardware but really are just simulated hardware devices created by the host

Para Virtualization : It is a virtualization in which guest machine is aware that it is in virtualized environment . If guest machine require RESOURCES like memory & cpu , it issues command to guest operating system instead of directly communication with actual hardware.

Full virtualization & para virtualization both comes under the Hardware virtualization.

Some of the difference between them are listed below :

Full Virtualization : It is a virtualization in which guest machine(virtual machines) is unaware that it is in virtualized environment therefore hardware is virtualized by the host operating system so that the guest can issue commands to what it thinks is actual hardware but really are just simulated hardware devices created by the host

Para Virtualization : It is a virtualization in which guest machine is aware that it is in virtualized environment . If guest machine require resources like memory & cpu , it issues command to guest operating system instead of directly communication with actual hardware.