X-Git-Url: http://git.annexia.org/?a=blobdiff_plain;f=virt-what.pod;h=0a724d4b8e3350c4c7574fe61e3c129d7a302f87;hb=6fe3b5f900679d28e844757af7abce501dde6246;hp=3fc4b25edbf516e0fbc860043f0f410b8a879eb7;hpb=7880dab8d6e6d85cb086960750916b7f578e537f;p=virt-what.git diff --git a/virt-what.pod b/virt-what.pod index 3fc4b25..0a724d4 100644 --- a/virt-what.pod +++ b/virt-what.pod @@ -1,3 +1,5 @@ +=encoding utf8 + =head1 NAME virt-what - detect if we are running in a virtual machine @@ -23,47 +25,139 @@ don't know about or cannot detect. =over 4 -=item openvz +=item B + +This is Microsoft Hyper-V hypervisor. + +Status: confirmed by RWMJ + +=item B + +This is an IBM SystemZ (or other S/390) hardware partitioning system. +Additional facts listed below may also be printed. + +=item B + +This is Linux running directly on a IBM SystemZ hardware partitioning +system. + +This is expected to be a highly unusual configuration - if +you see this result you should treat it with suspicion. + +Status: not confirmed + +=item B + +This is Linux running directly on an LPAR on an IBM SystemZ +hardware partitioning system. + +Status: not confirmed + +=item B + +This is a z/VM guest running in an LPAR on an IBM SystemZ +hardware partitioning system. + +Status: confirmed by RWMJ using a Fedora guest running in z/VM + +=item B + +This process is running in a Linux VServer container. + +Status: contributed by Barış Metin + +=item B + +This guest is running on the KVM hypervisor using hardware +acceleration. + +Note that if the hypervisor is using software acceleration +you should I see this, but should see the C fact +instead. + +Status: confirmed by RWMJ. + +=item B The guest appears to be running inside an OpenVZ or Virtuozzo container. Status: contributed by Evgeniy Sokolov -=item qemu +=item B + +The guest is running inside Parallels Virtual Platform +(Parallels Desktop, Parallels Server). + +Status: contributed by Justin Clift + +=item B + +The guest is running inside IBM PowerVM Lx86 Linux/x86 emulator. + +Status: data supplied by Jeffrey Scheel, not confirmed + +=item B + +This is QEMU hypervisor using software emulation. + +Note that for KVM (hardware accelerated) guests you should I see +this. + +Status: confirmed by RWMJ. + +=item B -This is QEMU or KVM. +This is a User-Mode Linux (UML) guest. -Status: confirmed by RWMJ. Currently we have no way to -tell the difference between QEMU and KVM guests. +Status: contributed by Laurent Léonard -=item virtualpc +=item B + +This is Hitachi Virtualization Manager (HVM) Virtage +hardware partitioning system. + +Status: data supplied by Bhavna Sarathy, not confirmed + +=item B + +This is a VirtualBox guest. + +Status: contributed by Laurent Léonard + +=item B The guest appears to be running on Microsoft VirtualPC. Status: not confirmed -=item vmware +=item B -The guest appears to be running on VMware. +The guest appears to be running on VMware hypervisor. -Status: not confirmed +Status: confirmed by RWMJ -=item xen +=item B -The guest appears to be running on Xen. +The guest appears to be running on Xen hypervisor. Status: confirmed by RWMJ -=item xen-dom0 +=item B This is the Xen dom0 (privileged domain). Status: confirmed by RWMJ -=item xen-domU +=item B + +This is a Xen domU (paravirtualized guest domain). + +Status: confirmed by RWMJ + +=item B -This is a Xen domU (normal guest domain). +This is a Xen guest fully virtualized (HVM). Status: confirmed by RWMJ @@ -95,8 +189,7 @@ You might include this information in status and monitoring programs. =head1 SEE ALSO -L, -L, +L, L, L, L, @@ -110,8 +203,8 @@ Richard W.M. Jones =head1 COPYRIGHT -(C) Copyright 2008 Red Hat Inc., -L +(C) Copyright 2008-2011 Red Hat Inc., +L 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 @@ -151,7 +244,7 @@ Run and keep I. It may contain error messages which you should submit with your bug report. -=item 3. Get version of virt-what and version of libvirt. +=item 3. Get version of virt-what. Run @@ -163,7 +256,7 @@ Go to L 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). +messages file (step 2) and as much other detail as possible. =item 5. Assign the bug to rjones @ redhat.com