1 <?xml version='
1.0'
?> <!--*-nxml-*-->
2 <!DOCTYPE refentry PUBLIC
"-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
4 <!-- SPDX-License-Identifier: LGPL-2.1+ -->
6 <refentry id=
"systemd-detect-virt"
7 xmlns:
xi=
"http://www.w3.org/2001/XInclude">
10 <title>systemd-detect-virt
</title>
11 <productname>systemd
</productname>
15 <refentrytitle>systemd-detect-virt
</refentrytitle>
16 <manvolnum>1</manvolnum>
20 <refname>systemd-detect-virt
</refname>
21 <refpurpose>Detect execution in a virtualized environment
</refpurpose>
26 <command>systemd-detect-virt
</command>
27 <arg choice=
"opt" rep=
"repeat">OPTIONS
</arg>
32 <title>Description
</title>
34 <para><command>systemd-detect-virt
</command> detects execution in
35 a virtualized environment. It identifies the virtualization
36 technology and can distinguish full machine virtualization from
37 container virtualization.
<filename>systemd-detect-virt
</filename>
38 exits with a return value of
0 (success) if a virtualization
39 technology is detected, and non-zero (error) otherwise. By default,
40 any type of virtualization is detected, and the options
41 <option>--container
</option> and
<option>--vm
</option> can be used
42 to limit what types of virtualization are detected.
</para>
44 <para>When executed without
<option>--quiet
</option> will print a
45 short identifier for the detected virtualization technology. The
46 following technologies are currently identified:
</para>
49 <title>Known virtualization technologies (both
50 VM, i.e. full hardware virtualization,
51 and container, i.e. shared kernel virtualization)
</title>
52 <tgroup cols='
3' align='left' colsep='
1' rowsep='
1'
>
53 <colspec colname=
"type" />
54 <colspec colname=
"id" />
55 <colspec colname=
"product" />
60 <entry>Product
</entry>
65 <entry valign=
"top" morerows=
"12">VM
</entry>
66 <entry><varname>qemu
</varname></entry>
67 <entry>QEMU software virtualization, without KVM
</entry>
71 <entry><varname>kvm
</varname></entry>
72 <entry>Linux KVM kernel virtual machine, with whatever software, except Oracle Virtualbox
</entry>
76 <entry><varname>zvm
</varname></entry>
77 <entry>s390 z/VM
</entry>
81 <entry><varname>vmware
</varname></entry>
82 <entry>VMware Workstation or Server, and related products
</entry>
86 <entry><varname>microsoft
</varname></entry>
87 <entry>Hyper-V, also known as Viridian or Windows Server Virtualization
</entry>
91 <entry><varname>oracle
</varname></entry>
92 <entry>Oracle VM VirtualBox (historically marketed by innotek and Sun Microsystems), for legacy and KVM hypervisor
</entry>
96 <entry><varname>xen
</varname></entry>
97 <entry>Xen hypervisor (only domU, not dom0)
</entry>
101 <entry><varname>bochs
</varname></entry>
102 <entry>Bochs Emulator
</entry>
106 <entry><varname>uml
</varname></entry>
107 <entry>User-mode Linux
</entry>
111 <entry><varname>parallels
</varname></entry>
112 <entry>Parallels Desktop, Parallels Server
</entry>
116 <entry><varname>bhyve
</varname></entry>
117 <entry>bhyve, FreeBSD hypervisor
</entry>
121 <entry><varname>qnx
</varname></entry>
122 <entry>QNX hypervisor
</entry>
126 <entry><varname>acrn
</varname></entry>
127 <entry><ulink url=
"https://projectacrn.org">ACRN hypervisor
</ulink></entry>
131 <entry valign=
"top" morerows=
"7">Container
</entry>
132 <entry><varname>openvz
</varname></entry>
133 <entry>OpenVZ/Virtuozzo
</entry>
137 <entry><varname>lxc
</varname></entry>
138 <entry>Linux container implementation by LXC
</entry>
142 <entry><varname>lxc-libvirt
</varname></entry>
143 <entry>Linux container implementation by libvirt
</entry>
147 <entry><varname>systemd-nspawn
</varname></entry>
148 <entry>systemd's minimal container implementation, see
<citerefentry><refentrytitle>systemd-nspawn
</refentrytitle><manvolnum>1</manvolnum></citerefentry></entry>
152 <entry><varname>docker
</varname></entry>
153 <entry>Docker container manager
</entry>
157 <entry><varname>podman
</varname></entry>
158 <entry><ulink url=
"https://podman.io">Podman
</ulink> container manager
</entry>
162 <entry><varname>rkt
</varname></entry>
163 <entry>rkt app container runtime
</entry>
167 <entry><varname>wsl
</varname></entry>
168 <entry><ulink url=
"https://docs.microsoft.com/en-us/windows/wsl/about">Windows Subsystem for Linux
</ulink></entry>
172 <entry><varname>proot
</varname></entry>
173 <entry><ulink url=
"https://proot-me.github.io/">proot
</ulink> userspace chroot/bind mount emulation
</entry>
179 <para>If multiple virtualization solutions are used, only the
180 "innermost" is detected and identified. That means if both
181 machine and container virtualization are used in
182 conjunction, only the latter will be identified (unless
183 <option>--vm
</option> is passed).
</para>
184 <para> Windows Subsystem for Linux is not a Linux container,
185 but an environment for running Linux userspace applications on
186 top of the Windows kernel using a Linux-compatible interface.
187 WSL is categorized as a container for practical purposes.
188 Multiple WSL environments share the same kernel and services
189 should generally behave like when being run in a container.
</para>
193 <title>Options
</title>
195 <para>The following options are understood:
</para>
199 <term><option>-c
</option></term>
200 <term><option>--container
</option></term>
202 <listitem><para>Only detects container virtualization (i.e.
203 shared kernel virtualization).
</para></listitem>
207 <term><option>-v
</option></term>
208 <term><option>--vm
</option></term>
210 <listitem><para>Only detects hardware virtualization.
</para></listitem>
214 <term><option>-r
</option></term>
215 <term><option>--chroot
</option></term>
217 <listitem><para>Detect whether invoked in a
218 <citerefentry><refentrytitle>chroot
</refentrytitle><manvolnum>2</manvolnum></citerefentry>
219 environment. In this mode, no output is written, but the return
220 value indicates whether the process was invoked in a
221 <function>chroot()
</function>
222 environment or not.
</para></listitem>
226 <term><option>--private-users
</option></term>
228 <listitem><para>Detect whether invoked in a user namespace. In this mode, no
229 output is written, but the return value indicates whether the process was invoked
230 inside of a user namespace or not. See
231 <citerefentry project='man-pages'
><refentrytitle>user_namespaces
</refentrytitle><manvolnum>7</manvolnum></citerefentry>
232 for more information.
</para></listitem>
236 <term><option>-q
</option></term>
237 <term><option>--quiet
</option></term>
239 <listitem><para>Suppress output of the virtualization
240 technology identifier.
</para></listitem>
244 <term><option>--list
</option></term>
246 <listitem><para>Output all currently known and detectable container and VM environments.
</para></listitem>
249 <xi:include href=
"standard-options.xml" xpointer=
"help" />
250 <xi:include href=
"standard-options.xml" xpointer=
"version" />
256 <title>Exit status
</title>
258 <para>If a virtualization technology is detected,
0 is returned, a
259 non-zero code otherwise.
</para>
263 <title>See Also
</title>
265 <citerefentry><refentrytitle>systemd
</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
266 <citerefentry><refentrytitle>systemd-nspawn
</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
267 <citerefentry><refentrytitle>chroot
</refentrytitle><manvolnum>2</manvolnum></citerefentry>,
268 <citerefentry project='man-pages'
><refentrytitle>namespaces
</refentrytitle><manvolnum>7</manvolnum></citerefentry>