1 [[chapter_virtual_machines]]
10 qm - Qemu/KVM Virtual Machine Manager
16 include::qm.1-synopsis.adoc[]
22 Qemu/KVM Virtual Machines
23 =========================
28 // http://pve.proxmox.com/wiki/Container_and_Full_Virtualization
29 // http://pve.proxmox.com/wiki/KVM
30 // http://pve.proxmox.com/wiki/Qemu_Server
32 Qemu (short form for Quick Emulator) is an open source hypervisor that emulates a
33 physical computer. From the perspective of the host system where Qemu is
34 running, Qemu is a user program which has access to a number of local resources
35 like partitions, files, network cards which are then passed to an
36 emulated computer which sees them as if they were real devices.
38 A guest operating system running in the emulated computer accesses these
39 devices, and runs as it were running on real hardware. For instance you can pass
40 an iso image as a parameter to Qemu, and the OS running in the emulated computer
41 will see a real CDROM inserted in a CD drive.
43 Qemu can emulate a great variety of hardware from ARM to Sparc, but {pve} is
44 only concerned with 32 and 64 bits PC clone emulation, since it represents the
45 overwhelming majority of server hardware. The emulation of PC clones is also one
46 of the fastest due to the availability of processor extensions which greatly
47 speed up Qemu when the emulated architecture is the same as the host
50 NOTE: You may sometimes encounter the term _KVM_ (Kernel-based Virtual Machine).
51 It means that Qemu is running with the support of the virtualization processor
52 extensions, via the Linux kvm module. In the context of {pve} _Qemu_ and
53 _KVM_ can be used interchangeably as Qemu in {pve} will always try to load the kvm
56 Qemu inside {pve} runs as a root process, since this is required to access block
60 Emulated devices and paravirtualized devices
61 --------------------------------------------
63 The PC hardware emulated by Qemu includes a mainboard, network controllers,
64 scsi, ide and sata controllers, serial ports (the complete list can be seen in
65 the `kvm(1)` man page) all of them emulated in software. All these devices
66 are the exact software equivalent of existing hardware devices, and if the OS
67 running in the guest has the proper drivers it will use the devices as if it
68 were running on real hardware. This allows Qemu to runs _unmodified_ operating
71 This however has a performance cost, as running in software what was meant to
72 run in hardware involves a lot of extra work for the host CPU. To mitigate this,
73 Qemu can present to the guest operating system _paravirtualized devices_, where
74 the guest OS recognizes it is running inside Qemu and cooperates with the
77 Qemu relies on the virtio virtualization standard, and is thus able to present
78 paravirtualized virtio devices, which includes a paravirtualized generic disk
79 controller, a paravirtualized network card, a paravirtualized serial port,
80 a paravirtualized SCSI controller, etc ...
82 It is highly recommended to use the virtio devices whenever you can, as they
83 provide a big performance improvement. Using the virtio generic disk controller
84 versus an emulated IDE controller will double the sequential write throughput,
85 as measured with `bonnie++(8)`. Using the virtio network interface can deliver
86 up to three times the throughput of an emulated Intel E1000 network card, as
87 measured with `iperf(1)`. footnote:[See this benchmark on the KVM wiki
88 http://www.linux-kvm.org/page/Using_VirtIO_NIC]
91 [[qm_virtual_machines_settings]]
92 Virtual Machines Settings
93 -------------------------
95 Generally speaking {pve} tries to choose sane defaults for virtual machines
96 (VM). Make sure you understand the meaning of the settings you change, as it
97 could incur a performance slowdown, or putting your data at risk.
100 [[qm_general_settings]]
104 [thumbnail="gui-create-vm-general.png"]
106 General settings of a VM include
108 * the *Node* : the physical server on which the VM will run
109 * the *VM ID*: a unique number in this {pve} installation used to identify your VM
110 * *Name*: a free form text string you can use to describe the VM
111 * *Resource Pool*: a logical group of VMs
118 [thumbnail="gui-create-vm-os.png"]
120 When creating a VM, setting the proper Operating System(OS) allows {pve} to
121 optimize some low level parameters. For instance Windows OS expect the BIOS
122 clock to use the local time, while Unix based OS expect the BIOS clock to have
130 Qemu can emulate a number of storage controllers:
132 * the *IDE* controller, has a design which goes back to the 1984 PC/AT disk
133 controller. Even if this controller has been superseded by recent designs,
134 each and every OS you can think of has support for it, making it a great choice
135 if you want to run an OS released before 2003. You can connect up to 4 devices
138 * the *SATA* (Serial ATA) controller, dating from 2003, has a more modern
139 design, allowing higher throughput and a greater number of devices to be
140 connected. You can connect up to 6 devices on this controller.
142 * the *SCSI* controller, designed in 1985, is commonly found on server grade
143 hardware, and can connect up to 14 storage devices. {pve} emulates by default a
144 LSI 53C895A controller.
146 A SCSI controller of type _VirtIO SCSI_ is the recommended setting if you aim for
147 performance and is automatically selected for newly created Linux VMs since
148 {pve} 4.3. Linux distributions have support for this controller since 2012, and
149 FreeBSD since 2014. For Windows OSes, you need to provide an extra iso
150 containing the drivers during the installation.
151 // https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows#During_windows_installation.
152 If you aim at maximum performance, you can select a SCSI controller of type
153 _VirtIO SCSI single_ which will allow you to select the *IO Thread* option.
154 When selecting _VirtIO SCSI single_ Qemu will create a new controller for
155 each disk, instead of adding all disks to the same controller.
157 * The *VirtIO Block* controller, often just called VirtIO or virtio-blk,
158 is an older type of paravirtualized controller. It has been superseded by the
159 VirtIO SCSI Controller, in terms of features.
161 [thumbnail="gui-create-vm-hard-disk.png"]
162 On each controller you attach a number of emulated hard disks, which are backed
163 by a file or a block device residing in the configured storage. The choice of
164 a storage type will determine the format of the hard disk image. Storages which
165 present block devices (LVM, ZFS, Ceph) will require the *raw disk image format*,
166 whereas files based storages (Ext4, NFS, GlusterFS) will let you to choose
167 either the *raw disk image format* or the *QEMU image format*.
169 * the *QEMU image format* is a copy on write format which allows snapshots, and
170 thin provisioning of the disk image.
171 * the *raw disk image* is a bit-to-bit image of a hard disk, similar to what
172 you would get when executing the `dd` command on a block device in Linux. This
173 format does not support thin provisioning or snapshots by itself, requiring
174 cooperation from the storage layer for these tasks. It may, however, be up to
175 10% faster than the *QEMU image format*. footnote:[See this benchmark for details
176 http://events.linuxfoundation.org/sites/events/files/slides/CloudOpen2013_Khoa_Huynh_v3.pdf]
177 * the *VMware image format* only makes sense if you intend to import/export the
178 disk image to other hypervisors.
180 Setting the *Cache* mode of the hard drive will impact how the host system will
181 notify the guest systems of block write completions. The *No cache* default
182 means that the guest system will be notified that a write is complete when each
183 block reaches the physical storage write queue, ignoring the host page cache.
184 This provides a good balance between safety and speed.
186 If you want the {pve} backup manager to skip a disk when doing a backup of a VM,
187 you can set the *No backup* option on that disk.
189 If you want the {pve} storage replication mechanism to skip a disk when starting
190 a replication job, you can set the *Skip replication* option on that disk.
191 As of {pve} 5.0, replication requires the disk images to be on a storage of type
192 `zfspool`, so adding a disk image to other storages when the VM has replication
193 configured requires to skip replication for this disk image.
195 If your storage supports _thin provisioning_ (see the storage chapter in the
196 {pve} guide), and your VM has a *SCSI* controller you can activate the *Discard*
197 option on the hard disks connected to that controller. With *Discard* enabled,
198 when the filesystem of a VM marks blocks as unused after removing files, the
199 emulated SCSI controller will relay this information to the storage, which will
200 then shrink the disk image accordingly.
203 The option *IO Thread* can only be used when using a disk with the
204 *VirtIO* controller, or with the *SCSI* controller, when the emulated controller
205 type is *VirtIO SCSI single*.
206 With this enabled, Qemu creates one I/O thread per storage controller,
207 instead of a single thread for all I/O, so it increases performance when
208 multiple disks are used and each disk has its own storage controller.
209 Note that backups do not currently work with *IO Thread* enabled.
216 [thumbnail="gui-create-vm-cpu.png"]
218 A *CPU socket* is a physical slot on a PC motherboard where you can plug a CPU.
219 This CPU can then contain one or many *cores*, which are independent
220 processing units. Whether you have a single CPU socket with 4 cores, or two CPU
221 sockets with two cores is mostly irrelevant from a performance point of view.
222 However some software licenses depend on the number of sockets a machine has,
223 in that case it makes sense to set the number of sockets to what the license
226 Increasing the number of virtual cpus (cores and sockets) will usually provide a
227 performance improvement though that is heavily dependent on the use of the VM.
228 Multithreaded applications will of course benefit from a large number of
229 virtual cpus, as for each virtual cpu you add, Qemu will create a new thread of
230 execution on the host system. If you're not sure about the workload of your VM,
231 it is usually a safe bet to set the number of *Total cores* to 2.
233 NOTE: It is perfectly safe to set the _overall_ number of total cores in all
234 your VMs to be greater than the number of of cores you have on your server (i.e.
235 4 VMs with each 4 Total cores running in a 8 core machine is OK) In that case
236 the host system will balance the Qemu execution threads between your server
237 cores just like if you were running a standard multithreaded application.
238 However {pve} will prevent you to allocate on a _single_ machine more vcpus than
239 physically available, as this will only bring the performance down due to the
240 cost of context switches.
242 [[qm_cpu_resource_limits]]
246 In addition to the number of virtual cores, you can configure how much resources
247 a VM can get in relation to the host CPU time and also in relation to other
249 With the *cpulimit* (`Host CPU Time') option you can limit how much CPU time the
250 whole VM can use on the host. It is a floating point value representing CPU
251 time in percent, so `1.0` is equal to `100%`, `2.5` to `250%` and so on. If a
252 single process would fully use one single core it would have `100%` CPU Time
253 usage. If a VM with four cores utilizes all its cores fully it would
254 theoretically use `400%`. In reality the usage may be even a bit higher as Qemu
255 can have additional threads for VM peripherals besides the vCPU core ones.
256 This setting can be useful if a VM should have multiple vCPUs, as it runs a few
257 processes in parallel, but the VM as a whole should not be able to run all
258 vCPUs at 100% at the same time. Using a specific example: lets say we have a VM
259 which would profit from having 8 vCPUs, but at no time all of those 8 cores
260 should run at full load - as this would make the server so overloaded that
261 other VMs and CTs would get to less CPU. So, we set the *cpulimit* limit to
262 `4.0` (=400%). If all cores do the same heavy work they would all get 50% of a
263 real host cores CPU time. But, if only 4 would do work they could still get
264 almost 100% of a real core each.
266 NOTE: VMs can, depending on their configuration, use additional threads e.g.,
267 for networking or IO operations but also live migration. Thus a VM can show up
268 to use more CPU time than just its virtual CPUs could use. To ensure that a VM
269 never uses more CPU time than virtual CPUs assigned set the *cpulimit* setting
270 to the same value as the total core count.
272 The second CPU resource limiting setting, *cpuunits* (nowadays often called CPU
273 shares or CPU weight), controls how much CPU time a VM gets in regards to other
274 VMs running. It is a relative weight which defaults to `1024`, if you increase
275 this for a VM it will be prioritized by the scheduler in comparison to other
276 VMs with lower weight. E.g., if VM 100 has set the default 1024 and VM 200 was
277 changed to `2048`, the latter VM 200 would receive twice the CPU bandwidth than
280 For more information see `man systemd.resource-control`, here `CPUQuota`
281 corresponds to `cpulimit` and `CPUShares` corresponds to our `cpuunits`
282 setting, visit its Notes section for references and implementation details.
287 Qemu can emulate a number different of *CPU types* from 486 to the latest Xeon
288 processors. Each new processor generation adds new features, like hardware
289 assisted 3d rendering, random number generation, memory protection, etc ...
290 Usually you should select for your VM a processor type which closely matches the
291 CPU of the host system, as it means that the host CPU features (also called _CPU
292 flags_ ) will be available in your VMs. If you want an exact match, you can set
293 the CPU type to *host* in which case the VM will have exactly the same CPU flags
296 This has a downside though. If you want to do a live migration of VMs between
297 different hosts, your VM might end up on a new system with a different CPU type.
298 If the CPU flags passed to the guest are missing, the qemu process will stop. To
299 remedy this Qemu has also its own CPU type *kvm64*, that {pve} uses by defaults.
300 kvm64 is a Pentium 4 look a like CPU type, which has a reduced CPU flags set,
301 but is guaranteed to work everywhere.
303 In short, if you care about live migration and moving VMs between nodes, leave
304 the kvm64 default. If you don’t care about live migration or have a homogeneous
305 cluster where all nodes have the same CPU, set the CPU type to host, as in
306 theory this will give your guests maximum performance.
310 You can also optionally emulate a *NUMA*
311 footnote:[https://en.wikipedia.org/wiki/Non-uniform_memory_access] architecture
312 in your VMs. The basics of the NUMA architecture mean that instead of having a
313 global memory pool available to all your cores, the memory is spread into local
314 banks close to each socket.
315 This can bring speed improvements as the memory bus is not a bottleneck
316 anymore. If your system has a NUMA architecture footnote:[if the command
317 `numactl --hardware | grep available` returns more than one node, then your host
318 system has a NUMA architecture] we recommend to activate the option, as this
319 will allow proper distribution of the VM resources on the host system.
320 This option is also required to hot-plug cores or RAM in a VM.
322 If the NUMA option is used, it is recommended to set the number of sockets to
323 the number of sockets of the host system.
328 Modern operating systems introduced the capability to hot-plug and, to a
329 certain extent, hot-unplug CPUs in a running systems. Virtualisation allows us
330 to avoid a lot of the (physical) problems real hardware can cause in such
332 Still, this is a rather new and complicated feature, so its use should be
333 restricted to cases where its absolutely needed. Most of the functionality can
334 be replicated with other, well tested and less complicated, features, see
335 xref:qm_cpu_resource_limits[Resource Limits].
337 In {pve} the maximal number of plugged CPUs is always `cores * sockets`.
338 To start a VM with less than this total core count of CPUs you may use the
339 *vpus* setting, it denotes how many vCPUs should be plugged in at VM start.
341 Currently only this feature is only supported on Linux, a kernel newer than 3.10
342 is needed, a kernel newer than 4.7 is recommended.
344 You can use a udev rule as follow to automatically set new CPUs as online in
348 SUBSYSTEM=="cpu", ACTION=="add", TEST=="online", ATTR{online}=="0", ATTR{online}="1"
351 Save this under /etc/udev/rules.d/ as a file ending in `.rules`.
353 Note: CPU hot-remove is machine dependent and requires guest cooperation.
354 The deletion command does not guarantee CPU removal to actually happen,
355 typically it's a request forwarded to guest using target dependent mechanism,
356 e.g., ACPI on x86/amd64.
363 For each VM you have the option to set a fixed size memory or asking
364 {pve} to dynamically allocate memory based on the current RAM usage of the
367 .Fixed Memory Allocation
368 [thumbnail="gui-create-vm-memory-fixed.png"]
370 When choosing a *fixed size memory* {pve} will simply allocate what you
373 Even when using a fixed memory size, the ballooning device gets added to the
374 VM, because it delivers useful information such as how much memory the guest
376 In general, you should leave *ballooning* enabled, but if you want to disable
377 it (e.g. for debugging purposes), simply uncheck
382 in the configuration.
384 .Automatic Memory Allocation
385 [thumbnail="gui-create-vm-memory-dynamic.png", float="left"]
387 // see autoballoon() in pvestatd.pm
388 When choosing to *automatically allocate memory*, {pve} will make sure that the
389 minimum amount you specified is always available to the VM, and if RAM usage on
390 the host is below 80%, will dynamically add memory to the guest up to the
391 maximum memory specified.
393 When the host is becoming short on RAM, the VM will then release some memory
394 back to the host, swapping running processes if needed and starting the oom
395 killer in last resort. The passing around of memory between host and guest is
396 done via a special `balloon` kernel driver running inside the guest, which will
397 grab or release memory pages from the host.
398 footnote:[A good explanation of the inner workings of the balloon driver can be found here https://rwmj.wordpress.com/2010/07/17/virtio-balloon/]
400 When multiple VMs use the autoallocate facility, it is possible to set a
401 *Shares* coefficient which indicates the relative amount of the free host memory
402 that each VM should take. Suppose for instance you have four VMs, three of them
403 running a HTTP server and the last one is a database server. To cache more
404 database blocks in the database server RAM, you would like to prioritize the
405 database VM when spare RAM is available. For this you assign a Shares property
406 of 3000 to the database VM, leaving the other VMs to the Shares default setting
407 of 1000. The host server has 32GB of RAM, and is currently using 16GB, leaving 32
408 * 80/100 - 16 = 9GB RAM to be allocated to the VMs. The database VM will get 9 *
409 3000 / (3000 + 1000 + 1000 + 1000) = 4.5 GB extra RAM and each HTTP server will
412 All Linux distributions released after 2010 have the balloon kernel driver
413 included. For Windows OSes, the balloon driver needs to be added manually and can
414 incur a slowdown of the guest, so we don't recommend using it on critical
416 // see https://forum.proxmox.com/threads/solved-hyper-threading-vs-no-hyper-threading-fixed-vs-variable-memory.20265/
418 When allocating RAM to your VMs, a good rule of thumb is always to leave 1GB
419 of RAM available to the host.
422 [[qm_network_device]]
426 [thumbnail="gui-create-vm-network.png"]
428 Each VM can have many _Network interface controllers_ (NIC), of four different
431 * *Intel E1000* is the default, and emulates an Intel Gigabit network card.
432 * the *VirtIO* paravirtualized NIC should be used if you aim for maximum
433 performance. Like all VirtIO devices, the guest OS should have the proper driver
435 * the *Realtek 8139* emulates an older 100 MB/s network card, and should
436 only be used when emulating older operating systems ( released before 2002 )
437 * the *vmxnet3* is another paravirtualized device, which should only be used
438 when importing a VM from another hypervisor.
440 {pve} will generate for each NIC a random *MAC address*, so that your VM is
441 addressable on Ethernet networks.
443 The NIC you added to the VM can follow one of two different models:
445 * in the default *Bridged mode* each virtual NIC is backed on the host by a
446 _tap device_, ( a software loopback device simulating an Ethernet NIC ). This
447 tap device is added to a bridge, by default vmbr0 in {pve}. In this mode, VMs
448 have direct access to the Ethernet LAN on which the host is located.
449 * in the alternative *NAT mode*, each virtual NIC will only communicate with
450 the Qemu user networking stack, where a built-in router and DHCP server can
451 provide network access. This built-in DHCP will serve addresses in the private
452 10.0.2.0/24 range. The NAT mode is much slower than the bridged mode, and
453 should only be used for testing.
455 You can also skip adding a network device when creating a VM by selecting *No
459 If you are using the VirtIO driver, you can optionally activate the
460 *Multiqueue* option. This option allows the guest OS to process networking
461 packets using multiple virtual CPUs, providing an increase in the total number
462 of packets transferred.
464 //http://blog.vmsplice.net/2011/09/qemu-internals-vhost-architecture.html
465 When using the VirtIO driver with {pve}, each NIC network queue is passed to the
466 host kernel, where the queue will be processed by a kernel thread spawn by the
467 vhost driver. With this option activated, it is possible to pass _multiple_
468 network queues to the host kernel for each NIC.
470 //https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Virtualization_Tuning_and_Optimization_Guide/sect-Virtualization_Tuning_Optimization_Guide-Networking-Techniques.html#sect-Virtualization_Tuning_Optimization_Guide-Networking-Multi-queue_virtio-net
471 When using Multiqueue, it is recommended to set it to a value equal
472 to the number of Total Cores of your guest. You also need to set in
473 the VM the number of multi-purpose channels on each VirtIO NIC with the ethtool
476 `ethtool -L ens1 combined X`
478 where X is the number of the number of vcpus of the VM.
480 You should note that setting the Multiqueue parameter to a value greater
481 than one will increase the CPU load on the host and guest systems as the
482 traffic increases. We recommend to set this option only when the VM has to
483 process a great number of incoming connections, such as when the VM is running
484 as a router, reverse proxy or a busy HTTP server doing long polling.
487 [[qm_usb_passthrough]]
491 There are two different types of USB passthrough devices:
493 * Host USB passthrough
494 * SPICE USB passthrough
496 Host USB passthrough works by giving a VM a USB device of the host.
497 This can either be done via the vendor- and product-id, or
498 via the host bus and port.
500 The vendor/product-id looks like this: *0123:abcd*,
501 where *0123* is the id of the vendor, and *abcd* is the id
502 of the product, meaning two pieces of the same usb device
505 The bus/port looks like this: *1-2.3.4*, where *1* is the bus
506 and *2.3.4* is the port path. This represents the physical
507 ports of your host (depending of the internal order of the
510 If a device is present in a VM configuration when the VM starts up,
511 but the device is not present in the host, the VM can boot without problems.
512 As soon as the device/port is available in the host, it gets passed through.
514 WARNING: Using this kind of USB passthrough means that you cannot move
515 a VM online to another host, since the hardware is only available
516 on the host the VM is currently residing.
518 The second type of passthrough is SPICE USB passthrough. This is useful
519 if you use a SPICE client which supports it. If you add a SPICE USB port
520 to your VM, you can passthrough a USB device from where your SPICE client is,
521 directly to the VM (for example an input device or hardware dongle).
528 In order to properly emulate a computer, QEMU needs to use a firmware.
529 By default QEMU uses *SeaBIOS* for this, which is an open-source, x86 BIOS
530 implementation. SeaBIOS is a good choice for most standard setups.
532 There are, however, some scenarios in which a BIOS is not a good firmware
533 to boot from, e.g. if you want to do VGA passthrough. footnote:[Alex Williamson has a very good blog entry about this.
534 http://vfio.blogspot.co.at/2014/08/primary-graphics-assignment-without-vga.html]
535 In such cases, you should rather use *OVMF*, which is an open-source UEFI implementation. footnote:[See the OVMF Project http://www.tianocore.org/ovmf/]
537 If you want to use OVMF, there are several things to consider:
539 In order to save things like the *boot order*, there needs to be an EFI Disk.
540 This disk will be included in backups and snapshots, and there can only be one.
542 You can create such a disk with the following command:
544 qm set <vmid> -efidisk0 <storage>:1,format=<format>
546 Where *<storage>* is the storage where you want to have the disk, and
547 *<format>* is a format which the storage supports. Alternatively, you can
548 create such a disk through the web interface with 'Add' -> 'EFI Disk' in the
549 hardware section of a VM.
551 When using OVMF with a virtual display (without VGA passthrough),
552 you need to set the client resolution in the OVMF menu(which you can reach
553 with a press of the ESC button during boot), or you have to choose
554 SPICE as the display type.
556 [[qm_startup_and_shutdown]]
557 Automatic Start and Shutdown of Virtual Machines
558 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
560 After creating your VMs, you probably want them to start automatically
561 when the host system boots. For this you need to select the option 'Start at
562 boot' from the 'Options' Tab of your VM in the web interface, or set it with
563 the following command:
565 qm set <vmid> -onboot 1
567 .Start and Shutdown Order
569 [thumbnail="gui-qemu-edit-start-order.png"]
571 In some case you want to be able to fine tune the boot order of your
572 VMs, for instance if one of your VM is providing firewalling or DHCP
573 to other guest systems. For this you can use the following
576 * *Start/Shutdown order*: Defines the start order priority. E.g. set it to 1 if
577 you want the VM to be the first to be started. (We use the reverse startup
578 order for shutdown, so a machine with a start order of 1 would be the last to
580 * *Startup delay*: Defines the interval between this VM start and subsequent
581 VMs starts . E.g. set it to 240 if you want to wait 240 seconds before starting
583 * *Shutdown timeout*: Defines the duration in seconds {pve} should wait
584 for the VM to be offline after issuing a shutdown command.
585 By default this value is set to 60, which means that {pve} will issue a
586 shutdown request, wait 60s for the machine to be offline, and if after 60s
587 the machine is still online will notify that the shutdown action failed.
589 NOTE: VMs managed by the HA stack do not follow the 'start on boot' and
590 'boot order' options currently. Those VMs will be skipped by the startup and
591 shutdown algorithm as the HA manager itself ensures that VMs get started and
594 Please note that machines without a Start/Shutdown order parameter will always
595 start after those where the parameter is set, and this parameter only
596 makes sense between the machines running locally on a host, and not
604 [thumbnail="gui-qemu-migrate.png"]
606 If you have a cluster, you can migrate your VM to another host with
608 qm migrate <vmid> <target>
610 There are generally two mechanisms for this
612 * Online Migration (aka Live Migration)
618 When your VM is running and it has no local resources defined (such as disks
619 on local storage, passed through devices, etc.) you can initiate a live
620 migration with the -online flag.
625 This starts a Qemu Process on the target host with the 'incoming' flag, which
626 means that the process starts and waits for the memory data and device states
627 from the source Virtual Machine (since all other resources, e.g. disks,
628 are shared, the memory content and device state are the only things left
631 Once this connection is established, the source begins to send the memory
632 content asynchronously to the target. If the memory on the source changes,
633 those sections are marked dirty and there will be another pass of sending data.
634 This happens until the amount of data to send is so small that it can
635 pause the VM on the source, send the remaining data to the target and start
636 the VM on the target in under a second.
641 For Live Migration to work, there are some things required:
643 * The VM has no local resources (e.g. passed through devices, local disks, etc.)
644 * The hosts are in the same {pve} cluster.
645 * The hosts have a working (and reliable) network connection.
646 * The target host must have the same or higher versions of the
647 {pve} packages. (It *might* work the other way, but this is never guaranteed)
652 If you have local resources, you can still offline migrate your VMs,
653 as long as all disk are on storages, which are defined on both hosts.
654 Then the migration will copy the disk over the network to the target host.
656 [[qm_copy_and_clone]]
660 [thumbnail="gui-qemu-full-clone.png"]
662 VM installation is usually done using an installation media (CD-ROM)
663 from the operation system vendor. Depending on the OS, this can be a
664 time consuming task one might want to avoid.
666 An easy way to deploy many VMs of the same type is to copy an existing
667 VM. We use the term 'clone' for such copies, and distinguish between
668 'linked' and 'full' clones.
672 The result of such copy is an independent VM. The
673 new VM does not share any storage resources with the original.
676 It is possible to select a *Target Storage*, so one can use this to
677 migrate a VM to a totally different storage. You can also change the
678 disk image *Format* if the storage driver supports several formats.
681 NOTE: A full clone need to read and copy all VM image data. This is
682 usually much slower than creating a linked clone.
685 Some storage types allows to copy a specific *Snapshot*, which
686 defaults to the 'current' VM data. This also means that the final copy
687 never includes any additional snapshots from the original VM.
692 Modern storage drivers supports a way to generate fast linked
693 clones. Such a clone is a writable copy whose initial contents are the
694 same as the original data. Creating a linked clone is nearly
695 instantaneous, and initially consumes no additional space.
698 They are called 'linked' because the new image still refers to the
699 original. Unmodified data blocks are read from the original image, but
700 modification are written (and afterwards read) from a new
701 location. This technique is called 'Copy-on-write'.
704 This requires that the original volume is read-only. With {pve} one
705 can convert any VM into a read-only <<qm_templates, Template>>). Such
706 templates can later be used to create linked clones efficiently.
709 NOTE: You cannot delete the original template while linked clones
713 It is not possible to change the *Target storage* for linked clones,
714 because this is a storage internal feature.
717 The *Target node* option allows you to create the new VM on a
718 different node. The only restriction is that the VM is on shared
719 storage, and that storage is also available on the target node.
721 To avoid resource conflicts, all network interface MAC addresses gets
722 randomized, and we generate a new 'UUID' for the VM BIOS (smbios1)
727 Virtual Machine Templates
728 -------------------------
730 One can convert a VM into a Template. Such templates are read-only,
731 and you can use them to create linked clones.
733 NOTE: It is not possible to start templates, because this would modify
734 the disk images. If you want to change the template, create a linked
735 clone and modify that.
737 Importing Virtual Machines and disk images
738 ------------------------------------------
740 A VM export from a foreign hypervisor takes usually the form of one or more disk
741 images, with a configuration file describing the settings of the VM (RAM,
743 The disk images can be in the vmdk format, if the disks come from
744 VMware or VirtualBox, or qcow2 if the disks come from a KVM hypervisor.
745 The most popular configuration format for VM exports is the OVF standard, but in
746 practice interoperation is limited because many settings are not implemented in
747 the standard itself, and hypervisors export the supplementary information
748 in non-standard extensions.
750 Besides the problem of format, importing disk images from other hypervisors
751 may fail if the emulated hardware changes too much from one hypervisor to
752 another. Windows VMs are particularly concerned by this, as the OS is very
753 picky about any changes of hardware. This problem may be solved by
754 installing the MergeIDE.zip utility available from the Internet before exporting
755 and choosing a hard disk type of *IDE* before booting the imported Windows VM.
757 Finally there is the question of paravirtualized drivers, which improve the
758 speed of the emulated system and are specific to the hypervisor.
759 GNU/Linux and other free Unix OSes have all the necessary drivers installed by
760 default and you can switch to the paravirtualized drivers right after importing
761 the VM. For Windows VMs, you need to install the Windows paravirtualized
764 GNU/Linux and other free Unix can usually be imported without hassle. Note
765 that we cannot guarantee a successful import/export of Windows VMs in all
766 cases due to the problems above.
768 Step-by-step example of a Windows OVF import
769 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
772 https://developer.microsoft.com/en-us/windows/downloads/virtual-machines/[Virtual Machines downloads]
773 to get started with Windows development.We are going to use one of these
774 to demonstrate the OVF import feature.
776 Download the Virtual Machine zip
777 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
779 After getting informed about the user agreement, choose the _Windows 10
780 Enterprise (Evaluation - Build)_ for the VMware platform, and download the zip.
782 Extract the disk image from the zip
783 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
785 Using the `unzip` utility or any archiver of your choice, unpack the zip,
786 and copy via ssh/scp the ovf and vmdk files to your {pve} host.
788 Import the Virtual Machine
789 ^^^^^^^^^^^^^^^^^^^^^^^^^^
791 This will create a new virtual machine, using cores, memory and
792 VM name as read from the OVF manifest, and import the disks to the +local-lvm+
793 storage. You have to configure the network manually.
795 qm importovf 999 WinDev1709Eval.ovf local-lvm
797 The VM is ready to be started.
799 Adding an external disk image to a Virtual Machine
800 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
802 You can also add an existing disk image to a VM, either coming from a
803 foreign hypervisor, or one that you created yourself.
805 Suppose you created a Debian/Ubuntu disk image with the 'vmdebootstrap' tool:
807 vmdebootstrap --verbose \
808 --size 10G --serial-console \
809 --grub --no-extlinux \
810 --package openssh-server \
811 --package avahi-daemon \
812 --package qemu-guest-agent \
813 --hostname vm600 --enable-dhcp \
814 --customize=./copy_pub_ssh.sh \
815 --sparse --image vm600.raw
817 You can now create a new target VM for this image.
819 qm create 600 --net0 virtio,bridge=vmbr0 --name vm600 --serial0 socket \
820 --bootdisk scsi0 --scsihw virtio-scsi-pci --ostype l26
822 Add the disk image as +unused0+ to the VM, using the storage +pvedir+:
824 qm importdisk 600 vm600.raw pvedir
826 Finally attach the unused disk to the SCSI controller of the VM:
828 qm set 600 --scsi0 pvedir:600/vm-600-disk-1.raw
830 The VM is ready to be started.
832 Managing Virtual Machines with `qm`
833 ------------------------------------
835 qm is the tool to manage Qemu/Kvm virtual machines on {pve}. You can
836 create and destroy virtual machines, and control execution
837 (start/stop/suspend/resume). Besides that, you can use qm to set
838 parameters in the associated config file. It is also possible to
839 create and delete virtual disks.
844 Using an iso file uploaded on the 'local' storage, create a VM
845 with a 4 GB IDE disk on the 'local-lvm' storage
847 qm create 300 -ide0 local-lvm:4 -net0 e1000 -cdrom local:iso/proxmox-mailgateway_2.1.iso
853 Send a shutdown request, then wait until the VM is stopped.
855 qm shutdown 300 && qm wait 300
857 Same as above, but only wait for 40 seconds.
859 qm shutdown 300 && qm wait 300 -timeout 40
866 VM configuration files are stored inside the Proxmox cluster file
867 system, and can be accessed at `/etc/pve/qemu-server/<VMID>.conf`.
868 Like other files stored inside `/etc/pve/`, they get automatically
869 replicated to all other cluster nodes.
871 NOTE: VMIDs < 100 are reserved for internal purposes, and VMIDs need to be
874 .Example VM Configuration
882 net0: e1000=EE:D2:28:5F:B6:3E,bridge=vmbr0
883 virtio0: local:vm-100-disk-1,size=32G
886 Those configuration files are simple text files, and you can edit them
887 using a normal text editor (`vi`, `nano`, ...). This is sometimes
888 useful to do small corrections, but keep in mind that you need to
889 restart the VM to apply such changes.
891 For that reason, it is usually better to use the `qm` command to
892 generate and modify those files, or do the whole thing using the GUI.
893 Our toolkit is smart enough to instantaneously apply most changes to
894 running VM. This feature is called "hot plug", and there is no
895 need to restart the VM in that case.
901 VM configuration files use a simple colon separated key/value
902 format. Each line has the following format:
909 Blank lines in those files are ignored, and lines starting with a `#`
910 character are treated as comments and are also ignored.
917 When you create a snapshot, `qm` stores the configuration at snapshot
918 time into a separate snapshot section within the same configuration
919 file. For example, after creating a snapshot called ``testsnapshot'',
920 your configuration file will look like this:
922 .VM configuration with snapshot
936 There are a few snapshot related properties like `parent` and
937 `snaptime`. The `parent` property is used to store the parent/child
938 relationship between snapshots. `snaptime` is the snapshot creation
939 time stamp (Unix epoch).
946 include::qm.conf.5-opts.adoc[]
952 Online migrations, snapshots and backups (`vzdump`) set a lock to
953 prevent incompatible concurrent actions on the affected VMs. Sometimes
954 you need to remove such a lock manually (e.g., after a power failure).
958 CAUTION: Only do that if you are sure the action which set the lock is
967 `/etc/pve/qemu-server/<VMID>.conf`::
969 Configuration file for the VM '<VMID>'.
972 include::pve-copyright.adoc[]