X-Git-Url: http://git.annexia.org/?a=blobdiff_plain;f=virt-what.pod;h=8fd9bc40fcabc890a6f3ece3273ce9802c4147a4;hb=f82984fb84e9fed84aa71a50a1bfdfdc356771bd;hp=f2f1a3f0158dd2afa65a5ac9d3bcaa9c6a155210;hpb=37f7b6e5f79d61ec4f8967f3de2ec63420aec894;p=virt-what.git diff --git a/virt-what.pod b/virt-what.pod index f2f1a3f..8fd9bc4 100644 --- a/virt-what.pod +++ b/virt-what.pod @@ -25,21 +25,79 @@ don't know about or cannot detect. =over 4 +=item B + +This is a Docker container. + +Status: confirmed by Charles Nguyen + =item B -This is Hyper-V. +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 -Status: from MSDN description, not tested. +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 is printed for backwards compatibility with older virt-what which +could not distinguish between a Linux VServer container guest and +host. + +=item B + This process is running in a Linux VServer container. Status: contributed by Barış Metin +=item B + +This process is running as the Linux VServer host (VxID 0). + +Status: contributed by Barış Metin and Elan Ruusamäe + +=item B + +This process is running in a Linux LXC container. + +Status: contributed by Marc Fournier + =item B -This is KVM. +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. @@ -50,15 +108,23 @@ container. Status: contributed by Evgeniy Sokolov +=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 +Status: data originally supplied by Jeffrey Scheel, confirmed by +Yufang Zhang and RWMJ =item B -This is QEMU using software emulation. +This is QEMU hypervisor using software emulation. Note that for KVM (hardware accelerated) guests you should I see this. @@ -71,9 +137,19 @@ This is a User-Mode Linux (UML) guest. Status: contributed by Laurent Léonard +=item B + +Some sort of virtualization appears to be present, but we are not sure +what it is. In some very rare corner cases where we know that +virtualization is hard to detect, we will try a timing attack to see +if certain machine instructions are running much more slowly than they +should be, which would indicate virtualization. In this case, the +generic fact C is printed. + =item B -This is Hitachi Virtualization Manager (HVM) Virtage logical partitioning. +This is Hitachi Virtualization Manager (HVM) Virtage +hardware partitioning system. Status: data supplied by Bhavna Sarathy, not confirmed @@ -91,13 +167,13 @@ Status: not confirmed =item B -The guest appears to be running on VMware. +The guest appears to be running on VMware hypervisor. Status: confirmed by RWMJ =item B -The guest appears to be running on Xen. +The guest appears to be running on Xen hypervisor. Status: confirmed by RWMJ @@ -119,15 +195,41 @@ This is a Xen guest fully virtualized (HVM). Status: confirmed by RWMJ -=item B +=back -This is a z/VM guest running on an IBM SystemZ mainframe. +=head1 EXIT STATUS -Status: confirmed by RWMJ using a Fedora guest running in z/VM. Not -tested whether this also works for Linux installed directly in an -LPAR. +Programs that use or wrap C should check that the exit +status is 0 before they attempt to parse the output of the command. -=back +A non-zero exit status indicates some error, for example, an +unrecognized command line argument. If the exit status is non-zero +then the output "facts" (if any were printed) cannot be guaranteed and +should be ignored. + +The exit status does I have anything to do with whether the +program is running on baremetal or under virtualization, nor with +whether C managed detection "correctly" (which is basically +unknowable given the large variety of virtualization systems out there +and that some systems deliberately emulate others). + +=head1 RUNNING VIRT-WHAT FROM OTHER PROGRAMS + +C is designed so that you can easily run it from +other programs or wrap it up in a library. + +Your program should check the exit status (see the section above). + +Some programming languages (notably Python: issue 1652) erroneously +mask the C signal and do not restore it when executing +subprocesses. C is a shell script and some shell commands +do not work correctly when you do this. You may see warnings from +C similar to this: + + echo: write error: Broken pipe + +The solution is to set the C signal handler back to C +before running C. =head1 IMPORTANT NOTE @@ -151,6 +253,13 @@ tool. You might include this information in status and monitoring programs. +=item System tuning (sometimes) + +You might use this program to tune an operating system so it runs +better as a virtual machine of a particular hypervisor. However if +installing paravirtualized drivers, it's better to check for the +specific features your drivers need (eg. for the presence of PCI devices). + =back =head1 SEE ALSO