KVM & OpenVZ Virtualization And Cloud Computing With Proxmox VE - Page 3

5 Creating OpenVZ Containers

To create an OpenVZ container, go to Virtual Machines > Create...

... and fill in the form. Select Container (OpenVZ) and then the template that you want to use. Specify a hostname (e.g. vm1.example.com), the amount of memory and swap, a root password, select Virtual Network (venet) and specify an IP address for the container (e.g., fill in a VMID, select a cluster node (if you haven't created a cluster (see chapter 3), you can select only the master, not any remote systems), specify if the container should automatically be started when the host boots, and fill in one or two DNS servers (e.g. and Then click on create:

The container is then created...

... and it should be listed on the List tab afterwards. The container is stoppped; to start it, click on the container:

This will open a page where you can control that container. To start it, click on the Start button:

You should then see the link Open VNC console - if you click on it...

... a browser-based console opens from where you can control the virtual machine (this is especially useful for desktop machines; if the virtual machine is a server, you can as well connect to it using SSH (e.g. with PuTTY)).


6 Creating Virtual Machines On Remote Systems In The Cluster

If you've created a cluster (see chapter 3), you can also create virtual machines on remote systems that belong to the cluster - just select a remote node under Cluster Node when you create a virtual machine (the screenshot shows this for OpenVZ, however, this works for KVM guests as well as long as the node supports hardware virtualization):

The List tab should then show that the virtual machine is running on a different node:


7 Creating KVM Guests

If the CPU supports hardware virtualization (Intel VT or AMD-V), you have the possibility to create KVM guests in addition to OpenVZ containers. Just select Fully virtualized (KVM) in the Type drop-down menu, and then either select the cdrom device or one of the ISO images that you've uploaded (if any) from the Installation Media drop-down menu. There are no network settings to be set as this will have to be done directly in the KVM guest. Make sure you select the correct Guest Type (Linux 2.6, Windows XP, etc.):

The KVM guest should be listed on the List tab afterwards; as always with new guests, it is stopped. Click on it...

... to get to its management page; click on the Start button there (if you've selected to install the guest from CD-ROM, please insert the OS CD or DVD into the target system's CD drive before you click on Start):

Then click on the Open VNC console link...

... to connect ot the graphical console of the guest; you should now be able to complete the OS installation just as if it was a physical system:

Share this page:

5 Comment(s)

Add comment


From: Anonymous at: 2009-04-08 19:32:48

Use: pveam update from the command line on your proxmox host.


From: at: 2009-03-08 18:33:38


To update the dead links from the 404 when downloading virtual appliances just run 'pveam update' in a shell on the host. Worked for me.

Proxmox forum reference: http://proxmox.com/forum/showthread.php?p=5730

From: pille at: 2009-11-25 09:30:58

for version 1.4 of PVE there's a port for 32bit-CPUs. obviously those CPUs don't support KVM, but at least you can run OpenVZ-containers on your old hosts and join them in the cluster. http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Lenny_on_32-Bit_Processor

From: Anonymous at: 2010-04-30 02:06:10

This is not cloud computing...

From: Anonymous at: 2010-12-13 06:09:57


This only multiple node and couldn't be failover, so when master node is down slave node can't take over the job.

 May be drbd and HA should be solution for replicate failover.