Add Parallels Virtual Platform (thanks Justin Clift).

[virt-what.git] / virt-what.pod

diff --git a/virt-what.pod b/virt-what.pod
index c5b88cf..cf4c1ff 100644 (file)
--- a/virt-what.pod
+++ b/virt-what.pod
@@ -31,6 +31,38 @@ This is Hyper-V.
 
 Status: from MSDN description, not tested.
 
+=item B<ibm_systemz>
+
+This is an IBM SystemZ (or other S/390) mainframe.  Additional
+facts listed below may also be printed.
+
+=item B<ibm_systemz-direct>
+
+This is Linux running directly on a IBM SystemZ mainframe.
+
+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 mainframe.
+
+Status: not confirmed
+
+=item B<ibm_systemz-zvm>
+
+This is a z/VM guest running in an LPAR on an IBM SystemZ mainframe.
+
+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.
@@ -44,6 +76,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 +91,10 @@ Status: data supplied by Jeffrey Scheel, not confirmed
 
 =item B<qemu>
 
-This is QEMU.
+This is QEMU using software emulation.
+
+Note that for KVM (hardware accelerated) guests you should I<not> see
+this.
 
 Status: confirmed by RWMJ.
 
@@ -193,7 +235,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
 
@@ -205,7 +247,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