General Settings
~~~~~~~~~~~~~~~~
-[thumbnail="qm-general-settings.png"]
+[thumbnail="gui-create-vm-general.png"]
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
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
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
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
Network Device
~~~~~~~~~~~~~~
+[thumbnail="gui-create-vm-network.png"]
+
Each VM can have many _Network interface controllers_ (NIC), of four different
types: