Thanks for the response, John. I sent a series to enable this on some of the cloud kernels for Noble yesterday:
https://lists.ubuntu.com/archives/kernel-team/2025-November/164536.html I wasn't a party to the internal discussions about this change, but my understanding was that there was concern about the re-enabling of cgroups v1 setting a precedent that they would be supported beyond their upstream lifetime. I had hoped enabling just for Noble would be an acceptable compromise, but at the time I didn't realize this also implied the need to find every 6.14 branch that was maintained for Noble and make the change in each one. I have no expectation that the support should be maintained beyond what upstream thinks its lifespan should be. The use case that got me involved was about giving users who were still on Noble and had managed to re-enable cgroups v1 in systemd, or who had java programs that were still looking at /proc/cgroups a bit more time to pick up fixed versions of those pieces of software and upgrade. My understanding is that it's not even possible to get systemd to enable cgroups v1 after Noble. If the consensus is that it would be acceptable to enable these config features in Plucky / Questing, I'm happy to submit a different version of the change that just enables it there instead. Or if you're already doing it, that's even better. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2122368 Title: enable MEMCG_V1 and CPUSETS_V1 on Noble 6.14+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws-6.14/+bug/2122368/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
