Rich, Yes the /run is indeed on a tmp filesystem. I did a "touch /autorelabel followed by a complete system shutdown to power off followed by a system startup. The timestamp on /run/libvirt/common is today's date with a timestamp consistent with system startup. Thanks for reaching out. John On Wed, 2024-01-03 at 14:40 +0000, Richard W.M. Jones wrote: > On Wed, Jan 03, 2024 at 08:17:58AM -0600, John W. Himpel wrote: > > I was able to resolve this issue by doing a complete system > > selinux > > relabeling. > > > > Thanks to those who reached out to assist. > > > > > > On Tue, 2024-01-02 at 09:47 -0600, John W. Himpel wrote: > > > I just updated libvirt to 9.10.0-3 and virt-manager to 4.1.0-4. > > > Before > > > the update, I could start my defined VMs from virt-manager > > > without > > > issue. Now I get the following: > > > > > > Error starting domain: can't connect to virtlogd. Unable to open > > > system.token /run/libvirt/common/system.token: Permission denied > > > > > > I am running virt-manager from my unpriviledged userid. My > > > userid is > > > already a member of the libvirt group. > > > > > > I see no error messages in the journal or in any of the logs > > > under > > > /var/log > > > > > > Any suggestions would be greatly appreciated. > > Glad you have fixed it. > > Is /run a tmpfs filesystem on your Fedora system? ie: > > $ mount | grep /run > tmpfs on /run type tmpfs > (rw,nosuid,nodev,seclabel,size=3200856k,nr_inodes=819200,mode=755,ino > de64) > > Rich. > _______________________________________________ Users mailing list -- users@xxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxx
