Massive VM freeze


May 16, 2022
When migrating from one host to another VM, there was a massive freeze of VMs that were already on the target node.

Config of the VM that migrated
agent: 1
boot: order=virtio0
cores: 5
hotplug: disk,network,usb,memory,cpu
machine: pc-q35-7.2
memory: 20480
meta: creation-qemu=7.2.0,ctime=1692943651
name: VM138
net0: virtio=45:1C:28:D2:E9:B:,bridge=vmbr0,firewall=1,tag=464
numa: 1
onboot: 1
ostype: win10
scsihw: virtio-scsi-single
smbios1: uuid=0de9fd08-2ccf-4105-b0c0-fcee1ef66d92
sockets: 1
virtio0: disk2:vm-138-disk-0,cache=writeback,iothread=1,size=75G
virtio1: disk2:vm-138-disk-1,backup=0,cache=writeback,iothread=1,size=40G
virtio2: disk2:vm-138-disk-2,backup=0,cache=writeback,iothread=1,size=10G
virtio3: disk2:vm-138-disk-3,cache=writeback,iothread=1,size=10G
vmgenid: 57d99bd2-174b-437f-a723-2aabfe4f8349

Node sender
CPU(s) 32 x Intel(R) Xeon(R) Gold 6134 CPU @ 3.20GHz (2 Sockets)
Kernel Version Linux 5.15.107-2-pve #1 SMP PVE 5.15.107-2 (2023-05-10T09:10Z)
PVE Manager Version pve-manager/7.4-4/4a8501a8

Receiver node
CPU(s) 48 x Intel(R) Xeon(R) Gold 6146 CPU @ 3.20GHz (2 Sockets)
Kernel Version Linux 5.15.116-1-pve #1 SMP PVE 5.15.116-1 (2023-08-29T13:46Z)
PVE Manager Version pve-manager/7.4-16/0f39f621
Can you provide the journal of the target node from that time?
Did you see any error messages on the hanging guests via VNC?


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!