User Tools

Site Tools


computing:proxmux

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
computing:proxmux [2023/06/19 18:16] oemb1905computing:proxmux [2023/12/17 23:48] oemb1905
Line 19: Line 19:
  
   vzdump <vmID>   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: This will create a VM in .vma format. Then, you can extract the vma to a raw image as follows:
Line 36: Line 37:
   zfs destroy pool/dataset   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 [[https://pve.proxmox.com/wiki/Windows_10_guest_best_practices|Windows VMs]].+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 [[https://pve.proxmox.com/wiki/Windows_10_guest_best_practices|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'':
  
- --- //[[jonathan@haacksnetworking.org|oemb1905]] 2023/06/19 12:15//+  vms/vm-102-disk-0 
 +  vms/vm-102-disk-1 
 +  vms/vm-102-disk-2 
 +   
 +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. 
 + 
 + --- //[[jonathan@haacksnetworking.org|oemb1905]] 2023/06/19 17:40//