Ubuntu recently change their package names for kvm.  This comment posted on qemu-0.11.0 Released provides an explanation:

qemu-kvm includes features and fixes from upstream qemu and so takes its naming scheme from upstream qemu. You can think of it as qemu optimized for kvm. Note too that qemu-kvm does not include the kernel module but only the userspace and considered to be stable.

kvm-xx on the other hand is the development branch of kvm and not considered to be stable. It’s naming scheme is arbitrary and it also takes features from upstream qemu.

…

kvm-kmod is different to kvm-xx. You can think of kvm-kmod as a subset of the kvm-xx. KVM-xx = userspace + kernel where kvm-kmod is the kernel part of it and qemu-kvm is the userspace part (the guest process itself). You can apply the kvm-kmod to any distro version or linux version.. it’s just the kernel driver. However, without the userspace part, you can’t do much with it.

Here  some results from testing I did in August 2009 on  KVM with the three different disk image drivers. First a single disk system running Ubuntu x64 9.04:

Continue reading →

If you install a vm with vmbuilder without virtio the swap section of /etc/fstab will use /dev/sda2 instead of /dev/vda2. You can use blkid

nic@vm-base:~$ sudo blkid
/dev/vda1: UUID="bac299c4-c545-46ca-aed3-26da4a56f6d7" TYPE="ext3"
/dev/vda2: TYPE="swap" UUID="0c75b2dd-6c6f-4729-b041-0d95475dc171"
/dev/vdb: UUID="jIkLcQ-zXUo-KIWR-zvmm-cpKP-9PpT-eE9RY3" TYPE="lvm2pv"

nic@vm-base:~$ cat /etc/fstab
# /etc/fstab: static file system information.
# <file system>                                 <mount point>   <type>  <options>       <dump>  <pass>
proc                                            /proc           proc    defaults        0       0
/dev/sda1                                       /               ext3    defaults        0       0
UUID="0c75b2dd-6c6f-4729-b041-0d95475dc171"     swap            swap    defaults        0       0

in order to get swap working with different driver types.

I’ve started running KVM recently and I’ll post a review at some point. I’m finding it very flexible and much much easier to use that Xen.

There are still a few questions regarding file caches and disk images. In general I’m happy that it’s ready for production.

Redhat has acquired Qumranet the developers of KVM. Will be interesting to see how this plays out in the Linux virtualisation world.

I haven’t tried KVM yet as I’ve been too busy and Xen is more mature – but many of the accounts I’ve read seem to indicate that for Linux its performance is very good maybe better in some cases than Xen. Management is another issue, but that is just a matter of time and development enegry.

From lwn.