Proxmox High Availability: Chapter No. 1 "Basic Concepts of A Proxmox Virtual Environment"

Proxmox High Availability
Simon M.C. Cheng

Chapter No. 1
"Basic Concepts of a Proxmox Virtual
Environment"
In this package, you will find:
The authors biography
A preview chapter from the book, Chapter no.1 "Basic Concepts of a Proxmox Virtual
Environment"
A synopsis of the books content
Information on where to buy this book

About the Author
Simon M.C. Cheng is an experienced engineer and has been working in the field of
system administration on Linux and Windows platforms for around 8 years. He has a
Bachelor's degree in Computing from The Hong Kong Polytechnic University.
He currently lives in Hong Kong and has previously worked in a number of different
roles, including as a technician at a college, IT officer at Geodis Wilson Hong Kong
Limited, senior systems engineer at Questex Media Limited and Ignite Media Group,
and a few more roles. In recent years, he has become interested in server virtualization
and has put his efforts into learning more about it.
If you have anything to share, you can contact him on LinkedIn or e-mail him at
.

For More Information:
www.packtpub.com/virtualization-and-cloud/proxmox-high-availability

I am deeply indebted to my acquisition editors, Ashish Bhanushali and
Subho Gupta, and the project co-ordinator, Kinjal Bari, who gave me
the chance to write my first book. It was a great gamble for them to
choose me because I had no prior experience in book publishing.
I would like to express my deepest gratitude to my responsible editor,
Ruchita Bhansali. She is a very helpful and responsible editor who put
in a lot of effort in this book and led me through the process of
publishing this book.
I am also grateful to all the reviewers from different technical
backgrounds for their comments, opinions, and valuable suggestions
for this book. These suggestions have definitely enriched and
expanded the content of this book. Thanks to them for making this
book interesting and enriching.
Last but not least, I would like to take this opportunity to give credit to
my parents and my girlfriend, Fanny. Without their understanding
and support, I would not have had the courage to accept this
new challenge.


Proxmox High Availability
Nowadays, the number of network services is rapidly increasing, due to which service
availability has become a concern. With the help of the easy-to-use tools provided by
Proxmox, users can easily improve their service by building their own clusters. The
support of various storage options provides flexibility with different forms of
network storage.
What This Book Covers
Chapter 1, Basic Concepts of a Proxmox Virtual Environment, explains the concept of
virtualization and compares Proxmox with other virtualization software.
Chapter 2, Getting Started with a High Availability (HA) Environment, includes the
functions provided by a Proxmox cluster and explains how it achieves high availability.
Chapter 3, Key Components for Building a Proxmox VE Cluster, explains all the
components required when building a Proxmox cluster environment.
Chapter 4, Configuring a Proxmox VE Cluster, demonstrates the actual installation and
configuration of a Proxmox cluster.
Chapter 5, Testing on a Proxmox Cluster, includes testing on a configured
Proxmox cluster.
Chapter 6, System Migration of an Existing System to a Proxmox VE Cluster, explains
how to migrate existing running systems, including Windows, Linux, and other
virtualization software fi le formats to a Proxmox cluster.
Chapter 7, Disaster Recovery on a Proxmox VE Cluster, talks about the backup of a
Proxmox cluster. The chapter also introduces the system restore process when a
Proxmox cluster fails.
Chapter 8, Troubleshooting on a Proxmox Cluster, introduces all the
troubleshooting content.


Basic Concepts of a Proxmox
Virtual Environment
Have you ever imagined how good it would be if you don't need to stop your
services during a system upgrade operation? Do you have a powerful server but
haven't used all of its resources? Do you want to set up a server platform quickly
using a system template? If the answer to all these questions is yes, then you will be
very happy to work with Proxmox Virtual Environment (also called Proxmox VE).
This chapter will show you some basic concepts of Proxmox VE before actually using
it, including the technology used, basic administration, and some options available
during set up.
The following topics are going to be covered in this chapter:
An explanation of server virtualization used by Proxmox VE
An introduction of basic administrative tools available in Proxmox VE
An explanation of different virtualization modes and storage options
Introduction to Proxmox Virtual
Environment
So what is Proxmox Virtual Environment actually used for? Proxmox VE is an open
source bare metal environment based on the Debian Linux distribution (also called
hypervisor or Virtual Machine Monitor (VMM)) for server virtualization. It allows
a user to install different operating systems (for example, Windows, Linux, Unix,
and others) on a single computer or a cluster built by grouping computers together.
It consists of powerful Kernel-based virtual machines and lightweight OpenVZ
containers as an alternative.


Basic Concepts of a Proxmox Virtual Environment
[ 6 ]
The main features for Proxmox VE can be summarized as follows:
Open source: It is fully open source under General Public License, version
3 (GNU AGPL, v3), which means you can freely view, alter, and remove the
source code, and distribute your own version as long as you are compliant
with the license.
Live migration: This allows moving a running virtual machine from one
physical server to another without downtime.
High availability: In Proxmox HA cluster mode, when one node fails, the
remaining virtual machines will be moved to a healthy node to make sure
there is minimal service interruption.
Bridged networking: Proxmox VE allows a user to build a private network
between the virtual machines. VLAN options are also available.
Flexible storage: A wide range of storage options are available, including
both local and network-based storage technologies such as LVM, iSCSI, NFS,
the Gluster lesystem, and the CEPH lesystem.
OS template: Proxmox VE allows users to build their own OS template for
further deployment. Of course, it is also possible for users to download a
template le from the Internet and import that le into their system.
Scheduled backup: A user interface is provided to users so that they can set
up their own backup strategy. The backup les can be stored locally or on
any supported storage option that you have congured.
Command-line (CLI) tool: Proxmox VE provides different CLI management
tools allowing users to access the virtual machine container, manage
resources, and so on.
You can try Proxmox for free at http://pve.proxmox.
com/wiki/Downloads.
Introduction to server virtualization
Have you ever heard about cloud computing? It is a hot topic in the IT industry and
claims that you can allocate nearly unlimited computer resources on a pay-as-you-go
basis. Are you not curious to know how they are able to provide such a service?
The underlying technology that allows them to be able to provide such a service is
hardware virtualization. If you don't understand how virtualization works, it could
be difcult for you to imagine how they can add or remove resources instantly. Let's
talk about how server virtualization works and what it offers us.


Chapter 1
[ 7 ]
Why should we use server virtualization? Since the new generation of server class
machines are becoming much more powerful, it becomes quite difcult to use up all
the system resources if we only install one Operating System (OS) on it. Also, renting
multiple server racks in a data center is expensive. Centralizing multiple servers
into a limited set of powerful servers seems to be a more cost-effective solution, thus
virtualization appears. Server virtualization allows users to create multiple system
objects called virtual machines (VMs) that act like normal computers. Virtualization
of physical devices implies that each virtual machine has its own CPU units (called
vCPU), memory, hard disk, and network card, according to a user's allocation. When
the user turns on the virtual machines, different OSes can be installed on them.
Therefore, better system resources utilization can be achieved. The following gure
shows the difference between a physical machine and a virtual machine:
CPU RAM HDD NIC
OS OS
User
Application
User
Application
Virtualization Layer
User application
Operation System
CPU RAM HDD NIC
Normal Server
CPU RAM HDD NIC
CPU RAM HDD NIC
Server with virtual machines
Depending on the kind of processor used, there are three different types
of virtualizations available: full virtualization, para-virtualization, and
hardware-assisted virtualization. In order to state the difference between these
virtualization methods, we need to know how a Control Processing Unit (CPU)
executes code that a user has passed.


[ 8 ]
During any process execution, a CPU is the computing unit that executes predened
instruction sets to generate the results that the program had dened. But, it is
dangerous if we give full access to all applications on our devices. For example, if
there is no restriction on hardware access, a web page will be able to inject suspicious
code into local memory and it may further damage the data stored in our computers.
Therefore, a term called protection ring ranking, which ranges from 0 to 3 under the
x86 architecture is used to protect our hardware. Normally, Ring 0 (also called
supervisor mode) is used in the OS to monitor and control system resources. Ring 3
(also called user mode) is used for a user application, and if we would like to have
access to hardware, a system call provided from the supervisor mode must be made.
The following gure shows the system ring structure for the x86 platform:
Device drivers
Device drivers
Applications
Ring 0
Kernel
Ring 1
Ring 2
Ring 3
Least privileged
Most privileged
Based on the levels of virtualization, we have the following different types of
virtualization types: full virtualization, para-virtualization, and hardware-assisted
virtualization:
Full virtualization: In this the VMM is placed under Ring 0 while the
virtualized guest OS is installed under Ring 1. However, some system
calls can only be executed under Ring 0. Therefore, a process called binary
translation is used to translate such system calls, and thus, the performance
is degraded. In this mode, the guest OS does not know it is being virtualized,
so it does not require kernel modication. Here is a simple structure for this
type of virtualization:


Chapter 1
[ 9 ]
VMM
VMM
Hardware
Hardware
Ring 3
Ring 0
Ring 1
Ring 3
Ring 0
Binary
Translation
User mode
Supervisor mode
Traditional system Full Virtualization
User APP
Guest OS
User APP
Para-virtualization: This is very similar to full virtualization, but custom
drivers are installed on the guest OS in order to access CPU resources
without downgrading to Ring 1. So, the performance of the guest OS
is near to that of the physical machine because the translation process is
not needed, but the guest OS requires a modied kernel. Thus, the guest
cannot run a different operating system from the host operation system.
The following diagram shows the structure of this virtualization:
VMM
Hardware
Ring 1
Ring 3
Ring 0
User mode
Supervisor mode
Para-virtualization
User APP
Guest OS
+ custom drivers
Hardware-assisted virtualization: CPU manufacturers introduce a new
functionality for a virtualized platform, Intel VT-x and AMD-V. The ring
level 0 to 3 is categorized into non-root modes, and a new level, -1, is
introduced as the root mode. The guest OS is now installed to Ring 0, which
means it can access hardware directly. Because it does not need a custom API
to make system calls under Ring 0, no kernel modication is needed. The
following diagram shows you the structure of the virtualization mode:
VMM
Hardware
Ring 1
Ring 3
Ring -1 non-root
User mode
Supervisor mode
Hardware assisted virtualization
User APP
Guest OS
root mode


[ 10 ]
Server virtualization basics guest
versus host
So, when both physical and virtualized platforms are running operating systems,
how can we distinguish them from each other? Here come the terms: host and guest,
explained in the following points:
Host OS: It is an operating system that provides virtualization capabilities
for creation, modication, and removal of virtual machines. A virtualization
package contains a component called Virtual Machine Monitor, which
provides an isolated environment to run multiple platforms.
Guest OS: This refers to the operating system installed inside the virtual
environment. The supported guest OS depends on the virtualization software,
and the performance of the guest OS depends on how many resources have
been allocated to it. The following diagram shows a simple diagram on how
we assign different system resources to our virtual machines:
Host OS
Quad-core CPU
8GB RAM
1 TB hard drive
Guest OS 1
vCPU1
1GB RAM
100 GB hard drive
Guest OS 2
CPU1, vCPU2 v
2GB RAM
200 GB hard drive
Comparing types of server virtualization
software
We have discussed why we need to learn server virtualization and how virtualization
works, so are you curious about how many types of major virtualization software are
on the market? What are the differences between them? Let's take a deep look at it:
Proxmox VE: As mentioned before, Proxmox VE is an open source
hypervisor based on GNU/Linux (Debian-based) with a RHEL-based
kernel and published under GNU AGPL v3. It differs from the alternative
virtualization software as Proxmox provides a central web-based
management without further installation. The underlying technologies used
are Open Virtuozzo (OpenVZ) and Kernel-based Virtual Machine (KVM),
which will be described in Version 1.6. Subscription plans are available for
accessing enterprise repository, software updates, and user support.


Chapter 1
[ 11 ]
XenServer: This is a native hypervisor based on GNU/Linux developed
by the Xen Project and published under GNU AGPL v2 as open source.
For XenServer, a concept of domain is used for all virtual machines,
and the most privileged domain (for example, a domain that allows direct
access to hardware) dom0, is used by the hypervisor to manage other
domU virtual machines. It supports para-virtualization, which allows a user
to run virtualized guests on a CPU without support for virtualization; for
example, no Intel VT-x or AMD-V is needed. Amazon Web Service (AWS)
is a production example of using XenServer.
VMware ESX/ESXi: This is a bare-metal hypervisor developed by VMware
based on a customized kernel called vmkernel, which is a microkernel
developed by VMware.
The difference between ESX and ESXi is that ESXi is a free version of ESX
with some resource limitations. ESX has a hardware compatibility list that
includes many drivers for network cards and SCSI cards. An extra hardware
driver can be added to the base installation if needed. On top of the
para-virtualization and hardware-assisted virtualization, ESX provides
full virtualization as another option.
There are two management tools available: vSphere client and vCenter
server. VSphere client is enough for normal administration operation on
one ESX while vCenter server allows the user to manage multiple ESXs,
including the conguration of advanced features such as high availability
and live migration.
Hyper-V server: This is a proprietary virtualization platform produced by
Microsoft Corporation running under the Windows platform starting from
Windows Server 2008. If you are mainly using a Windows platform as your
virtualized guest, it is recommended that you use Hyper-V, especially if you
have enabled an Active Directory domain services.
Hyper-V provides better migration options to users; it not only provides
live migration, but also provides unlimited guest movements between hosts. The
benet of the features of an Active Directory domain is that Hyper-V provides
replica on virtual machines, which allows a user to copy a specic VM from the
source's site to the target site asynchronously via a WAN or a secure VPN.


[ 12 ]
Comparison table of hypervisors
We have learned that there are many virtualization platforms on the market, so what
are the differences between them? Let's take a look at the following table:
Virtualization
platform
Proxmox XenServer VMware
ESX/ESXi
Hyper-V server
Latest version 3.2 6.1 5.5 Server 2012 R2
License GNU GPL v3 GNU GPL v2 Proprietary Free
Open Source Yes Yes No No
Base OS Linux Linux Vmkernel Windows
Console OS No Yes Yes No
Management
tools
Web GUI XenCenter vSphere Client
vCenter
Hyper-V
Manager
Host HA Yes Yes Yes (vCenter) Yes
Guest HA Yes Yes,
(XenMotion)
Yes, (vMotion) Yes (Live
Migration)
Supported
storage
LVM
groupNFS,
iSCSI, RBD,
NAS, and SAS
NFS, iSCSI,
fiber channel,
NAS, SAS, and
CIFS
Fibre Channel,
iSCSI, NAS,
and SAS
SMB, iSCSI,
Fibre channel,
NAS, and SAS
Supported
virtualization
technology*
FV
(KVM)
OpenVZ
PV
HV
FV
PV
HV
PV
HV
License model Per CPU Per CPU Per CPU Per VM and host
In the previous table, FV stands for full virtualization, PV stands for
para-virtualization, and HV stands for hardware-assisted virtualization.
Basic administration on Proxmox VE
After we have talked about so many concepts, let's learn how to congure Proxmox!
I assume you have downloaded and installed your own Proxmox. If you face any
difculty during the installation, you can refer to the following link:
https://pve.proxmox.com/wiki/Quick_installation


Chapter 1
[ 13 ]
The following steps will help you perform basic administration in Proxmox VE:
1. After the installation, you should be able to see the following screen:
2. In this step, access the Proxmox VE using a web browser, and make sure
you have network access and you are connected in the same subnet as
Proxmox. Then, type in a URL in the following format in your browser:
https://<Proxmox_IP>:8006. When you rst visit the page, your browser
will warn you that the SSL certicate is not a trusted one. It is normal if you
have experience in building your self-signed SSL certicate on your web
server. If you have a domain name for your Proxmox server and would like
to have a SSL certicate signed by an authorized CA, please take a look at the
following sites:
Apache CSR creation using OpenSSL http://www.digicert.com/
csr-creation-apache.htm
HTTPS certificate configuration http://pve.proxmox.com/wiki/
HTTPSCertificateConfiguration
3. Next, simply choosing Continue to this website in Internet Explorer adds to the
exception. Similarly, choose I understand the risk in Firefox and Chrome. Next,
just log in to the system with the root account since we haven't created our own
user account. Being logged in, the following warning message indicates that
you do not have a valid subscription plan. You can ignore this warning message
if you currently don't need to have technical support.


[ 14 ]
4. Within the web GUI, you will be able to manage most features of the
Proxmox platform. For example, you can create new virtual machines
by using the buttons located in the upper-right corner, as shown in the
following screenshot:
There are two ways to create new virtual machines: Create VM and Create CT.
5. By clicking on the Create CT button, you can create a virtualized Linux
platform under the OpenVZ container. It is recommended for GNU/Linux
guests because the Linux kernel is shared with the host server, which means
that the used memory on the host server will be reduced. When you go
through the wizard after clicking on the Create CT button, a virtualized OS is
created based on the OS template you used. An OS template is an operation
system (for example, CentOS, Debian, and others) with customized packages
installed and predened system parameters. The templates are available
in the form of a brand new system or installed with a web server or an
application like Drupal. Typically, no graphical user interface (GUI) is
preinstalled in the virtualized guests if you use this type of installation.
Uploading the OS template or the ISO le
to Proxmox
Before we can start trying to build our own virtual machines with OpenVZ, we have
to rst upload either an OS template or an ISO le that contains the operating system
installation les to Proxmox. The following steps will help us understand how to
do this:
1. Double-click on the icon that is named as the hostname of Proxmox, then
choose local, click on Content, and choose Upload from the panel on the
right-hand side, as shown in the following screenshot:


Chapter 1
[ 15 ]
2. After we have clicked on the Upload button, three options are available,
as shown in the following screenshot:
The three options available are as follows:
ISO image: This is used as the installation source file for
Kernel-based virtualization
VZDump backup file: This is used to upload backup files created
by Proxmox for restoration
OpenVZ template: This is used for the installation source for
OpenVZ virtualization
3. Then, we can simply browse the le that we would like to upload. Pay
attention when uploading the OpenVZ template le; you need to use
the following naming format:
{OSName}-{OSVersion}-{OSName}_{OSType}_{amd64/i386}.tar.gz
This format is shown in the following example:
centos-6-CentOS_standard_amd64.tar.gz
The output can be seen in the following screenshot:
We are now ready to create our own virtual machines; let's see how we can create an
OpenVZ-based virtual machine rst. For example, the OpenVZ template le will be
stored inside /var/lib/vz/template/cache/; you can also manually upload it to
that directory if you don't wish to use the web interface.


[ 16 ]
Creating an OpenVZ-based virtual machine
To create an OpenVZ-based virtual machine, please follow these steps:
1. Click on the Create CT button, and the following window pops up; a system
hostname and a password for the root account can be dened, as shown in the
2. Next, the system will ask you for the template you want to use; for example,
you can choose centOS-6-CentOS_devel_amd64.tar.gz:
3. Then, you will be asked to assign resources to the VM; we can accept the
default setting for testing purposes:


Chapter 1
[ 17 ]
4. After we have allocated system resources to the new virtual machine,
we reach an important part: networking. Here, you have the following
two options:
Routed mode: This uses the default network interface used by
Proxmox, and simply specifies an IP address. Only select routed
mode if you create a guest system that lies in the same IP subnet
as the host system. It would be slightly easier during the system
configuration than in the Bridged mode.
Bridged mode: This allows you to choose a network adapter other
than the default one (including a VLAN-enabled interface). It requires
a DHCP server for IP assignment or is manually configured under VM.
A demonstration on how to configure the Bridged mode will be shown
in Chapter 4, Configuring a Proxmox VE Cluster.
In the following screenshot, we choose the Routed mode and specify an IP
address for demonstration:
5. The following settings regarding the DNS parameters are saved to
the /etc/resolv.conf le in the virtualized guest:
6. A summary for the conguration is displayed before the VM is created.


[ 18 ]
7. After the VM creation is completed, you can view its status in the Summary
tab, as shown in the following screenshot:
Creating a kernel-based virtual machine
We have seen how to create OpenVZ-based virtual machines; now, let's learn how
we can create a kernel-based virtual machine:
1. Click on the Create VM button in the top-right corner, as shown in the
2. Specify a name for identication, but please note that the name is not directly
applied to the VM's hostname, as shown in the following screenshot:


Chapter 1
[ 19 ]
3. Then, we need to choose the type of platform we are going to create, shown
as follows:
4. Next, the OS installation source is specied, shown as follows:
5. After that, we have to allocate the hard disk for the virtual machine. Pay
attention to the hard disk's Format you have chosen; the raw format will
instantly allocate the space you have dened (that is, if you dened a 20 GB
hard disk, a disk image with 20 GB will be created under the host server) while
the QEMU format will only allocate the space based on the current usage of
the guest OS. If the guest OS takes up 8 GB, then a disk image with 8 GB in size
will be created. For more details, refer to the Virtual disk options under Proxmox
VE section. The hard disk window is shown in the following screenshot:


[ 20 ]
6. The number of cores/sockets and the CPU types have to be specied for the
guest, as shown in the following screenshot:
7. Of course, we need to allocate the amount of memory for the guest platform,
shown as follows:
8. For the network part, similar to the OpenVZ creation, we have bridged
mode and NAT mode. Here, we can specify Model for the virtualized
VM; generally, choosing Intel E1000 and Realtek RTL8139 should be ne.
The VirtIO option provides better performance, but the driver must be
installed on the guest OS before it can be used. This is shown in the
9. A summary of the congurations is displayed for conrmation.


Chapter 1
[ 21 ]
10. Just as it appears for OpenVZ, we can nd our created VM under the menu,
as follows:
Isn't it easy to create a virtual machine with a web interface? By the way, you can
identify whether a virtual machine is an OpenVZ container or KVM by its associated
icons, as shown in the following screenshot:
Accessing the new virtual machine
Congratulations! You have just created your own virtual machine! Wait, how can
we access the system? That's a good question; here, we have two options to achieve
our goal. One option is to access it from the web browser. What? Access an operating
system with a web browser? Yes, let's see how it works:
1. Right-click on the virtual machine you would like to access from the panel on
the left-hand side, and then choose console.
Prior to Proxmox 3.2, a new console mode, SPICE, was introduced, which
provides a better usage performance especially in a KVM machine. You can
refer to https://pve.proxmox.com/wiki/SPICE for more details.
Make sure you have the latest JAVA runtime (JRE), preferably with JAVA 7
on your browser, and allow it to run if there is any prompt message. You can
download it from http://www.oracle.com/technetwork/java/javase/
downloads/index.html. If you cannot run the applet, refer to Chapter 8,
Troubleshooting on a Proxmox Cluster, for troubleshooting.


[ 22 ]
Pay attention to OpenVZ-based VM; you will see that it cannot be accessed from the
console because you have to congure a getty service inside the VM. So, we need to
use another method for this purpose, for example, the OpenVZ management CLI:
1. Access your Proxmox console with the root account, as shown in the
2. You can check the existing running OpenVZ containers with the
vzlist command as shown in the following screenshot:
3. Then, access it with vzctl enter <CTID>, for example, vzctl enter 102.
4. Create a new le under /etc/init.d/tty.conf with vi or any text editor
you like.
5. Paste the following code in the tty.conf le:
# This service maintains agetty on tty1 from the point the
# system is started until it is shut down again.
start on stopped rc RUNLEVEL=[2345]
stop on runlevel [!2345]
respawn
exec /sbin/agetty -8 tty1 38400
6. Reboot the guest VM or type start tty to reboot.


Chapter 1
[ 23 ]
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 les as normal les in the host OS, so it is not recommended to use OpenVZ
if there are condential les stored in the virtual machine. Kernel-based Virtual
Machine (KVM) is basically a hardware-assisted virtualization with the modied 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:
QEMU
VM
(guest system)
KVM kernel module
1) ioctl() 4) Return
2) VM Entry 3) VM Exit
Linux kernel (hypervisor)
0) /dev/kvm
User space


[ 24 ]
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:
User space
virt-manager
libvirt
QEMU
VM
(guest system)
KVM kernel module
Linux kernel (hypervisor)
/dev/kvm Intel VT-x
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
Virtual disk options under Proxmox VE
During the virtual machine creation, the following virtual disk options are available:
RAW: This is a raw le format. The disk space is allocated during the
creation and will use up the specied size. When compared with QCOW2,
it gives a better overall performance.


Chapter 1
[ 25 ]
QCOW2: This is an enhanced version of QCOW, which offers a provisioning
ability for disk storage used by QEMU. QCOW2 offers a capability to create
multiple virtual machine snapshots compared to the older version. The
following features are supported:
Thin-provisioning: During the disk creation, a file smaller than the
specified size is created, and the specified size will be configured
as the maximum size of the disk image. The file size will grow
according to the usage inside the guest system; this is called
thin-provisioning.
Snapshot: QCOW2 allows the user to create snapshots of the current
system. With the use of the copy-on-write technology and a read-only
base image, differential backup can be achieved.
VMDK: This file format for a disk image is used by VMware. The
virtual disk file can be imported back to VMware Player, ESX, and
ESXi. It also provides a thin-provisioning function such as QCOW2.
Introducing the OpenVZ template
Since the OpenVZ lesystem is only le-based, it is possible to pack the
congurations and the disk image into a le for further deployment. We can create
our own template le (which will be introduced in Chapter 7, Disaster Recovery on a
Proxmox VE Cluster), or download the template le (also called a virtual appliance)
via a web interface or from http://download.proxmox.com/appliances/.
Use these steps to download an OpenVZ template:
1. Log in to the web interface of Proxmox, and nd local storage from the panel
on the left-hand side.
2. Click on the Content tab and choose Templates, as shown in the


[ 26 ]
3. Next, we need to nd a suitable template to download; for example,
we can download a system with Drupal installed, as shown in the
4. After we click on the Download button, the following progress window is
shown along with the download details:
5. When the download completes, the template le is listed on the templates
page, as shown in the following screenshot:


Chapter 1
[ 27 ]
Summary
In this chapter, we introduced the different modes of server virtualization, the
reasons for using it, and how it actually works. We also caught a glimpse of the
development on server virtualization by knowing the background technologies.
Besides that, we learned the features and strengths of the different hypervisors on
the market. Moreover, we went through some basic administration techniques of
Proxmox, including the creation of virtual machines, importing OpenVZ templates,
and viewing a guest system via the web console. Most importantly, we learned how
to distinguish KVM and OpenVZ, which affects our decision during VM creation,
for example, security versus performance.
In the next chapter, we are going to learn some concepts on high availability and the
introduction of the Proxmox cluster.


Where to buy this book
You can buy Proxmox High Availability from the Packt Publishing website:
.
Free shipping to the US, UK, Europe and selected Asian countries. For more information, please
read our shipping policy.
Alternatively, you can buy the book from Amazon, BN.com, Computer Manuals and
most internet book retailers.

www.PacktPub.com


Proxmox High Availability: Chapter No. 1 "Basic Concepts of A Proxmox Virtual Environment"

Uploaded by

Document Informationclick to expand document information

Copyright:

Available Formats

Proxmox High Availability: Chapter No. 1 "Basic Concepts of A Proxmox Virtual Environment"

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Proxmox High Availability: Chapter No. 1 "Basic Concepts of A Proxmox Virtual Environment"

Uploaded by

Copyright:

Available Formats

Proxmox High Availability

Simon M.C. Cheng

You might also like

Proxmox High Availability: Chapter No. 1 "Basic Concepts of A Proxmox Virtual Environment"

Uploaded by

Document Informationclick to expand document informationChapter No. 1 Basic Concepts of a Proxmox Virtual Environment Introduce, design, and implement high availability clusters using Proxmox

Document Informationclick to expand document information

Copyright:

Available Formats

Proxmox High Availability: Chapter No. 1 "Basic Concepts of A Proxmox Virtual Environment"

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Proxmox High Availability: Chapter No. 1 "Basic Concepts of A Proxmox Virtual Environment"

Uploaded by

Copyright:

Available Formats

Proxmox High Availability

Simon M.C. Cheng

You might also like