alpha
Login
or
Join now
gazagnaire.org
/
ocaml-solo5
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
Solo5 hvt ABI and MFT1/ABI1 note format as wire codecs
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
Overview
Issues
Pulls
Pipelines
ocaml-solo5
/
scripts
2 files
at
main
Thomas Gazagnaire
solo5: update to Solo5 v0.12.0 and add a power-off watchdog
2w ago
5f1e1398
dune
solo5: update to Solo5 v0.12.0 and add a power-off watchdog Solo5 v0.11 extended struct hvt_boot_info with ring-I/O feature negotiation, so the refreshed reference headers grow the boot-info codec by host_features, guest_features and net_ring. The tenders offer no features and a v0.11+ guest answers by falling back to hypercall I/O; such guests also reserve 2 MiB of BSS for ring write buffers, so the boot harnesses give the real unikernels more RAM. The tender watchdog returns, this time counting only time spent inside the guest: the budget covers a single vcpu-run entry with no VM exit, so a guest blocked host-side in a long POLL is never killed, the accounting flaw that got the old per-hypercall watchdog removed. Both backends cancel the run from a watchdog thread (hv_vcpus_exit on hvf, SIGURG on kvm, its syscalls allowlisted only when armed), and the boot harnesses assert the watchdog's own diagnostic for runaway guests instead of relying on shell timeouts.
2 weeks ago
import.ml
solo5: update to Solo5 v0.12.0 and add a power-off watchdog Solo5 v0.11 extended struct hvt_boot_info with ring-I/O feature negotiation, so the refreshed reference headers grow the boot-info codec by host_features, guest_features and net_ring. The tenders offer no features and a v0.11+ guest answers by falling back to hypercall I/O; such guests also reserve 2 MiB of BSS for ring write buffers, so the boot harnesses give the real unikernels more RAM. The tender watchdog returns, this time counting only time spent inside the guest: the budget covers a single vcpu-run entry with no VM exit, so a guest blocked host-side in a long POLL is never killed, the accounting flaw that got the old per-hypercall watchdog removed. Both backends cancel the run from a watchdog thread (hv_vcpus_exit on hvf, SIGURG on kvm, its syscalls allowlisted only when armed), and the boot harnesses assert the watchdog's own diagnostic for runaway guests instead of relying on shell timeouts.
2 weeks ago