While trying to run a lucid image on Lucid UEC the instance isn't able to be started.
According to the libvirt log file:
ubuntu@mabolo:~$ sudo cat /var/log/libvirt/qemu/i-4EC209E0.log
LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 512 -smp 2 -name i-4EC209E0 -uuid a4315a8f-5c7c-ca4c-f158-4139e1663fd9 -nographic -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/i-4EC209E0.monitor,server,nowait -monitor chardev:monitor -boot c -kernel /var/lib/eucalyptus/instances//admin/i-4EC209E0/kernel -append root=/dev/sda1 console=ttyS0 -drive file=/var/lib/eucalyptus/instances//admin/i-4EC209E0/disk,if=scsi,index=0,boot=on -net nic,macaddr=d0:0d:4e:c2:09:e0,vlan=0,model=e1000,name=e1000.0 -net tap,fd=65,vlan=0,name=tap.0 -chardev file,id=serial0,path=/var/lib/eucalyptus/instances//admin/i-4EC209E0/console.log -serial chardev:serial0 -parallel none -usb
qemu: could not load kernel '/var/lib/eucalyptus/instances//admin/i-4EC209E0/kernel': Success
The following messages can be found in the kernel dmesg:
[324292.651948] type=1505 audit(1266263729.611:11): operation="profile_load" pid=28516 name="libvirt-a4315a8f-5c7c-ca4c-f158-4139e1663fd9"
[324292.661181] device vnet0 entered promiscuous mode
[324292.663037] br0: port 2(vnet0) entering learning state
[324292.664674] type=1503 audit(1266263729.620:12): operation="open" pid=28524 parent=1 profile="libvirt-a4315a8f-5c7c-ca4c-f158-4139e1663fd9" requested_mask="r::" denied_mask="r::" fsuid=0 ouid=0 name="/proc/28524/status"
[324292.664695] type=1503 audit(1266263729.620:13): operation="capable" pid=28524 parent=1 profile="libvirt-a4315a8f-5c7c-ca4c-f158-4139e1663fd9" name="setpcap"
[324292.961606] br0: port 2(vnet0) entering disabled state
[324293.039824] device vnet0 left promiscuous mode
[324293.039828] br0: port 2(vnet0) entering disabled state
[324322.741666] type=1505 audit(1266263759.752:14): operation="profile_remove" pid=28601 name="libvirt-a4315a8f-5c7c-ca4c-f158-4139e1663fd9" namespace="default"
eucalyptus: 1.6.2~bzr1189-0ubuntu1
libvirt: 0.7.5-5ubuntu7
qemu-kvm: 0.12.2-0ubuntu6
I suspect something is wrong before qemu-kvm is involved.
I just verified that I can do the following on 'mabolo':
=== go.sh ===
tmpd=$PWD/t
mkdir ${tmpd}
qemu-img create -f qcow2 "${tmpd}/disk" 1G
LC_ALL=C PATH=/usr/
=== end go.sh ===
The differences in the command above are really only in where the monitor and are directed. With the above, kvm will successfully load the kernel and panic with "cant find root" (because there is no root in the newly created disk image).
I tested above with kernel lucid-server-