Re: [pve-devel] [PATCH v2 qemu-server] fix #4501: TCP migration: start vm: move port reservation and usage closer together

2023-12-27 Thread Hannes Dürr
I live-migrated 300 vms with: migration: insecure max_workers: 30 and 10 parallel workers (as described here https://forum.proxmox.com/threads/live-migration.127355/#post-557181) Had zero issues with the patch applied, without the patch i had ~30 errors Tested-by: Hannes Duerr On 12/20/23

Re: [pve-devel] [PATCH v2 qemu-server] fix #4501: TCP migration: start vm: move port reservation and usage closer together

2023-12-20 Thread Thomas Lamprecht
On 19/12/2023 14:44, Fiona Ebner wrote: > Currently, volume activation, PCI reservation and resetting systemd > scope happen in between, so the 5 second expiretime used for port > reservation is not always enough. > > It's possible to defer telling QEMU where it should listen for > migration and

[pve-devel] [PATCH v2 qemu-server] fix #4501: TCP migration: start vm: move port reservation and usage closer together

2023-12-19 Thread Fiona Ebner
Currently, volume activation, PCI reservation and resetting systemd scope happen in between, so the 5 second expiretime used for port reservation is not always enough. It's possible to defer telling QEMU where it should listen for migration and do so after it has been started via QMP. Therefore,