OS: Ubuntu 13.04 Cloudmin: 7.2.kvm Webmin: 1.650
For some time now, I cannot start virtual machines using cloudmin, all failing with the above message - perhaps after upgrading from Ubuntu 12.04.
When I look for the command which cloudmin is using ps ax, I get e.g. this:
qemu-system-x86_64 -machine accel=kvm:tcg -name updatetest.localhost -m 1024 -drive file=/dev/volg2/updatetest_localhost_img,media=disk,index=0,if=virtio -boot c -net tap,vlan=0,script=/kvm/updatetest.localhost-eth0.sh -net nic,vlan=0,macaddr=02:54:00:XX:XX:XX,model=virtio -vnc :2,password -usbdevice tablet -k de -usbdevice tablet
Starting it manually (without -monitor and -vnc options), the machine works as expected.
So, how can I - tell cloudmin to use qemu-system-x86_64 instead of kvm command, or
tell cloudmin to ignore the deprecated message so it lets the vm start
/usr/bin/kvm looks like this:
echo "W: kvm binary is deprecated, please use qemu-system-x86_64 instead" >&2 exec qemu-system-x86_64 -machine accel=kvm:tcg "$@"
Best regards and thanx in advance Falko
Comments
Submitted by JamieCameron on Mon, 09/30/2013 - 21:24 Comment #1
Thanks - I will have Cloudmin use this command in the next release.
Submitted by Issues on Mon, 10/14/2013 - 22:41 Comment #2
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by lulatsch66 on Wed, 11/13/2013 - 10:49 Comment #3
Hello Jamie,
thanx for your efforts - just got new webmin-server-manager release "7.3gpl" installed.
And .... no virtual machine is recognized as "running" any more.
Now I've found the line there this can be corrected - IMHO the term "qemu-system-x86_64" must be added there:
/usr/share/webmin/server-manager/kvm-type-lib.pl around line 6636:
while($cmd =~ s/(\d)(<|>)((\/\S+)|&\d+)\s$//) { }
if ($line =~ /^\s(\S+\/|)(qemu-kvm|kvm|qemu|qemu-system-x86_64)\s+(.)/) {
Best regards Falko
Submitted by JamieCameron on Wed, 11/13/2013 - 11:32 Comment #4
Thanks for catching that - I will include this fix in the next Cloudmin release.
Submitted by Issues on Wed, 11/27/2013 - 11:41 Comment #5
Automatically closed -- issue fixed for 2 weeks with no activity.