+Fedora
+----------------------------------------------------------------------
+
+We provide packages for Fedora >= 11 in Fedora. Use those, or build
+from our source RPMs - it's far simpler that way.
+
+You can compile libguestfs on Fedora 10 but you cannot use it with the
+version of qemu in Fedora 10. You need to compile your own qemu, see
+section 'qemu' below.
+
+
+RHEL / EPEL / CentOS etc
+----------------------------------------------------------------------
+
+We provide packages in EPEL which cover RHEL/CentOS >= 5. Use those
+or build from our source RPMs.
+
+
+Debian
+----------------------------------------------------------------------
+
+libguestfs is now built as a package in Debian by Guido Gunther and
+the other Debian libvirt maintainers. See:
+
+http://wiki.debian.org/Teams/DebianLibvirtTeam#Packages
+
+You can build for Debian in two different ways, either building a
+Fedora-based appliance using febootstrap, yum, rpm, fakeroot,
+fakechroot (all packaged in Debian). However the recommended way is
+to build a Debian-based appliance using debootstrap and debirf.
+
+Both ways are supported by the configure script.
+
+
+qemu
+----------------------------------------------------------------------
+
+By far the most common problem is with broken or incompatible
+qemu releases.
+
+First of all, you need qemu >= 0.10.4, which contains a vmchannel
+implementation. There are several, conflicting, incompatible things
+called 'vmchannel' which at one time or another have been added or
+proposed for qemu/KVM. The _only_ one we support is this one:
+
+ http://lists.gnu.org/archive/html/qemu-devel/2009-02/msg01042.html
+
+Secondly, different versions of qemu have problems booting the
+appliance for different reasons. This varies between versions of
+qemu, and Linux distributions which add their own patches.
+
+If you find a problem, you could try using your own qemu built from
+source (qemu is very easy to build from source), with a 'qemu
+wrapper'. Qemu wrappers are described in the guestfs(3) manpage.
+
+
+Note on using KVM
+----------------------------------------------------------------------
+
+By default the configure script will look for qemu-kvm (KVM support).
+You will need a reasonably recent processor for this to work. KVM is
+much faster than using plain Qemu.
+
+You may also need to enable KVM support for non-root users, by following
+these instructions:
+
+ http://www.linux-kvm.org/page/FAQ#How_can_I_use_kvm_with_a_non-privileged_user.3F
+
+On some systems, this will work too:
+
+ chmod o+rw /dev/kvm
+
+On some systems, the chmod will not survive a reboot, and you will
+need to make edits to the udev configuration.
+
+
+Supermin appliance
+----------------------------------------------------------------------
+
+If you configure with --enable-supermin then we will build a supermin
+appliance (supermin = super-minimized). This is a very specialized
+appliance which is built on-the-fly at runtime (specifically, when you
+call guestfs_launch).
+
+The normal appliance is a self-contained Linux operating system, based
+on the Fedora/RHEL/CentOS Linux distro. So it contains a complete
+copy of all the libraries and programs needed, like kernel, libc,
+bash, coreutils etc etc.
+
+The supermin appliance removes the kernel and all the executable
+libraries and programs from the appliance. That just leaves a
+skeleton of config files and some data files, which is obviously
+massively smaller than the normal appliance. At runtime we rebuild
+the appliance on-the-fly from the libraries and programs on the host
+(eg. pulling in the real /lib/libc.so, the real /bin/bash etc.)
+
+Although this process of rebuilding the appliance each time sounds
+slow, it turns out to be faster than using the prebuilt appliance.
+(Most of the saving comes from not compressing the appliance - it
+transpires that decompressing the appliance is the slowest part of the
+whole boot sequence). On my machine, a new appliance can be built in
+under a fifth of a second, and the boot time is several seconds
+shorter.
+
+The big advantage of the supermin appliance for distributions like
+Fedora is that it gets security fixes automatically from the host, so
+there is no need to rebuild the whole of libguestfs for a security
+update in some underlying library.
+
+There are several DISADVANTAGES:
+
+It won't work at all except in very narrow, controlled cases like the
+Fedora packaging case. We control the dependencies of the libguestfs
+RPM tightly to ensure that the required binaries are actually present
+on the host.
+
+Furthermore there are certain unlikely changes in the packages on the
+host which could break a supermin appliance, eg. an updated library
+which depends on an additional data file.
+
+Also supermin appliances are subjected to changes in the host kernel
+which might break compatibility with qemu -- these are, of course,
+real bugs in any case.
+
+Lastly, supermin appliances really can't be moved between branches of
+distributions (eg. built on Fedora 12 and moved to Fedora 10) because
+they are not self-contained and they rely on certain libraries being
+around. You shouldn't do this anyway.
+
+Use supermin appliances with caution.
+
+