+If you are already in the fish/ subdirectory, then the following
+command will also work:
+
+ ../run ./guestfish [...]
+
+You can also make a symlink (note: NOT a hard link) from your $PATH to
+the run script, eg:
+
+ cd ~/bin
+ ln -s ~/libguestfs/run libguestfs-run
+ cd ~/libguestfs
+ libguestfs-run ./inspector/virt-inspector [...]
+
+You can also run the C programs under valgrind like this:
+
+ ./run valgrind [valgrind opts...] ./cat/virt-cat [virt-cat opts...]
+
+This also works with sudo (eg. if you need root access for libvirt or
+to access a block device):
+
+ sudo ./run ./cat/virt-cat -d LinuxGuest /etc/passwd
+
+
+qemu
+----------------------------------------------------------------------
+
+By far the most common problem is with broken or incompatible
+qemu releases.
+
+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.
+
+
+vmchannel