Compatibility and limitations
App and base versions
Section titled “App and base versions”The catalog advertises the app version a base was built with and its minimum app version. The picker labels compatibility and refuses a base that needs a newer application.
| Base generation | Antinomie 0.3.0 |
|---|---|
| BusyBox / Debian GNOME for 0.3.0 | Supported; configurable transport and Never drop policy |
| Bases for 0.2.0 | Supported with legacy 256 KiB, drop-on-full buffers |
| Bases for 0.1.0 | Supported with legacy transport behavior |
| A base requiring a newer app | Update the app before using it |
Current catalog recommendations for the 0.3.0 bases are 256 MiB RAM / 1 GiB disk for BusyBox and 4,096 MiB RAM / 16 GiB disk for Debian GNOME. Actual workloads can need more resources.
Updating the app does not replace an installed base or VM disk. New guest features require an appropriate new base. Keep existing VMs when you need their installed software or history.
Host and program compatibility
Section titled “Host and program compatibility”- The released application targets Linux x86-64.
- Guests use the project’s patched Linux 6.12.94 kernel.
- A guest executable needs a compatible architecture and any required interpreter and shared libraries.
- WSL2 needs a working graphical display. KVM availability depends on the host and nested virtualization configuration; TCG remains an alternative.
Operational limits
Section titled “Operational limits”Only one VM runs at a time in 0.3.0. Live VM snapshot restoration, migration and transport reconnection are not supported workflows.
Static analysis targets the initially launched executable. It does not automatically acquire every executable from descendants or later executions. Desktop launch modes need an already logged-in graphical session for the run’s guest user.
Observation limits
Section titled “Observation limits”Captured memory can change while it is read and may include missing ranges or errors. A record does not make the guest’s state an atomic snapshot.
Never drop waits only within its configured deadline and can affect execution timing. A missing call can result from loss or unavailable capture; absence alone does not prove an action never happened.
Antinomie uses virtualization and kernel instrumentation. It does not promise invisibility to the guest or immunity to VM escapes. For hostile specimens, use an appropriately isolated host and network environment.