K V M f o r S e r v e r V i r t u a l i z a t i o n

K V M  f o r  S e r v e r  V i r t u a l i z a t i o n

KVM stands for Kernal-based virtual machine. It is considered as the newest hypervisor to enter the virtualization market. Like many other Type1 hypervisor it is embedded into an OS such as Linux. KVM is implemented as a module within the Linux Kernel.

KVM has contributed to areas such as memory management, performance, and virtual I/O as part of the open source community. KVM is a loadable kernel module within the Linux kernel that allows the Linux operating system to function as a Type 1 bare metal hypervisor.

A hypervisor can be defined as a very specialized operating system designed to run VMs instead of arbitrary applications.A hypervisor also deals with standard OS tasks such as managing memory, scheduling processes, handling drivers, doing I/O, etc.

KVM Architecture:

1.Scheduling, resource control, and memory management: Virtual machines under KVM in Linux are simply treated as any other running process during execution.

2.Storage: VM images are treated like any other Linux file on a disk device. Thus storage support is any type of storage that is supported by Linux today, which includes local disk, a variety of file systems, NAS, iSCSI, and SAN.

3.Hardware support: KVM inherits the entire Linux device ecosystem and is able to access any device that Linux supports.

4.Security: KVM also is able to leverage the Linux security model, SELinux, which essentially “sandboxes” processes so that if a process becomes compromised the problem is limited to that process and does not compromise the entire system.

VM serves as foundation of clouds of many types such as internal, external, private, and public.

Some of the challenges or opportunities of KVM include:

Challenges:

1.KVM maturity.

KVM is the newest hypervisor on the market and thus has had the least time to mature. KVM has certainly progressed at an impressive rate and by being part of the main Linux kernel.

2.Expanding beyond Linux.

Being so closely tied to Linux comes with benefits and challenges. Many customers will see KVM as a solution primarily for virtualizing Linux on Linux, even though Windows is well supported.

3.Monetizing the cloud.

Service providers may be showing interest in and adopting open source, but monetizing it is a more difficult problem

4.Ecosystem support

Virtualization is no longer just a server consolidation tool; it is the foundation for the dynamic datacenter and cloud.

Virtualization interconnects with every part of the datacenter (servers, storage, networking, security, management, etc.), and the ecosystem support for any hypervisor must be far reaching and diverse in order to succeed today.

5.Creating a robust management ecosystem

While many of the base-level APIs and libraries have been established, higher-level tools continue to progress. Red Hat’s open sourcing of RHEV-M in hopes of unifying the community around a central KVM management interface will be key for KVM and the opensource ecosystem.

Opportunities:

1.Leveraging the reach of Linux.

Because KVM is an inherent part of Linux, KVM will reach everywhere that Linux exists today, making it available to anyone using Linux.The Linux ecosystem is far larger than Red Hat alone,and the nonpaid Linux server operating system market accounts for 42% of the overall Linux market

2.The public cloud.

Public cloud providers have shown an early preference for using open source software to build their offerings because of the cost and the open, freely modifiable nature of the code.

 

References;

http://www-03.ibm.com/systems/resources/systems_virtualization_idc__kvmforservervirtualization.pdf

 

 

 

Leave a Reply

100 Arbor Oak Drive, #200
Ashland, Virginia 23005-2261
Phone: 1-(804)-368-8631
Toll Free: 1-(877)-230-7449
Website: http://www.ooacllc.com
Email: info@ooacllc.com