- Timestamp:
- 12/11/2014 09:17:51 PM (9 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 7.10, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 4e95ca30
- Parents:
- 92cd4cad
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
postlfs/virtualization/qemu.xml
r92cd4cad rdada702 161 161 <para> 162 162 You will need a dedicated group that will contain users (other than root) 163 allowed to access the KVM device. Add the group and allow network 164 bridging connectivity for that group by running the following commands as 165 the <systemitem class="username">root</systemitem> user: 163 allowed to access the KVM device. Create this group by running the following 164 command as the <systemitem class="username">root</systemitem> user: 166 165 </para> 167 166
Note:
See TracChangeset
for help on using the changeset viewer.