New TUI tool kudu manages Linux VMs without libvirt dependency

kudu introduces a terminal-based workflow for VM management on Linux, targeting users who avoid graphical tools or libvirt’s abstraction layer. By interfacing directly with QEMU, it eliminates libvirt’s complexity but shifts configuration responsibility to the user. This trade-off may appeal to engineers who need fine-grained control over VM parameters or operate in environments where libvirt is unavailable or undesirable.

The tool supports multiple architectures (x86_64, aarch64, riscv64) but requires specific QEMU binaries and UEFI firmware packages for each. Installation is straightforward via pre-built binaries or Arch Linux’s package manager, while other distributions must build from source using Cargo. This distribution model favors users comfortable with manual setup or Arch-based systems, potentially limiting adoption elsewhere until broader packaging support emerges.

kudu’s reliance on QEMU means users must handle low-level details like KVM module loading and group permissions manually. While the tool can run without KVM acceleration, performance-critical workloads will require proper configuration. The FAQ addresses common pitfalls, but the absence of libvirt’s automation may increase operational overhead for teams accustomed to its abstractions. This design choice prioritizes simplicity and direct hardware access over convenience.

The project’s strict contribution guidelines, rejecting LLM-generated code and requiring small, focused PRs, signal a preference for maintainable, human-reviewed changes. This approach may slow development but could improve code quality. The GPLv3 license ensures modifications remain open-source, aligning with the tool’s positioning as a community-driven alternative to existing solutions. For now, kudu’s niche appears to be engineers who value terminal-based control and are willing to trade libvirt’s features for direct QEMU access.