Multipass version 1.10.0
A new Multipass release!
There are some significant additions to this release:
- Modifying instances is now supported. You can modify the number of cores, memory, and disk space allocated to an instance. Note that instances can only be modified when they are not running and disk space can only be increased. See https://multipass.run/docs/modify-an-instance#heading--set-the-cpu-ram-or-disk-of-an-instance for more information.
- On Windows, Multipass now supports creating generation 2 virtual machines in Hyper-V along with disabling dynamic memory. These apply only to new instances launched and not existing instances.
- Specifying mounts at launch time is now possible via
multipass launch --mount
. - It’s now possible to use a URL when using the
--cloud-init
option inlaunch
. - There are few enhancements to the
multipass exec
andmultipass alias
commands. See https://multipass.run/docs/exec-command and `multipass alias` command | Multipass documentation respectively for details.
Installers for Windows and macOS installers are now available, and the Snap is available in the stable
snap channel:
snap refresh multipass --stable
or
snap install multipass --stable
Note: This will be the last release that supports macOS 10.14. Starting with version 1.11, Multiipass will only support macOS 10.15 and higher.
More highlights:
- Launching an instance using the
lxd
driver will now use the general cloud image instead of the KVM image. This is due to the KVM kernel in the image having unfixed bugs. (#2491) multipass transfer
now handles a directory being a target. (#1165)- The Multipass icon is now shown in the “Windows Apps & Features” Multipass entry. (#2595)
- It’s now possible to
unalias
all defined aliases at once. (#2298)
Notable bug fixes:
- LXD VMs constructed with wrong storage pool on daemon startup (#2591)
- [lxd] long startup delay due to image refresh (#2516)
- [macos/qemu] Multiple qemu processes running for the same instance (#2592)
- multipass launch --help-all launches an instance (#2635)
- [blueprints] No error message when Blueprint name doesn’t match instance name in yaml (#2542)
You can find the full list of changes since 1.9.2 in our v1.10.0 milestone and even more detailed in the full commit log.
Feedback
Please file issues here for problems and feature requests, or come to our discourse to chat. We’re also on #multipass
on Libera Chat. See you there