update static/schema information

Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This commit is contained in:
Thomas Lamprecht 2023-11-21 20:28:42 +01:00
parent 3d5a1655f2
commit fa22697b2d
7 changed files with 1731 additions and 480 deletions

File diff suppressed because it is too large Load Diff

View File

@ -68,13 +68,18 @@ Specify external http proxy which is used for downloads (example: 'http://userna
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)` ::
@ -187,7 +192,11 @@ Privilege options for user-settable tags
`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>...]` ;;

View File

@ -126,6 +126,10 @@ Try to be more verbose. For now this only enables debug log-level on start.
Description for the Container. Shown in the web-interface CT's summary. This is saved as comment inside the configuration file.
`--dev[n]` `[[path=]<Path>] [,gid=<integer>] [,mode=<Octal access mode>] [,uid=<integer>]` ::
Device to pass through to the container
`--features` `[force_rw_sys=<1|0>] [,fuse=<1|0>] [,keyctl=<1|0>] [,mknod=<1|0>] [,mount=<fstype;fstype;...>] [,nesting=<1|0>]` ::
Allow containers access to advanced features.
@ -659,6 +663,10 @@ Try to be more verbose. For now this only enables debug log-level on start.
Description for the Container. Shown in the web-interface CT's summary. This is saved as comment inside the configuration file.
`--dev[n]` `[[path=]<Path>] [,gid=<integer>] [,mode=<Octal access mode>] [,uid=<integer>]` ::
Device to pass through to the container
`--features` `[force_rw_sys=<1|0>] [,fuse=<1|0>] [,keyctl=<1|0>] [,mknod=<1|0>] [,mount=<fstype;fstype;...>] [,nesting=<1|0>]` ::
Allow containers access to advanced features.
@ -847,6 +855,10 @@ A list of settings you want to delete.
Description for the Container. Shown in the web-interface CT's summary. This is saved as comment inside the configuration file.
`--dev[n]` `[[path=]<Path>] [,gid=<integer>] [,mode=<Octal access mode>] [,uid=<integer>]` ::
Device to pass through to the container
`--digest` `<string>` ::
Prevent changes if current configuration file has different SHA1 digest. This can be used to prevent concurrent modifications.

View File

@ -32,6 +32,26 @@ Try to be more verbose. For now this only enables debug log-level on start.
Description for the Container. Shown in the web-interface CT's summary. This is saved as comment inside the configuration file.
`dev[n]`: `[[path=]<Path>] [,gid=<integer>] [,mode=<Octal access mode>] [,uid=<integer>]` ::
Device to pass through to the container
`gid`=`<integer> (0 - N)` ;;
Group ID to be assigned to the device node
`mode`=`<Octal access mode>` ;;
Access mode to be set on the device node
`path`=`<Path>` ;;
Path to the device to pass through to the container
`uid`=`<integer> (0 - N)` ;;
User ID to be assigned to the device node
`features`: `[force_rw_sys=<1|0>] [,fuse=<1|0>] [,keyctl=<1|0>] [,mknod=<1|0>] [,mount=<fstype;fstype;...>] [,nesting=<1|0>]` ::
Allow containers access to advanced features.

View File

@ -104,7 +104,7 @@ Use specific network for all ceph related traffic
Placement group bits, used to specify the default number of placement groups.
+
NOTE: 'osd pool default pg num' does not work for default pools.
Depreacted. This setting was deprecated in recent Ceph versions.
`--size` `<integer> (1 - 7)` ('default =' `3`)::
@ -212,6 +212,11 @@ NOTE: Requires option(s): `db_dev`
Enables encryption of the OSD.
`--osds-per-device` `<integer> (1 - N)` ::
OSD services per physical device. Only useful for fast NVMe devices"
." to utilize their performance better.
`--wal_dev` `<string>` ::
Block device name for block.wal.

View File

@ -459,7 +459,7 @@ Configure an USB device (n is 0 to 4, for machine version >= 7.1 and ostype l26
Number of hotplugged vcpus.
`--vga` `[[type=]<enum>] [,memory=<integer>]` ::
`--vga` `[[type=]<enum>] [,clipboard=<vnc>] [,memory=<integer>]` ::
Configure the VGA hardware.
@ -1279,7 +1279,7 @@ Configure an USB device (n is 0 to 4, for machine version >= 7.1 and ostype l26
Number of hotplugged vcpus.
`--vga` `[[type=]<enum>] [,memory=<integer>]` ::
`--vga` `[[type=]<enum>] [,clipboard=<vnc>] [,memory=<integer>]` ::
Configure the VGA hardware.

View File

@ -1219,11 +1219,15 @@ Specifies whether if given host option is a USB3 device or port. For modern gues
Number of hotplugged vcpus.
`vga`: `[[type=]<enum>] [,memory=<integer>]` ::
`vga`: `[[type=]<enum>] [,clipboard=<vnc>] [,memory=<integer>]` ::
Configure the VGA Hardware. If you want to use high resolution modes (>= 1280x1024x16) you may need to increase the vga memory option. Since QEMU 2.9 the default VGA display type is 'std' for all OS types besides some Windows versions (XP and older) which use 'cirrus'. The 'qxl' option enables the SPICE display server. For win* OS you can select how many independent displays you want, Linux guests can add displays them self.
You can also run without any graphic card, using a serial device as terminal.
`clipboard`=`<vnc>` ;;
Enable a specific clipboard. If not set, depending on the display type the SPICE one will be added.
`memory`=`<integer> (4 - 512)` ;;
Sets the VGA memory (in MiB). Has no effect with serial display.