From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com, Shannon Sterz <s.sterz@proxmox.com>
Subject: [pve-devel] applied: [PATCH manager v2] 8 to 9: use check for unified cgroup v2 support via pve-container
Date: Thu, 7 Aug 2025 16:54:55 +0200 [thread overview]
Message-ID: <175457836714.113987.193439260852613390.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250807142246.341381-1-s.sterz@proxmox.com>
On Thu, 07 Aug 2025 16:22:46 +0200, Shannon Sterz wrote:
> ...instead of re-implementing a custom check here. This has the
> side-effect that the check implemented by pve-container is much more
> robust and is less likely to yield false positive. So users won't get
> warnings about containers that actually do have the required unified
> cgroup v2 support.
>
> This was reported for an OpenSUSE Slowroll container on the forum:
> https://forum.proxmox.com/threads/169302/
>
> [...]
Applied, thanks! Made a separate commit running 'make tidy' first and
rebased on top of that to get a clean change.
[1/1] 8 to 9: use check for unified cgroup v2 support via pve-container
commit: ea1f2523515d7639f754a0588ffd8800cdb3321f
and for stable-8:
[1/1] 8 to 9: use check for unified cgroup v2 support via pve-container
commit: 24cd98ac41e83efd3c235cd50e47c66429bb106b
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-08-07 14:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 14:22 [pve-devel] " Shannon Sterz
2025-08-07 14:54 ` Fiona Ebner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=175457836714.113987.193439260852613390.b4-ty@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.sterz@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox