run make update

[pve-docs.git] / qm-cloud-init-opts.adoc

diff --git a/qm-cloud-init-opts.adoc b/qm-cloud-init-opts.adoc
index 67b2edd8f0c44e67561fa7e459acd3a035a96c15..43e44158dab874d676f04e8c9cf08143979b6c93 100644 (file)
--- a/qm-cloud-init-opts.adoc
+++ b/qm-cloud-init-opts.adoc
@@ -1,3 +1,19 @@
+`cicustom`: `[meta=<volume>] [,network=<volume>] [,user=<volume>]` ::
+
+Specify custom files to replace the automatically generated ones at start.
+
+`meta`=`<volume>` ;;
+
+Specify a custom file containing all meta data passed to the VM via cloud-init. This is provider specific meaning configdrive2 and nocloud differ.
+
+`network`=`<volume>` ;;
+
+Specify a custom file containing all network data passed to the VM via cloud-init.
+
+`user`=`<volume>` ;;
+
+Specify a custom file containing all user data passed to the VM via cloud-init.
+

 `cipassword`: `<string>` ::
 
 Password to assign the user. Using this is generally not recommended. Use ssh keys instead. Also note that older cloud-init versions do not support hashed passwords.
 `cipassword`: `<string>` ::
 
 Password to assign the user. Using this is generally not recommended. Use ssh keys instead. Also note that older cloud-init versions do not support hashed passwords.


@@ -17,7 +33,7 @@ Specify IP addresses and gateways for the corresponding interface.
 IP addresses use CIDR notation, gateways are optional but need an IP of the same type specified.
 +
 The special string 'dhcp' can be used for IP addresses to use DHCP, in which case no explicit gateway should be provided.
 IP addresses use CIDR notation, gateways are optional but need an IP of the same type specified.
 +
 The special string 'dhcp' can be used for IP addresses to use DHCP, in which case no explicit gateway should be provided.

-SLAAC is not supported by cloud-init but at least netplan activates SLAAC when selecting 'dhcp' so it should work with up-to-date netplan versions.
+For IPv6 the special string 'auto' can be used to use stateless autoconfiguration.

 +
 If cloud-init is enabled and neither an IPv4 nor an IPv6 address is specified, it defaults to using dhcp on IPv4.
 
 +
 If cloud-init is enabled and neither an IPv4 nor an IPv6 address is specified, it defaults to using dhcp on IPv4.