Summary: | app-emulation/libvirtd-0.x.x does not start anymore with qemu-kvm | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Rafael Kolless <rafael> |
Component: | Current packages | Assignee: | Doug Goldstein (RETIRED) <cardoe> |
Status: | RESOLVED FIXED | ||
Severity: | critical | CC: | blshadow, ikelos, larstobi |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://blog.cardoe.com/archives/2009/11/22/kvm-changes-in-gentoo/ | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 294169 | ||
Bug Blocks: |
Description
Rafael Kolless
2009-11-25 20:54:48 UTC
Attach your emerge --info, emerge -pv qemu-kvm libvirtd, your log from libvirtd and a backtrace. For info how to get a backtrace, see http://www.gentoo.org/proj/en/qa/backtraces.xml Actually it crashes because it can´t find /usr/bin/kvm anymore. It´s a real simple error. I remerge kvm-88-r2 out of an overlay and the error is gone. qemu-kvm is fully incompatible to libvirtd Jep! I can confirm this error here. Downgrade to kvm-88-r2 helped. My /usr/bin/kvm is also missing. I can confirm this bug. Made an update today and I can't start or use my kvm machines anymore with libvirt. Please readd app-emulation/kvm. (In reply to comment #4) > I can confirm this bug. Made an update today and I can't start or use my kvm > machines anymore with libvirt. Please readd app-emulation/kvm. > I think part of the issue is that libvirt is looking for /usr/bin/kvm. I symlinked my qemu to /usr/bin/kvm and it worked for me. See http://wiki.libvirt.org/page/Tips#Libvirt_wont_connect_to_qemu_hypervisor_.28KVM.29 After upgrading to qemu-kvm (up from the old kvm), you should rebuild libvirt; in my case that worked and picked up the new qemu/kvm binary. I had problems with the existing VMs (which had the old binary in the xml), but libvirtd starts and works after a rebuild. Well, it seems not to work for me? When I want to start with kvm-0.11 and libvirt, I get this error: internal error no supported architecture for os type 'hvm' (In reply to comment #7) > Well, it seems not to work for me? > When I want to start with kvm-0.11 and libvirt, I get this error: > internal error no supported architecture for os type 'hvm' > you probably built qemu-kvm without defining QEMU_SOFTMMU_TARGETS; this is different than what is discussed here. Also, in case this helps, any pre-existing VMs built before the re-merge of kvm and qemu will specify a vm-type of kvm in their XML descriptor file. This can be altered to read qemu and the machine will continue to boot normally (and if qemu-kvm is installed, with kvm extensions). As such this probably doesn't affect new VMs after the rebuild, just existing ones. Symlinking /usr/bin/qemu to /usr/bin/kvm will solve the problem, but isn't as good as setting the vm type in the XML descriptor file itself... qemu-kvm installs a /usr/bin/kvm symlink. You should have never used an architecture type of "kvm". It was always "hvm". This issue should really be completely solved now. As I stated in my last comment, fixed. |