| Summary: | app-emulation/libvirt-0.7.4 +kvm - not able to create a kvm emulation type VM (qemu only available option) using GUI- | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Dragos Delcea <dragos.delcea> |
| Component: | Current packages | Assignee: | Lance Albertson (RETIRED) <ramereth> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | blshadow, ephemient, marineam, xen |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Dragos Delcea
2009-11-23 10:09:51 UTC
(In reply to comment #0) > when using libvirt-0.7.4 I'm no longer able to create a kvm accelerated VM > using the GUI; it was possible to do this with 0.7.2. > haven't tried with cli commands What use flags are libvirt built with? What versions of libvirt, and qemu-kvm do you have? Can you please try with libvirt-0.7.4-r2 and see if you're still encountering issues? Thanks! libvirt assumes that only "/usr/bin/kvm" or "/usr/bin/qemu-kvm" can be kvm, and that anything else is not. The app-emulation/qemu-kvm package does not install any binaries by those names, so libvirt forcibly disables kvm mode.
I have a horrible patch applied to my system:
--- a/src/qemu/qemu_conf.c 2009-12-17 21:20:55.018848525 -0500
+++ b/src/qemu/qemu_conf.c 2009-12-17 21:21:50.998909749 -0500
@@ -641,18 +641,9 @@
*/
if (STREQ(info->arch, hostmachine) ||
(STREQ(hostmachine, "x86_64") && STREQ(info->arch, "i686"))) {
- const char *const kvmbins[] = { "/usr/bin/qemu-kvm", /* Fedora */
- "/usr/bin/kvm" }; /* Upstream .spec */
-
- for (i = 0; i < ARRAY_CARDINALITY(kvmbins); ++i) {
- if (access(kvmbins[i], X_OK) == 0 &&
- access("/dev/kvm", F_OK) == 0) {
- haskvm = 1;
- kvmbin = kvmbins[i];
- if (!binary)
- binary = kvmbin;
- break;
- }
+ if (access("/dev/kvm", F_OK) == 0) {
+ haskvm = 1;
+ kvmbin = binary;
}
if (access("/dev/kqemu", F_OK) == 0)
But it would be better to use feature probes like libvirt already does for other qemu features.
This was a bug with qemu-kvm and is fixed in the 0.12 series already. |