1VIRT-WHAT(1) Virtualization Support VIRT-WHAT(1)
2
3
4
6 virt-what - detect if we are running in a virtual machine
7
9 virt-what [options]
10
12 "virt-what" is a shell script which can be used to detect if the
13 program is running in a virtual machine.
14
15 The program prints out a list of "facts" about the virtual machine,
16 derived from heuristics. One fact is printed per line.
17
18 If nothing is printed and the script exits with code 0 (no error), then
19 it can mean either that the program is running on bare-metal or the
20 program is running inside a type of virtual machine which we don't know
21 about or cannot detect.
22
24 openvz
25 The guest appears to be running inside an OpenVZ or Virtuozzo
26 container.
27
28 Status: contributed by Evgeniy Sokolov
29
30 kvm This is KVM.
31
32 Status: confirmed by RWMJ.
33
34 qemu
35 This is QEMU.
36
37 Status: confirmed by RWMJ.
38
39 uml This is a User-Mode Linux (UML) guest.
40
41 Status: contributed by Laurent Leonard
42
43 virtualbox
44 This is a VirtualBox guest.
45
46 Status: contributed by Laurent Leonard
47
48 virtualpc
49 The guest appears to be running on Microsoft VirtualPC.
50
51 Status: not confirmed
52
53 vmware
54 The guest appears to be running on VMware.
55
56 Status: confirmed by RWMJ
57
58 xen The guest appears to be running on Xen.
59
60 Status: confirmed by RWMJ
61
62 xen-dom0
63 This is the Xen dom0 (privileged domain).
64
65 Status: confirmed by RWMJ
66
67 xen-domU
68 This is a Xen domU (paravirtualized guest domain).
69
70 Status: confirmed by RWMJ
71
72 xen-hvm
73 This is a Xen guest fully virtualized (HVM).
74
75 Status: confirmed by RWMJ
76
78 Most of the time, using this program is the wrong thing to do. Instead
79 you should detect the specific features you actually want to use. (As
80 an example, if you wanted to issue Xen hypervisor commands you would
81 look for the "/proc/xen/privcmd" file).
82
83 However people keep asking for this, so we provide it. There are a few
84 legitimate uses:
85
86 Bug reporting tool
87 If you think that virtualization could affect how your program
88 runs, then you might use "virt-what" to report this in a bug
89 reporting tool.
90
91 Status display and monitoring tools
92 You might include this information in status and monitoring
93 programs.
94
96 <http://www.libvirt.org/>, <http://et.redhat.com/~rjones/>,
97 <http://www.vmware.com/>,
98 <http://www.microsoft.com/windows/products/winfamily/virtualpc>,
99 <http://xensource.com/>, <http://bellard.org/qemu/>,
100 <http://kvm.qumranet.com/>, <http://openvz.org/>
101
103 Richard W.M. Jones <rjones @ redhat . com>
104
106 (C) Copyright 2008 Red Hat Inc., <http://libvirt.org/>
107
108 This program is free software; you can redistribute it and/or modify it
109 under the terms of the GNU General Public License as published by the
110 Free Software Foundation; either version 2 of the License, or (at your
111 option) any later version.
112
113 This program is distributed in the hope that it will be useful, but
114 WITHOUT ANY WARRANTY; without even the implied warranty of
115 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
116 General Public License for more details.
117
118 You should have received a copy of the GNU General Public License along
119 with this program; if not, write to the Free Software Foundation, Inc.,
120 675 Mass Ave, Cambridge, MA 02139, USA.
121
123 Bugs can be viewed on the Red Hat Bugzilla page:
124 <https://bugzilla.redhat.com/>.
125
126 If you find a bug in virt-what, please follow these steps to report it:
127
128 1. Check for existing bug reports
129 Go to <https://bugzilla.redhat.com/> and search for similar bugs.
130 Someone may already have reported the same bug, and they may even
131 have fixed it.
132
133 2. Capture debug and error messages
134 Run
135
136 virt-what > virt-what.log 2>&1
137
138 and keep virt-what.log. It may contain error messages which you
139 should submit with your bug report.
140
141 3. Get version of virt-what and version of libvirt.
142 Run
143
144 virt-what --version
145
146 4. Submit a bug report.
147 Go to <https://bugzilla.redhat.com/> and enter a new bug. Please
148 describe the problem in as much detail as possible.
149
150 Remember to include the version numbers (step 3) and the debug
151 messages file (step 2).
152
153 5. Assign the bug to rjones @ redhat.com
154 Assign or reassign the bug to rjones @ redhat.com (without the
155 spaces). You can also send me an email with the bug number if you
156 want a faster response.
157
158
159
160virt-what-1.3 2010-10-18 VIRT-WHAT(1)