On 1/2/25 4:16 PM, Jeffrey Walton wrote:
On Thu, Jan 2, 2025 at 12:26 PM Robert McBroom via users <users@lists.fedoraproject.org> wrote:On 12/29/24 4:40 AM, Barry Scott wrote: On 29 Dec 2024, at 00:12, Jonathan Billings <billi...@negate.org> wrote: libvirtd was changed to use socket activation, so it *should* start if the libvirtd.socket is enabled and activated Running Virtual machine Manager will connect to the socket and every thing will start running. To use Virtual machine manager without password prompts add your user to the libvirt group. sudo useradd -G libvert -a <username> useradd -G libvirt -a rm3 useradd: invalid option -- 'a' Usage: useradd [options] LOGIN useradd -D useradd -D [options]This is from a Ubuntu 20 machine with QEMU/KVM: $ cat /etc/group | grep virt libvirt:x:145:jwalton,lboszormenyi,djb,pgutmann,apolyakov libvirt-qemu:x:64055:libvirt-qemu libvirt-dnsmasq:x:146: And from a Fedora 41 machine: $ cat /etc/group | grep virt libvirt:x:978:jwalton,djb,pgutmann,apolyakov
You shouldn't need to use virtual machine manager to start libvirtd. It should run at boot (if enabled) and start up any VMs that are set for starting at boot. I haven't had any issues with that, although all my VM hosts were installed a long time ago and only upgraded. I haven't tried setting it up on a recently installed system, so maybe something has changed.
-- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
