fixes two issues via patches to get knetwork compiling

kopete-4.10.4-kopete-linphonemediaengine.patch
----------------------------------------------
patch copied from here:
  https://bugs.kde.org/show_bug.cgi?id=318825

kopete-4.10.4-kopete-stun.patch
-------------------------------
  when compiling kopete/protocols/jabber/googletalk/libjingle/talk/session/phone/channelmanager.cc
  it would produce this error:

  kopete/protocols/jabber/googletalk/libjingle/talk/p2p/base/stunrequest.h:91:9: error: ‘StunMessageType’ does not name a type

  problem:
    this is cased by a cyclic use of stun.h, stunrequest.h and channelmanager.cc with the outcome,
    that kdenetwork couldn't be compiled since kopete fails to build.

  solution:
    move the StunMessageType enum into its own #ifndef
VM builds: Use qemu instead of the obsolete qemu-kvm
VM builds: Use ext4 instead of ext2
VM builds: Panic on OOM
VM builds: Increase the default memory size to 512 MB
VM builds: Use 9p/virtfs instead of CIFS

9p (with caching enabled) is much faster than CIFS and doesn't require
Samba or virtual networking.  For instance, building GNU Hello with
CIFS takes ~323s on my laptop, but with 9p it takes 54s.

More measurements will be needed to see if "cache=fscache" is really
faster than "cache=loose" (the former seems to be a little bit
faster).
Remove runInGenericVM

It's not used anywhere and probably doesn't work anymore.
heroku gem: add expression
Merge pull request #709 from qknight/kdenetwork-kopete-fixes

fixes two issues via patches to get knetwork compiling; both patches are minimal and mine is now also upstream
kde4: unify used libcanberra

I wondered why I'm getting two versions in the closure of KDE apps.
kile: minor update
kdiff3: maintenance update
Add loopback network device and localhost entry to /etc/hosts for VM tests.
Update acpi-call for Linux 3.10 compatibility
Update fdm
testdisk: Add to channel
Add CentOS 6.4 to vm images