| Summary: | Cannot build qemu 1.0 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Olav Vitters <olav> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | misc, n54, pterjan, tmb |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | gcc-4.6.2-1.mga2.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Olav Vitters
2012-01-17 09:22:50 CET
It looks like a qemu-kvm problem. Fix_save-restore_of_in-kernel_i8259.patch addresses part of it (you would get a 3rd undefined symbol without the patch). I'll try to look at it tomorrow. CC:
(none) =>
pterjan I think it's good to switch to qemu... kvm is merged into it, CC:
(none) =>
n54 I've prepared a clean chroot environment, disabled the patch, switched to qemu (instead of qemu-kvm) and bm -l'ed it. And finally it WORKSFORME. The last thing is to adjust %files.. Fedora uses qemu-kvm and is able to compile it. My goal is to ensure gnome-boxes works. At the moment, it doesn't. Does it work with plain qemu? I'm not the qemu maintainer btw. Fedora does not build the ppc target
Manuel Hiebel
2012-01-18 12:14:10 CET
CC:
(none) =>
misc Qemu didn't merged kvm, or they would not have kept the project. So we will not switch. https://wiki.archlinux.org/index.php/QEMU#Difference_between_qemu_and_qemu-kvm Upstream QEMU is a pure emulator, with no hardware acceleration. qemu versions < 0.15.0 do have initial KVM support when QEMU is started with the -enable-kvm parameter, but this implementation is still buggy and nowhere as complete as in qemu-kvm, as many functions still do not work. Starting with qemu version 0.15.0, the qemu-kvm tree has been fully integrated with the qemu tree, and there should not be any difference between qemu -enable-kvm and qemu-kvm. See the [QEMU changelog] for more details. Upstream QEMU is capable of emulating many different platforms (arm, i386, m68k, mips, ppc, sparc, x86_64, etc). On the other hand, you have qemu-kvm, which is qemu (i386 and x86_64 architecture support only) with KVM (kernel-based virtual machine) additions, allowing you to run virtual machines at close to native speed. qemu-kvm is the version you want if you have a CPU that supports hardware virtualization and you only need to run virtual machines for the i386 and x86_64 architectures (Linux, Windows, BSD, etc). Michael, what do you think? In my opinion there is no reason to stick to qemu-kvm. (In reply to comment #8) > https://wiki.archlinux.org/index.php/QEMU#Difference_between_qemu_and_qemu-kvm > > Upstream QEMU is capable of emulating many different platforms (arm, i386, > m68k, mips, ppc, sparc, x86_64, etc). On the other hand, you have qemu-kvm, > which is qemu (i386 and x86_64 architecture support only) with KVM > (kernel-based virtual machine) additions, This is not true, qemu-kvm also contains all the qemu code for other archs and we build them in our package. Pascal, and besides this? ping Build is fixed Status:
NEW =>
RESOLVED |