X-Git-Url: https://git.proxmox.com/?p=pve-docs.git;a=blobdiff_plain;f=qm.adoc;h=a67cf8e52080a72c85e0a2c0bc8d18246c99b081;hp=8eab627e8423554947f8c56fb0ec8e1dbe29c8a4;hb=b473f999f6bd6fb541fb46559db1855dd6899160;hpb=5db724de29143ffa5f0484723d9b8009b15c7ee0

diff --git a/qm.adoc b/qm.adoc
index 8eab627..a67cf8e 100644
--- 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,7 +317,7 @@ of RAM available to the host.
 Network Device
 ~~~~~~~~~~~~~~
 
-[thumbnail="qm-network.png"]
+[thumbnail="gui-create-vm-network.png"]
 
 Each VM can have many _Network interface controllers_ (NIC), of four different
 types: