Changeset 9a04a8e9

Timestamp:

12/11/2013 01:00:40 PM (10 years ago)

Author:

Igor Živković <igor@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 7.10, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

c9ba90cb

Parents:

ef5a37b

Message:

allow users to use the kvm device

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@12374 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:

• postlfs/virtualization/qemu.xml (modified) (1 diff)

postlfs/virtualization/qemu.xml

@@ -160 +160 @@
 <screen role="root"><userinput>make install &amp;&amp;
 [ -e  /usr/lib/libcacard.so ] &amp;&amp; chmod -v 755 /usr/lib/libcacard.so</userinput></screen>
-    
+
+    <para>
+      You will need a dedicated group that will contain users (other than root)
+      allowed to access the KVM device. Add the group by running the following
+      command as the <systemitem class="username">root</systemitem> user:
+    </para>
+
+<screen role="root"><userinput>groupadd -g 61 kvm</userinput></screen>
+
+    <para>
+      Add any users that might use the KVM device to that group:
+    </para>
+
+<screen role="root"><userinput>usermod -a -G kvm <replaceable>&lt;username&gt;</replaceable></userinput></screen>
+
+    <para>
+      You will also need to add an Udev rule so that the KVM device gets correct
+      permissions:
+    </para>
+
+<screen role="root"><userinput>cat > /lib/udev/rules.d/65-kvm.rules &lt;&lt; "EOF"
+<literal>KERNEL=="kvm", NAME="%k", GROUP="kvm", MODE="0660"</literal>
+EOF</userinput></screen>
+
     <note><!--<para>The main program <command>qemu-system-x86_64</command> doesn't
     make a distinction between i386 and x86_64 so even on an i386 system you