X-Git-Url: http://git.annexia.org/?a=blobdiff_plain;f=virt-what.pod;h=4304297d4f813746b3634ae5a3eb877d19150dc9;hb=5e85dccc07d94b8a380601fdc2c5d471e062e0b2;hp=c5b88cf0430b16182d3b2d5d5702ae9710b42c7b;hpb=9f20b2537f837e3f100c7d116579fb32607ea82b;p=virt-what.git diff --git a/virt-what.pod b/virt-what.pod index c5b88cf..4304297 100644 --- a/virt-what.pod +++ b/virt-what.pod @@ -27,13 +27,53 @@ don't know about or cannot detect. =item B -This is Hyper-V. +This is Microsoft Hyper-V hypervisor. -Status: from MSDN description, not tested. +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 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. @@ -44,15 +84,26 @@ 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, confimed by +Yufang Zhang and RWMJ =item B -This is QEMU. +This is QEMU hypervisor using software emulation. + +Note that for KVM (hardware accelerated) guests you should I see +this. Status: confirmed by RWMJ. @@ -64,7 +115,8 @@ Status: contributed by Laurent Léonard =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 @@ -82,13 +134,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 @@ -112,6 +164,40 @@ Status: confirmed by RWMJ =back +=head1 EXIT STATUS + +Programs that use or wrap C should check that the exit +status is 0 before they attempt to parse the output of the command. + +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 Most of the time, using this program is the I thing to do. @@ -193,7 +279,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 @@ -205,7 +291,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