Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Proxmox High Availability

You're reading from   Proxmox High Availability Discover how to introduce, design, and implement high availability clusters for your business without hassle

Arrow left icon
Product type Paperback
Published in Oct 2014
Publisher
ISBN-13 9781783980888
Length 258 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
CHENG MAN CHENG MAN
Author Profile Icon CHENG MAN
CHENG MAN
Arrow right icon
View More author details
Toc

Table of Contents (10) Chapters Close

Preface 1. Basic Concepts of a Proxmox Virtual Environment FREE CHAPTER 2. Getting Started with a High Availability (HA) Environment 3. Key Components for Building a Proxmox VE Cluster 4. Configuring a Proxmox VE Cluster 5. Testing on a Proxmox Cluster 6. System Migration of an Existing System to a Proxmox VE Cluster 7. Disaster Recovery on a Proxmox VE Cluster 8. Troubleshooting on a Proxmox Cluster Index

Virtualization options in Proxmox VE

There are two types of virtualizations available in Proxmox: OpenVZ and KVM. What are the differences between them?

OpenVZ is an operating-system-level virtualization based on the GNU/Linux kernel and the host operation system. Theoretically, OpenVZ is not a type of virtualization but more like the jail concept in Linux. Since a patched Linux kernel is needed, only Linux guests can be created. All guests are called containers that share the same kernel and architecture as long as the host OS, while each container reserves a separate user space.

There is no overhead for OpenVZ as containers can call hardware resources directly. However, since all containers share the system kernel of the host OS, a system-related problem might appear during the host OS kernel upgrade. Besides, OpenVZ stores container files as normal files in the host OS, so it is not recommended to use OpenVZ if there are confidential files stored in the virtual machine. Kernel-based Virtual Machine (KVM) is basically a hardware-assisted virtualization with the modified Linux kernel built with the KVM module. KVM itself does not perform any emulation or virtualization. Instead, it simply exposes the /dev/kvm interface. QEMU is chosen as a software-based emulator to simulate hardware for the virtualized environment. The structure of KVM is shown as follows:

Virtualization options in Proxmox VE

As we can see, overheads on frequent requests appear in QEMU-emulated devices. Thus, an improved version for KVM is published with VirtIO drivers. VirtIO creates a buffer for both the guest system and QEMU, which speeds up the I/O performance and reduces the overhead. To enjoy the performance burst, a VirtIO driver must be installed separately on each emulated hardware device. In the following diagram, we have demonstrated the new structure of the KVM machines with the VirtIO drivers installed:

Virtualization options in Proxmox VE

The following table shows the supported operating systems provided by OpenVZ and KVM:

Virtualization method

Supported operating system

OpenVZ

CentOS, Debian, Fedora, Scientific Linux, SUSE, and Ubuntu

KVM

FreeBSD, Windows Server 2000/XP/2003/2008, Windows 7/8, and all OS supported by OpenVZ

You have been reading a chapter from
Proxmox High Availability
Published in: Oct 2014
Publisher:
ISBN-13: 9781783980888
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image