add missing file

[pve-docs.git] / qm.adoc

diff --git a/qm.adoc b/qm.adoc
index c430d171e3e20c791d55e3f878bcb5df59615163..6d52c50f860cbae1cdd85ee3a33e16ec45168349 100644 (file)
--- a/qm.adoc
+++ b/qm.adoc
@@ -418,7 +418,7 @@ For each VM you have the option to set a fixed size memory or asking
 host.
 
 .Fixed Memory Allocation
-[thumbnail="gui-create-vm-memory-fixed.png"]
+[thumbnail="gui-create-vm-memory.png"]
 
 When setting memory and minimum memory to the same amount
 {pve} will simply allocate what you specify to your VM.
@@ -435,10 +435,9 @@ it (e.g. for debugging purposes), simply uncheck
 in the configuration.
 
 .Automatic Memory Allocation
-[thumbnail="gui-create-vm-memory-dynamic.png", float="left"]
 
 // see autoballoon() in pvestatd.pm
-When setting the minimum memory lower that the memory, {pve} will make sure that the
+When setting the minimum memory lower than 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.
@@ -503,7 +502,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
-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*.