The programs it needs
The bricks are programs that Virtualbricks runs: the VDE programs for the switches, the links and the interfaces of this computer, and QEMU for the virtual machines. On Debian and Ubuntu they come in these packages:
| Package | Programs |
|---|---|
vde2 |
vde_switch, vde_plug, dpipe, vde_plug2tap, vde_pcapplug,
vdeterm, unixterm |
vde2-cryptcab |
vde_cryptcab, for
the tunnels |
vde-netemu |
vde-netemu, for
the Netemu links |
qemu-system-x86 |
qemu-system-x86_64 and qemu-system-i386 |
qemu-system-arm,
qemu-system-mips, qemu-system-ppc, qemu-system-riscv, qemu-system-s390x, qemu-system-sparc, qemu-system-misc |
The other architectures, as qemu-system-aarch64 in qemu-system-arm; on Ubuntu 24.04, qemu-system-misc has those of RISC-V |
qemu-utils |
qemu-img, which
reads and makes the disk images |
The menu of the programs shows each once, by the name QEMU gives it:
Debian's other names, as qemu-system-arm64 for
qemu-system-aarch64, only where a machine uses
one. Some programs have no default machine type, as qemu-system-aarch64 and qemu-system-arm: choose one in the section Machine, as virt, or the
machine doesn't start.
No distribution ships vde_router, the
program of the router.
Where Virtualbricks looks
Each project has a folder for the QEMU programs and one for the VDE
programs, in its settings: choose File › Settings, then
the page of the project. A program that isn't in its folder is looked
for in the folders of PATH.
Under each folder, the Settings window says what it holds: the version of QEMU and its programs, and whether the programs of the bricks are there, or which one is missing and the package that has it. A folder that doesn't exist is an error, and OK stays greyed until it is fixed.
When a program is missing
New Brick shows a warning sign on the kinds whose program is missing, and says which one.
At start, Virtualbricks warns about the programs it can't find. Missing programs, in the settings of this computer, turns the warning off.
A brick whose program is missing doesn't start, and the Logs window says why. Install the package, and start it again.
See also
The terminal, KSM, the folders of the programs, and the other settings.
What each brick is for, and the program that runs it.
The messages, a brick that doesn't start, a refused start, a project that can't be read.