Virtual machine freeze after migration

[zemzema]

Hello all,

I recently configure PVE cluster version 7.3 consist of four nodes: two Supermicro servers and two Fujitsu servers.
When I try migration of virtual hosts from Supermicro nodes to Fujitsu nodes virtual hosts freeze after migration and gain processor usage to about 80%.
Migration from Fujitsu nodes to Supermicro nodes works well.

Before PVE version 7.3-3 I have installed version 6.2-4 on same hardware and migration in both direction worked fine.

Is there any solution for this issue?

Thanks.

 

[Moayad]

Can you share the VM config and the output of pveversion -v?

 

[zemzema]

Thanks . There are output of pvevresion and VM config.

root@host1:~# pveversion -v
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_ADDRESS = "sr_RS",
LC_NAME = "sr_RS",
LC_MONETARY = "sr_RS",
LC_PAPER = "sr_RS",
LC_IDENTIFICATION = "sr_RS",
LC_TELEPHONE = "sr_RS",
LC_MEASUREMENT = "sr_RS",
LC_NUMERIC = "sr_RS",
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
proxmox-ve: 7.3-1 (running kernel: 5.15.74-1-pve)
pve-manager: 7.3-3 (running version: 7.3-3/c3928077)
pve-kernel-5.15: 7.2-14
pve-kernel-helper: 7.2-14
pve-kernel-5.15.74-1-pve: 5.15.74-1
ceph-fuse: 15.2.17-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-8
libpve-guest-common-perl: 4.2-3
libpve-http-server-perl: 4.1-5
libpve-storage-perl: 7.2-12
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.7-1
proxmox-backup-file-restore: 2.2.7-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.3
pve-cluster: 7.3-1
pve-container: 4.4-2
pve-docs: 7.3-1
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-7
pve-firmware: 3.5-6
pve-ha-manager: 3.5.1
pve-i18n: 2.8-1
pve-qemu-kvm: 7.1.0-4
pve-xtermjs: 4.16.0-1
qemu-server: 7.3-1
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+2
vncterm: 1.7-1
zfsutils-linux: 2.1.6-pve1

root@host1:/etc/pve/qemu-server# cat 142.conf
agent: 1,fstrim_cloned_disks=1
balloon: 2048
bootdisk: scsi0
cores: 4
ide2: none,media=cdrom
memory: 8192
name: MintWS
net0: virtio=32:47:5C:91:EA:2E,bridge=vmbr2,tag=1001
numa: 0
onboot: 1
ostype: l26
scsi0: gluster-image:142/vm-142-disk-0.qcow2,size=32G
scsihw: virtio-scsi-pci
smbios1: uuid=9a0af4c5-8f50-47a4-a8a0-6f148e77f277
sockets: 1
vmgenid: 04db387e-4fc6-46be-b320-b950ee744be5


Best regards.

 

[Moayad]

Hi,

Thank you for the output!

Only the 142 VM has the issue with migration? I would check the "Requirements" from our official document [0]

[0] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#qm_migration