Cerca


stampa pdf
Proxmox


DESCRIPTION

Proxmox is a virtualisation distribution which offers you the possibility to
administrate virtual Servers (VPS) using parallel OpenVZ and Linux KVM
technologies. Administration is made easy via the web interface with just a few
clicks. Please log in to the interface at the addresshttps://votreserveur.ovh.net with your login/root password.

The 2 virtualisation technology: OpenVZ and KVM Linux are different with regards to the virtualisation point and therefore with regards to the performance too. Proxmox enables you to have VPS using these 2 technology at the same time.

Isolating with OpenVZ


OpenVZ uses very powerful isolation. Each VE (Virtual Environment) has its own network card and other material, and can use a different distribution. However, it is not possible to install other operating systems other than Linux (Windows, *BSD, ...) or different kernels in the VE.

As OpenVZ virtual environments are very powerful, it is recommended to use this virtualisation method with Linux KVM. On installation you have available a number of templates (Linux distributions prepared by OVH for the use in OpenVZ VE) that you can use when you create a VPS through the web interface. This will enable you to start the 1st VPS in just 3 clicks and less than 2 minutes after the installation of your server with Proxmox!

Virtualisation with Linux Kernel Virtual Machine (Linux KVM)


Linux KVM offers "full virtualisation" and requires a CPU with virtualisation technology
(VMX). It permits you to install any OS using an .iso file created with an installation CD. Place the .iso files in the folder /var/lib/vz/template/iso/ on
the server to use them via the web interface.

Virtual networks with Proxmox
Just as a real network can be complicated, so also can virtual networks.
Moreover it isn't possible to check a network cable or other equipement to
verify what's happening inside. Here's a few details that can help you understand how Proxmox works.

Network - OpenVZ

The easiest way to put a VE (virtual environment) on a network, is to use the IP block
available with EG/MG/HG or IP failover. In this case OpenVZ will take care of the routing configuration. On the server you can verify the allowed IPs using `ip
route show`, to what VE should appear and be routed to the venetX interface, eg.
.venet0.. To do this choose Network Type .Virtual Network (venet) when creating
it (and not .veth.).

Network - Linux KVM

Linux KVM creates "complete" virtualisations. We're going to create a complete virtual network of VPSs, including network adapter equivalents, bandwidth
and switch.

- switch: bridge "vmbr1"
- interfaces: eth0, tap1, ...
- Connexion is established when the KVM instance starts, and adds tapX interfacesto the bridge.

All data entered in the tap0 interface, comes out from the other side: eth0 of KVM instance. And all that comes out from the KVM instance, comes out from eth0 interface.

It's sufficient to direct (=route) KVM traffic instances
to the vmbr1 bridge without an IP address (see scheme below)

In this way, MAC addresses attributed to TAP interfaces won't come out of the server, because all trafic is routed to eth0.





How to prepare a virtual network with Linux KVM

To start with, choose Network Type "Bridged Ethernet (tap)". Next we have to do a few operations manually:

On the host:
# ip route add YOUR_IP_FAILOVER dev vmbr1


On the guest, if it's Linux:
# ifconfig eth0 YOUR_IP_FAILOVER/32 up # configure interface
# ip route add default dev eth0 # add default route
# echo "nameserver 213.186.33.99" > /etc/resolv.conf # configure DNS^

If it's a different OS (Windows, *BSD, ...), we have to change the commands to have the same effect.

Commands to use with Windows OS:
  • configure windows with IP failover. Netmask (255.255.255.255) won't be accepted, so put temporarly "255.255.255.0"
  • change netmask with registry editor to avoid problems in the future:
    • click on "start" - > "execute"
    • write "regedit" and confirm
    • search in HKEY_LOCAL_MACHINE\SYSTEM\ key "SubnetMask" with "255.255.255.0" value and change it to "255.255.255.255"

NB: In the current version, there's a known bug, connu, KVM instances don't reeceive unique MAC address. You have to change it with the second virtual KVM server, and it can be done in the configuration file /etc/qemu-server/NNN.conf, NNN being VPS number, and add "macaddr=52:54:00:12:xx:xx" in "network" line. Eg, replace xx:xx with your VPS number to avoid double allocation.


In order to receive more information about VPS installation, please go to the Proxmox site, In case you have any problems or questions, please subscribe to the mailing list dedicated to VPS, vps@ml.ovh.net, sending an empty message to vps-subscribe@ml.ovh.net (although it's in French).