add screenshot for start/shutdown order

diff --git a/images/screenshot/gui-qemu-edit-start-order.png b/images/screenshot/gui-qemu-edit-start-order.png
new file mode 100644 (file)
index 0000000..7be8ee0
Binary files /dev/null and b/images/screenshot/gui-qemu-edit-start-order.png differ

diff --git a/pct.adoc b/pct.adoc
index b3659c4fcdd8b6f97d690fc21be302a18279f164..1170ad1c6c47c68b6e7771135b9b7608052e9fde 100644 (file)
--- a/pct.adoc
+++ b/pct.adoc
@@ -518,6 +518,10 @@ the following command:
 
  pct set <ctid> -onboot 1
 
+.Start and Shutdown Order
+// use the screenshot from qemu - its the same
+[thumbnail="gui-qemu-edit-start-order.png"]
+
 If you want to fine tune the boot order of your containers, you can use the following
 parameters :
 

diff --git a/qm.adoc b/qm.adoc
index a67cf8e52080a72c85e0a2c0bc8d18246c99b081..b9b7ca160fb8bf9eada37ccd1377cca31bc0045b 100644 (file)
--- a/qm.adoc
+++ b/qm.adoc
@@ -457,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