systemd-detect-virt — Detect execution in a virtualized environment
systemd-detect-virt [OPTIONS...]
systemd-detect-virt detects execution in
a virtualized environment. It identifies the virtualization
technology and can distinguish full VM virtualization from
container virtualization. systemd-detect-virt
exits with a return value of 0 (success) if a virtualization
technology is detected, and non-zero (error) otherwise. By default
any type of virtualization is detected, and the options
--container and --vm can be used
to limit what types of virtualization are detected.
When executed without --quiet will print a
short identifier for the detected virtualization technology. The
following technologies are currently identified:
Table 1. Known virtualization technologies (both VM, i.e. full hardware virtualization, and container, i.e. shared kernel virtualization)
| Type | ID | Product |
|---|---|---|
| VM | qemu | QEMU software virtualization |
kvm | Linux KVM kernel virtual machine | |
zvm | s390 z/VM | |
vmware | VMware Workstation or Server, and related products | |
microsoft | Hyper-V, also known as Viridian or Windows Server Virtualization | |
oracle | Oracle VM VirtualBox (historically marketed by innotek and Sun Microsystems) | |
xen | Xen hypervisor (only domU, not dom0) | |
bochs | Bochs Emulator | |
uml | User-mode Linux | |
| container | openvz | OpenVZ/Virtuozzo |
lxc | Linux container implementation by LXC | |
lxc-libvirt | Linux container implementation by libvirt | |
systemd-nspawn | systemd's minimal container implementation, see systemd-nspawn(1) | |
docker | Docker container manager |
If multiple virtualization solutions are used, only the
"innermost" is detected and identified. That means if both VM
virtualization and container virtualization are used in
conjunction, only the latter will be identified (unless
--vm is passed).
The following options are understood: