summaryrefslogtreecommitdiffstats
path: root/virt-what.pod
blob: 06308b4bc3705c105efa3ae1ae2897b3f7884cd3 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
=encoding utf8

=head1 NAME

virt-what - detect if we are running in a virtual machine

=head1 SUMMARY

virt-what [options]

=head1 DESCRIPTION

C<virt-what> is a shell script which can be used to detect if the
program is running in a virtual machine.

The program prints out a list of "facts" about the virtual machine,
derived from heuristics.  One fact is printed per line.

If nothing is printed and the script exits with code 0 (no error),
then it can mean I<either> that the program is running on bare-metal
I<or> the program is running inside a type of virtual machine which we
don't know about or cannot detect.

=head1 FACTS

=over 4

=item B<hyperv>

This is Hyper-V.

Status: from MSDN description, not tested.

=item B<kvm>

This is KVM.

Status: confirmed by RWMJ.

=item B<openvz>

The guest appears to be running inside an OpenVZ or Virtuozzo
container.

Status: contributed by Evgeniy Sokolov

=item B<powervm_lx86>

The guest is running inside IBM PowerVM Lx86 Linux/x86 emulator.

Status: data supplied by Jeffrey Scheel, not confirmed

=item B<qemu>

This is QEMU using software emulation.

Note that for KVM (hardware accelerated) guests you should I<not> see
this.

Status: confirmed by RWMJ.

=item B<uml>

This is a User-Mode Linux (UML) guest.

Status: contributed by Laurent Léonard

=item B<virtage>

This is Hitachi Virtualization Manager (HVM) Virtage logical partitioning.

Status: data supplied by Bhavna Sarathy, not confirmed

=item B<virtualbox>

This is a VirtualBox guest.

Status: contributed by Laurent Léonard

=item B<virtualpc>

The guest appears to be running on Microsoft VirtualPC.

Status: not confirmed

=item B<vmware>

The guest appears to be running on VMware.

Status: confirmed by RWMJ

=item B<xen>

The guest appears to be running on Xen.

Status: confirmed by RWMJ

=item B<xen-dom0>

This is the Xen dom0 (privileged domain).

Status: confirmed by RWMJ

=item B<xen-domU>

This is a Xen domU (paravirtualized guest domain).

Status: confirmed by RWMJ

=item B<xen-hvm>

This is a Xen guest fully virtualized (HVM).

Status: confirmed by RWMJ

=back

=head1 IMPORTANT NOTE

Most of the time, using this program is the I<wrong> thing to do.
Instead you should detect the specific features you actually want to
use.  (As an example, if you wanted to issue Xen hypervisor commands
you would look for the C</proc/xen/privcmd> file).

However people keep asking for this, so we provide it.  There are a
few legitimate uses:

=over 4

=item Bug reporting tool

If you think that virtualization could affect how your program runs,
then you might use C<virt-what> to report this in a bug reporting
tool.

=item Status display and monitoring tools

You might include this information in status and monitoring programs.

=back

=head1 SEE ALSO

L<http://people.redhat.com/~rjones/virt-what/>,
L<http://www.vmware.com/>,
L<http://www.microsoft.com/windows/products/winfamily/virtualpc>,
L<http://xensource.com/>,
L<http://bellard.org/qemu/>,
L<http://kvm.qumranet.com/>,
L<http://openvz.org/>

=head1 AUTHORS

Richard W.M. Jones <rjones @ redhat . com>

=head1 COPYRIGHT

(C) Copyright 2008-2011 Red Hat Inc.,
L<http://people.redhat.com/~rjones/virt-what/>

This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.

=head1 REPORTING BUGS

Bugs can be viewed on the Red Hat Bugzilla page:
L<https://bugzilla.redhat.com/>.

If you find a bug in virt-what, please follow these steps to report it:

=over 4

=item 1. Check for existing bug reports

Go to L<https://bugzilla.redhat.com/> and search for similar bugs.
Someone may already have reported the same bug, and they may even
have fixed it.

=item 2. Capture debug and error messages

Run

 virt-what > virt-what.log 2>&1

and keep I<virt-what.log>.  It may contain error messages which you
should submit with your bug report.

=item 3. Get version of virt-what and version of libvirt.

Run

 virt-what --version

=item 4. Submit a bug report.

Go to L<https://bugzilla.redhat.com/> and enter a new bug.
Please describe the problem in as much detail as possible.

Remember to include the version numbers (step 3) and the debug
messages file (step 2).

=item 5. Assign the bug to rjones @ redhat.com

Assign or reassign the bug to B<rjones @ redhat.com> (without the
spaces).  You can also send me an email with the bug number if you
want a faster response.

=back