Is there a way to use facl to specifically grant permission to all the
files/dirs that libvirt needs instead of using groups?
I am automating the install of libvirt and would like to be able to use it
without sudo or having to logout/login. I have done a similar thing on a
docker install using set
The host cpu here is intel i5 1135g7 (this is a laptop).
Using libvirt 9.0.0
Using "virsh capabilities" command, the //host/cpu/model part reads
Broadwell-noTSX-IBRS
But there are also the Skylake cpus available, which are newer than
broadwell, and thus should better match an intel core 11th ge
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 d
On 2 Jan 2024 09:47 -0600, from j...@jlhimpel.net (John W. Himpel):
> 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
Michael,
Thanks for the quick response.
I see the following:
[Tue, 02 Jan 2024 15:27:09 virt-manager 4054] DEBUG (connection:482)
conn=qemu:///system changed to state=Active
[Tue, 02 Jan 2024 15:27:13 virt-manager 4054] DEBUG (vmmenu:210)
Starting vm 'testFedora'
[Tue, 02 Jan 2024 15:27:13 virt-
On 2 Jan 2024 10:45 -0600, from j...@jlhimpel.net (John W. Himpel):
> After further investigation, I see that /run/libvirt/common has
> permissions of:
> drwx--. 2 root root 60 Jan 1 22:44 common
>
> Since I am running virt-manager from my userid, I think this is
> probably the issue.
Maybe
