summaryrefslogtreecommitdiff
path: root/system/kvm-kmod/README
diff options
context:
space:
mode:
Diffstat (limited to 'system/kvm-kmod/README')
-rw-r--r--system/kvm-kmod/README18
1 files changed, 9 insertions, 9 deletions
diff --git a/system/kvm-kmod/README b/system/kvm-kmod/README
index f8bf89e67b..dc3d0cea5d 100644
--- a/system/kvm-kmod/README
+++ b/system/kvm-kmod/README
@@ -7,13 +7,13 @@ which are both available as separate Slackbuilds.
KVM-KMOD consists of a kernel module, 'kvm.ko', that provides the
core virtualization infrastructure and a processor specific module,
'kvm-intel.ko' or 'kvm-amd.ko'. Slackware provides these modules
-in the 'a/slackware-modules*' packages and the associated headers
-in the 'd/slackware-headers*' packages. In most cases the
-Slackware provided versions are sufficient to run QEMU-KVM.
-KVM-KMOD is only needed if you want to change the KVM modules and
-headers to a different version.
+in the 'a/kernel-modules*' packages. In most cases, the provided
+versions are sufficient to run QEMU-KVM. KVM-KMOD is only needed
+if you want to change the KVM modules to a different version.
-KVM-KMOD updates the modules and headers without overwriting the
-Slackware provided versions. If you uninstall KVM-KMOD you will
-need to run 'depmod -a' to regenerate the modules.dep and map
-files to regain access to the Slackware provided versions.
+KVM-KMOD updates the modules without overwriting the ones provided
+by Slackware. If you uninstall KVM-KMOD, you will need to run
+'depmod -a' to regenerate the modules.dep and map files to regain
+access to the Slackware provided versions.
+
+You need to have a "kvm" group on the system in order to use this.