mention that NAT mode is not available on the WebUI

[pve-docs.git] / qm.adoc

diff --git a/qm.adoc b/qm.adoc
index 55de57c30fd6e01dd97e09883a0b5d1c6d8a0fb2..60cd1ddd8211c4d918bbfa8173219aef571ab6bf 100644 (file)
--- a/qm.adoc
+++ b/qm.adoc
@@ -163,7 +163,7 @@ On each controller you attach a number of emulated hard disks, which are backed
 by a file or a block device residing in the configured storage. The choice of
 a storage type will determine the format of the hard disk image. Storages which
 present block devices (LVM, ZFS, Ceph) will require the *raw disk image format*,
 by a file or a block device residing in the configured storage. The choice of
 a storage type will determine the format of the hard disk image. Storages which
 present block devices (LVM, ZFS, Ceph) will require the *raw disk image format*,

-whereas files based storages (Ext4, NFS, GlusterFS) will let you to choose
+whereas files based storages (Ext4, NFS, CIFS, GlusterFS) will let you to choose

 either the *raw disk image format* or the *QEMU image format*.
 
  * the *QEMU image format* is a copy on write format which allows snapshots, and
 either the *raw disk image format* or the *QEMU image format*.
 
  * the *QEMU image format* is a copy on write format which allows snapshots, and


@@ -420,15 +420,15 @@ host.
 .Fixed Memory Allocation
 [thumbnail="gui-create-vm-memory-fixed.png"]
 
 .Fixed Memory Allocation
 [thumbnail="gui-create-vm-memory-fixed.png"]
 

-When choosing a *fixed size memory* {pve} will simply allocate what you
-specify to your VM.
+When setting memory and minimum memory to the same amount
+{pve} will simply allocate what you specify to your VM.

 
 Even when using a fixed memory size, the ballooning device gets added to the
 VM, because it delivers useful information such as how much memory the guest
 really uses.
 In general, you should leave *ballooning* enabled, but if you want to disable
 it (e.g. for debugging purposes), simply uncheck
 
 Even when using a fixed memory size, the ballooning device gets added to the
 VM, because it delivers useful information such as how much memory the guest
 really uses.
 In general, you should leave *ballooning* enabled, but if you want to disable
 it (e.g. for debugging purposes), simply uncheck

-*Ballooning* or set
+*Ballooning Device* or set

 
  balloon: 0
 
 
  balloon: 0
 


@@ -438,7 +438,7 @@ in the configuration.
 [thumbnail="gui-create-vm-memory-dynamic.png", float="left"]
 
 // see autoballoon() in pvestatd.pm
 [thumbnail="gui-create-vm-memory-dynamic.png", float="left"]
 
 // see autoballoon() in pvestatd.pm

-When choosing to *automatically allocate memory*, {pve} will make sure that the
+When setting the minimum memory lower that the memory, {pve} will make sure that the

 minimum amount you specified is always available to the VM, and if RAM usage on
 the host is below 80%, will dynamically add memory to the guest up to the
 maximum memory specified.
 minimum amount you specified is always available to the VM, and if RAM usage on
 the host is below 80%, will dynamically add memory to the guest up to the
 maximum memory specified.


@@ -503,7 +503,8 @@ have direct access to the Ethernet LAN on which the host is located.
 the Qemu user networking stack, where a built-in router and DHCP server can
 provide network access. This built-in DHCP will serve addresses in the private
 10.0.2.0/24 range. The NAT mode is much slower than the bridged mode, and
 the Qemu user networking stack, where a built-in router and DHCP server can
 provide network access. This built-in DHCP will serve addresses in the private
 10.0.2.0/24 range. The NAT mode is much slower than the bridged mode, and

-should only be used for testing.
+should only be used for testing. This mode is only available via CLI or the API,
+but not via the WebUI.

 
 You can also skip adding a network device when creating a VM by selecting *No
 network device*.
 
 You can also skip adding a network device when creating a VM by selecting *No
 network device*.


@@ -883,6 +884,9 @@ Finally attach the unused disk to the SCSI controller of the VM:
 
 The VM is ready to be started.
 
 
 The VM is ready to be started.
 

+
+include::qm-cloud-init.adoc[]
+

 Managing Virtual Machines with `qm`
 ------------------------------------
 
 Managing Virtual Machines with `qm`
 ------------------------------------