Installed qemu-server (max feature level for 5.0 is pve0) is too old to run machine type 'pc-i440fx-5.0+pve1'

[alebeta]

Hi all,

since updated to pve 6.2 I get error when trying to migrate VMs

Installed qemu-server (max feature level for 5.0 is pve0) is too old to run machine type 'pc-i440fx-5.0+pve1'

When I check package version among all the nodes, they are in the same version. Why it could be happening?

thanks

 

[Stefan_R]

'pc-i440fx-5.0+pve1' is not a feature level currently in use anywhere... Can you post your VM config (/etc/pve/qemu-server/<vmid>.conf) as well as the output of 'pveversion -v' on both nodes?

Note that the feature level for a running VM is only set on startup, so if you ran into some kind of bug it might be enough to just reboot the VM after making sure both nodes are fully up-to-date.

 

[alebeta]

'pc-i440fx-5.0+pve1' is not a feature level currently in use anywhere... Can you post your VM config (/etc/pve/qemu-server/<vmid>.conf) as well as the output of 'pveversion -v' on both nodes?

Note that the feature level for a running VM is only set on startup, so if you ran into some kind of bug it might be enough to just reboot the VM after making sure both nodes are fully up-to-date.

Hi Stefan,

thanks for the message, the problem dissapear after rebooting the node. I could not collect more useful data. If I have the same problem in the future I will write here and provide more information.

thanks for the help

 

[Leah]

I have nearly the same problem now. I can't migrate a VM from a node running 6.2-10 (node7) to a node running 6.1-8 (node13). Same error message: TASK ERROR: Installed QEMU version '4.1.1' is too old to run machine type 'pc-i440fx-5.0+pve0', please upgrade node 'node13'

Upgrading node13 is for now not the perfect solution because we debug another problem with proxmox that causes the fencing to reboot nodes without a reason and we just need to rebalance because of load problems.

pveversion -v node7

proxmox-ve: 6.2-1 (running kernel: 5.4.44-2-pve)
pve-manager: 6.2-10 (running version: 6.2-10/a20769ed)
pve-kernel-5.4: 6.2-4
pve-kernel-helper: 6.2-4
pve-kernel-5.3: 6.1-6
pve-kernel-5.0: 6.0-11
pve-kernel-5.4.44-2-pve: 5.4.44-2
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.18-1-pve: 5.3.18-1
pve-kernel-5.0.21-5-pve: 5.0.21-10
ceph: 14.2.9-pve1
ceph-fuse: 14.2.9-pve1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.4
libpve-access-control: 6.1-2
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-5
libpve-guest-common-perl: 3.1-1
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.2-5
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-9
pve-cluster: 6.1-8
pve-container: 3.1-12
pve-docs: 6.2-5
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-3
pve-qemu-kvm: 5.0.0-11
pve-xtermjs: 4.3.0-1
qemu-server: 6.2-11
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.4-pve1

pveversion -v node13

proxmox-ve: 6.1-2 (running kernel: 5.3.18-3-pve)
pve-manager: 6.1-8 (running version: 6.1-8/806edfe1)
pve-kernel-helper: 6.1-8
pve-kernel-5.3: 6.1-6
pve-kernel-5.3.18-3-pve: 5.3.18-3
ceph: 14.2.9-pve1
ceph-fuse: 14.2.9-pve1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libpve-access-control: 6.0-6
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.0-17
libpve-guest-common-perl: 3.0-5
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-5
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-3
lxc-pve: 3.2.1-1
lxcfs: 4.0.1-pve1
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-3
pve-cluster: 6.1-4
pve-container: 3.0-23
pve-docs: 6.1-6
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.0-10
pve-firmware: 3.0-7
pve-ha-manager: 3.0-9
pve-i18n: 2.0-4
pve-qemu-kvm: 4.1.1-4
pve-xtermjs: 4.3.0-1
qemu-server: 6.1-7
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1

VM config:

root@node7:~# cat /etc/pve/qemu-server/158.conf
agent: 1
bootdisk: scsi0
cores: 20
memory: 26624
name: srv.example.com
net0: virtio=5A:BC:CC:ff:ff:ff,bridge=vmbr0,firewall=1,rate=90
numa: 0
onboot: 1
ostype: l26
scsi0: HDD:vm-158-disk-0,iops_rd=1000,iops_rd_max=1250,size=600G
scsihw: virtio-scsi-pci
serial0: socket
smbios1: uuid=521866bc-5b9b-aaaa-a478-ee1f406c6c18
sockets: 1
startup: down=300
vmgenid: 10e8fcee-cfbd-aaaa-b389-25682673f414

[PENDING]
cores: 10
cpu: host,flags=+md-clear
numa: 1
sockets: 2

 

[Leah]

It also occures on a migration attempt from 6.2-6 to 6.1-8

 

[fabian]

it's often not possible to migrate from a newer to an older Qemu machine unless you pin the machine type to a specific version. either upgrade the target node, or restart the VM with 'machine' set to something compatible with the outdated target node.

 

[Leah]

or restart the VM with 'machine' set to something compatible with the outdated target node.

But the machine type is on both new and old only "Default (i440fx)". The only other option in the web interface is q35. So I don't know how to change it to something else and more "compatible".

 

[fabian]

But the machine type is on both new and old only "Default (i440fx)". The only other option in the web interface is q35. So I don't know how to change it to something else and more "compatible".

e.g., with

qm set XXX -machine pc-i440fx-4.1+pve2

 

[Leah]

Ok...so this is not possible with the Webinterface. Is there a list of "possible valid machine types" somewhere?

 

[fabian]

kvm -machine help

gives you the stem, +pveX at the end gets bumped when we need to change the HW layout or something else that would be a breaking change. usually we try to align those with Qemu releases and guard them just on the Qemu version, but sometimes that is not possible and we use the suffix. e.g. for 4.1 we bumped from +pve1 to +pve2 when we bumped the number of SCSI disk slots which was an incompatible change. the starting point for each machine type is +pve0, which can be omitted.

 

[richmash]

e.g., with

qm set XXX -machine pc-i440fx-4.1+pve2

Thanks, @fabian, this solution worked for my exact problem.