Fresh installation of PVE 8 and migrated VM/ct could not get vmid from pid... unexpected cgroup entry 12:blkio:/qemu.slice

[Inlakesh]

We have done a fresh installation of PVE 8 and migrated VM's & CT's from a proxmox v 5.14

Everything worked OK until we updated PVE 8 to the latest version.
Now the syslog shows this:
Oct 06 10:09:51 pv1 qmeventd[10453]: could not get vmid from pid 45690
Oct 06 10:09:51 pv1 qmeventd[10453]: unexpected cgroup entry 12:blkio:/qemu.slice
Oct 06 10:09:51 pv1 qmeventd[10453]: could not get vmid from pid 34438
Oct 06 10:09:51 pv1 qmeventd[10453]: unexpected cgroup entry 12:blkio:/qemu.slice
Oct 06 10:09:51 pv1 qmeventd[10453]: could not get vmid from pid 47248
Oct 06 10:09:51 pv1 qmeventd[10453]: unexpected cgroup entry 12:blkio:/qemu.slice
Oct 06 10:09:51 pv1 qmeventd[10453]: could not get vmid from pid 42412
Oct 06 10:09:51 pv1 qmeventd[10453]: unexpected cgroup entry 12:blkio:/qemu.slice
Oct 06 10:09:51 pv1 qmeventd[10453]: could not get vmid from pid 32971
Oct 06 10:09:51 pv1 qmeventd[10453]: unexpected cgroup entry 12:blkio:/qemu.slice
Oct 06 10:09:51 pv1 qmeventd[10453]: could not get vmid from pid 29838
Oct 06 10:09:51 pv1 qmeventd[10453]: unexpected cgroup entry 12:blkio:/qemu.slice
Oct 06 10:09:51 pv1 qmeventd[10453]: could not get vmid from pid 44885
Oct 06 10:09:52 pv1 qmeventd[10453]: unexpected cgroup entry 12:blkio:/qemu.slice
Oct 06 10:09:52 pv1 qmeventd[10453]: could not get vmid from pid 52379
Oct 06 10:09:52 pv1 qmeventd[10453]: unexpected cgroup entry 12:blkio:/qemu.slice
Oct 06 10:09:52 pv1 qmeventd[10453]: could not get vmid from pid 60962
Oct 06 10:09:52 pv1 qmeventd[10453]: unexpected cgroup entry 12:blkio:/qemu.slice
Oct 06 10:09:52 pv1 qmeventd[10453]: could not get vmid from pid 84510
Oct 06 10:09:52 pv1 qmeventd[10453]: unexpected cgroup entry 12:blkio:/qemu.slice
Oct 06 10:09:52 pv1 qmeventd[10453]: could not get vmid from pid 81935
Oct 06 10:09:52 pv1 qmeventd[10453]: unexpected cgroup entry 12:blkio:/qemu.slice
Oct 06 10:09:52 pv1 qmeventd[10453]: could not get vmid from pid 65381
Oct 06 10:09:52 pv1 qmeventd[10453]: unexpected cgroup entry 12:blkio:/qemu.slice
Oct 06 10:09:52 pv1 qmeventd[10453]: could not get vmid from pid 86481
Oct 06 10:09:52 pv1 qmeventd[10453]: unexpected cgroup entry 12:blkio:/qemu.slice
Oct 06 10:09:52 pv1 qmeventd[10453]: could not get vmid from pid 118073
Oct 06 10:09:52 pv1 qmeventd[10453]: unexpected cgroup entry 12:blkio:/qemu.slice
Oct 06 10:09:52 pv1 qmeventd[10453]: could not get vmid from pid 116282
Oct 06 10:09:52 pv1 qmeventd[10453]: unexpected cgroup entry 12:blkio:/qemu.slice
Oct 06 10:09:52 pv1 qmeventd[10453]: could not get vmid from pid 200750.............................

What can we do to resolve this?

Appreciate any guidance.

 

[t.lamprecht]

Now the syslog shows this:
Oct 06 10:09:51 pv1 qmeventd[10453]: could not get vmid from pid 45690
Oct 06 10:09:51 pv1 qmeventd[10453]: unexpected cgroup entry 12:blkio:/qemu.slice
Oct 06 10:09:51 pv1 qmeventd[10453]: could not get vmid from pid 34438

This error stems from a parsing bug when the legacy-cgroup controller is used, i.e., you probably set the systemd.unified_cgroup_hierarchy=0 as per our docs to support ancient containers distros.

This is fixed and shipped with qemu-server version 8.0.7, which is due to getting moved to the enterprise repository in the next few days.

 

[Inlakesh]

This error stems from a parsing bug when the legacy-cgroup controller is used, i.e., you probably set the systemd.unified_cgroup_hierarchy=0 as per our docs to support ancient containers distros.

This is fixed and shipped with qemu-server version 8.0.7, which is due to getting moved to the enterprise repository in the next few days.

Thanks for your answer and update notice, much appreciated. So I will wait for the update and hoping for this to disapear then.