Skip to content

About

Standalone Linux XCP-ng management client with Rune UI and a Rust backend connecting directly to XAPI.

Resources

Stars

1 star

Watchers

0 watching

Forks

Repository files navigation

XenAdmin RS

A Linux desktop client for direct management of XCP-ng hosts and pools. The UI uses Rune. The backend uses Rust and XAPI.

The client must work when Xen Orchestra is unavailable. Connections, credentials, inventory, VM consoles, and host discovery must work without an XO service. The client requires a reachable XAPI service and the user's host permissions.

XenAdmin RS listing the virtual machines of a two-host XCP-ng pool, with the selected guest's details and actions beside the table

The inventory of a pool the client is connected to directly: its two hosts and their guests in the tree, each guest's state, host and size in the table, and the selected guest's details and actions on the right.

A guest's graphical desktop shown in the client's console view, with a terminal open in the guest

A guest's console, opened through the host that runs the guest. Keyboard and pointer go to the guest, and text on the clipboard can be typed into it as key presses.

Live CPU charts for one guest in the client's performance view

A guest's performance, read from its host every five seconds, with longer ranges and a choice of data sources.

The pictures are of version 0.19.0 connected to the project's disposable lab, a pool of two nested XCP-ng 8.3 hosts.

Project status

Beta. Version 0.19.0 is the current release (packages, changelog, release report), for XCP-ng 8.3 with the client running as a Wayland application. Its supported part is connections and certificate trust, the live inventory, VM power, the console, snapshots, performance charts and activity; on the main branch, towards 0.20.0, host maintenance and moving a VM within its pool have joined it. Everything else below is experimental: implemented, in most cases with one recorded successful run, and marked with a notice in the client. The feature scope draws that line. The Cargo workspace builds the Rune desktop application, a read-only host probe and a small sandbox helper. No Xen Orchestra service is used.

Implemented scope, as reviewed operations with durable partial and unknown outcomes: saved and concurrent connections with certificate trust, credentials and endpoint failover; event-driven inventory; VM power, properties, devices, consoles, snapshots, checkpoints and schedules; VM creation from templates, cloning and deletion; storage and network lifecycle including local, NFS, iSCSI and CHAP repositories, ISO libraries, VLANs, bonds, multipathing and management addressing; import, export, conversion and same- or cross-pool migration; host and pool administration including maintenance, HA, pool join and dissolution, security and host backups; metrics, tasks and alerts; organization, saved searches, tags, folders, vApps and bulk actions; a portable archive and an AppImage. The retained parity ledger tracks all 202 retained rows and is the completion authority; an implemented row is not a qualified workflow until its live, failure and interruption paths are recorded.

Verification so far. The offline suite (core, protocol, TLS and Rune fixtures) runs in CI. Live qualification runs against a disposable nested XCP-ng 8.3.0 lab: the live qualification report records a hundred and eleven scenarios, including three driven desktop sessions, the last with the packaged AppImage, and the operator's sessions on a real seat, covering connections and recovery, power and consoles, snapshots and checkpoints, devices, storage and networking, shared NFS and iSCSI repositories with HA, live migration and evacuation, host maintenance, reboots and power cycles, coordinator handover and endpoint failover, together with sixty-five numbered findings and observations: host behaviours the client now handles, host observations, client fixes and four product decisions, since settled. Per-row results are in lab/ACCEPTANCE.md, and the verification traceability report maps the core verification scenarios to their evidence.

Known limits of this release are listed in the changelog: the failure and interruption paths of the experimental areas are mostly unrecorded, only XCP-ng 8.3.0 has been exercised, clipboard exchange with a guest is experimental, and screen readers are not supported. The implementation plan records how the supported part was qualified and what comes next.

Run it

cargo build --locked --workspace
./target/debug/xenadmin-rs

Explore the interface using synthetic inventory:

./target/debug/xenadmin-rs -- --demo

Use Add connection to enter a host endpoint and session-only credentials. On narrow windows, use Connect and Details in the compact controls. Self-signed installations can use independently verified, endpoint-specific certificate fingerprints. The demo cannot issue host actions.

The running guide covers Linux dependencies, certificate trust, the host probe, local state, checks, and packaging. ./scripts/check.sh runs the local checks; ./scripts/package.sh builds a release archive under artifacts/. The installation guide covers the portable archive, the AppImage, the optional installer and removal.

Start here

The recovery release acceptance gate is to locate, start, and use the console of an XO VM with XO unreachable. It was recorded on the disposable lab on 2026-11-11 with the Xen Orchestra appliance imported through the client and managing the pool: XO shut down and unreachable, the VM located, started and consoled through the direct host connection, and XO answering again afterwards. It was run through the core facade and then through the packaged 0.17.0 AppImage started on an empty state directory, with keyboard input in the appliance's console and the client's connections observed going to the two pool hosts only.

Release history

0.18.0 was the first published version and 0.19.0 is the second, both betas, with their packages on the project's releases page and their notes in the changelog. The versions before them were development checkpoints that froze source locally and recorded their verification:

The per-increment reports under docs/reports/ are linked from the ledger rows they verify.

Development

The workspace pins Rust 1.99.1 and Rune f3d04f3f2069d177d04c963b0ba9f6b2065e46eb; Cargo.lock pins the dependency graph. xenadmin-core owns protocol and operation behavior without Rune dependencies. xenadmin-desktop adapts snapshots and console frames to Rune. xenadmin-xapi holds the generated XAPI record views, enumerations and catalogue. xenadmin-process is the post-fork helper for the offline image sandbox. host-probe consumes the same core through its public facade.

The project uses the MIT license for original work, with one exception: crates/xenadmin-xapi, the XAPI bindings generated from the upstream API description, is under the LGPL 2.1 with a linking exception, as its LICENSE and NOTICE say. Binary archives include that crate's licence and notice with the supplied dependency and embedded-font notices. This is an independent project, not an official XCP-ng or Vates application.

Use ./scripts/dev.sh to enable private local inspection of the running desktop, and ./scripts/inspect.sh to query it. See development diagnostics.

About

Standalone Linux XCP-ng management client with Rune UI and a Rust backend connecting directly to XAPI.

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages