| Summary: | gnome-extra/gnome-boxes: cannot find /usr/bin/qemu-kvm (no such file or directory) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Francesco Turco <fturco> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | CC: | cardoe, genzilla, qemu+disabled |
| Priority: | Normal | Keywords: | NeedPatch |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://bugzilla.gnome.org/show_bug.cgi?id=731112 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Francesco Turco
2014-06-02 15:48:34 UTC
GNOME developer Zeeshan Ali said me to use the "virsh edit" command to change the following line: > <emulator>/usr/bin/qemu-kvm</emulator> into: > <emulator>/usr/bin/qemu-system-x86_64</emulator> Now I can successfully launch the VM without the need for the symlink. But I still wonder if there's some Gentoo problem that need to be fixed for avoiding users to resort to this kind of tricks. @gnome, is gnome-boxes only compatible with qemu-system-x86_64? In that case, we should patch the value to use that one I think Well, looks like we should show a warning telling people to fix their VMs with that command instead :/. But that should be probably done by kvm maintainers as will affect to the old VMs I have the same problem (but I start the VM from a shell script), no qemu-kvm. I have KVM build into the kernel (checked it yesterday while building a new kernel), but no qemu-kvm. I replaced it with qemu-system-i386 and that worked, but it is considerable slower (I also tried qemu-system-x86_64, but that one was even slower than the i386 one). (In reply to Myckel Habets from comment #4) > I have the same problem (but I start the VM from a shell script), no > qemu-kvm. I have KVM build into the kernel (checked it yesterday while > building a new kernel), but no qemu-kvm. I replaced it with qemu-system-i386 > and that worked, but it is considerable slower (I also tried > qemu-system-x86_64, but that one was even slower than the i386 one). For the slowness, apparently you have the pass -enable-kvm to the command line. This made it fast again. grepping in sources I see no hard coded path to qemu-kvm, then, probably the message deserves qemu ebuild itself but I am not sure since I am not familiar with this at all :( @cardoe, @qemu team, what do you think? Thanks a lot I just ran into the same problem using virt-manager. I am new to kvm/qemu stuff and tried to start a "proof of concept vm" I created a few months ago. After adding the symlink /usr/bin/qemu-kvm -> /usr/bin/qemu-system-x86_64 it worked. Then I tried to use "virsh edit" as the alternative solution suggested, but that required a domain name: error: command 'edit' requires <domain> option Afaik "virsh list" is supposed to tell me my domain name, but in my case the returned list was empty: Id Name State ---------------------------------------------------- So I ended up deleting my vm and creating a new one, since it wasn't important for me. ( Just in case anyone else has the same problem. ) what config file ? the qemu ebuild already warns about qemu-kvm going away, and specifically checks for /etc/libvirt/qemu/*.xml. |
