mirror of
https://github.com/Ponce/slackbuilds
synced 2024-12-01 01:00:03 +01:00
4b3c0cbf2a
Remove the depmod.d config file, as it doesn't appear to be needed any more. I'm leaving the bit of code that created it (it's only commented out for now) since I don't know for *sure* that it's not needed any more. What I do know is that IF it IS still needed, the previous file wasn't working anyway since the modules were installed to a new location by upstream, and we (both maintainer and I) missed that fact when updating the build script. Oops :) Signed-off-by: Robby Workman <rworkman@slackbuilds.org> |
||
|---|---|---|
| .. | ||
| doinst.sh | ||
| fixup_udev_rules.diff | ||
| kvm-kmod.info | ||
| kvm-kmod.SlackBuild | ||
| README | ||
| slack-desc | ||
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. 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/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 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. By default, this script uses the "users" group for determining who has permission to use /dev/kvm, but if you prefer something else, set KVMGROUP when running the script, e.g.: KVMGROUP=wheel sh kvm-kmod.SlackBuild