Question about VM migration when using local zfs

macleod

Well-Known Member
Aug 3, 2017
66
8
48
46
Hello!
Two migration scenarios, source and destination servers are using local zfs storage, let's call it local-zfs.
1st scenario (with preparing):
1. set replication to destination, schedule manual replication, wait until completed - only used space is copied
2. migrate - will copy disk delta, memory etc
3. delete replication (cleanup)
!!! only actual used space are copied !!!
2nd scenario (direct migration):
- space allocation (thin storage will become think, fortunately zfs is smart enough to not allocate zeroed blocks)
- whole disk copy (zfs is smart also in this step, but whole disk seems to be network transferred)
- copy memory etc.
!!! whole disk is copied, and as anyone know using lvm is far worse, because on destination thin will become think, and a guest trim is needed !!!
It is clear that for a sparse VM scenario 1 is far superior (in duration and network transfer), but why the default migration operation cannot detect the fact that source/destination is zfs and optimize the operation ?
 
Hello,

because one of the main development goals is to keep things general.
This way you reduce the codebase and the possibility of errors.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!