Pantavisor 029 Release
Pantavisor 029 is out, and it’s a meaningful update on the runtime side — with a new hosted D-Bus system bus for xconnect, several control-daemon and logging improvements, and a round of reliability fixes — paired with a meta-pantavisor build that republishes images across all supported boards.
Pantavisor runtime
The headline feature this cycle is a managed, hosted D-Bus system bus for xconnect. Pantavisor can now host its own system bus and generate the policy, UIDs, and link graph needed to safely expose it to containers, with validation and idempotent policy generation so re-applying configuration doesn’t leave the bus in an inconsistent state. The bus runs under a dedicated, role-scoped jail, and injected proxy sockets are now reachable the way containers expect, making xconnect’s dbus story considerably more robust and self-contained — configurable via a new xconnect.dbus.systembus.enabled entry.
Beyond that, there’s a handful of smaller but useful runtime additions: the logserver can now forward LXC container logs directly to stdout, log timestamps can be switched between absolute and relative, and a new loop-device index base setting lets you reserve a block of loop devices for a given device. On the control side, pv-ctrl gains a synchronous storage garbage-collection endpoint and an “unclaim” command, and pvtx now supports explicit, custom commit revision names (consistently prefixed under locals/) along with a fix to how it locates the control socket.
Notable fixes
This release cleans up a number of correctness and reliability issues. Update downloads now report progress on the regular heartbeat instead of firing an event per object, cutting down on chatter during large transfers. Cloud logging is sturdier too — log fragments that the server permanently rejects are now dropped and logged rather than retried forever, and cloud log pushes are chunked with clearer transport error reporting. Kernel module unloading now correctly reverses load order, containers are stopped before their volumes are unmounted on a forced stop, and the app engine now reboots rather than powers off in response to SIGTERM. On the configuration front, user-meta deletions are now properly honored, and a bug that silently ignored user-set updater timeout values has been fixed. pv-ctrl also logs every rejected command along with the operation that triggered it, and a small memory leak in command handling was closed.
Documentation
The docs site got a structural cleanup this release, split into overview, reference, and tools sections with normalized navigation and fixed cross-repository links. The new hosted D-Bus system bus is documented alongside its configuration option, and the underlying design proposal for xconnect’s hosted bus is included for anyone who wants the full rationale.
Build system & BSP images
meta-pantavisor 029 republishes images, PV exports, BSPs, and (where applicable) SDK toolchains for all supported machines — including the Orange Pi 3 LTS, Banana Pi M2 Berry, i.MX8QXP MEK, Raspberry Pi (32- and 64-bit), i.MX8M Nano/Mini Var-SOM boards, Orange Pi R1, Docker x86_64, Radxa ROCK 5A, Verdin iMX8MM, and Colibri iMX6ULL. The underlying component set (busybox-pv, dropbear, libthttp, lxc6-pv, picohttpparser, and pantavisor itself) is unchanged from the previous build, so this is primarily a packaging refresh that carries the pantavisor 029 runtime out to every supported board.
Getting started
Head to the Pantavisor documentation to get started, or grab the latest images and BSPs for your board from the meta-pantavisor release. If you’re upgrading an existing fleet, check out the xconnect docs for details on the new hosted D-Bus bus before enabling it.
As always, we’d love to hear how this release works for you — drop a reply below with questions, feedback, or anything you run into.