3 virt-what - detect if we are running in a virtual machine
11 C<virt-what> is a shell script which can be used to detect if the
12 program is running in a virtual machine.
14 The program prints out a list of "facts" about the virtual machine,
15 derived from heuristics. One fact is printed per line.
17 If nothing is printed and the script exits with code 0 (no error),
18 then it can mean I<either> that the program is running on bare-metal
19 I<or> the program is running inside a type of virtual machine which we
20 don't know about or cannot detect.
28 The guest appears to be running inside an OpenVZ or Virtuozzo
31 Status: contributed by Evgeniy Sokolov
37 Status: confirmed by RWMJ.
43 Status: confirmed by RWMJ.
47 The guest appears to be running on Microsoft VirtualPC.
53 The guest appears to be running on VMware.
59 The guest appears to be running on Xen.
61 Status: confirmed by RWMJ
65 This is the Xen dom0 (privileged domain).
67 Status: confirmed by RWMJ
71 This is a Xen domU (paravirtualized guest domain).
73 Status: confirmed by RWMJ
77 This is a Xen guest fully virtualized (HVM).
79 Status: confirmed by RWMJ
85 Most of the time, using this program is the I<wrong> thing to do.
86 Instead you should detect the specific features you actually want to
87 use. (As an example, if you wanted to issue Xen hypervisor commands
88 you would look for the C</proc/xen/privcmd> file).
90 However people keep asking for this, so we provide it. There are a
95 =item Bug reporting tool
97 If you think that virtualization could affect how your program runs,
98 then you might use C<virt-what> to report this in a bug reporting
101 =item Status display and monitoring tools
103 You might include this information in status and monitoring programs.
109 L<http://www.libvirt.org/>,
110 L<http://et.redhat.com/~rjones/>,
111 L<http://www.vmware.com/>,
112 L<http://www.microsoft.com/windows/products/winfamily/virtualpc>,
113 L<http://xensource.com/>,
114 L<http://bellard.org/qemu/>,
115 L<http://kvm.qumranet.com/>,
116 L<http://openvz.org/>
120 Richard W.M. Jones <rjones @ redhat . com>
124 (C) Copyright 2008 Red Hat Inc.,
125 L<http://libvirt.org/>
127 This program is free software; you can redistribute it and/or modify
128 it under the terms of the GNU General Public License as published by
129 the Free Software Foundation; either version 2 of the License, or
130 (at your option) any later version.
132 This program is distributed in the hope that it will be useful,
133 but WITHOUT ANY WARRANTY; without even the implied warranty of
134 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
135 GNU General Public License for more details.
137 You should have received a copy of the GNU General Public License
138 along with this program; if not, write to the Free Software
139 Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
141 =head1 REPORTING BUGS
143 Bugs can be viewed on the Red Hat Bugzilla page:
144 L<https://bugzilla.redhat.com/>.
146 If you find a bug in virt-what, please follow these steps to report it:
150 =item 1. Check for existing bug reports
152 Go to L<https://bugzilla.redhat.com/> and search for similar bugs.
153 Someone may already have reported the same bug, and they may even
156 =item 2. Capture debug and error messages
160 virt-what > virt-what.log 2>&1
162 and keep I<virt-what.log>. It may contain error messages which you
163 should submit with your bug report.
165 =item 3. Get version of virt-what and version of libvirt.
171 =item 4. Submit a bug report.
173 Go to L<https://bugzilla.redhat.com/> and enter a new bug.
174 Please describe the problem in as much detail as possible.
176 Remember to include the version numbers (step 3) and the debug
177 messages file (step 2).
179 =item 5. Assign the bug to rjones @ redhat.com
181 Assign or reassign the bug to B<rjones @ redhat.com> (without the
182 spaces). You can also send me an email with the bug number if you
183 want a faster response.