qm.adoc: change section ordering

[pve-docs.git] / qm.adoc

diff --git a/qm.adoc b/qm.adoc
index d77c4b0f3571fe3817e28c0b433b9f5f22dfb171..a0492fb1145ed46b69d9e834004741314d4e9621 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
 ~~~~~~~~~~~~~~~~
 
 General Settings
 ~~~~~~~~~~~~~~~~
 

-[thumbnail="qm-general-settings.png"]
+[thumbnail="gui-create-vm-general.png"]

 
 General settings of a VM include
 
 
 General settings of a VM include
 


@@ -115,7 +115,7 @@ General settings of a VM include
 OS Settings
 ~~~~~~~~~~~
 
 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
 
 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.
 
 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
 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
 ~~~
 
 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
 
 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


@@ -269,9 +269,15 @@ For each VM you have the option to set a fixed size memory or asking
 {pve} to dynamically allocate memory based on the current RAM usage of the
 host. 
 
 {pve} to dynamically allocate memory based on the current RAM usage of the
 host. 
 

+.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 choosing a *fixed size memory* {pve} will simply allocate what you
 specify to your VM.
 

+.Automatic Memory Allocation
+[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
 minimum amount you specified is always available to the VM, and if RAM usage on
 // see autoballoon() in pvestatd.pm
 When choosing to *automatically allocate memory*, {pve} will make sure that the
 minimum amount you specified is always available to the VM, and if RAM usage on


@@ -311,6 +317,8 @@ of RAM available to the host.
 Network Device
 ~~~~~~~~~~~~~~
 
 Network Device
 ~~~~~~~~~~~~~~
 

+[thumbnail="gui-create-vm-network.png"]
+

 Each VM can have many _Network interface controllers_ (NIC), of four different
 types:
 
 Each VM can have many _Network interface controllers_ (NIC), of four different
 types:
 


@@ -449,10 +457,14 @@ the following command:
 
  qm set <vmid> -onboot 1
 
 
  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
 
 * *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


@@ -472,6 +484,24 @@ start after those where the parameter is set, and this parameter only
 makes sense between the machines running locally on a host, and not
 cluster-wide.
 
 makes sense between the machines running locally on a host, and not
 cluster-wide.
 

+
+[[qm_migration]]
+Migration
+---------
+
+If you have a cluster, you can migrate your VM to another host with
+
+ qm migrate <vmid> <target>
+
+When your VM is running and it has no local resources defined (such as disks
+on local storage, passed through devices, etc.) you can initiate a live
+migration with the -online flag.
+
+If you have local resources, you can still offline migrate your VMs,
+as long as all disk are on storages, which are defined on both hosts.
+Then the migration will copy the disk over the network to the target host.
+
+

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