[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[MirageOS-devel] [ANN] mirage 3.2.0 released

  • To: mirageos-devel@xxxxxxxxxxxxxxxxxxxx
  • From: Hannes Mehnert <hannes@xxxxxxxxxxx>
  • Date: Mon, 24 Sep 2018 09:42:25 +0200
  • Delivery-date: Mon, 24 Sep 2018 07:43:25 +0000
  • List-id: Developer list for MirageOS <mirageos-devel.lists.xenproject.org>
  • Openpgp: id=11B5464249B5BD858FFF6328BC896588DF7C28EE


it is my pleasure to announce that mirage 3.2.0 has been released to
opam-repository(*).  This release contains breaking changes with earlier

It requires solo5 0.4.0, which renames "ukvm" to "hvt" (thanks to Martin
It requires tcpip 3.5.0, which removes complexity from stack
initialisation (thanks to Hannes Mehnert)

Mirage now comes with the hvt (Hardware Virtualization Tender) target
(earlier known as ukvm), which works on Linux/KVM, OpenBSD/VMM (since
6.4), and FreeBSD/VMM|BHyve.

# Upgrading from Mirage 3.1.x or earlier

Due to conflicting packages, opam will not upgrade mirage to version
3.2.0 or newer if a version of mirage-solo5 older than 0.4.0 is
installed in the switch. To perform the upgrade you must run `opam
upgrade mirage` explicitly.

## Changes required to rebuild and run ukvm unikernels

As of Solo5 0.4.0, the ukvm target has been renamed to hvt. If you are
working out of an existing, dirty, source tree, you should initially run:

mirage configure -t hvt
mirage clean
mirage configure -t hvt

and then proceed as normal. If you are working with a clean source tree,
then simply configuring with the new hvt target is sufficient:

`mirage configure -t hvt`

Note that the build products have changed:

The unikernel binary is now named `<unikernel>.hvt`,
the `ukvm-bin` binary is now named `solo5-hvt`.

# adapt to mirage-protocols, mirage-stack, tcpip changes

This is a breaking change: mirage 3.2.0 requires mirage-protocols 1.4.0,
mirage-stack 1.3.0, and tcpip 3.5.0 to work (charru-client-mirage 0.10
and mirage-qubes-ipv4 0.6 are adapted to the changes).  An older mirage
won't be able to use these new libraries correctly.  Conflicts were
introduced in the opam-repository.

In more detail,  direct and socket stack initialisation changed, which
is automatically generated by the mirage tool for each unikernel (as
part of `main.ml`).  A record was built up, which is no longer needed.

Several unneeded type aliases were removed:
  `netif` from Mirage_protocols.ETHIF
  `ethif` and `prefix` from Mirage_protocols.IP
  `ip` from Mirage_protocols.{UDP,TCP}
  `netif` and `'netif config` from Mirage_stack.V4
  `'netif stackv4_config` and `socket_stack_config` in Mirage_stack



* which since a week switched to opam 2.0, and thus you'll only see
updates if you upgraded your opam to 2.0 (you can do so by following the
instructions on https://opam.ocaml.org/blog/opam-2-0-0/)

MirageOS-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.