I tried to create a kvm disk image via it's GUI utility but it fails when it actually goes to create the disk image with the following message: Unable to complete install: 'internal error Cannot find QEMU binary /usr/lib64/xen/bin/qemu-dm: No such file or directory' On Gentoo that file is actually located at /usr/bin/kvm-img Here are my libvirt USE flags. [ebuild R ] app-emulation/libvirt-0.4.6 USE="avahi kvm parted -iscsi -lvm -openvz -qemu -sasl (-selinux) -xen"
Hm, this is very strange indeed. I greped though the source and the only refrences to qemu-dm are in the documentation and in xen_internal.c which should nt have anything to do with creating a disk for kvm (or xen for that mater, qemu-dm is the emulator binary that libvirt uses for xen). Could you provide the exact steps you took to hit this problem? Creating disks for kvm is working for me with the same use flags. My best guess is that for whatever reason your virtual machine xml file was originally created for a xen guest so it lists qemu-dm instead of kvm and the error you are seeing is for guest startup, not disk creation. Changing the emulator tag to <emulator>/usr/bin/kvm</emulator> should fix that. After editing the file use virsh define to reload the xml file.
First time I ever used this stuff so it could be user error. 1) Edited /etc/libvirt/libvirtd.conf and changed unix_sock_group to "kvm" since that's the group that Gentoo uses instead of upstream's "libvirt" group. 2) started libvirt via /etc/init.d/libvirtd start 3) Started virt-manager 4) Clicked File -> Add Connection 5) Changed Hypervisor from Xen to QEMU (only other choice) 6) Connection was local 7) Clicked Connect 8) Clicked on local qemu 9) Clicked New on the bottom 10) Clicked Forward 11) System Name: "TestVM" 12) Forward 13) Only available choices here are Fully Virtualized, CPU x86_64, blank hypervisor 14) Forward 15) Local install media 16) OS Type: UNIX 17) OS Variant: FreeBSD 7.x 18) Forward 19) ISO Image location: /home/doug/7.0-RELEASE-i386-disc1.iso 20) Forward 21) Simple File, Location: /var/lib/libvirt/images/TestVM.img, Size: 8000 MB 22) Uncheck Allocate entire virtual disk now 23) Forward 24) Virtual Network, Network: Default 25) Forward 26) VM Max Memory and VM Startup Memory: 256 MB. VCPUs: 1 27) Forward 28) Finish Immediately get error message that reads as follows.. Unable to complete install: 'internal error Cannot find QEMU binary /usr/lib64/xen/bin/qemu-dm: No such file or directory' Details: Unable to complete install '<class 'libvirt.libvirtError'> internal error Cannot find QEMU binary /usr/lib64/xen/bin/qemu-dm: No such file or directory Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/create.py", line 722, in do_install dom = guest.start_install(False, meter = meter) File "//usr/lib64/python2.5/site-packages/virtinst/Guest.py", line 732, in start_install return self._do_install(consolecb, meter, removeOld, wait) File "//usr/lib64/python2.5/site-packages/virtinst/Guest.py", line 767, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "//usr/lib64/python2.5/site-packages/libvirt.py", line 892, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error Cannot find QEMU binary /usr/lib64/xen/bin/qemu-dm: No such file or directory '
I can confirm the problems because I'm experiencing the exact problem. Any progress in fixing the problem?
app-emulation/virt-manager-0.6.1 fixed the Problem for me
@ Evildad: could you post the output of emerge -pv libvirt virt-manager please? Cause i still experience this problem with version 0.6.1 of virt-manager.
I made the Version Bumps in my local Oberlay. emerge -pv libvirt virt-manager These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] app-emulation/libvirt-0.6.1 USE="hal kvm -avahi -iscsi -lvm -lxc -openvz -parted -qemu -sasl (-selinux) -uml -xen" 0 kB [1] [ebuild R ] app-emulation/virt-manager-0.6.1 USE="-gnome-keyring" 0 kB [1]
(In reply to comment #4) > app-emulation/virt-manager-0.6.1 fixed the Problem for me > as we have 0.7.0 closing this one for now, please reopen if it's still (or again) a problem w/ 0.7.0.
