Make sure to state that the host system in the "Create a new image"
example is a Debian Wheezy system. Most of the things work in every
distro, but some commands (e.g. kvm) may have a different name or
a slightly different functionality.

The program would crash if no image properties were available and
the user chose "Edit properties" or "Delete Properties" in the
customization menu

Allow the characters that kamaki allows

Before shrinking a filesystem use the e2fsck -y if the underlined
guestfs library supports it.

Otherwise print a warning.

The fix was backported to version 1.16.11

--print-sysprep should be --print-syspreps

It used to be a function in util module

The machine hardware name fetched by `uname -m' should have been
stripped, and a --enable-kvm option should be added if the returned
executable was qemu-system-<arch>

If the media is windows and guestfs version is less than 1.17.18
raise a Fatal Error. The versions below this have a bug and
inspect_os will fail if the HKLM\SYSTEM\MountedDevices registry key
is missing. This key gets deleted by Microsoft Sysprep

Before libguestfs 1.18.4 you cannot shutdown the backend and then
relaunch it

Conflicts:
	image_creator/os_type/unix.py
	image_creator/version.py
	version

Don't try to scrub data unless the used guestfs appliance supports
it

On some systems it is kvm, on some others it is qemu-system-x86_64. On
32bit PC it is qemu-system-i386

Group the system preparation tasks to simple and advanced.

Remove constants BOOT_TIMEOUT, SHUTDOWN_TIMEOUT and CONNECTION_RETRIES
and add then as sysprep_parameters

This is needed since the input we get from the input dialogs is
always strings.

Fix some bugs and some other coding issues found using pylint