We have a system we are adding as a KVM Host System. While scanning for KVM instances on the hosts, we are getting the following error:
Finding running KVM processes ..
.. found 1 processes
Processing KVM command /usr/libexec/qemu-kvm -S -M rhel5.4.0 -m 4096 -smp 4 -name klingon -uuid 5f0290ca-a729-5a79-18bf-b40285d30c20 -no-kvm-pit-reinjection -monitor pty -pidfile /var/run/libvirt/qemu//klingon.pid -boot c -drive file=/boot_drives/klingon.img,if=virtio,index=0,boot=on,cache=none -drive file=,if=ide,media=cdrom,index=2 -drive file=/dev/disk/by-path/ip-10.7.7.5:3260-iscsi-iqn.1986-03.com.sun:02:5c09ee61-ad3d-6b27-d1bd-d5b2b9008e10-lun-0,if=virtio,index=1 -net nic,macaddr=54:52:00:0e:41:9c,vlan=0,model=virtio -net tap,fd=15,script=,vlan=0,ifname=vnet0 -serial pty -parallel none -usb -vnc 127.0.0.1:0 -k en-us ..
.. could not work out primary disk image
This is the only KVM instance configured on the system. It was created using virt-manager and has 3 disks attached to it. The boot drive is a file-based disk image on an NFS server (index=0). There is an iSCSI disk attached using its "by-path" name under /dev (index=1). Finally, there is a cdrom device with no disk inserted (index=2).
The host system is running CentOS 5.5 with latest updates.
Are there any workarounds to get this KVM instance recognized?
Jamie has a patch for this, see https://www.virtualmin.com/node/14808