`bwlimit`: `[clone=<LIMIT>] [,default=<LIMIT>] [,migration=<LIMIT>] [,move=<LIMIT>] [,restore=<LIMIT>]` ::
-Set bandwidth/io limits various operations.
+Set I/O bandwidth limit for various operations (in KiB/s).
`clone`=`<LIMIT>` ;;
Select the default Console viewer. You can either use the builtin java applet (VNC; deprecated and maps to html5), an external virt-viewer comtatible application (SPICE), an HTML5 based vnc viewer (noVNC), or an HTML5 based console client (xtermjs). If the selected viewer is not available (e.g. SPICE not activated for the VM), the fallback is noVNC.
-`crs`: `ha=<basic|static>` ::
+`crs`: `[ha=<basic|static>] [,ha-rebalance-on-start=<1|0>]` ::
Cluster resource scheduling settings.
Configures how the HA manager should select nodes to start or recover services. With 'basic', only the number of services is used, with 'static', static CPU and memory configuration of services is considered.
+`ha-rebalance-on-start`=`<boolean>` ('default =' `0`);;
+
+Set to use CRS for selecting a suited node when a HA services request-state changes from stop to start.
+
`description`: `<string>` ::
Datacenter description. Shown in the web-interface datacenter notes panel. This is saved as comment inside the configuration file.
Default keybord layout for vnc server.
-`language`: `<ca | da | de | en | es | eu | fa | fr | he | it | ja | nb | nn | pl | pt_BR | ru | sl | sv | tr | zh_CN | zh_TW>` ::
+`language`: `<ar | ca | da | de | en | es | eu | fa | fr | he | hr | it | ja | ka | kr | nb | nl | nn | pl | pt_BR | ru | sl | sv | tr | ukr | zh_CN | zh_TW>` ::
Default GUI language.
-`mac_prefix`: `<string>` ::
+`mac_prefix`: `<string>` ('default =' `BC:24:11`)::
-Prefix for autogenerated MAC addresses.
+Prefix for the auto-generated MAC addresses of virtual guests. The default `BC:24:11` is the Organizationally Unique Identifier (OUI) assigned by the IEEE to Proxmox Server Solutions GmbH for a MAC Address Block Large (MA-L). You're allowed to use this in local networks, i.e., those not directly reachable by the public (e.g., in a LAN or NAT/Masquerading).
+
+Note that when you run multiple cluster that (partially) share the networks of their virtual guests, it's highly recommended that you extend the default MAC prefix, or generate a custom (valid) one, to reduce the chance of MAC collisions. For example, add a separate extra hexadecimal to the Proxmox OUI for each cluster, like `BC:24:11:0` for the first, `BC:24:11:1` for the second, and so on.
+ Alternatively, you can also separate the networks of the guests logically, e.g., by using VLANs.
++
+For publicly accessible guests it's recommended that you get your own https://standards.ieee.org/products-programs/regauth/[OUI from the IEEE] registered or coordinate with your, or your hosting providers, network admins.
`max_workers`: `<integer> (1 - N)` ::
Upper, exclusive boundary for free next-id API range.
+`notify`: `[fencing=<always|never>] [,package-updates=<auto|always|never>] [,replication=<always|never>] [,target-fencing=<TARGET>] [,target-package-updates=<TARGET>] [,target-replication=<TARGET>]` ::
+
+Cluster-wide notification settings.
+
+`fencing`=`<always | never>` ;;
+
+UNUSED - Use datacenter notification settings instead.
+
+`package-updates`=`<always | auto | never>` ('default =' `auto`);;
+
+DEPRECATED: Use datacenter notification settings instead.
+Control how often the daily update job should send out notifications:
+* 'auto' daily for systems with a valid subscription, as those are assumed to be production-ready and thus should know about pending updates.
+* 'always' every update, if there are new pending updates.
+* 'never' never send a notification for new pending updates.
+
+`replication`=`<always | never>` ;;
+
+UNUSED - Use datacenter notification settings instead.
+
+`target-fencing`=`<TARGET>` ;;
+
+UNUSED - Use datacenter notification settings instead.
+
+`target-package-updates`=`<TARGET>` ;;
+
+UNUSED - Use datacenter notification settings instead.
+
+`target-replication`=`<TARGET>` ;;
+
+UNUSED - Use datacenter notification settings instead.
+
`registered-tags`: `<tag>[;<tag>...]` ::
A list of tags that require a `Sys.Modify` on '/' to set and delete. Tags set here that are also in 'user-tag-access' also require `Sys.Modify`.
`user-allow`=`<existing | free | list | none>` ('default =' `free`);;
-Controls which tags can be set or deleted on resources a user controls (such as guests). Users with the `Sys.Modify` privilege on `/` are always unrestricted. 'none' no tags are usable. 'list' tags from 'user-allow-list' are usable. 'existing' like list, but already existing tags of resources are also usable.'free' no tag restrictions.
+Controls which tags can be set or deleted on resources a user controls (such as guests). Users with the `Sys.Modify` privilege on `/` are alwaysunrestricted.
+* 'none' no tags are usable.
+* 'list' tags from 'user-allow-list' are usable.
+* 'existing' like list, but already existing tags of resources are also usable.
+* 'free' no tag restrictions.
`user-allow-list`=`<tag>[;<tag>...]` ;;