You are not logged in.
virsh # list --all
Id Name State
----------------------------------------------------
- centos5_i386 shut off
- centos6 shut off
- ubuntu12.04 shut off
virsh # start centos5_i386
error: Failed to start domain centos5_i386
error: Cannot check QEMU binary /usr/bin/qemu-kvm: No such file or directory
Offline
libvirt is trying to start the wrong executable.
$ pacman -Ql qemu | grep /usr/bin
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Offline
libvirt is trying to start the wrong executable.
$ pacman -Ql qemu | grep /usr/bin
yeah, but this is updated by system, which replace qemu-kvm with qemu, qemu-kvm has /usr/bin/qemu-kvm. I checked the wiki, it said:
Note: qemu-kvm is a fork of qemu which will eventually disappear when all its features become part of qemu.
Note: qemu-kvm no longer exists as all of its features have been merged into qemu.
the 2nd does not exist when I checked the wiki first time today. So I guess 1st sentence is true now, and I should modify the xml configuration of the guest os
<devices>
<emulator>/usr/bin/qemu-kvm</emulator>
which value should I fill it up? I tried qemu-x86_64, qemu-img, both are wrong.
Offline
Yes, the two have now merged.
Depends on your system.I'm running qemu-system-x86_64, but that's because my system is 64 bit. You might want the 32 bit one - if you "man qemu" it's the one shown in the usage line.
qemu-img is the image maintenance utility.
(edit -fixed executable name)
Last edited by skanky (2013-03-05 16:31:32)
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Offline
ok, seems qemu-system-i386, qemu-system-x86_64 are all right.
not sure if it's the answer.
Offline
Working for me. You may need to revisit your system attributes though. The default devices may have changed.
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Offline
Yes, the two have now merged.
Depends on your system.I'm running qemu-x86_64, but that's because my system is 64 bit. You might want the 32 bit one - if you "man qemu" it's the one shown in the usage line.
qemu-img is the image maintenance utility.
Thanks. but neither i386 or x86_64 is right for me. As I mentioned earlier, system-i386 and system-x86_64 is right for me.
when I 'man qemu', seems is the manual for qemu-system-i386?
and seems there is wrong in the manual, 'qemu-system-x86_84 --drive file=gluster://192.0.2.1/testvol/a.img', which should be qemu-system-x86_64.
so how should I choose i386 and x86_64, based on host os or guest os? I think should be host os.
Offline
skanky wrote:Yes, the two have now merged.
Depends on your system.I'm running qemu-x86_64, but that's because my system is 64 bit. You might want the 32 bit one - if you "man qemu" it's the one shown in the usage line.
qemu-img is the image maintenance utility.
Thanks. but neither i386 or x86_64 is right for me. As I mentioned earlier, system-i386 and system-x86_64 is right for me.
when I 'man qemu', seems is the manual for qemu-system-i386?
and seems there is wrong in the manual, 'qemu-system-x86_84 --drive file=gluster://192.0.2.1/testvol/a.img', which should be qemu-system-x86_64.
so how should I choose i386 and x86_64, based on host os or guest os? I think should be host os.
Yes sorry, my typo - see my post edit.
It's based on host OS - at least I assume so as that's what I based my decsion on and it works for me.
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Offline
I created a symlink to make this easier. All of my VMs are 64-bit.
ln -s /usr/bin/qemu-{system-x86_64,kvm}
Seems to be working great for me. Thanks guys!
Offline
cyberyoung wrote:skanky wrote:Yes, the two have now merged.
Depends on your system.I'm running qemu-x86_64, but that's because my system is 64 bit. You might want the 32 bit one - if you "man qemu" it's the one shown in the usage line.
qemu-img is the image maintenance utility.
Thanks. but neither i386 or x86_64 is right for me. As I mentioned earlier, system-i386 and system-x86_64 is right for me.
when I 'man qemu', seems is the manual for qemu-system-i386?
and seems there is wrong in the manual, 'qemu-system-x86_84 --drive file=gluster://192.0.2.1/testvol/a.img', which should be qemu-system-x86_64.
so how should I choose i386 and x86_64, based on host os or guest os? I think should be host os.
Yes sorry, my typo - see my post edit.
It's based on host OS - at least I assume so as that's what I based my decsion on and it works for me.
really thanks for your help.
Offline
really thanks for your help.
No problem.
"...one cannot be angry when one looks at a penguin." - John Ruskin
"Life in general is a bit shit, and so too is the internet. And that's all there is." - scepticisle
Offline