You are not logged in.
Pages: 1
Having performed a fresh install of Beowulf, only adding in the policy kit stuff from ASCII, I noticed that dmesg had warnings from (e)udev about no group "kvm", so I gave the command
addgroup --gid 125 kvm
and that has removed the warnings. I chose "125" as that was the value on my ACII installation.
Is this something that eudev should have set up?
Geoff
Offline
Just curious how you did a fresh install of Beowulf. The only way to get to beowulf is via an upgrade or the mini.iso which is pretty buried in the experimental repos and not with the other releases.
Offline
As described here :-
https://dev1galaxy.org/viewtopic.php?pid=13540#p13540
I installed it in a VM using Xen. I used debootstrap with the Beowulf repositories, which gave me a minimal install. I added the ASCII repositories to install the needed polkit stuff and then went on to install task-lxqt-desktop and stuff like that. It all works pretty well.
Geoff
Offline
The actual warning from dmesg is :-
[ 4.106843] udevd[373]: starting version 3.2.7
[ 4.171397] random: udevd: uninitialized urandom read (16 bytes read)
[ 4.171916] random: udevd: uninitialized urandom read (16 bytes read)
[ 4.171933] random: udevd: uninitialized urandom read (16 bytes read)
[ 4.259442] udevd[373]: specified group 'kvm' unknown
[ 4.480625] udevd[374]: starting eudev-3.2.7
Geoff
Offline
As described here :-
https://dev1galaxy.org/viewtopic.php?pid=13540#p13540
Thanks for reminding me. That's not going to happen for me this lifetime so quickly faded from memory. LOL!
Offline
maybe this is relevant : https://github.com/gentoo/eudev/issues/160 (?)
never had such an issue with eudev in beowulf. dist-upgraded fresh bare ascii, then installed DE, etc, including qemu-kvm & libvirt, groups were created ok it seems :
kvm:x:111:
libvirt:x:112:
no such udevd message..
Offline
Yes, that sounds like it. I would also understand from the link you give that the eudev people will be fixing the problem.
Geoff
Offline
Pages: 1