Cant migrate AARCH64 VM

[sysadminfromhell]

I´m using a 2 Node Proxmox Cluster.
The VM is a AARCH64 VM which i tried to migrate to the other node for a restart after an Update from the system.

I got this error:

Can't use an undefined value as an ARRAY reference at /usr/share/perl5/PVE/QemuServer.pm line 3268.

If I cut the "arch: aarch64" from the config its working but the VM doesnt boot anymore because its installed in aarch64.
Is there a way to fix this?

Kind regards,

 

[oguz]

hi,

could you post the full tasklog from the migration and your pveversion -v output from both nodes?

 

[sysadminfromhell]

sure, here u go:

root@Node01:~# pveversion -v
proxmox-ve: 7.1-1 (running kernel: 5.10.83-1-pve)
pve-manager: 7.1-8 (running version: 7.1-8/7cd00e36)
pve-kernel-libc-dev: 5.10.95-1
pve-kernel-5.10.83-1-pve: 5.10.83-4
ceph-fuse: 16.2.7
corosync: 3.1.5-pve2
criu: 3.15-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
ksmtuned: 4.20150326
libjs-extjs: 7.0.0-1
libknet1: 1.20-4
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.1-1
libpve-access-control: 7.1-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-14
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.0-4
libpve-storage-perl: 7.0-15
libqb0: not correctly installed
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.7-1
novnc-pve: 1.2.0-2
proxmox-backup-client: 2.1.2-1
proxmox-backup-file-restore: 2.1.2-1
proxmox-mini-journalreader: 1.3-1rpve1
proxmox-widget-toolkit: 3.4-4
pve-cluster: 7.1-3
pve-container: 4.1-3
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-ha-manager: 3.3-1
pve-i18n: 2.6-2
pve-qemu-kvm: 6.0.0-4
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-4rpve1
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.3-9

root@Node02:~# pveversion -v
proxmox-ve: 7.1-1 (running kernel: 5.15.19-2-pve)
pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)
pve-kernel-helper: 7.1-12
pve-kernel-5.15: 7.1-11
pve-kernel-5.13: 7.1-7
pve-kernel-5.15.19-2-pve: 5.15.19-2
pve-kernel-5.15.19-1-pve: 5.15.19-1
pve-kernel-5.13.19-4-pve: 5.13.19-9
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
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.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-6
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-3
libpve-guest-common-perl: 4.1-1
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.1-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-2
proxmox-backup-client: 2.1.5-1
proxmox-backup-file-restore: 2.1.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-6
pve-cluster: 7.1-3
pve-container: 4.1-4
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-5
pve-ha-manager: 3.3-3
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.1-2
pve-xtermjs: 4.16.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.2-pve1

2022-02-24 16:14:42 starting migration of VM 201 to node 'Node02' (172.16.24.100)
2022-02-24 16:14:42 starting VM 201 on remote node 'Node02'
2022-02-24 16:14:43 [Node02] Can't use an undefined value as an ARRAY reference at /usr/share/perl5/PVE/QemuServer.pm line 3268.
2022-02-24 16:14:43 ERROR: online migrate failure - remote command failed with exit code 255
2022-02-24 16:14:43 aborting phase 2 - cleanup resources
2022-02-24 16:14:43 migrate_cancel
2022-02-24 16:14:44 ERROR: migration finished with problems (duration 00:00:02)
TASK ERROR: migration problems

 

[oguz]

thanks, from the outputs it looks like your servers are using different versions for some important packages (which can affect migration, like pve-qemu, qemu-server and kernel versions), that's most likely the reason it's failing.

if the uptime for that VM is irrelevant i'd suggest you to upgrade both nodes to the same levels (though i know that you're migrating because of the upgrade of the other node).

you could upgrading the select packages on the node01 before retrying the migration to node02:

apt update
apt install pve-qemu qemu-server