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.
+`description`: `<string>` ::
+
+Datacenter description. Shown in the web-interface datacenter notes panel. This is saved as comment inside the configuration file.
+
`email_from`: `<string>` ::
Specify email address to send notification from (default is root@$hostname)
+
WARNING: 'hardware' and 'both' are EXPERIMENTAL & WIP
-`ha`: `shutdown_policy=<freeze|failover|conditional>` ::
+`ha`: `shutdown_policy=<enum>` ::
Cluster wide HA settings.
-`shutdown_policy`=`<conditional | failover | freeze>` ('default =' `conditional`);;
+`shutdown_policy`=`<conditional | failover | freeze | migrate>` ('default =' `conditional`);;
-Describes the policy for handling HA services on poweroff or reboot of a node. Freeze will always freeze services which are still located on the node on shutdown, those services won't be recovered by the HA manager. Failover will not mark the services as frozen and thus the services will get recovered to other nodes, if the shutdown node does not come up again quickly (< 1min). 'conditional' chooses automatically depending on the type of shutdown, i.e., on a reboot the service will be frozen but on a poweroff the service will stay as is, and thus get recovered after about 2 minutes.
+Describes the policy for handling HA services on poweroff or reboot of a node. Freeze will always freeze services which are still located on the node on shutdown, those services won't be recovered by the HA manager. Failover will not mark the services as frozen and thus the services will get recovered to other nodes, if the shutdown node does not come up again quickly (< 1min). 'conditional' chooses automatically depending on the type of shutdown, i.e., on a reboot the service will be frozen but on a poweroff the service will stay as is, and thus get recovered after about 2 minutes. Migrate will try to move all running services to another node when a reboot or shutdown was triggered. The poweroff process will only continue once no running services are located on the node anymore. If the node comes up again, the service will be moved back to the previously powered-off node, at least if no other migration, reloaction or recovery took place.
`http_proxy`: `http://.*` ::
Migration is secure using SSH tunnel by default. For secure private networks you can disable it to speed up migration. Deprecated, use the 'migration' property instead!
+`next-id`: `[lower=<integer>] [,upper=<integer>]` ::
+
+Control the range for the free VMID auto-selection pool.
+
+`lower`=`<integer>` ('default =' `100`);;
+
+Lower, inclusive boundary for free next-id API range.
+
+`upper`=`<integer>` ('default =' `1000000`);;
+
+Upper, exclusive boundary for free next-id API range.
+
`u2f`: `[appid=<APPID>] [,origin=<URL>]` ::
u2f
U2F Origin override. Mostly useful for single nodes with a single URL.
+`webauthn`: `[id=<DOMAINNAME>] [,origin=<URL>] [,rp=<RELYING_PARTY>]` ::
+
+webauthn configuration
+
+`id`=`<DOMAINNAME>` ;;
+
+Relying part ID. Must be the domain name without protocol, port or location. Changing this *will* break existing credentials.
+
+`origin`=`<URL>` ;;
+
+Site origin. Must be a `https://` URL (or `http://localhost`). Should contain the address users type in their browsers to access the web interface. Changing this *may* break existing credentials.
+
+`rp`=`<RELYING_PARTY>` ;;
+
+Relying party name. Any text identifier. Changing this *may* break existing credentials.
+
projects / pve-docs.git / blobdiff