Introduction to KVM

KVM stands for Kernel Virtual Machine or rather Kernel based Virtual Machine.

This means that the virtual machine manager which actually manages the virtual machines is built into kernel itself unlike other virtual machine managers like virtualbox, vmplayer, etc which work on top of the OS - Windows or Linux.

Topic
Virtualbox
KVM
Xen
Company
Oracle
RedHat
Linux foundation
Intended user
Small medium business
Enterprise
Personal
Small Medium Business
Enterprise
Hypervisor type
Type 2
Type 2
Type 1 (Bare metal)
Virtualization type
Hardware assisted virtualization
Paravirtualization
Full virtualization
Hardware assisted virtualiation
Paravirtualization
Hardware assisted virtualization
paravirtualization
Architecture
x86
x64
x86
x64
Power
x86
x64
Supported storage
iSCSI, USB,Firewire, SAS
SATA,SCSI,PATA
USB
iSCSI
NFS
Virtual CPUs per VM
32
32
512
Virtual CPUs per host
128
16
512
Supported host OS
Fedora
Mac OS X
Solaris
RHEL
Ubuntu
Windows XP, 7,8.10
CentOS
Fedora
Mac OS X
Solaris
RHEL
Ubuntu
CentOS
Fedora
Mac OS X
Solaris
RHEL
Ubuntu
CentOS
Supported Guest OS
All
All
All Linux
No Windows
Price
Free
Free
Open source

Difference between KVM and QEMU

QEMU is a generic and open source machine emulator and virtualizer.  When used as a machine emulator, it can 

QEMU uses emulation; KVM uses processor extensions (HVM) for virtualization. Though both use the same binary (qemu-system-x86_64), they differ in the hardware acceleration type.  In case of KVM, the acceleration type is "kvm" while in case of qemu, the hardware acceleration type is "tcg".

the key difference is that the Virtual CPU is actually emulated (or virtualized) by the hypervisor. Therefore, the hypervisor software has to translate the instructions meant for the Virtual CPU and convert it into instructions for the physical CPU. This translation has a big performance overhead. To minimize these overheads, modern processors  support virtualization extensions. Intel support a technology called VT-x and the AMD equivalent is AMD-V. Using these technologies, a slice of physical CPU can be directly mapped to the Virtual CPU. Hence the instructions meant for the Virtual CPU can be directly executed the physical CPU slice. 

KVM is the Linux kernel module that enables this mapping of physical CPU to Virtual CPU. This mapping provides the hardware acceleration for Virtual Machine and boosts its performance. Moreover, QEMU uses this acceleration when Virt Type is chosen as KVM.
Then what is TCG? If your server CPU does not support virtualization extension, then it is the job of the emulator (or hypervisor) to execute the Virtual CPU instruction using translation. QEMU uses TCG or Tiny Code Generator to optimally translate and execute the Virtual CPU instructions on the physical CPU.
QEMU and KVM by themselves are Type-2 hypervisors, but when QEMU uses KVM for hardware acceleation, then the combination becomes a Type-1 hypervisor. 

Comments

Post a Comment

Popular posts from this blog

Amazon Scenario Questions

1.       You work for a automotive company which is migrating their production environment in to AWS. The company has 4 separate segments, Dev, Test, UAT & Production. They require each segment to be logically isolated from each other. What VPC configuration should you recommend? -           Create a separate VPC for each segment.  Then create VPN tunnels from your HQ to each VPC so that the appropriate teams can each speak to their dedicated VPC 2.       You are solutions architect working for a busy ecommerce store. Due to your organisations unique security requirements, you decide to utilize EC2 running a MySQL database, rather than using RDS. You need to architect this EC2 instance to maximise your disk IO. Which of the following would give you the best disk performance? -           Add 2 x additional Provisioned IOPS (PIOPS) SSD volumes and create a RAID 0 and install MySQL on this RAID 0. 3.        You are designing an AWS solution for a new customer and they wan
Read more

Using ssh keys to login to VMs

1. first generate a public / private key pair using ssh-keygen     ssh-keygen -t rsa -b 4096 -C "ranjit"       - accept the prompts       - if needed, enter a filename - e.g rsa-mykey       - no need of passphrase    after the command executes, 2 files are generated:    rsa-mykey   - this is the private key file    rsa-mykey.pub  - this is the public key file  2.   store the public key file to authorized_keys  :e.g cp rsa-mykey.pub ~/.ssh/authorized_keys  3.   Use the private key file to login into the machine with tools like Putty  4.  Putty does not accept this private key file as it is in openssh ssh-2 format. So convert to putty        private  file format using puttygen        a)  open puttygen        b)  load the private key file        c)  then save the private key file  5.  Use the saved private key file (e.g .ppk) to login to the machine using Putty.
Read more

Accessing NATted VMs from Host machine using Port Forwarding

Usually when we create VMs in Virtualbox and select the Networking option as NAT,  the IPs assigned would be 10.0.2.0/24   - The IP address range for VMs can be managed by creating a NAT network in Virtualbox and specifying the IP range File->Preferences->Network   + new nat network.   Give the name and set the IP address range Then these IP addresses that are assigned to the launched VMs are not accessible from host. E.g. if host IP is 10.20.10.186 and VM IP is 10.0.2.15 , then you can ping 10.0.2.15 from 10.20.10.186, but the reverse is possible, i.e you can ping 10.20.10.186 from 10.0.2.15. so now to connect to the VMs through SSH, we need to enable and configure port forwarding in virtualbox. so go to File->Preferences->Network->NatNetwork (given name to the nat network). Then click on Port Forwarding and add rules for each VM E.g Rule 1    Protocol: TCP  Host IP: 127.0.0.1   Host Port: 2000   Destination IP: 10.0.2.15 Dest Port: 22 Rule 2    Protocol:
Read more