gui-create-ct-general.png: update screenshot

[pve-docs.git] / qm.adoc

diff --git a/qm.adoc b/qm.adoc
index 0964976471330007cc018e9261c4171c28d17184..b9b7ca160fb8bf9eada37ccd1377cca31bc0045b 100644 (file)
--- a/qm.adoc
+++ b/qm.adoc
@@ -101,7 +101,7 @@ could incur a performance slowdown, or putting your data at risk.
 General Settings
 ~~~~~~~~~~~~~~~~
 
-[thumbnail="qm-general-settings.png"]
+[thumbnail="gui-create-vm-general.png"]
 
 General settings of a VM include
 
@@ -115,7 +115,7 @@ General settings of a VM include
 OS Settings
 ~~~~~~~~~~~
 
-[thumbnail="qm-os-settings.png"]
+[thumbnail="gui-create-vm-os.png"]
 
 When creating a VM, setting the proper Operating System(OS) allows {pve} to
 optimize some low level parameters. For instance Windows OS expect the BIOS
@@ -154,7 +154,7 @@ containing the drivers during the installation.
 the Virtio SCSI controller, is an older type of paravirtualized controller
 which has been superseded in features by the Virtio SCSI Controller.
 
-[thumbnail="qm-hard-disk.png"]
+[thumbnail="gui-create-vm-hard-disk.png"]
 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
@@ -201,7 +201,7 @@ Note that backups do not currently work with *IO Thread* enabled.
 CPU
 ~~~
 
-[thumbnail="qm-cpu-settings.png"]
+[thumbnail="gui-create-vm-cpu.png"]
 
 A *CPU socket* is a physical slot on a PC motherboard where you can plug a CPU.
 This CPU can then contain one or many *cores*, which are independent
@@ -270,13 +270,13 @@ For each VM you have the option to set a fixed size memory or asking
 host. 
 
 .Fixed Memory Allocation
-[thumbnail="qm-memory-fixed.png"]
+[thumbnail="gui-create-vm-memory-fixed.png"]
 
 When choosing a *fixed size memory* {pve} will simply allocate what you
 specify to your VM.
 
 .Automatic Memory Allocation
-[thumbnail="qm-memory-auto.png", float="left"]
+[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
@@ -317,6 +317,8 @@ of RAM available to the host.
 Network Device
 ~~~~~~~~~~~~~~
 
+[thumbnail="gui-create-vm-network.png"]
+
 Each VM can have many _Network interface controllers_ (NIC), of four different
 types:
 
@@ -455,10 +457,14 @@ the following command:
 
  qm set <vmid> -onboot 1
 
-In some case you want to be able to fine tune the boot order of your VMs, for
-instance if one of your VM is providing firewalling or DHCP to other guest
-systems.
-For this you can use the following parameters:
+.Start and Shutdown Order
+
+[thumbnail="gui-qemu-edit-start-order.png"]
+
+In some case you want to be able to fine tune the boot order of your
+VMs, for instance if one of your VM is providing firewalling or DHCP
+to other guest systems.  For this you can use the following
+parameters:
 
 * *Start/Shutdown order*: Defines the start order priority. E.g. set it to 1 if
 you want the VM to be the first to be started. (We use the reverse startup