<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html><body>
<p>On 12.02.2012 13:24, Robby Workman wrote:</p>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px; width:100%"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->
<pre>On Tue, 7 Feb 2012 15:40:13 +0100
Matteo Bernardini <<a href="mailto:matteo.bernardini@gmail.com">matteo.bernardini@gmail.com</a>> wrote:</pre>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px; width:100%">sorry for the delay, but I was fiddling with the stuff :) trying to ease maintaining also for end users and to follow Robby's concerns, I've adapted the qemu slackbuild to build also qemu-kvm and make a single package (by default, but there's a switch to disable building it). it's an experiment I assembled very fast but seems to work on my machines.</blockquote>
<pre>
After a small amount of tweaking, here's the result:
<a href="http://slackbuilds.org/cgit/slackbuilds/log/?h=qemu-merged">http://slackbuilds.org/cgit/slackbuilds/log/?h=qemu-merged</a>
(there are two commits, with fffd199a being the important one.
Another approach is this one:
<a href="http://slackbuilds.org/cgit/slackbuilds/log/?h=qemu-kvm">http://slackbuilds.org/cgit/slackbuilds/log/?h=qemu-kvm</a>
(which has already been mentioned for review).
Given the options, I think I like the first one (qemu-merged)
better, BUT there's a very real potential to miss some files
that aren't included in the qemu package (see TODO: in the
build script), and who knows what kind of damned-near-impossible-
to-figure-out errors that would induce in qemu runtime :/
The second approach is not as "clean" as the first, but it's less
error-prone in the future probably.
In both cases, the qemu and qemu-kvm versions have to be in sync,
so that's an issue that we need to fix regardless...
All that said, perhaps there's another approach that I'm missing,
and if so, I'd like to hear it. I'm obviously not in favor of
leaving things as they are, but other suggestions will certainly
be entertained...
-RW
</pre>
</blockquote>
<p>IMHO our merge of the qemu-kvm SlackBuild into qemu SlackBuild is premature. It remains the intention of the KVM Team to discontinue qemu-kvm once qemu properly merges the code from kvm. The KVM Team doesn't believe they are there yet so why do we?</p>
<p><a href="http://blog.vmsplice.net/2011/03/should-i-use-qemu-or-kvm.html">Stephan Hajnoczi: Should I use QEMU or KVM?</a> see the section: "What is the difference between qemu.git and qemu-kvm.git?"</p>
<p>I recommend continued support of the qemu-kvm SlackBuild with focus on the x86 Intel, x86 AMD CPUs however the PowerPC and S390 CPUs should not be forgotten. All other qemu CPU emulation should be directed to the qemu SlackBuild until such time as the KVM Team says qemu-kvm is deprecated.</p>
<p><a href="http://www.linux-kvm.org/page/Processor_support">Processor Support - KVM</a></p>
<p>It's a complicated issue. I hope I'm still tracking properly.</p>
<p>Stu</p>
<div> </div>
</body></html>