vzdump: mention new parameter 'pbs-entries-max'

[pve-docs.git] / pct.adoc

diff --git a/pct.adoc b/pct.adoc
index ebae3e9b165baa01ef427a2a0e6aa278cdf83d98..9f4dc7fa4358e49a818c74bea425e02101bab36c 100644 (file)
--- a/pct.adoc
+++ b/pct.adoc
@@ -59,7 +59,7 @@ VM, but without the additional overhead. This means that Proxmox Containers can
 be categorized as ``System Containers'', rather than ``Application Containers''.
 
 NOTE: If you want to run application containers, for example, 'Docker' images, it
-is recommended that you run them inside a Proxmox Qemu VM. This will give you
+is recommended that you run them inside a Proxmox QEMU VM. This will give you
 all the advantages of application containerization, while also providing the
 benefits that VMs offer, such as strong isolation from the host and the ability
 to live-migrate, which otherwise isn't possible with containers. 
@@ -427,8 +427,9 @@ cpulimit: 0.5
 
 `cpuunits`: :: This is a relative weight passed to the kernel scheduler. The
 larger the number is, the more CPU time this container gets. Number is relative
-to the weights of all the other running containers. The default is 1024. You
-can use this setting to prioritize some containers.
+to the weights of all the other running containers. The default is `100` (or
+`1024` if the host uses legacy cgroup v1). You can use this setting to
+prioritize some containers.
 
 
 [[pct_memory]]
@@ -721,9 +722,8 @@ environment, you can either
   decades old OS versions just fine there.
 
 * Switch back to the legacy 'cgroup' controller. Note that while it can be a
-  valid solution, it's not a permanent one. There's a high likelihood that a
-  future {pve} major release, for example 8.0, cannot support the legacy
-  controller anymore.
+  valid solution, it's not a permanent one. Starting from {pve} 9.0, the legacy
+  controller will not be supported anymore.
 ====
 
 [[pct_cgroup_change_version]]