[Slackbuilds-users] qemu and qemu-kvm descriptions could really do with a bit of clarification
larryhaja at gmail.com
Mon Apr 15 13:51:22 UTC 2013
I haven't been keeping track of qemu/qemu-kvm status on the Slackware front
but I believe that qemu/qemu-kvm will be merged in future SBo updates
The kqemu is only needed for older versions of qemu for better performance
or older processors that don't have VT (I believe) built into them so that
either kvm-intel/kvm-amd modules are loaded. So, if you're building the
latest version of qemu, you should not have to worry about kqemu unless
your processor doesn't support it.
To test if you have VT capabilities the run the following
# grep '(vmx|svm)' /proc/cpuinfo
If there isn't any output then your processor doesn't support KVM and you
will need kqemu for better performance.
On Mon, Apr 15, 2013 at 4:29 AM, Sebastian Arcus <shop at open-t.co.uk> wrote:
> I've just spent an hour trying to get my head around to what is the
> difference between qemu and qemu-kvm and which one do I need. I couldn't
> even figure out if they somehow need each other. If it wasn't for the page
> below from the qemu website that states qemu-kvm is actually a fork of qemu
> (which seems to have been absorbed back into the qemu package upstream) I
> would still be trying to figure it all out:
> I don't want to start a flame war (in case this is one of those debatable
> topics with supporters on both sides) - but I think the description at SBo
> for both packages could do with a little note that either package can do
> the job (although there probably are some differences between them). Also
> the SBo page for qemu states:
> "When used as a virtualizer [...] A host driver called QEMU accellerator
> (also known as KQEMU) is needed."
> Is the above still a valid statement - or does it apply only to processors
> without virtualization extensions? From what I've read so far, it seems
> that the cpu's with virtualization extensions are served by the kvm-intel
> or kvm-amd modules nowadays?
> That is unless I got it all wrong and I still need to research some more
> to get clued up :-)
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.**org <SlackBuilds-users at slackbuilds.org>
> Archives - http://lists.slackbuilds.org/**pipermail/slackbuilds-users/<http://lists.slackbuilds.org/pipermail/slackbuilds-users/>
> FAQ - http://slackbuilds.org/faq/
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SlackBuilds-users