X-Git-Url: http://git.annexia.org/?a=blobdiff_plain;ds=inline;f=virt-what.pod;h=cf4c1ff0084c654949b63e006d65acaa9c55f0db;hb=4216f66a14702bf1a430a70be1be46d27b8b67c9;hp=c5b88cf0430b16182d3b2d5d5702ae9710b42c7b;hpb=9f20b2537f837e3f100c7d116579fb32607ea82b;p=virt-what.git diff --git a/virt-what.pod b/virt-what.pod index c5b88cf..cf4c1ff 100644 --- a/virt-what.pod +++ b/virt-what.pod @@ -31,6 +31,38 @@ This is Hyper-V. Status: from MSDN description, not tested. +=item B + +This is an IBM SystemZ (or other S/390) mainframe. Additional +facts listed below may also be printed. + +=item B + +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 + +This is Linux running directly on an LPAR on an IBM SystemZ mainframe. + +Status: not confirmed + +=item B + +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 + +This process is running in a Linux VServer container. + +Status: contributed by Barış Metin + =item B This is KVM. @@ -44,6 +76,13 @@ 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. @@ -52,7 +91,10 @@ Status: data supplied by Jeffrey Scheel, not confirmed =item B -This is QEMU. +This is QEMU using software emulation. + +Note that for KVM (hardware accelerated) guests you should I see +this. Status: confirmed by RWMJ. @@ -193,7 +235,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 +247,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