Installation: Tips and Tricks
- 1 Install Proxmox VE server
- 2 Get Appliance Templates
- 3 Optional: Reverting Thin-LVM to "old" Behavior of /var/lib/vz (Proxmox 4.2 and later)
Install Proxmox VE server
Optional: Install Proxmox VE on Debian 6 Squeeze (64 bit)
Optional: Install Proxmox VE on Debian 7 Wheezy (64 bit)
EOL April 2016
Optional: Install Proxmox VE on Debian 8 Jessie (64 bit)
This page will cover the install of X11 and a basic Desktop on top of Proxmox. Optional:_Linux_Mint_Mate_Desktop is also available.
Optional: Install Proxmox VE over iSCSI
Get Appliance Templates
Just go to your content tab of your storage (e.g. "local") and download pre-built Virtual Appliances directly to your server. This list is maintained by the Proxmox VE 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.
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.
Optional: Reverting Thin-LVM to "old" Behavior of
/var/lib/vz (Proxmox 4.2 and later)
If you installed Proxmox 4.2 (or later), you see yourself confronted with a changed layout of your data. There is no mounted
/var/lib/vz LVM volume anymore, instead you find a thin-provisioned volume. This is technically the right choice, but one sometimes want to get the old behavior back, which is described here. This section describes the steps to revert to the "old" layout on a freshly installed Proxmox 4.2:
- After the Installation your storage configuration in
/etc/pve/storage.cfgwill look like this:
dir: local path /var/lib/vz content iso,vztmpl,backup lvmthin: local-lvm thinpool data vgname pve content rootdir,images
- You can delete the thin-volume via GUI or manually and have to set the local directory to store images and container aswell. You should have such a config in the end:
dir: local path /var/lib/vz maxfiles 0 content backup,iso,vztmpl,rootdir,images
- Now you need to recreate
root@pve-42 ~ > lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert data pve twi-a-tz-- 16.38g 0.00 0.49 root pve -wi-ao---- 7.75g swap pve -wi-ao---- 3.88g root@pve-42 ~ > lvremove pve/data Do you really want to remove active logical volume data? [y/n]: y Logical volume "data" successfully removed root@pve-42 ~ > lvcreate --name data -l +100%FREE pve Logical volume "data" created. root@pve-42 ~ > mkfs.ext4 /dev/pve/data mke2fs 1.42.12 (29-Aug-2014) Discarding device blocks: done Creating filesystem with 5307392 4k blocks and 1327104 inodes Filesystem UUID: 310d346a-de4e-48ae-83d0-4119088af2e3 Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000 Allocating group tables: done Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done
- Then add the new volume in your
/dev/pve/data /var/lib/vz ext4 defaults 0 1
- Restart to check if everything survives a reboot.
You should end up with a working "old-style" configuration where you "see" your files as it was before Proxmox 4.2