Skip to main content

VManager — the virtual-machine stack

VManager

VManager — end-to-end KVM/QEMU virtual-machine management for Linux: a typed core with a command-line tool and a desktop GUI over the same library.

What it is

End-to-end KVM and QEMU virtual-machine management for Linux, through both a command line and a desktop application: host preparation, hypervisor installation, VM creation and configuration, snapshots, backups and monitoring. It includes an isolation flow for analysing live, hostile software inside a hardened VM with verifiable host-protection guarantees. It is the consumer application the federation's VM-domain libraries were extracted from, and its single-host mode needs no daemon and no database.

It belongs to VManager — the virtual-machine stack — a working application, and the libraries that were carved out of it. That cluster states its own boundaries on the work page, including what it deliberately does not own.

State

Status
Active development
Registered version
0.4.0
Category
application
Cluster
VManager — the virtual-machine stack
Release wave
5
Language recorded
python

Versions shown here are the versions the registry records for the working tree. The package index is the publication contract, and the two are not guaranteed to agree — the index is what an install command actually resolves against. recorded at build · 2026-09-04

A project page is one row of the federation registry, read at build: the registered version, the projects it depends on, and the projects that depend on it — all of them the registry's own values. recorded at build · 2026-09-16

how it connects

Relations

Declared dependencies, by scope

Declared dependents, by scope

No registered project depends on it yet.

Left: what VManager depends on. Right: what depends on it. The map draws at most 6 per side — 5 further dependencies are named in the lists above. Every relation the registry records for VManager is published here and named above. Relations are read from mgf-libraries.json, synced from mgf-standard at 87915ba on 2026-09-16.

A project's release wave is its position in the dependency order recorded upstream — a barrier that says what must be published first, never a date. recorded at build · 2026-09-16

under the hood

Engineering
Third-party packages declared
15
Optional extras
dev · docs · gui · gui-dev · observability
Requires Python
>=3.11

The registry records a direct third-party declaration count for each project. This site can sum those row counts, but it does not have the names needed to deduplicate them or describe a resolved installation. recorded at build · 2026-09-16

The rule families it is measured against

VManager answers to the same corpus every registered project does: 323 anchored rules in 25 families, of which 313 are binding. This is the corpus, not a score — nothing on this page claims a conformance result for VManager, because no durable per-project record of one is published. The corpus, family by family →

Counted from mgf-rules-index.json, synced from mgf-standard at 169b511 on 2026-09-04.

Every registered project is measured against the same corpus: the rule families, their sizes, and how many of their rules are binding come from the standard's own machine-readable index, not from prose about it. recorded at build · 2026-09-04

the record

Evidence

Read the declared runtime graph

Inside VManager's declared runtime graph

  • VManager itself.
  • 6 further Magogi libraries in its declared runtime graph, directly or through them: mgf-common · mgf-vm-core · mgf-vm-forensics · mgf-vm-interchange · mgf-vm-libvirt · mgf-vm-sdk
  • a sum of direct third-party declaration counts — 15 on VManager's row and 24 across the declared runtime graph. The registry supplies no names, so this is not a unique package count or a resolved installation.

Outside this graph

  • the other 47 published components are not reached by these declared runtime relationships. The explorer counts the same graph. This graph is a registry model, not a package-resolver result.
  • anything from these clusters: Hardware resource broker · Telematics · Cloud & cost · Fleet engineering practice · Applications & ventures
  • a hosted service, an account, or a runtime the Foundation operates for you.

The design rules require a third-party dependency that performs input or output to sit behind an interface with both a production and a test implementation. The rule states the required design; the registry's dependency counts do not verify implementation conformance. recorded at build · 2026-09-04

A project's declared runtime graph, and what stays outside it, is computed only from registry edges scoped as runtime. Optional and test declarations remain outside that view; the graph is not a resolved installation. recorded at build · 2026-09-16