X-Git-Url: http://git.annexia.org/?a=blobdiff_plain;f=virt-what.pod;h=0a724d4b8e3350c4c7574fe61e3c129d7a302f87;hb=6fe3b5f900679d28e844757af7abce501dde6246;hp=7bd7613164c10c1e5f0a6f0d651a1be1649fb735;hpb=8bbf673608a6554c4db01a21cfaa0ab3619d8ade;p=virt-what.git

diff --git a/virt-what.pod b/virt-what.pod
index 7bd7613..0a724d4 100644
--- a/virt-what.pod
+++ b/virt-what.pod
@@ -27,13 +27,53 @@ don't know about or cannot detect.
 
 =item B<hyperv>
 
-This is Hyper-V.
+This is Microsoft Hyper-V hypervisor.
 
-Status: from MSDN description, not tested.
+Status: confirmed by RWMJ
+
+=item B<ibm_systemz>
+
+This is an IBM SystemZ (or other S/390) hardware partitioning system.
+Additional facts listed below may also be printed.
+
+=item B<ibm_systemz-direct>
+
+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<ibm_systemz-lpar>
+
+This is Linux running directly on an LPAR on an IBM SystemZ
+hardware partitioning system.
+
+Status: not confirmed
+
+=item B<ibm_systemz-zvm>
+
+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<linux_vserver>
+
+This process is running in a Linux VServer container.
+
+Status: contributed by Barış Metin
 
 =item B<kvm>
 
-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<not> see this, but should see the C<qemu> fact
+instead.
 
 Status: confirmed by RWMJ.
 
@@ -44,6 +84,13 @@ container.
 
 Status: contributed by Evgeniy Sokolov
 
+=item B<parallels>
+
+The guest is running inside Parallels Virtual Platform
+(Parallels Desktop, Parallels Server).
+
+Status: contributed by Justin Clift
+
 =item B<powervm_lx86>
 
 The guest is running inside IBM PowerVM Lx86 Linux/x86 emulator.
@@ -52,7 +99,10 @@ Status: data supplied by Jeffrey Scheel, not confirmed
 
 =item B<qemu>
 
-This is QEMU.
+This is QEMU hypervisor using software emulation.
+
+Note that for KVM (hardware accelerated) guests you should I<not> see
+this.
 
 Status: confirmed by RWMJ.
 
@@ -64,7 +114,8 @@ Status: contributed by Laurent Léonard
 
 =item B<virtage>
 
-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 +133,13 @@ Status: not confirmed
 
 =item B<vmware>
 
-The guest appears to be running on VMware.
+The guest appears to be running on VMware hypervisor.
 
 Status: confirmed by RWMJ
 
 =item B<xen>
 
-The guest appears to be running on Xen.
+The guest appears to be running on Xen hypervisor.
 
 Status: confirmed by RWMJ
 
@@ -138,8 +189,7 @@ You might include this information in status and monitoring programs.
 
 =head1 SEE ALSO
 
-L<http://www.libvirt.org/>,
-L<http://et.redhat.com/~rjones/>,
+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/>,
@@ -153,8 +203,8 @@ Richard W.M. Jones <rjones @ redhat . com>
 
 =head1 COPYRIGHT
 
-(C) Copyright 2008 Red Hat Inc.,
-L<http://libvirt.org/>
+(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
@@ -194,7 +244,7 @@ Run
 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.
+=item 3. Get version of virt-what.
 
 Run
 
@@ -206,7 +256,7 @@ 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).
+messages file (step 2) and as much other detail as possible.
 
 =item 5. Assign the bug to rjones @ redhat.com