We had the same issues. You need to stay on kernel 5.4, since there have been breaking changes/fixes since kernel 5.8 for AMD EPYC.
Those changes are incompatible Netcup's host kernel - they're using a custom kernel 5.4.
See also...
Thanks. Shouldn't you also link this in the wiki? There you only find the hint that it might be insecure because procfs and sysfs are mounted from the host into the container.
For myself, I haven't had any problems with uninstalling dbus by the way. Seems like none of my applications need it.
I've done some trial-and-error. For me, commenting out these two works:
# ProtectProc=invisible
# ProtectControlGroups=yes
Warning: I don't have a clue, how this affects security. Maybe using nested is better (or worse).
Hallo zusammen!
tl;dr
Upgrade auf Proxmox 7 (Kernel >= 5.10) bringt alle VMs zum Hängen
Einleitung
Ich habe einen großen VPS bei einem deutschen Host (mit N beginnend). Das Host-System verwendet einen AMD EPYC 7702P und eine unbekannte KVM-Version. Mir wurde das SVM-Flag des Prozessors...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.