обнаружение выполнения в виртуализированной среде (Detect execution in a virtualized environment)
Имя (Name)
systemd-detect-virt - Detect execution in a virtualized
environment
Синопсис (Synopsis)
systemd-detect-virt [OPTIONS...]
Описание (Description)
systemd-detect-virt detects execution in a virtualized
environment. It identifies the virtualization technology and can
distinguish full machine 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, │
│ │ │ without KVM │
│ ├────────────────────┼────────────────────┤
│ │ kvm │ Linux KVM kernel │
│ │ │ virtual machine, │
│ │ │ in combination │
│ │ │ with QEMU. Not │
│ │ │ used for other │
│ │ │ virtualizers using │
│ │ │ the KVM │
│ │ │ interfaces, such │
│ │ │ as Oracle │
│ │ │ VirtualBox or │
│ │ │ Amazon EC2 Nitro, │
│ │ │ see below. │
│ ├────────────────────┼────────────────────┤
│ │ amazon │ Amazon EC2 Nitro │
│ │ │ using Linux KVM │
│ ├────────────────────┼────────────────────┤
│ │ 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), for │
│ │ │ legacy and KVM │
│ │ │ hypervisor │
│ ├────────────────────┼────────────────────┤
│ │ powervm │ IBM PowerVM │
│ │ │ hypervisor — comes │
│ │ │ as firmware with │
│ │ │ some IBM POWER │
│ │ │ servers │
│ ├────────────────────┼────────────────────┤
│ │ xen │ Xen hypervisor │
│ │ │ (only domU, not │
│ │ │ dom0) │
│ ├────────────────────┼────────────────────┤
│ │ bochs │ Bochs Emulator │
│ ├────────────────────┼────────────────────┤
│ │ uml │ User-mode Linux │
│ ├────────────────────┼────────────────────┤
│ │ parallels │ Parallels Desktop, │
│ │ │ Parallels Server │
│ ├────────────────────┼────────────────────┤
│ │ bhyve │ bhyve, FreeBSD │
│ │ │ hypervisor │
│ ├────────────────────┼────────────────────┤
│ │ qnx │ QNX hypervisor │
├──────────┼────────────────────┼────────────────────┤
│acrn │ ACRN hypervisorPodmanWindows Subsystem │
│ │ │ for LinuxprootPouch
If multiple virtualization solutions are used, only the
"innermost" is detected and identified. That means if both
machine and container virtualization are used in conjunction,
only the latter will be identified (unless --vm is passed).
Windows Subsystem for Linux is not a Linux container, but an
environment for running Linux userspace applications on top of
the Windows kernel using a Linux-compatible interface. WSL is
categorized as a container for practical purposes. Multiple WSL
environments share the same kernel and services should generally
behave like when being run in a container.
