summaryrefslogtreecommitdiff
path: root/system/qemu-kvm/README
diff options
context:
space:
mode:
Diffstat (limited to 'system/qemu-kvm/README')
-rw-r--r--system/qemu-kvm/README46
1 files changed, 20 insertions, 26 deletions
diff --git a/system/qemu-kvm/README b/system/qemu-kvm/README
index 4c9a99a300..f2db915c53 100644
--- a/system/qemu-kvm/README
+++ b/system/qemu-kvm/README
@@ -1,29 +1,23 @@
-KVM (Kernel-based Virtual Machine) is a full virtualization solution
-for Linux on x86 hardware containing virtualization extensions
-(Intel VT or AMD-V). KVM is divided into the KVM-KMOD package
-(kernel modules) and the QEMU-KVM package (slightly modified QEMU)
-which are both available as separate Slackbuilds.
+qemu-kvm is a generic and open source virtualizer. 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 is a generic and open source virtualizer. QEMU-KVM achieves
-near native performances by leveraging the KVM-KMOD modules and
-executing the guest code directly on the host CPU. QEMU-KVM can
-virtualize many system guest types (e.g. alpha, arm, i386, ppc, x86_64,
-s390, sparc). Slackware provides pre-built KVM-KMOD modules or you
-can build different versions with the KVM-KMOD SlackBuild.
+While qemu-kvm can virtualize many system guest types (e.g. alpha, arm,
+i386, ppc, x86_64, s390, sparc), not all these system guest types utilize
+the kvm-kmod modules. For those system guest types that don't utilize
+the kvm-kmod modules, it is recommended to use the qemu package instead
+of this qemu-kvm package.
-QEMU-KVM requires a system group and uses 'kvm' as the default. If you
-want to use a different group like 'users' then run the script like this:
-KVMGROUP=users sh qemu-kvm.SlackBuild
+The qemu-kvm SlackBuild renames the primary binary from 'qemu-system-
+x86_64' to 'qemu-kvm' so that the qemu SlackBuild won't overwrite it
+if both packages are installed on the same host system. The qemu-kvm
+SlackBuild patches the installed udev rules so that you no longer are
+required to use the system group 'kvm' as the default. The 'users'
+group is set as the default in this SlackBuild. If you want to use a
+different group, then run the SlackBuild like this:
+ KVMGROUP=group sh qemu-kvm.SlackBuild
-After package installation, make sure you have the KVMGROUP present on
-your system and that all desired users are members of that group.
-Don't forget to load the KVM-INTEL or KVM-AMD module depending on your
-processor.
-
-The script builds only x86 and x86_64 Linux Target CPU emulators by default.
-If you need to emulate all target CPUs, set BUILD_ARCH to "all" but be
-aware that the compilation will take a lot longer, and you should really
-be using plain "qemu" for the others (since they can't use the KVM stuff
-anyway. The default "x86_64" value works fine for for 32-bit or 64-bit
-QEMU-KVM hosts providing full system emulation supporting Linux, BSD, and
-Windows guests.
+Don't forget to load the 'kvm-intel' or 'kvm-amd' module (depending on
+your processor) prior to running 'qemu-kvm'.