Redhat Virtualization
Redhat Virtualization
Redhat Virtualization
Agenda
Physical Vs Logical(Demo) Virtualization: The What? Virtualization: The How? Virtualization: The Why? Redhat Virtualization(Demo)
Physical Vs Logical
A demonstration for Logical Volume Manager (L.V.M) is suffice enough to give an insight of how great the things are if scaled ahead the physical boundaries
#pvdisplay
Create volume group of the three partitions thus formed #vgcreate vg0 /dev/hda{5,6,7}
#vgdisplay
create the logical volume of the volume group thus formed using command: #lvcreate -L +50M /dev/vg0 -n lv0
#lvdisplay
We can even extend this logical volume thus formed using the following command depending upon our use: #lvextend -L +25M /dev/vg0/lv0 Display the logical partition which actually exists for use: #ls /dev/vg* Finally after the partition is created: mount a file system to it using command: mkfs.ext3 -L /lvm_data /dev/vg0/lv0 Mounting it on a directory to use. mount /dev/vg0/ /mnt
In Past
One operating system on one machine , so ,the OS had complete control of the resources in that machine. Various applications would run on that machine, but these applications could affect each other. Machine utilisation was very low, most times it was below 20%.
Even Now!!
!!Virtualization!!
Virtualization, in computing, is the creation of a virtual (rather than actual) version of something, such as a hardware platform, operating system, a storage device or network resources.
The usual goal of virtualization is to centralize administrative tasks while improving scalability and overall hardware-resource utilization.
Virtual Machine Monitor(or Hypervisor) Each virtual machine interfaces with its host system via the virtual machine monitor (VMM). Being the primary link between a VM and the host OS and hardware, the VMM provides a crucial role.
OS and Apps in a VM don't know that the VMM exists or that they share CPU resources with other VMs VMM should isolate Guest SW stacks from one another VMM should run protected from all Guest software VMM should present a virtual platform interface to Guest SW
The center (reserved for the most privileged code) is used for the segments containing the critical software, usually the kernel of an operating system.
Virtualization Types:
Full Virtualization Para Virtualization
Full Virtualization
Complete simulation of the underlying hardware. Every salient feature of the hardware is reflected into one of several virtual machines including the full instruction set, input/output operations, interrupts, memory access, and whatever other elements are used by the software that runs on the bare machine, and that is intended to run in a virtual machine.
Para Virtualization
presents a software interface to virtual machines that is similar but not identical to that of the underlying hardware.
The intent of the modified interface is to reduce the portion of the guest's execution time spent performing operations which are substantially more difficult to run in a virtual environment compared to a non-virtualized environment.
Major Hypervisors
Xen : University of Cambridge Computer Laboratory Fully open sourced Set of patches against the Linux kernel
VMware ESX : Closed source Proprietary drivers VirtualBox: a free hypervisor from SUN Systems. Limited functionality KVM: Most used Hypervisor in Linux.
Xen Vs KVM
Xen
Hypervisor that supports x86, x86_64, Itanium, and ARM architectures. can run Linux, Windows, Solaris, and some of the BSDs as guests on their supported CPU architectures. can do full virtualization on systems that support virtualization extensions, but can also work as a hypervisor on machines that don't have the virtualization extensions.
If you want to run a Xen host, you need to have a supported kernel.
Though after kernel 2.6.23 ,linux has started to put in into the mainline.
KVM Hypervisor that is in the mainline Linux kernel. runs on x86 and x86-64 systems with hardware supporting virtualization extensions. KVM isn't an option on older CPUs made before the virtualization extensions were developed, and it rules out newer CPUs (like Intel's Atom CPUs) that don't include virtualization extensions.
If you're getting a recent Linux kernel, you've already got KVM built in.
System Requirements
Xen para-virtualization requirements
Para-virtualized guests require a Red Hat Enterprise Linux 5 installation tree available over the network using the NFS, FTP or HTTP protocols.
KVM requirements The KVM hypervisor requires: an Intel processor with the Intel VT and the Intel 64 extensions, or an AMD processor with the AMD-V and the AMD64 extensions.
Red Hat
Virtualization
Shared Storage
GUI Installation
Open the Virtual Machine Manager window. Select Applications System ToolsVirtual Machine Manager.
Add a connection. Select File Add Connection. The Add Connection pop-up appears.
CLI Installation
#virt-install --prompt
:Future?
More manageble
oVirt (free platform virtualization management web application software developed by Red Hat)
Installation
Administration
On Scale of 5(best)
Hows That!!!
Target
The Enthusiasts
The Architects The Executives
The Followers
References
Websites:
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Virtualization/ http://en.wikipedia.org/wiki/Xen http://xen.org/ http://www.server-world.info/en/note?os=Ubuntu_10.04&p=kvm http://www.linuxforu.com/2011/09/vmware-player-virtualbox-kvm-virtualizationcomparative-review/http://www.linuxforu.com/2011/09/vmware-player-virtualbox-kvmvirtualization-comparative-review/
https://www.linux.com/news/enterprise/systems-management/327628-kvm-or-xenchoosing-a-virtualization-platform
Contd..
Documents and Books: Xen and the Art of Virtualization
Paper by: Paul Barham, University of Cambridge Computer Laboratory
!!Queries!!