system/qemu: Clean up some left over verbiage wrt qemu-kvm

Signed-off-by: Robby Workman <rworkman@slackbuilds.org>
This commit is contained in:
Robby Workman 2013-04-17 00:31:21 -05:00 committed by Niels Horn
parent 2f37dd822b
commit 7a56f78ad7

View file

@ -4,11 +4,10 @@ When used as a machine emulator, QEMU can run OSes and programs made for
one machine (e.g. an ARM board) on a different machine (e.g. your own PC).
By using dynamic translation, it achieves very good performances.
qemu-kvm achieves near native performances by leveraging the kvm-kmod
modules and executing the guest code directly on the host CPU.
Slackware provides pre-built 32/64 bit x86 kvm-kmod modules or you can
build different versions with the kvm-kmod package.
qemu-kvm code has been merged back into qemu since version 1.3.0.
qemu (with kvm enabled) achieves near native performances by leveraging
the kvm-kmod modules and executing the guest code directly on the host
CPU. Slackware provides pre-built 32/64 bit x86 kvm-kmod modules or you
can build different versions with the kvm-kmod package.
By default, this script builds only the x86 and arm emulation targets
for qemu; if you prefer to build all supported targets, do this:
@ -22,6 +21,8 @@ something different, then run the build script like this:
KVMGROUP=group ./qemu.SlackBuild
Don't forget to load the 'kvm-intel' or 'kvm-amd' module (depending on
your processor) prior to launching qemu-system-x86_64 with kvm enabled.
your processor) prior to launching qemu-system-ARCH with kvm enabled.
For older/unmaintained qemu frontends, this build also creates a symlink
to qemu-system-ARCH at /usr/bin/qemu-kvm.
spice and usbredir are optional dependencies.