Driver¶
See also: How to set up the driver,
local.driver, Instance, Platform
A driver is the technology through which Multipass emulates a running machine. It corresponds to a hypervisor or intermediary technology to run virtual machines. The driver is sometimes also referred to as “backend”.
Multipass relies on a driver to operate. It supports multiple drivers, but it runs with a single driver at a time. There is a Multipass setting to select the driver: local.driver.
On some platforms, it is possible to select a driver during installation. Until it is manually set, a platform-appropriate default driver is used.
Supported drivers¶
Different sets of drivers are available on different platforms:
On Linux, Multipass uses QEMU.
On macOS, the options are QEMU, the Apple Virtualization framework, and VirtualBox (deprecated).
On Windows, Multipass supports the Host Compute System API, Hyper-V (deprecated), and VirtualBox (deprecated).
Default drivers¶
When Multipass is installed, the following drivers are selected by default:
On Linux and macOS,
qemuis used.On Windows,
hcsis the default.
Deprecated drivers¶
Linux:
As of Multipass version 1.16, LXD and libvirt are no longer available.
macOS:
As of Multipass version 1.13, Hyperkit is no longer available.
As of Multipass version 1.17, VirtualBox is deprecated (see Move from VirtualBox to another driver).
Windows:
As of Multipass version 1.17, the
hypervdriver is deprecated in favor of thehcsdriver (see Migrate from Hyper-V to the HCS driver on Windows)Also as of Multipass version 1.17 VirtualBox is deprecated with no migration planned (see Move from VirtualBox to another driver).
Instance scopes¶
In general, Multipass instances are tied to a single driver, with the Exceptions listed below. The set of instances that were launched with one driver are available only while that driver is in use.
When a new driver is selected, Multipass switches to a separate instance scope. There, the set of existing instances is empty to begin with. Users can launch instances with the same name in different drivers and changes to instances with one driver have no effect on the instances of another.
Nonetheless, instances are preserved across drivers. After switching back to a previously-used driver, Multipass restores the corresponding instance scope. It attempts to restore the state instances were in just before the switch and users can interact with them just as before.
Exceptions¶
There are two exceptions to the above:
On macOS, and only on Multipass version 1.12, stopped Hyperkit instances are automatically migrated to QEMU by Multipass’s version 1.12 (see How to migrate from Hyperkit to QEMU on macOS).
On Windows, and only on Multipass version 1.17, stopped
hypervinstances are automatically migrated to thehcsdriver by Multipass’s version 1.17 (see Migrate from Hyper-V to the HCS driver on Windows).
Feature disparities¶
While we strive to offer a uniform interface across the board, not all features are available on all backends and there are some behaviour differences:
Feature |
Not supported on… |
Notes |
|---|---|---|
Native mounts |
|
This affects the |
Snapshots |
|
This affects the |
Suspend |
|
This affects the |
Note
There are also feature disparities depending on the host platform. See Platform for more details.