If qemu-nbd is not present at the host system, only accept raw images
as input media. This is a workaround for ancient systems like CentOS 6.x
where the nbd module is not compiled in the default kernel and the qemu
package does not include the qemu-nbd executable.

Do not use qcow2 to snapshot images that are raw. qemu-nbd is not
present in some old systems like CentOS 6.x. All we can do to support
those systems is to use the device mapper in as many cases as possible.

This complies better with the python conventions

Hotfix 0.7.3

Support kamaki 0.13rc5. From this version on, kamaki uses ssl
certificates by default. For now, instruct kamaki to ignore the
certificates.

Hotfix 0.7.2

Bug fixes and documentation updates

Do not search for specific words in it. The messages may be in a
language other than English. Focus on the Numbers.

Do not use format=raw in the -drive option of KVM when booting the
Windows VM. The format could also be qcow2 if the original input media
is a regular file.

Populate this section with instructions on how to troubleshoot
libguestfs's launch failures.

Detect Kubuntu, Lubuntu and Xubuntu

 * Add instructions for CentOS 7
 * Use curl in favor of wget on Fedora and CentOS systems.

When bundling a host, make sure that the UUIDs and the Labels of the
original file systems are preserved.

Fix a bug in host-bundling operation were in some cases the computed
new image size was wrong.

Older versions of qemu-img do not accept a '--output json' option

The printed name of the sysprep tasks is constructed from the method
name by replacing the _ with " ". This can be used to overwrite it.

If you print the snapshotting message before disk.file is referenced,
you may end up outputting messages like this:

Snapshotting media source ... Examining source media `<image_file>' ...

Instead of:

Examining source media `<image_file>' ... looks like a block device
Snapshotting media source ... done

If you are a regular user, some root commands like modprobe may not be
in your path.

This exception does not exist in python 2.x

Start by waiting for 5sec before retrying and double the interval
after each retry.

The original value was 5min but was rather small. In Desktop versions
of windows the VirtIO installation may take longer.

When the button is pressed it displays further information about an
installed VirtIO driver.

Feature image format support