inspect: document also MINIX as OS

Followup of commit 5b65d05d5a31415aaa6f284f73da745e0ee0408a.
resize: Rewrite the tests to use a stochastic testing method.

The previous tests were very limited, and ran the same two tests
on every run.

Randomly test:
 - MBR vs GPT
 - Primary, extended partitions
 - Expanding vs shrinking
 - Use of multiple --resize parameters
 - Source and target raw vs qcow2 formats
 - Resizing various different filesystem types
 - LV expand
 - extra partition or no extra partition

To run the test over and over again (useful for finding regressions in
virt-resize), do:

  while (cd resize; LIBGUESTFS_TRACE=1 ../run ./test-virt-resize.pl) >&/tmp/log ; do echo -n .; done

If it fails, you can see the failure in /tmp/log.

To rerun a specific test, search for the 'seed:' in the output of the
original test, and specify it on the command line:

  (cd resize; ../run ./test-virt-resize.pl --seed=<SEED>)
resize: Don't test MBR extended partitions while virt-resize handling is broken.

The intention is to fix virt-resize and then revert this commit.
p2v: Fix reference to virt-v2v(1) in manual page.
sysprep: add no-op --no-selinux-relabel (RHBZ#1148072)

Add a no-op --no-selinux-relabel option, to be compatible with
virt-sysprep < 1.26.
v2v: Add note to man page about removing VMware tools before conversion.

Thanks: Matthew Booth.
lib: Avoid rewriting LV names when creating canonical device name (RHBZ#1148355).

Thanks: Timothée Ravier
v2v: Copy -o rhev information from old virt-v2v manual page.
v2v: Copy post-conversion tasks section from old virt-v2v documentation.

Copied verbatim, apart from some minor reformatting.
Version 1.27.57.
v2v: 'du -b' doesn't show real (sparse) size.

This caused the actual size to be wrong (in OVF output).
Use --block-size=1 instead.
v2v: Print the difference between our disk size estimate and actual size.
mllib: Coloured messages, errors, warnings.

Uses ANSI terminal codes to colour the output.
appliance: Use dhclient or dhcpcd instead of hard-coding IP address of appliance.

qemu in SLIRP mode offers DHCP services to the appliance.  We don't
use them, but use a fixed IP address intead.  This changes the
appliance to get its IP address using DHCP.

Note: This is only used when the network is enabled.  dhclient is
somewhat slower, but the penalty (a few seconds) is only paid for
network users.

On SuSE or other distros, dhcpcd could be used if available.
launch: libvirt: Use qemu-bridge-helper to implement a full network (RHBZ#1148012).

When using the libvirt backend, don't use the SLIRP.  Use
qemu-bridge-helper via libvirt to give us a full network connection.

One consequence of this is that 'ping' works in
'virt-builder --run-command'.

A less useful consequence is that the host firewall will prevent
connections on non-standard ports to the host.  So you can't (eg)
connect to a rsync daemon on the host listening on an arbitrary port,
which worked before.

The default bridge is 'virbr0', but you can override this by setting
LIBGUESTFS_BACKEND_SETTINGS=network_bridge=<some_bridge>

Note: this does not fix virt-rescue (since it overrides the default
backend and uses 'direct' for various reasons).
appliance: Change example ping lines to ping 8.8.8.8.

This are commented out (still) so this change does nothing.
tests: rsync: Skip this test when the backend is libvirt.

It would work, except if you have a host firewall which will block
inbound connections on virbr0 to non-standard ports.
tests: Disable UML tests in 'check-release'.

This effectively demotes UML to unsupported status.  This has happened
because UML has regressed quite a lot upstream.  There are multiple
grave bugs revealed by running the test suite and I don't have the
inclination to fix them.
Version 1.27.58.
RHEL 7: Emphasize libguestfs-winsupport package (RHBZ#627468).

This RHEL-only patch changes the error messages when the
inspection code cannot find an operating system inside the guest
image.  For a Windows guest this may happen because the user has not
installed the separate 'libguestfs-winsupport' package.  Therefore we
emphasize that the user may need to install this package.

Notes:

(1) In RHEL there are two pieces of inspection code, the old Perl code
(deprecated upstream) and the new C core inspection API.  Therefore
this patch has to touch two places with essentially the same change.

(2) This patch doesn't try to be clever and detect if it was a Windows
guest.  This should reduce the chance of failure.

Output from (Perl) virt-inspector now looks like this:

 $ virt-inspector disk.img
 No operating system could be detected inside this disk image.

 This may be because the file is not a disk image, or is not a virtual machine
 image, or because the OS type is not understood by virt-inspector.

 If you feel this is an error, please file a bug report including as much
 information about the disk image as possible.

 RHEL notice
 -------------
 libguestfs will return this error for Microsoft Windows guests if the
 separate 'libguestfs-winsupport' package is not installed. If the
 guest is running Microsoft Windows, please try again after installing
 'libguestfs-winsupport'.

Output from guestfish (ie. C core inspection API) now looks like this:

 $ guestfish -i disk.img
 guestfish: no operating system was found on this disk

 RHEL notice
 -------------
 libguestfs will return this error for Microsoft Windows guests if the
 separate 'libguestfs-winsupport' package is not installed. If the
 guest is running Microsoft Windows, please try again after installing
 'libguestfs-winsupport'.