We are pleased to announce the release of MirageOS 3.6.0. This release updates MirageOS to support Solo5 0.6.0 and later.
New features:
- Support for the Solo5
spt
(sandboxed process tender) target viamirage configure -t spt
. Thespt
target runs MirageOS unikernels in a minimal strict seccomp sandbox on Linuxx86_64
,aarch64
andppc64le
hosts. - Support for the Solo5 application manifest, enabling support for multiple network and block storage devices on the
hvt
,spt
andmuen
targets. Thegenode
andvirtio
targets are still limited to using a single network or block storage device. - Several notable security enhancements to Solo5 targets, such as enabling stack smashing protection throughout the toolchain by default and improved page protections on some targets. For details, please refer to the Solo5 0.6.0 release notes.
Additional user-visible changes:
- Solo5 0.6.0 has removed the compile-time specialization of the
solo5-hvt
tender. As a result, asolo5-hvt
binary is no longer built atmirage build
time. Use thesolo5-hvt
binary installed in your$PATH
by OPAM to run the unikernel. -
mirage build
now produces silentocamlbuild
output by default. To get the old behaviour, run with--verbose
or set the log level toinfo
ordebug
. - New functions
Mirage_key.is_solo5
andMirage_key.is_xen
, analogous toMirage_key.is_unix
.
Thanks to @hannes for help with the release engineering for MirageOS 3.6.0.