slackbuilds_ponce/system/kvm-kmod
Erik Hanson 4248415dde Add REQUIRED field to .info files.
Signed-off-by: Erik Hanson <erik@slackbuilds.org>
2012-08-19 21:57:51 -05:00
..
doinst.sh
fixup_udev_rules.diff system/kvm-kmod: Updated for version 3.3.6. 2012-05-21 17:58:15 -05:00
kvm-kmod.info Add REQUIRED field to .info files. 2012-08-19 21:57:51 -05:00
kvm-kmod.SlackBuild system/kvm-kmod: Updated for version 3.3.6. 2012-05-21 17:58:15 -05:00
README system/kvm-kmod: Updated for version 3.2. 2012-02-18 09:12:29 -02:00
slack-desc system/kvm-kmod: Updated for version 3.3.6. 2012-05-21 17:58:15 -05:00

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