[Mirage 3.x] Port to new Mirage/Xen platform stack #1183
Conversation
|
Also note that I have not updated the libvirt XML generation code which is probably wrong; needs someone with a libvirt + Xen setup to test this. |
mato
force-pushed
the
3.8+xen-pvh-via-solo5
branch
from
0fe90e8
to
b31f18e
Compare
|
I retargeted the 3 branch of this repository (3.7 and 3.8 no longer exist now). I pushed a commit to not link the tcpip.xen sublibrary anymore -- in mirage-xen 6.0.0 the checksum C code is provided by mirage-xen itself. |
hannesm
force-pushed
the
3.8+xen-pvh-via-solo5
branch
from
fe8b239
to
69c985e
Compare
This adapts the `mirage` front-end tool to the new Mirage/Xen platform stack (see mirage#1159). User-visible changes: - `.xe` (Xenserver) filegeneration has been removed, I have no way to test this. - "Unknown" argument filtering in `Bootvar` / `argv` has been removed, this was causing problems and I do not know of any users apart from Qubes OS where this can be solved differently, see comments in mirage#1159. Note that Xen unikernels now include a dummy Solo5 manifest to keep the rest of the build system and Solo5 layers happy; this does not contain any devices as they are not required and Xen device naming does not follow Solo5 requirements.
Thus, tcpip.xen is not needed to be linked anymore.
…unds for the upcoming release
hannesm
force-pushed
the
3.8+xen-pvh-via-solo5
branch
from
69c985e
to
54c6eef
Compare
|
I rebased on top of the 3 branch, and adjusted the version constraints for implementation packages (mirage-net-xen etc.) - which are now released to opam-repository. I expect the CI building mirage-skeleton to succeed, and this being ready to be merged and released (pending a changes entry). |
|
I have tested So, we're good to go for merging and releasing! 🎉 |
These two things are hardly related, keep them separate
hannesm
force-pushed
the
3.8+xen-pvh-via-solo5
branch
from
45fb51b
to
547546b
Compare
hannesm
force-pushed
the
3.8+xen-pvh-via-solo5
branch
from
6a59430
to
af9ead6
Compare
hannesm
force-pushed
the
3.8+xen-pvh-via-solo5
branch
from
af9ead6
to
5ac2758
Compare
mirage does not contain any tests, avoid unneccessary rebuilds
This adapts the
miragefront-end tool to the new Mirage/Xen platform stack (see #1159).User-visible changes:
.xe(Xenserver) filegeneration has been removed, I have no way to test this.Bootvar/argvhas been removed, this was causing problems and I do not know of any users apart from Qubes OS where this can be solved differently, see comments in Xen PVH: Third time lucky #1159.Note that Xen unikernels now include a dummy Solo5 manifest to keep the rest of the build system and Solo5 layers happy; this does not contain any devices as they are not required and Xen device naming does not follow Solo5 requirements.