User Tools

Site Tools



  • proxmux
  • Jonathan Haack
  • Haack's Networking


Been testing proxmux on home back up server. The server is my old production SuperMicro, which is now used for offsite backups in the home office. I have two 6TB drives in a zfs mirror for vm spinning (no spare), and the other 6x 6TBs are in 3 two-way mirrors for actual production backups. I am using the Debian underbelly with the 3 two-way mirrors to run my normal rsnapshot version control scripts, etc., while I use one pool for testing proxmux functionality. So far everything is working fine, and it's fun to use. Until I am offering advanced business / small enterprise support though, there's not really a need for the tools. But/and, that's not the purpose - the purpose is testing for now for a later date. The first thing I tested was how to bring in an existing virtual machine. To do that, create a machine in the GUI with no OS, and a trivial small HD size. Make sure the other resources match what you need for the VM. Then, run these commands on the command line within the proxmux host:

qm importdisk 500 <dataset>
qm set 500 --scsi0 vms:vm-500-disk-0

These commands bring in the image block by block, and then re-assign the virtual disk that VM 500 uses to the image you just brought in, instead of the placeholder image you created in the GUI during the step prior. In order to export a VM at the command line, execute:

vzdump <vmID>
vzdump <vmID> --dumpdir /mnt/backups/machines/pve-images/<vmname>

This will create a VM in .vma format. Then, you can extract the vma to a raw image as follows:

vma extract /var/lib/vz/dump/vzdump-qemu-101-2023_06_18-12_17_40.vma /mnt/backups/vma-extract

Optionallly, you can use the python tool I don't see any value in using this, however, as it is much slower than the native tool and is also just in raw format. Example syntax is:

python3 vzdump-qemu-101-2023_06_18-12_17_40.vma /mnt/backups/vma

In order to see where the virtual machine's zdevs are, run the following:

zfs list

To delete one (be careful), use the following

zfs destroy pool/dataset

I've migrated my Windows VM here for testing to avoid cumbersome EFI/TPM setup on virt-manager. Here's a page from ProxMux wiki on best practices for Windows VMs. Once thing I noticed when doing the Windows install is that PVE makes two more vdevs for the TPM / EFI, so you get something like the following in zfs list:


Be careful not to delete those thinking wrongly that they are extraneous - those are obviously required for booting, but it might not be clear upon first look. Also, I chose to install those on the zpool and PVE's default was to store those locally - so they will likely not appear if you did not pick the option to store them on the pool.

oemb1905 2023/06/19 17:40

computing/proxmux.txt · Last modified: 2023/06/19 23:41 by oemb1905