Moving lvm-thin volumes on proxmox between vm-s or ct-s

it’s pretty straight forward following this official howto:

lvs shows you all volumes in their volume group (in my case ‘ssd’)

LV               VG  Attr       LSize    Pool   Origin Data%  Meta%  Move Log Cpy%Sync Convert
data             pve twi-a-tz--   32.12g               0.00   1.58                            
root             pve -wi-ao----   16.75g                                                      
swap             pve -wi-ao----    8.00g                                                      
guests           ssd twi-aotz--   <2.33t               74.93  45.51                           
vm-100-disk-0    ssd Vwi-a-tz--   12.00g guests        72.69                                  
vm-101-disk-0    ssd Vwi-a-tz--   12.00g guests        85.22                                  
vm-101-disk-1    ssd Vwi-a-tz--   50.00g guests        99.95                                  
vm-102-disk-0    ssd Vwi-a-tz--   12.00g guests        97.57                                  
vm-102-disk-1    ssd Vwi-a-tz--   50.00g guests        64.54                                  
vm-103-disk-0    ssd Vwi-a-tz--   12.00g guests        74.37                                  
vm-103-disk-1    ssd Vwi-a-tz--  150.00g guests        52.42                                  
vm-104-disk-0    ssd Vwi-a-tz--   12.00g guests        90.74                                  
vm-104-disk-1    ssd Vwi-a-tz--   10.00g guests        95.27                                  
vm-105-disk-0    ssd Vwi-a-tz--   12.00g guests        55.79                                  
vm-105-disk-1    ssd Vwi-a-tz--   10.00g guests        32.89                                  
vm-106-disk-0    ssd Vwi-a-tz--   12.00g guests        77.78                                  
vm-106-disk-1    ssd Vwi-a-tz--   10.00g guests        99.82                                  
vm-107-disk-0    ssd Vwi-a-tz--   32.00g guests        0.00                                   
vm-107-disk-1    ssd Vwi-a-tz--  500.00g guests        95.41                                  
vm-108-disk-0    ssd Vwi-aotz--    8.00g guests        43.73                                  
vm-109-disk-0    ssd Vwi-a-tz--   12.00g guests        52.41                                  
vm-109-disk-1    ssd Vwi-a-tz--   50.00g guests        2.22                                   
vm-110-disk-0    ssd Vwi-a-tz--   12.00g guests        51.14                                  
vm-110-disk-1    ssd Vwi-a-tz--   50.00g guests        2.22                                   
vm-111-disk-0    ssd Vwi-a-tz--   12.00g guests        84.85                                  
vm-111-disk-1    ssd Vwi-a-tz--  100.00g guests        16.97                                  
vm-112-disk-0    ssd Vwi-a-tz--    8.00g guests        13.53                                  
vm-113-disk-0    ssd Vwi-a-tz--    8.00g guests        11.55                                  
vm-114-disk-0    ssd Vwi-a-tz--   16.00g guests        84.31                                  
vm-115-disk-0    ssd Vwi-a-tz--   16.00g guests        97.12                                  
vm-116-disk-0    ssd Vwi-a-tz--    8.00g guests        31.49                                  
vm-117-cloudinit ssd Vwi-aotz--    4.00m guests        50.00                                  
vm-117-disk-0    ssd Vwi-aotz--   10.00g guests        39.71                                  
vm-117-disk-1    ssd Vwi-aotz-- 1000.00g guests        97.47     

If the id of the new ct or vm is not equal to the id of the volume’s previous attachment, rename them, i.e.

lvrename ssd/vm-101-disk-1 ssd/vm-117-disk-2

this will make vm-101-disk-1 available as vm-117-disk-2, you have to increase the count in the end of the name.

then edit the config of the actual vm.

take the line from /etc/pve/qemu-server/<vm id>.conf that describes the volume to the new <vm id>.conf

the tricky thing was to run qm rescan afterwards which fixed syntax and made the volume appear in the web gui where i could finally attache it to the new vm.