Q
Evaluate Weigh the pros and cons of technologies, products and projects you are considering.

How does KVM technology differ from the competition?

KVM is an open source Linux module that is widely considered to be a type 1 hypervisor because it runs directly on hardware and can use processor extensions.

KVM is an important virtualization technology that adds hypervisor capabilities to the Linux kernel, which, in...

turn, allocates memory, provides security and schedules processes efficiently. In addition, Linux is easily stripped of unnecessary code, allowing for enormous optimization and highly efficient operation.

Through the years, KVM technology has evolved to support more processors and OSes -- even Windows guests. As Linux gains traction in mainstream data centers, administrators should have a better understanding of KVM technology and the benefits it can bring to the enterprise.

How is KVM different than other types of hypervisors?

First introduced in 2007, KVM is an open source Linux module that competes with other commercial hypervisors like VMware ESXi and Microsoft Hyper-V.

Linux employs a strong modular approach to software deployment, allowing administrators to add or remove modules to compile the fastest and most efficient codebase possible for distribution. KVM is just one of those possible modules, and it can be compiled into the Linux kernel to bring hypervisor functionality to Linux.

The open source nature of KVM -- and the entire Linux environment -- means that the kernels and modules can be modified and optimized as desired to improve performance or add other functionality. This is dramatically different than commercial hypervisor products that are delivered as opaque, monolithic -- potentially less efficient or unnecessary -- code that can't be adapted or streamlined by IT staff.

The Linux kernel handles the file system, block devices and physical drivers. KVM exposes an interface that allows an administrator to establish a KVM guest -- a KVM VM. KVM configures VM address space, delivers virtual CPUs, handles I/O streams, provides a firmware image to the guest and maps each guest's video output back to the host kernel for display. Once established, a KVM guest receives vCPUs and I/O, which is then passed to the guest OS kernel, where the guest drivers and file system can interact with the guest application -- workload. Thus, every VM becomes a regular Linux process that can operate at near-bare-metal speeds.

There is some debate over the role of KVM as a type 1 or type 2 hypervisor. The reliance of KVM technology on an underlying kernel causes KVM to be incorrectly classified as a type 2 -- hosted -- hypervisor. However, this architectural relationship doesn't accurately reflect the fact that KVM runs directly on hardware, and can use processor virtualization extensions, such as Intel VT-x and AMD-V. KVM technology simply uses the Linux kernel as a minimum OS, just as ESXi and Hyper-V require some minimum OS capabilities to function.

Today, KVM is widely recognized as a type 1 bare-metal hypervisor capable of enterprise-class performance. Examples of stand-alone KVM distributions include Red Hat Enterprise Virtualization Hypervisor.

However, the open source flexibility of KVM -- and Linux as a whole -- presents other challenges for enterprise IT staff. Organizations that choose to use Linux in production are generally hesitant to tinker with Linux builds. Pre-established Linux distributions that include KVM technology, such as Red Hat Enterprise Linux, SUSE Linux Enterprise Server, the Fedora Project and others, can eliminate the risks and costs of organizing and compiling a Linux environment for the business.

However, organizations that choose to adapt and modify the Linux environment, including KVM, will need extensive skills in coding, compiling and testing Linux builds. Consequently, Linux is well-suited to enterprise use, but it's often used for specific applications; KVM coexists with other commercial OS and hypervisor products.

Next Steps

Compare different hypervisor technologies

Navigate between host hypervisors and nested hypervisors

Use Proxmox to reduce virtualization costs

This was last published in April 2017

Dig Deeper on Open source virtualization

PRO+

Content

Find more PRO+ content and other member only offers, here.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Join the conversation

1 comment

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

In what other ways does KVM differ from competing hypervisors?
Cancel

-ADS BY GOOGLE

SearchVMware

SearchWindowsServer

SearchCloudComputing

SearchVirtualDesktop

SearchDataCenter

Close