all lists on lists.proxmox.com
 help / color / mirror / Atom feed
* [pve-devel] [PATCH kernel] d/rules: enable CONFIG_MEMCG_V1 needed for legacy containers
@ 2024-11-05 13:27 Fiona Ebner
  2024-11-06 16:16 ` [pve-devel] applied: " Thomas Lamprecht
  0 siblings, 1 reply; 2+ messages in thread
From: Fiona Ebner @ 2024-11-05 13:27 UTC (permalink / raw)
  To: pve-devel

As reported in the community forum [0], containers requiring cgroup v1
would not start anymore, even when systemd.unified_cgroup_hierarchy=0
was set on the kernel commandline. The error message would be:

> cgfsng_setup_limits_legacy: 3442 No such file or directory - Failed to set "memory.limit_in_bytes" to "536870912"

Kernel commit e93d4166b40a ("mm: memcg: put cgroup v1-specific code
under a config option") made it necessary to explicitly enable the new
associated Kconfig flag.

[0]: https://forum.proxmox.com/threads/156830/

Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---
 debian/rules | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/rules b/debian/rules
index f19a5b8..e1444b7 100755
--- a/debian/rules
+++ b/debian/rules
@@ -65,6 +65,7 @@ PMX_CONFIG_OPTS= \
 -e CONFIG_MODULE_SIG_SHA512 \
 -d CONFIG_MEMCG_DISABLED \
 -e CONFIG_MEMCG_SWAP_ENABLED \
+-e CONFIG_MEMCG_V1 \
 -e CONFIG_HYPERV \
 -m CONFIG_VFIO_IOMMU_TYPE1 \
 -e CONFIG_VFIO_VIRQFD \
-- 
2.39.5



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


^ permalink raw reply	[flat|nested] 2+ messages in thread

* [pve-devel] applied: [PATCH kernel] d/rules: enable CONFIG_MEMCG_V1 needed for legacy containers
  2024-11-05 13:27 [pve-devel] [PATCH kernel] d/rules: enable CONFIG_MEMCG_V1 needed for legacy containers Fiona Ebner
@ 2024-11-06 16:16 ` Thomas Lamprecht
  0 siblings, 0 replies; 2+ messages in thread
From: Thomas Lamprecht @ 2024-11-06 16:16 UTC (permalink / raw)
  To: Proxmox VE development discussion, Fiona Ebner

Am 05/11/2024 um 14:27 schrieb Fiona Ebner:
> As reported in the community forum [0], containers requiring cgroup v1
> would not start anymore, even when systemd.unified_cgroup_hierarchy=0
> was set on the kernel commandline. The error message would be:
> 
>> cgfsng_setup_limits_legacy: 3442 No such file or directory - Failed to set "memory.limit_in_bytes" to "536870912"
> 
> Kernel commit e93d4166b40a ("mm: memcg: put cgroup v1-specific code
> under a config option") made it necessary to explicitly enable the new
> associated Kconfig flag.
> 
> [0]: https://forum.proxmox.com/threads/156830/
> 
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
>  debian/rules | 1 +
>  1 file changed, 1 insertion(+)
> 
>

applied, thanks!


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2024-11-06 16:16 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-11-05 13:27 [pve-devel] [PATCH kernel] d/rules: enable CONFIG_MEMCG_V1 needed for legacy containers Fiona Ebner
2024-11-06 16:16 ` [pve-devel] applied: " Thomas Lamprecht

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal