Pre-existing kvm instances are not bootable through cloudmin

This is related to the KVM instance referenced in https://www.virtualmin.com/node/14808

This KVM instance was auto-detected when the server was added as a KVM Host. The problem is that if I shut down the KVM instance and then try to start it through Cloudmin, it is started with a much more abbreviated set of options which does not include the extra drives that should be attached to the VM.

If I start the VM through virt-manager, this is the process that is started:

root 25870 1 42 16:16 ? 00:14:51 /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=16,script=,vlan=0,ifname=vnet0 -serial pty -parallel none -usb -vnc 127.0.0.1:0 -k en-us

if I start it through Cloudmin, this is the process that gets started:

root 27646 1 49 16:55 ? 00:00:07 /usr/libexec/qemu-kvm -name klingon -m 4096 -drive file=/boot_drives/klingon.img,if=virtio,index=0,boot=on,cache=none -boot c -serial stdio -vnc :1

Seemingly important options that get dropped include:

-M rhel5.4.0
-smp 4
-uuid 5f0290ca-a729-5a79-18bf-b40285d30c20
-no-kvm-pit-reinjection
-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

I guess if the VM was created through Cloudmin, then we would not run into these issues?

I'm also guessing you are trying to avoid integrating with libvirt using Sys::Virt? It would certainly simplify things if the config interoperated with libvirt...