1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] qemu new upstream release (1.0-rc1) and should we move from qemu-kvm to qemu?
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20qemu%20new%20upstream%20release%20%281.0-rc1%29%20and%20should%20we%20move%0A%20from%20qemu-kvm%20to%20qemu%3F&In-Reply-To=%3C4EBE9443.4070009%40gmx.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="009499.html">
<LINK REL="Next" HREF="009501.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] qemu new upstream release (1.0-rc1) and should we move from qemu-kvm to qemu?</H1>
<B>Kamil Rytarowski</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20qemu%20new%20upstream%20release%20%281.0-rc1%29%20and%20should%20we%20move%0A%20from%20qemu-kvm%20to%20qemu%3F&In-Reply-To=%3C4EBE9443.4070009%40gmx.com%3E"
TITLE="[Mageia-dev] qemu new upstream release (1.0-rc1) and should we move from qemu-kvm to qemu?">n54 at gmx.com
</A><BR>
<I>Sat Nov 12 16:44:03 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="009499.html">[Mageia-dev] tar-1.26
</A></li>
<LI>Next message: <A HREF="009501.html">[Mageia-dev] qemu new upstream release (1.0-rc1) and should we move from qemu-kvm to qemu?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#9500">[ date ]</a>
<a href="thread.html#9500">[ thread ]</a>
<a href="subject.html#9500">[ subject ]</a>
<a href="author.html#9500">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Let me paste from the Arch Linux wiki documentation:
--
Difference between qemu and qemu-kvm
Depending on your needs, you can choose either to install upstream qemu
or qemu-kvm from the official repositories.
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).
Not all processors support KVM. You will need an x86-based machine
running a recent ( >= 2.6.22 ) Linux kernel on an Intel processor with
VT-x (virtualization technology) extensions or an AMD processor with SVM
(Secure Virtual Machine) extensions (also called AMD-V). Xen has a
complete list of compatible processors. For Intel processors, see also
the Intel® Virtualization Technology List.
<A HREF="https://wiki.archlinux.org/index.php/QEMU#Difference_between_qemu_and_qemu-kvm">https://wiki.archlinux.org/index.php/QEMU#Difference_between_qemu_and_qemu-kvm</A>
--
And now from the qemu changelog
~~
KVM
Common
Countless fixes ported over from qemu-kvm, core is now shared with
that tree, i.e. has the same quality
Pimped up threading model, now fully synchronized with qemu-kvm tree
Removed dependency on external kernel headers, all supported KVM
features are now built into the binary
<A HREF="http://wiki.qemu.org/ChangeLog/0.15#KVM">http://wiki.qemu.org/ChangeLog/0.15#KVM</A>
~~
What do you think? Can we move?
There is also one important patch missed in Mageia -
<A HREF="http://lists.gnu.org/archive/html/qemu-devel/2011-11/msg00787.html">http://lists.gnu.org/archive/html/qemu-devel/2011-11/msg00787.html</A> it's
dependency for the GNS3 simulator. OpenSUSE already includes it
<A HREF="https://build.opensuse.org/package/files?package=qemu&project=openSUSE%3ATools">https://build.opensuse.org/package/files?package=qemu&project=openSUSE%3ATools</A>
If nobody is against I will do it and contact the maintainer (misc).
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="009499.html">[Mageia-dev] tar-1.26
</A></li>
<LI>Next message: <A HREF="009501.html">[Mageia-dev] qemu new upstream release (1.0-rc1) and should we move from qemu-kvm to qemu?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#9500">[ date ]</a>
<a href="thread.html#9500">[ thread ]</a>
<a href="subject.html#9500">[ subject ]</a>
<a href="author.html#9500">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|
