You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our aged QEMU expects CONFIG_MEMCG_V1=y, but the debian-sources kernel config does not turn it on. The issue can be fixed by enabling that option in the ebuild, using the function that exists for that purpose. The symptom is that libvirt VMs don't start, because the expected memgroup-v1 facility doesn't exist, so there isn't a dir for it where there should be.
Now that things are working again, the exact error message is lost (it doesn't get logged), but it's something like "No such file or directory" for a path like /sys/fs/cgroup/memory/machine/qemu-8-v0.libvirt-qemu/memory.use_hierarchy.
(It seems CONFIG_MEMCG_V1 is a new kconfig option in linux-6.11)
The text was updated successfully, but these errors were encountered:
Our aged QEMU expects
CONFIG_MEMCG_V1=y
, but thedebian-sources
kernel config does not turn it on. The issue can be fixed by enabling that option in the ebuild, using the function that exists for that purpose. The symptom is thatlibvirt
VMs don't start, because the expectedmemgroup-v1
facility doesn't exist, so there isn't a dir for it where there should be.Now that things are working again, the exact error message is lost (it doesn't get logged), but it's something like "No such file or directory" for a path like
/sys/fs/cgroup/memory/machine/qemu-8-v0.libvirt-qemu/memory.use_hierarchy
.(It seems
CONFIG_MEMCG_V1
is a new kconfig option inlinux-6.11
)The text was updated successfully, but these errors were encountered: