Back to bug 1953515

Who	When	What	Removed	Added
Red Hat Bugzilla	2021-04-26 09:43:02 UTC	Pool ID		sst_kernel_ft_rhel_9
Red Hat One Jira (issues.redhat.com)	2021-04-26 09:43:44 UTC	Link ID		Red Hat Issue Tracker RHELPLAN-76576
Steve Meisner	2021-04-30 13:37:44 UTC	Keywords		Triaged
Chao Ye	2021-10-19 01:28:28 UTC	Status	NEW	CLOSED
		Resolution	---	CURRENTRELEASE
		Last Closed		2021-10-19 01:28:28 UTC
Jaroslav Klech	2021-10-19 05:57:12 UTC	Docs Contact		jklech
		Doc Type	If docs needed, set a value	Enhancement
		CC		jklech
		Doc Text		.Cgroup-v2 enabled by default in RHEL 9 Cgroup v2 implements a single hierarchy model that simplifies the management of cgroups and ensures that a process can only be a member of a single cgroup at a time. Deep integration with SystemD greatly improves the end user experience when configuring resource control on a Red Hat Enterprise Linux system.
Jaroslav Klech	2021-10-19 11:44:09 UTC	Doc Text	.Cgroup-v2 enabled by default in RHEL 9 Cgroup v2 implements a single hierarchy model that simplifies the management of cgroups and ensures that a process can only be a member of a single cgroup at a time. Deep integration with SystemD greatly improves the end user experience when configuring resource control on a Red Hat Enterprise Linux system.	.`cgroup-v2` enabled by default in RHEL 9 The control groups version 2 (`cgroup-v2`) feature implements a single hierarchy model that simplifies the management of control groups. Also, it ensures that a process can only be a member of a single control group at a time. Deep integration with `systemd` improves the end user experience when configuring resource control on a RHEL system. Note that both `cgroup-v1` and `cgroup-v2` are fully enabled in the kernel. There is no default from the kernel point of view. The `cgroup` default is what `systemd` decides to mount at startup.
Jaroslav Klech	2021-10-20 12:49:12 UTC	CC		llong
		Flags		needinfo?(llong)
Waiman Long	2021-10-20 14:07:20 UTC	Flags	needinfo?(llong)
Jaroslav Klech	2021-10-21 08:41:46 UTC	Doc Text	.`cgroup-v2` enabled by default in RHEL 9 The control groups version 2 (`cgroup-v2`) feature implements a single hierarchy model that simplifies the management of control groups. Also, it ensures that a process can only be a member of a single control group at a time. Deep integration with `systemd` improves the end user experience when configuring resource control on a RHEL system. Note that both `cgroup-v1` and `cgroup-v2` are fully enabled in the kernel. There is no default from the kernel point of view. The `cgroup` default is what `systemd` decides to mount at startup.	.`cgroup-v2` enabled by default in RHEL 9 The control groups version 2 (`cgroup-v2`) feature implements a single hierarchy model that simplifies the management of control groups. Also, it ensures that a process can only be a member of a single control group at a time. Deep integration with `systemd` improves the end user experience when configuring resource control on a RHEL system. Development of new features is mostly done for `cgroup-v2` and it has some features that are missing in `cgroup-v1`. Similarly, `cgroup-v1` contains some features that are missing in `cgroup-v2`. Also, the control interfaces are different. Therefore, third party software with direct dependency on `cgroup-v1` may not work correctly when running in the `cgroup-v2` environment. Note that both `cgroup-v1` and `cgroup-v2` are fully enabled in the kernel. There is no default from the kernel point of view. The `cgroup` default is what `systemd` decides to mount at startup.
Jaroslav Klech	2021-10-21 13:34:42 UTC	Doc Text	.`cgroup-v2` enabled by default in RHEL 9 The control groups version 2 (`cgroup-v2`) feature implements a single hierarchy model that simplifies the management of control groups. Also, it ensures that a process can only be a member of a single control group at a time. Deep integration with `systemd` improves the end user experience when configuring resource control on a RHEL system. Development of new features is mostly done for `cgroup-v2` and it has some features that are missing in `cgroup-v1`. Similarly, `cgroup-v1` contains some features that are missing in `cgroup-v2`. Also, the control interfaces are different. Therefore, third party software with direct dependency on `cgroup-v1` may not work correctly when running in the `cgroup-v2` environment. Note that both `cgroup-v1` and `cgroup-v2` are fully enabled in the kernel. There is no default from the kernel point of view. The `cgroup` default is what `systemd` decides to mount at startup.	.`cgroup-v2` enabled by default in RHEL 9 The control groups version 2 (`cgroup-v2`) feature implements a single hierarchy model that simplifies the management of control groups. Also, it ensures that a process can only be a member of a single control group at a time. Deep integration with `systemd` improves the end user experience when configuring resource control on a RHEL system. Development of new features is mostly done for `cgroup-v2` and it has some features that are missing in `cgroup-v1`. Similarly, `cgroup-v1` contains some features that are missing in `cgroup-v2`. Also, the control interfaces are different. Therefore, third party software with direct dependency on `cgroup-v1` may not work correctly when running in the `cgroup-v2` environment. To be able to use `cgroup-v1`, you need to add the following parameters to the kernel command-line: * `systemd.unified_cgroup_hierarchy=0` * `systemd.legacy_systemd_cgroup_controller` Note that both `cgroup-v1` and `cgroup-v2` are fully enabled in the kernel. There is no default from the kernel point of view. The `cgroup` default is what `systemd` decides to mount at startup.
Jaroslav Klech	2021-10-21 13:41:30 UTC	Doc Text	.`cgroup-v2` enabled by default in RHEL 9 The control groups version 2 (`cgroup-v2`) feature implements a single hierarchy model that simplifies the management of control groups. Also, it ensures that a process can only be a member of a single control group at a time. Deep integration with `systemd` improves the end user experience when configuring resource control on a RHEL system. Development of new features is mostly done for `cgroup-v2` and it has some features that are missing in `cgroup-v1`. Similarly, `cgroup-v1` contains some features that are missing in `cgroup-v2`. Also, the control interfaces are different. Therefore, third party software with direct dependency on `cgroup-v1` may not work correctly when running in the `cgroup-v2` environment. To be able to use `cgroup-v1`, you need to add the following parameters to the kernel command-line: * `systemd.unified_cgroup_hierarchy=0` * `systemd.legacy_systemd_cgroup_controller` Note that both `cgroup-v1` and `cgroup-v2` are fully enabled in the kernel. There is no default from the kernel point of view. The `cgroup` default is what `systemd` decides to mount at startup.	.`cgroup-v2` enabled by default in RHEL 9 The control groups version 2 (`cgroup-v2`) feature implements a single hierarchy model that simplifies the management of control groups. Also, it ensures that a process can only be a member of a single control group at a time. Deep integration with `systemd` improves the end-user experience when configuring resource control on a RHEL system. Development of new features is mostly done for `cgroup-v2`, which has some features that are missing in `cgroup-v1`. Similarly, `cgroup-v1` contains some features that are missing in `cgroup-v2`. Also, the control interfaces are different. Therefore, third party software with direct dependency on `cgroup-v1` does not have to work correctly when running in the `cgroup-v2` environment. To be able to use `cgroup-v1`, you need to add the following parameters to the kernel command-line: * `systemd.unified_cgroup_hierarchy=0` * `systemd.legacy_systemd_cgroup_controller` Note that both `cgroup-v1` and `cgroup-v2` are fully enabled in the kernel. There is no default from the kernel point of view. The `cgroup` default is what `systemd` decides to mount at startup.
Jaroslav Klech	2021-10-25 13:36:25 UTC	Flags		needinfo?(llong)
		Doc Text	.`cgroup-v2` enabled by default in RHEL 9 The control groups version 2 (`cgroup-v2`) feature implements a single hierarchy model that simplifies the management of control groups. Also, it ensures that a process can only be a member of a single control group at a time. Deep integration with `systemd` improves the end-user experience when configuring resource control on a RHEL system. Development of new features is mostly done for `cgroup-v2`, which has some features that are missing in `cgroup-v1`. Similarly, `cgroup-v1` contains some features that are missing in `cgroup-v2`. Also, the control interfaces are different. Therefore, third party software with direct dependency on `cgroup-v1` does not have to work correctly when running in the `cgroup-v2` environment. To be able to use `cgroup-v1`, you need to add the following parameters to the kernel command-line: * `systemd.unified_cgroup_hierarchy=0` * `systemd.legacy_systemd_cgroup_controller` Note that both `cgroup-v1` and `cgroup-v2` are fully enabled in the kernel. There is no default from the kernel point of view. The `cgroup` default is what `systemd` decides to mount at startup.	.`cgroup-v2` enabled by default in RHEL 9 The control groups version 2 (`cgroup-v2`) feature implements a single hierarchy model that simplifies the management of control groups. Also, it ensures that a process can only be a member of a single control group at a time. Deep integration with `systemd` improves the end-user experience when configuring resource control on a RHEL system. Development of new features is mostly done for `cgroup-v2`, which has some features that are missing in `cgroup-v1`. Similarly, `cgroup-v1` contains some features that are missing in `cgroup-v2`. Also, the control interfaces are different. Therefore, third party software with direct dependency on `cgroup-v1` does not have to run properly in the `cgroup-v2` environment. To be able to use `cgroup-v1`, you need to add the following parameters to the kernel command-line: * `systemd.unified_cgroup_hierarchy=0` * `systemd.legacy_systemd_cgroup_controller` Note that both `cgroup-v1` and `cgroup-v2` are fully enabled in the kernel. There is no default from the kernel point of view. The `cgroup` default is what `systemd` decides to mount at startup.
Waiman Long	2021-10-25 16:06:38 UTC	Flags	needinfo?(llong)
Jaroslav Klech	2021-10-26 05:40:11 UTC	Doc Text	.`cgroup-v2` enabled by default in RHEL 9 The control groups version 2 (`cgroup-v2`) feature implements a single hierarchy model that simplifies the management of control groups. Also, it ensures that a process can only be a member of a single control group at a time. Deep integration with `systemd` improves the end-user experience when configuring resource control on a RHEL system. Development of new features is mostly done for `cgroup-v2`, which has some features that are missing in `cgroup-v1`. Similarly, `cgroup-v1` contains some features that are missing in `cgroup-v2`. Also, the control interfaces are different. Therefore, third party software with direct dependency on `cgroup-v1` does not have to run properly in the `cgroup-v2` environment. To be able to use `cgroup-v1`, you need to add the following parameters to the kernel command-line: * `systemd.unified_cgroup_hierarchy=0` * `systemd.legacy_systemd_cgroup_controller` Note that both `cgroup-v1` and `cgroup-v2` are fully enabled in the kernel. There is no default from the kernel point of view. The `cgroup` default is what `systemd` decides to mount at startup.	.`cgroup-v2` enabled by default in RHEL 9 The control groups version 2 (`cgroup-v2`) feature implements a single hierarchy model that simplifies the management of control groups. Also, it ensures that a process can only be a member of a single control group at a time. Deep integration with `systemd` improves the end-user experience when configuring resource control on a RHEL system. Development of new features is mostly done for `cgroup-v2`, which has some features that are missing in `cgroup-v1`. Similarly, `cgroup-v1` contains some legacy features that are missing in `cgroup-v2`. Also, the control interfaces are different. Therefore, third party software with direct dependency on `cgroup-v1` may not run properly in the `cgroup-v2` environment. To be able to use `cgroup-v1`, you need to add the following parameters to the kernel command-line: * `systemd.unified_cgroup_hierarchy=0` * `systemd.legacy_systemd_cgroup_controller` Note that both `cgroup-v1` and `cgroup-v2` are fully enabled in the kernel. There is no default from the kernel point of view. The `cgroup` default is what `systemd` decides to mount at startup.
Jaroslav Klech	2021-10-26 08:51:40 UTC	Doc Text	.`cgroup-v2` enabled by default in RHEL 9 The control groups version 2 (`cgroup-v2`) feature implements a single hierarchy model that simplifies the management of control groups. Also, it ensures that a process can only be a member of a single control group at a time. Deep integration with `systemd` improves the end-user experience when configuring resource control on a RHEL system. Development of new features is mostly done for `cgroup-v2`, which has some features that are missing in `cgroup-v1`. Similarly, `cgroup-v1` contains some legacy features that are missing in `cgroup-v2`. Also, the control interfaces are different. Therefore, third party software with direct dependency on `cgroup-v1` may not run properly in the `cgroup-v2` environment. To be able to use `cgroup-v1`, you need to add the following parameters to the kernel command-line: * `systemd.unified_cgroup_hierarchy=0` * `systemd.legacy_systemd_cgroup_controller` Note that both `cgroup-v1` and `cgroup-v2` are fully enabled in the kernel. There is no default from the kernel point of view. The `cgroup` default is what `systemd` decides to mount at startup.	.`cgroup-v2` enabled by default in RHEL 9 The control groups version 2 (`cgroup-v2`) feature implements a single hierarchy model that simplifies the management of control groups. Also, it ensures that a process can only be a member of a single control group at a time. Deep integration with `systemd` improves the end-user experience when configuring resource control on a RHEL system. Development of new features is mostly done for `cgroup-v2`, which has some features that are missing in `cgroup-v1`. Similarly, `cgroup-v1` contains some legacy features that are missing in `cgroup-v2`. Also, the control interfaces are different. Therefore, third party software with direct dependency on `cgroup-v1` may not run properly in the `cgroup-v2` environment. To be able to use `cgroup-v1`, you need to add the following parameters to the kernel command-line: * `systemd.unified_cgroup_hierarchy=0` * `systemd.legacy_systemd_cgroup_controller` Note that both `cgroup-v1` and `cgroup-v2` are fully enabled in the kernel. There is no default from the kernel point of view. The `cgroup` default is what `systemd` decides to mount at startup. For information how to change kernel command-line parameters, see link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/managing_monitoring_and_updating_the_kernel/configuring-kernel-command-line-parameters_managing-monitoring-and-updating-the-kernel[Configuring kernel command-line parameters].
Jaroslav Klech	2021-10-26 08:53:53 UTC	Doc Text	.`cgroup-v2` enabled by default in RHEL 9 The control groups version 2 (`cgroup-v2`) feature implements a single hierarchy model that simplifies the management of control groups. Also, it ensures that a process can only be a member of a single control group at a time. Deep integration with `systemd` improves the end-user experience when configuring resource control on a RHEL system. Development of new features is mostly done for `cgroup-v2`, which has some features that are missing in `cgroup-v1`. Similarly, `cgroup-v1` contains some legacy features that are missing in `cgroup-v2`. Also, the control interfaces are different. Therefore, third party software with direct dependency on `cgroup-v1` may not run properly in the `cgroup-v2` environment. To be able to use `cgroup-v1`, you need to add the following parameters to the kernel command-line: * `systemd.unified_cgroup_hierarchy=0` * `systemd.legacy_systemd_cgroup_controller` Note that both `cgroup-v1` and `cgroup-v2` are fully enabled in the kernel. There is no default from the kernel point of view. The `cgroup` default is what `systemd` decides to mount at startup. For information how to change kernel command-line parameters, see link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/managing_monitoring_and_updating_the_kernel/configuring-kernel-command-line-parameters_managing-monitoring-and-updating-the-kernel[Configuring kernel command-line parameters].	.`cgroup-v2` enabled by default in RHEL 9 The control groups version 2 (`cgroup-v2`) feature implements a single hierarchy model that simplifies the management of control groups. Also, it ensures that a process can only be a member of a single control group at a time. Deep integration with `systemd` improves the end-user experience when configuring resource control on a RHEL system. Development of new features is mostly done for `cgroup-v2`, which has some features that are missing in `cgroup-v1`. Similarly, `cgroup-v1` contains some legacy features that are missing in `cgroup-v2`. Also, the control interfaces are different. Therefore, third party software with direct dependency on `cgroup-v1` may not run properly in the `cgroup-v2` environment. To be able to use `cgroup-v1`, you need to add the following parameters to the kernel command-line: * `systemd.unified_cgroup_hierarchy=0` * `systemd.legacy_systemd_cgroup_controller` Note that both `cgroup-v1` and `cgroup-v2` are fully enabled in the kernel. There is no default from the kernel point of view. The `cgroup` default is what `systemd` decides to mount at startup.
Jaroslav Klech	2021-10-26 11:25:07 UTC	Doc Text	.`cgroup-v2` enabled by default in RHEL 9 The control groups version 2 (`cgroup-v2`) feature implements a single hierarchy model that simplifies the management of control groups. Also, it ensures that a process can only be a member of a single control group at a time. Deep integration with `systemd` improves the end-user experience when configuring resource control on a RHEL system. Development of new features is mostly done for `cgroup-v2`, which has some features that are missing in `cgroup-v1`. Similarly, `cgroup-v1` contains some legacy features that are missing in `cgroup-v2`. Also, the control interfaces are different. Therefore, third party software with direct dependency on `cgroup-v1` may not run properly in the `cgroup-v2` environment. To be able to use `cgroup-v1`, you need to add the following parameters to the kernel command-line: * `systemd.unified_cgroup_hierarchy=0` * `systemd.legacy_systemd_cgroup_controller` Note that both `cgroup-v1` and `cgroup-v2` are fully enabled in the kernel. There is no default from the kernel point of view. The `cgroup` default is what `systemd` decides to mount at startup.	.`cgroup-v2` enabled by default in RHEL 9 The control groups version 2 (`cgroup-v2`) feature implements a single hierarchy model that simplifies the management of control groups. Also, it ensures that a process can only be a member of a single control group at a time. Deep integration with `systemd` improves the end-user experience when configuring resource control on a RHEL system. Development of new features is mostly done for `cgroup-v2`, which has some features that are missing in `cgroup-v1`. Similarly, `cgroup-v1` contains some legacy features that are missing in `cgroup-v2`. Also, the control interfaces are different. Therefore, third party software with direct dependency on `cgroup-v1` may not run properly in the `cgroup-v2` environment. To use `cgroup-v1`, you need to add the following parameters to the kernel command-line: ---- systemd.unified_cgroup_hierarchy=0 systemd.legacy_systemd_cgroup_controller ---- NOTE: Both `cgroup-v1` and `cgroup-v2` are fully enabled in the kernel. There is no default control group version from the kernel point of view, and is decided by `systemd` to mount at startup.

Back to bug 1953515