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.

Not to disrespect Ubuntu, but Jaunty must be the worse release they have made in a long time. Whether it be an unusable desktop because of a poor kernel – upgrading to 2.6.30 is a good idea – or just poor packaging – md overwriting the mdadm.conf file? WTF?  See here and here for the workaround lists, and here to fix the md issue.

Karmic is getting good reviews. Lets hope its an easy upgrade and sets the scene for an amazing 10.4 release.

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 →

Just did an install of the 9.04 desktop. Very clean. Intend to do some testing with kvm, virtual box and win4lin.

From Professional VMware blog, here is another method to fix your lost Ethernet device on Ubuntu.

Another method of doing this, is to edit the ‘persistent-net-generator.rules’ file to include something similar to:

# ignore VMware virtual interfaces
ATTR{address}==”00:0c:29:*”, GOTO=”persistent_net_generator_end”

According to this thread, if you need to use the linux-image-virtual package on ubuntu then it only supports the “bus logic” scsi controller with ESX.

I tried several methods last night including Unetbootin, and this is the one that worked best.

• Using Windows to prepare USB install of Ubuntu 8.10
• Preparing Files for USB Memory Stick Booting

Basically copy the ISO on the USB root directory, add vmlinuz and initrd.gz from main/installer-i386/current/images/hd-media/. Then add syslinux.cfg with:

default vmlinuz
append initrd=initrd.gz

If you have boot problems you might also need to run install-mbr /dev/sda from the mbr package.

I keep smacking into this issue. So a couple notes to myself for future reference.

• Tinydns / DJBDNS on Ubuntu Hardy Heron
• upstart breaks inittab

Before install touch /etc/inittab and afterwards add this to /etc/event.d/svscan:

start on runlevel 3
start on runlevel 4
start on runlevel 5

stop on runlevel 0
stop on runlevel 1
stop on runlevel 6

respawn
exec /usr/bin/svscanboot