X-Git-Url: http://git.annexia.org/?a=blobdiff_plain;f=virt-what.pod;h=2e4a8b325b501bc4c9dc1318bc45d930989d766e;hb=fe3fbe4ec266cdf79f84202f6605ac301604059d;hp=06308b4bc3705c105efa3ae1ae2897b3f7884cd3;hpb=9975d7cf6f74ea588d79a82a9a3843aa6629f4da;p=virt-what.git diff --git a/virt-what.pod b/virt-what.pod index 06308b4..2e4a8b3 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. @@ -196,7 +228,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 @@ -208,7 +240,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