VM migration speed

[kellogs]

Dear All,

May I know if the following is acceptable migration speed for a VM 2TiB size and 2x10G interface?


Task viewer: VM 108 - Migrate

task started by HA resource agent
2024-06-11 19:14:30 use dedicated network address for sending migration traffic (172.16.200.42)
2024-06-11 19:14:30 starting migration of VM 108 to node 'compute-200-42' (172.16.200.42)
2024-06-11 19:14:30 starting VM 108 on remote node 'compute-200-42'
2024-06-11 19:14:33 start remote tunnel
2024-06-11 19:14:34 ssh tunnel ver 1
2024-06-11 19:14:34 starting online/live migration on unix:/run/qemu-server/108.migrate
2024-06-11 19:14:34 set migration capabilities
2024-06-11 19:14:34 migration downtime limit: 100 ms
2024-06-11 19:14:34 migration cachesize: 2.0 GiB
2024-06-11 19:14:34 set migration parameters
2024-06-11 19:14:34 start migrate command to unix:/run/qemu-server/108.migrate
2024-06-11 19:14:35 migration active, transferred 279.6 MiB of 16.0 GiB VM-state, 449.6 MiB/s
2024-06-11 19:14:36 migration active, transferred 683.1 MiB of 16.0 GiB VM-state, 504.9 MiB/s
2024-06-11 19:14:37 migration active, transferred 1.1 GiB of 16.0 GiB VM-state, 1.2 GiB/s
2024-06-11 19:14:38 migration active, transferred 1.2 GiB of 16.0 GiB VM-state, 9.2 GiB/s
2024-06-11 19:14:39 average migration speed: 3.2 GiB/s - downtime 76 ms
2024-06-11 19:14:39 migration status: completed
2024-06-11 19:14:44 migration finished successfully (duration 00:00:14)
TASK OK

 

[spirit]

you can disable ssh encryption by editing

/etc/pve/datacenter.cfg

migration: insecure

 

[justinclift]

@kellogs Be careful with that. If you tell Proxmox to do insecure migrations, then it opens raw tcp connections between the hosts to transfer the VM memory.

That means a completely unencrypted copy of the VM memory goes over the wire, so in a hostile network environment it could go very badly.

If this is just on an internal home network or similar though, it'll be fine. And it does speed up migrations.