Installation
Introduction
Proxmox VE installs the complete operating system and management tools in 3 to 5 minutes (depends on the used hardware).
Including the following:
- Complete operating system (Debian Lenny 64)
- Partition the hard drive with LVM2
- Proxmox VE Kernel with OpenVZ and KVM support
- Backup/Restore tools
- Web based management interface
Please note, the complete server is used and all existing data is removed.
Video tutorials
List of all tutorials: Video Tutorials
Proxmox VE installation
- Proxmox VE installation (Video)
- ProxMox VE Install from USB - Courtesy Griffon's IT Library
- Falko Timme Proxmox VE Installation Walk Thru'
- Debugging Installation
- Post Install Migration of KVMs
Screen cast video demo of container installation
Note: These external videos are based on a beta version of Proxmox VE
System requirements
For production servers, high quality server equipment is needed. Keep in mind, if you run 10 Virtual Servers on one machine and you got a hardware failure, 10 services are lost. Proxmox VE supports clustering, means that multiple Proxmox VE installations can centrally managed via the included cluster functionality.
Proxmox VE can use local storage (DAS) and SAN. For details see Storage_Model
Minimum requirements for evaluation:
- CPU: 64bit (Intel EMT64 or AMD64), Intel VT/AMD-V capable CPU/Mainboard (for KVM Full Virtualization support)
- Minimum 1 GB RAM
- Hard drive
- One NIC
Recommended system requirements:
- CPU: 64bit (Intel EMT64 or AMD64), Multi core CPU recommended, Intel VT/AMD-V capable CPU/Mainboard (for KVM Full Virtualization support)
- 4 GB is good, more is better
- Hardware RAID with batteries protected write cache (BBU)
- Fast hard drives, best results with 15k rpm SAS, Raid10
- Two NIC
Certified hardware
Basically you can use all hardware supporting Debian Lenny 64 bit. If you are unsure, just pick one of these:
Steps to get your Proxmox VE up and running
Install Proxmox VE server
- Download ISO image and burn it on a CD (see Downloads)
- Network lead plugged into eth0 (usually NIC 1) otherwise your newly installed Proxmox VE server's network won't work
- Boot from CD and start the automatic installer on your dedicated hardware
- Follow the instructions on the screen
- LogIn via SSH and make sure you're up-to-date:
aptitude update && aptitude upgrade
Note: In case your hardware fails to install the Proxmox VE v1.5, (eg., some Intel Atom Boards) then install v1.4 and upgrade to v1.5. The same applies to the Gigabyte EP45-UD3L mainboard even with BIOS FW F9 when ProxMox v1.8 cannot be installed.
Note: Upgrading from Proxmox VE 1.4 to v1.8 during aptitude safe-upgrade can result in the following:
The following packages have unmet dependencies: stomp.py: Depends: python-support (>= 0.90.0) but it is not installable
It can be alleviated with:
aptitude install python-support aptitude safe-upgrade
Proxmox VE installation (Video)
Optional: Install Proxmox VE on existing Debian Lenny (64 bit)
See Install Proxmox VE on Debian Lenny
Optional: Install Proxmox VE on existing Debian Lenny (32 bit)
See Install Proxmox VE on Debian Lenny on 32-Bit Processor (Unofficial)
Optional: Install Proxmox VE over iSCSI
See Proxmox ISCSI installation
Proxmox VE web interface
Configuration is done via web interface, just point your browser to the given IP address during installation (https://youripaddress). Please make sure that your browser has sun-java6-plugin installed (GCJ for Firefox does not work yet. If you use OpenJDK instead, Firefox works well with icedtea6-plugin) as this is used for console view. Proxmox VE is tested for IE7/IE8, Firefox 2.x and 3.x. Its also known to work on all Webkit based browsers (safari, google chrome) and Opera.
Default login is "root" and the root password is defined during the installation process.
Configure basic system setting
Please review the following settings, see "Configuration/System":
- Network
- DNS
- Time settings
- Options: language (for the management web interface)
- Options: set the keyboard layout (needed by VNC clients)
Get Appliance Templates
Download
Just go to "Appliance Templates" and download pre-built Virtual Appliances directly to your server. This list is maintained by the Proxmox team and more and more Appliances will be available. This is the easiest way and a good place to start.
If you have a NFS server you can use a NFS share for storing ISO images. To start, configure the NFS ISO store on the web interface (Configuration/Storage).
Upload from your desktop
If you already got Virtually Appliances you can upload them via the upload button. To install a virtual machine from an ISO image (using KVM full virtualization) just upload the ISO file via the upload button (limited to 2 GB).
Directly to file system
Templates and ISO images are stored on the Proxmox VE server (see /var/lib/vz/template/cache for openvz templates and /var/lib/vz/template/iso for ISO images). You can also transfer templates and ISO images via secure copy (scp) to these directories. If you work on a windows desktop, you can use a graphical scp client like winscp.
Create Virtual Machines
Container (OpenVZ) Virtual Machines - Default
Go to "VM Manager/Virtual Machines - Create":
Configuration:
- Type: select "Container (OpenVZ)"
- Template: select "proxmox-mailgateway" (or whatever you want)
- Hostname: give a unique server name
- Memory (MB): default 512 MB
- Swap (MB): default 512 MB (in version 1.x the swap memory setting is added to the RAM memory due to lacking Kernel support: in future version this will change)
- Password: set the root password
- VMID: just use the given ID or overwrite the suggested one
- Cluster Node: If you have several Proxmox VE servers, select the node where you want to create the new virtual machine
- Start at boot: tick this if you want the Virtual Machine started on reboot of the Proxmox VE server
- Disk space (GB): default value 8 GB - please note you can change this later without reboot or modifications within the Virtual Appliance (very cool).
Network:
- Network Type: default Virtual Network (venet) - in only some case you need Bridged Ethernet(veth) (see Differences_between_venet_and_veth on OpenVZ wiki for details)
- IP Address: give a unique IP (if you select Brigded Ethernet, the IP configuration has to be done in the Virtual Machine)
- DNS Domain: e.g. yourdomain.com
- First/Second DNS Servers: enter DNS servers
Now review your settings and create your first Virtual Machine. After you clicked "Create", all settings are applied - wait for completion (this process can take between a view seconds and up to a minute, depends on the used template and your hardware). Now, go to "VM Manager/Virtual Machines - List" to see the newly created Virtual Machine.
Video Tutorials
Fully virtualized Machines (KVM)
Go to "VM Manager/Virtual Machines - Create":
Configuration:
- Type: select "Fully virtualized (KVM)"
- Installation Media: select "cdrom device" (from the Proxmox VE server, or a previously uploaded ISO image)
- Name: give a unique name
- Disk space (GB): specify the size of the disk - will not pre-allocated - give enough as changing later is not possible without command line interactions and guest specific issues
- Memory (MB): specify memory as you would give on physical hardware (SWAP is handled within the guest)
- VMID: just use the given ID or overwrite the suggested one, start with (101 and higher)
- Cluster Node: If you have several Proxmox VE servers, select the node where you want to create the new virtual machine
- Start at boot: tick this if you want the Virtual Machine started on reboot of the Proxmox VE server
- Disk type: select IDE for windows guests, (optional VIRTIO, especially for Linux guests. For Windows you need an additional VIRTIO driver ISO image)
- Guest Type: select what you need (32 and 64 bit guests are possible)
Network:
- Network Type: Bridged Ethernet(tap)
- Bridge: select one (default only one is configured)
- Network Card: select the emulated hardware - rtl8139 is default (if you have VIRTIO drivers in your guest, use VIRTIO)
Now review your settings and create your first Virtual Machine. After you clicked "Create", all settings are applied - wait for completion. Now, go to "VM Manager/Virtual Machines - List" to see the newly created Virtual Machine.
Video Tutorials
Managing Virtual Machines
Go to "VM Manager/Virtual Machines" to see a list of your Virtual Machines.
Basic tasks can be done by clicking on the red arrow - drop down menu:
- start, restart, shutdown, stop
- migrate: migrate a Virtual Machine to another physical host (you need at least two Proxmox VE servers - see Proxmox VE Cluster
- console: using the VNC console for container virtualization automatically logs in via root. For managing KVM Virtual Machine, the console shows the screen of the full virtualized machine)
For a detailed view and configuration changes just click on a Virtual Machine row in the list of VMs.
"Logs" on a container Virtual Machine:
- Boot/Init: shows the Boot/Init logs generated during start or stop
- Command: see the current/last executed task
- Syslog: see the real time syslog of the Virtual Machine
Networking and Firewall
A detail guide on how to virtualize your VPS network infrastructure. [3]
On adding a second network card and enabling it on the Configuration -> System -> vmbr0 page and choosing the eth1 card as the the bridged interface, the /etc/network/interfaces file will look like:
# network interface settings
auto lo
iface lo inet loopback
iface eth0 inet manual
iface eth1 inet manual
auto vmbr0
iface vmbr0 inet static
address 192.168.1.100
netmask 255.255.255.0
gateway 192.168.1.1
bridge_ports eth1
bridge_stp off
bridge_fd 0
The D-Link DGE-530T Gigabit PCI Desktop Adapter is detected with e1000e Intel(R) PRO/1000 Network Driver during modprobe while bootup and works well. This card is one of a few that comes with a half height low profile bracket as well.