Re: libvirtd.service start
On 3/23/24 10:42, Robert McBroom via users wrote: On 3/22/24 6:30 AM, Barry Scott wrote: On 22 Mar 2024, at 00:54, Robert McBroom via users wrote: looking at the status it shows preset:disabled As I understand it preset is used somewhere in the initial installation of fedora to figure out which services should be enabled by default. After installation it's not used normally. As a user you can symlink services into the right place in /etc/systemd/system or use the systemctl enable/disable commands to do the symlinking for you. I don't see any entry for libvirtd in /etc/systemd/system after having started it. There is an entry in /etc/systemd/system/multi-user.target.wants pointing to /usr/lib/systemd/system/libvirtd.service which looks unchanged. What symlink would be expected? After a system boot Nothing. It's just running. There might be a .pid file somewhere. -- ___ 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
Re: libvirtd.service start
> On 23 Mar 2024, at 17:43, Robert McBroom via users > wrote: > > There is an entry in /etc/systemd/system/multi-user.target.wants pointing to > /usr/lib/systemd/system/libvirtd.service which looks unchanged. > > What symlink would be expected? > That symlink, its how enable is implemented. Barry -- ___ 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
Re: libvirtd.service start
On 3/22/24 6:30 AM, Barry Scott wrote: On 22 Mar 2024, at 00:54, Robert McBroom via users wrote: looking at the status it shows preset:disabled As I understand it preset is used somewhere in the initial installation of fedora to figure out which services should be enabled by default. After installation it's not used normally. As a user you can symlink services into the right place in /etc/systemd/system or use the systemctl enable/disable commands to do the symlinking for you. I don't see any entry for libvirtd in /etc/systemd/system after having started it. There is an entry in /etc/systemd/system/multi-user.target.wants pointing to /usr/lib/systemd/system/libvirtd.service which looks unchanged. What symlink would be expected? After a system boot [ ~]# systemctl status libvirtd ○ libvirtd.service - libvirt legacy monolithic daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; preset: disabled) Drop-In: /usr/lib/systemd/system/service.d └─10-timeout-abort.conf Active: inactive (dead) TriggeredBy: ○ libvirtd-ro.socket ○ libvirtd.socket ○ libvirtd-admin.socket Docs: man:libvirtd(8) https://libvirt.org/ [ ~]# systemctl start libvirtd [ ~]# systemctl status libvirtd ● libvirtd.service - libvirt legacy monolithic daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; preset: disabled) Drop-In: /usr/lib/systemd/system/service.d └─10-timeout-abort.conf Active: active (running) since Sat 2024-03-23 13:06:24 EDT; 7s ago TriggeredBy: ● libvirtd-ro.socket ● libvirtd.socket ● libvirtd-admin.socket Docs: man:libvirtd(8) https://libvirt.org/ Main PID: 10683 (libvirtd) Tasks: 20 (limit: 32768) Memory: 42.1M (peak: 42.7M) CPU: 500ms CGroup: /system.slice/libvirtd.service └─10683 /usr/sbin/libvirtd --timeout 120 Mar 23 13:06:23 HPZ440.attlocal.net systemd[1]: Starting libvirtd.service - libvirt legacy monolithic daemon... Mar 23 13:06:24 HPZ440.attlocal.net systemd[1]: Started libvirtd.service - libvirt legacy monolithic daemon. -- ___ 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
Re: libvirtd.service start
On Mar 22, 2024, at 00:53, Samuel Sieb wrote: >> Nothing from the journal tells anything that I understand >> # journalctl -b -u libvirtd >> Mar 21 09:31:17 HPZ440.attlocal.net systemd[1]: Starting libvirtd.service - >> libvirt legacy monolithic daemon... >> Mar 21 09:31:18 HPZ440.attlocal.net systemd[1]: Started libvirtd.service - >> libvirt legacy monolithic daemon. >> Mar 21 09:33:18 HPZ440.attlocal.net systemd[1]: libvirtd.service: >> Deactivated successfully. > > I'm not sure what's going on here. systemd kind of starts it, but then > apparently either systemd shuts it down or the service decides it has nothing > to do and quits. I notice it’s exactly 2 minutes. If you notice the process running, it says it runs with “--timeout 120”. I wonder if this is the similar to the virtnetworkd bug we saw last year? Try disabling the timeout with: echo LIBVIRTD_ARGS= > /etc/sysconfig/libvirtd && systemctl restart libvirtd -- Jonathan Billings-- ___ 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
Re: libvirtd.service start
> On 22 Mar 2024, at 00:54, Robert McBroom via users > wrote: > > looking at the status it shows preset:disabled As I understand it preset is used somewhere in the initial installation of fedora to figure out which services should be enabled by default. After installation it's not used normally. As a user you can symlink services into the right place in /etc/systemd/system or use the systemctl enable/disable commands to do the symlinking for you. Barry -- ___ 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
Re: libvirtd.service start
On 3/21/24 20:49, Robert McBroom via users wrote: On 3/21/24 4:51 PM, Samuel Sieb wrote: On 3/21/24 12:20, Robert McBroom via users wrote: Status then shows systemctl status libvirtd ●libvirtd.service - libvirt legacy monolithic daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; preset: disabled) Thought systemctl enable libvirtd would change the preset notation but it didn't It doesn't. That's the system preset. "enable" only changes the first enabled/disable option, but that overrides the preset, so it should be starting at boot if you've rebooted since changing that setting. You can use "journalctl -b -u libvirtd" to find out what has happened. -- Saw no indication that any setting had changed. The status shows that it's enabled. Nothing from the journal tells anything that I understand # journalctl -b -u libvirtd Mar 21 09:31:17 HPZ440.attlocal.net systemd[1]: Starting libvirtd.service - libvirt legacy monolithic daemon... Mar 21 09:31:18 HPZ440.attlocal.net systemd[1]: Started libvirtd.service - libvirt legacy monolithic daemon. Mar 21 09:33:18 HPZ440.attlocal.net systemd[1]: libvirtd.service: Deactivated successfully. I'm not sure what's going on here. systemd kind of starts it, but then apparently either systemd shuts it down or the service decides it has nothing to do and quits. Try running just "journalctl -b" and see if there are any other relevant messages around that time. Mar 21 09:56:36 HPZ440.attlocal.net systemd[1]: Starting libvirtd.service - libvirt legacy monolithic daemon... Mar 21 09:56:36 HPZ440.attlocal.net systemd[1]: Started libvirtd.service - libvirt legacy monolithic daemon. Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: libvirt version: 10.1.0, package: 1.fc40 (Fedora Project, 2024-03-01-18:35:13, ) This must be from you starting it. -- ___ 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
Re: libvirtd.service start
On 3/21/24 4:51 PM, Samuel Sieb wrote: On 3/21/24 12:20, Robert McBroom via users wrote: On 3/20/24 10:32 AM, Jerry James wrote: On Wed, Mar 20, 2024 at 7:49 AM Robert McBroom via users wrote: Recently libvirtd.service is not starting on boot. I have to manually start it with systemctl start libvirtd. Do I need to put that command in a startup script? libvirtd.service is socket activated, so it should run automatically when needed. Does something not work if you don't start it manually? virt- manager starts but says it cannot connect to anything. I have six virtual machines I use for various purposes. systemctl status libvirtd shows disabled and dead. After starting it manually all machines are present. Status then shows systemctl status libvirtd ●libvirtd.service - libvirt legacy monolithic daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; preset: disabled) Thought systemctl enable libvirtd would change the preset notation but it didn't It doesn't. That's the system preset. "enable" only changes the first enabled/disable option, but that overrides the preset, so it should be starting at boot if you've rebooted since changing that setting. You can use "journalctl -b -u libvirtd" to find out what has happened. -- Saw no indication that any setting had changed. Nothing from the journal tells anything that I understand # journalctl -b -u libvirtd Mar 21 09:31:17 HPZ440.attlocal.net systemd[1]: Starting libvirtd.service - libvirt legacy monolithic daemon... Mar 21 09:31:18 HPZ440.attlocal.net systemd[1]: Started libvirtd.service - libvirt legacy monolithic daemon. Mar 21 09:33:18 HPZ440.attlocal.net systemd[1]: libvirtd.service: Deactivated successfully. Mar 21 09:56:36 HPZ440.attlocal.net systemd[1]: Starting libvirtd.service - libvirt legacy monolithic daemon... Mar 21 09:56:36 HPZ440.attlocal.net systemd[1]: Started libvirtd.service - libvirt legacy monolithic daemon. Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: libvirt version: 10.1.0, package: 1.fc40 (Fedora Project, 2024-03-01-18:35:13, ) Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: hostname: HPZ440.attlocal.net Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: internal error: Failed to start QEMU binary /usr/bin/qemu-system-alpha for probing: /usr/bin/qemu-system-alpha: error while l> Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: Failed to probe capabilities for /usr/bin/qemu-system-alpha: internal error: Failed to start QEMU binary /usr/bin/qemu-system> Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: internal error: Failed to start QEMU binary /usr/bin/qemu-system-arm for probing: /usr/bin/qemu-system-arm: error while loadi> Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: Failed to probe capabilities for /usr/bin/qemu-system-arm: internal error: Failed to start QEMU binary /usr/bin/qemu-system-a> Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: internal error: Failed to start QEMU binary /usr/bin/qemu-system-arm for probing: /usr/bin/qemu-system-arm: error while loadi> Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: Failed to probe capabilities for /usr/bin/qemu-system-arm: internal error: Failed to start QEMU binary /usr/bin/qemu-system-a> Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: internal error: Failed to start QEMU binary /usr/bin/qemu-system-aarch64 for probing: /usr/bin/qemu-system-aarch64: error whi> Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: Failed to probe capabilities for /usr/bin/qemu-system-aarch64: internal error: Failed to start QEMU binary /usr/bin/qemu-syst> Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: internal error: Failed to start QEMU binary /usr/bin/qemu-system-cris for probing: /usr/bin/qemu-system-cris: error while loa> Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: Failed to probe capabilities for /usr/bin/qemu-system-cris: internal error: Failed to start QEMU binary /usr/bin/qemu-system-> Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: internal error: Failed to start QEMU binary /usr/bin/qemu-system-lm32 for probing: /usr/bin/qemu-system-lm32: error while loa> Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: Failed to probe capabilities for /usr/bin/qemu-system-lm32: internal error: Failed to start QEMU binary /usr/bin/qemu-system-> Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: internal error: Failed to start QEMU binary /usr/bin/qemu-system-m68k for probing: /usr/bin/qemu-system-m68k: error while loa> Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: Failed to probe capabilities for /usr/bin/qemu-system-m68k: internal error: Failed to start QEMU binary /usr/bin/qemu-system-> Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: internal error: Failed to start QEMU binary /usr/bin/qemu-system-microblaze for probing: /usr/bin/qemu-system-microblaze: err> Mar 21 09:56:37 HPZ440.attlocal.net libvirtd[10039]: Failed to probe
Re: libvirtd.service start
On 3/21/24 4:29 PM, Jerry James wrote: On Thu, Mar 21, 2024 at 1:20 PM Robert McBroom via users wrote: virt- manager starts but says it cannot connect to anything. I have six virtual machines I use for various purposes. In virt-manager, if you select the Edit menu and then "Connection Details", is the "Autoconnect" item selected? It is -- ___ 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
Re: libvirtd.service start
On 3/21/24 17:54, Robert McBroom via users wrote: On 3/21/24 4:15 PM, Barry wrote: On 21 Mar 2024, at 19:21, Robert McBroom via users wrote: systemctl enable libvirtd would change the preset notation but it didn't Did this add libvirtd to the multi user target? If so it will start when you boot fedora. Is that what you mean by preset? Barry looking at the status it shows preset:disabled Maybe have to stop libvirtd and then enable it You can't change the preset, other than editing some files that you shouldn't modify. That setting is merely informational at this point. -- ___ 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
Re: libvirtd.service start
On 3/21/24 4:15 PM, Barry wrote: On 21 Mar 2024, at 19:21, Robert McBroom via users wrote: systemctl enable libvirtd would change the preset notation but it didn't Did this add libvirtd to the multi user target? If so it will start when you boot fedora. Is that what you mean by preset? Barry looking at the status it shows preset:disabled Maybe have to stop libvirtd and then enable it -- ___ 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
Re: libvirtd.service start
> Am 21.03.2024 um 21:51 schrieb Samuel Sieb : > > On 3/21/24 12:20, Robert McBroom via users wrote: >> On 3/20/24 10:32 AM, Jerry James wrote: >>> On Wed, Mar 20, 2024 at 7:49 AM Robert McBroom via users >>> wrote: Recently libvirtd.service is not starting on boot. I have to manually start it with systemctl start libvirtd. Do I need to put that command in a startup script? >>> libvirtd.service is socket activated, so it should run automatically >>> when needed. Does something not work if you don't start it manually? >> virt- manager starts but says it cannot connect to anything. I have six >> virtual machines I use for various purposes. >> systemctl status libvirtd >> shows disabled and dead. After starting it manually all machines are present. >> Status then shows >> systemctl status libvirtd >> ●libvirtd.service - libvirt legacy monolithic daemon >> Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; >> preset: disabled) >> Thought >> systemctl enable libvirtd >> would change the preset notation but it didn't > > It doesn't. That's the system preset. "enable" only changes the first > enabled/disable option, but that overrides the preset, so it should be > starting at boot if you've rebooted since changing that setting. > > You can use "journalctl -b -u libvirtd" to find out what has happened. As you noticed: > systemctl status libvirtd > ● libvirtd.service - libvirt legacy monolithic daemon ^ Fedora uses the current modularized version See: - https://fedoraproject.org/wiki/Changes/LibvirtModularDaemons - https://libvirt.org/daemons.html#switching-to-modular-daemons -- Peter Boy https://fedoraproject.org/wiki/User:Pboy p...@fedoraproject.org Timezone: CET (UTC+1) / CEST (UTC+2) Fedora Server Edition Working Group member Fedora Docs team contributor and board member Java developer and enthusiast -- ___ 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
Re: libvirtd.service start
On 3/21/24 12:20, Robert McBroom via users wrote: On 3/20/24 10:32 AM, Jerry James wrote: On Wed, Mar 20, 2024 at 7:49 AM Robert McBroom via users wrote: Recently libvirtd.service is not starting on boot. I have to manually start it with systemctl start libvirtd. Do I need to put that command in a startup script? libvirtd.service is socket activated, so it should run automatically when needed. Does something not work if you don't start it manually? virt- manager starts but says it cannot connect to anything. I have six virtual machines I use for various purposes. systemctl status libvirtd shows disabled and dead. After starting it manually all machines are present. Status then shows systemctl status libvirtd ●libvirtd.service - libvirt legacy monolithic daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; preset: disabled) Thought systemctl enable libvirtd would change the preset notation but it didn't It doesn't. That's the system preset. "enable" only changes the first enabled/disable option, but that overrides the preset, so it should be starting at boot if you've rebooted since changing that setting. You can use "journalctl -b -u libvirtd" to find out what has happened. -- ___ 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
Re: libvirtd.service start
On Thu, Mar 21, 2024 at 1:20 PM Robert McBroom via users wrote: > virt- manager starts but says it cannot connect to anything. I have six > virtual machines I use for various purposes. In virt-manager, if you select the Edit menu and then "Connection Details", is the "Autoconnect" item selected? -- Jerry James http://www.jamezone.org/ -- ___ 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
Re: libvirtd.service start
> On 21 Mar 2024, at 19:21, Robert McBroom via users > wrote: > > systemctl enable libvirtd > > would change the preset notation but it didn't > Did this add libvirtd to the multi user target? If so it will start when you boot fedora. Is that what you mean by preset? Barry -- ___ 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
Re: libvirtd.service start
On 3/20/24 10:32 AM, Jerry James wrote: On Wed, Mar 20, 2024 at 7:49 AM Robert McBroom via users wrote: Recently libvirtd.service is not starting on boot. I have to manually start it with systemctl start libvirtd. Do I need to put that command in a startup script? libvirtd.service is socket activated, so it should run automatically when needed. Does something not work if you don't start it manually? virt- manager starts but says it cannot connect to anything. I have six virtual machines I use for various purposes. systemctl status libvirtd shows disabled and dead. After starting it manually all machines are present. Status then shows systemctl status libvirtd ●libvirtd.service - libvirt legacy monolithic daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; preset: disabled) Drop-In: /usr/lib/systemd/system/service.d └─10-timeout-abort.conf Active: active (running)since Thu 2024-03-21 09:56:36 EDT; 5h 13min ago TriggeredBy: ●libvirtd-ro.socket ●libvirtd-admin.socket ●libvirtd.socket Docs: man:libvirtd(8) https://libvirt.org/ Main PID: 10039 (libvirtd) Tasks: 21 (limit: 32768) Memory: 40.6M (peak: 92.4M) CPU: 25.975s CGroup: /system.slice/libvirtd.service └─10039 /usr/sbin/libvirtd --timeout 120 Mar 21 09:56:38 HPZ440.attlocal.net libvirtd[10039]: internal error: Failed to start QEMU binary /usr/bin/qemu-> Mar 21 09:56:38 HPZ440.attlocal.net libvirtd[10039]: Failed to probe capabilities for /usr/bin/qemu-system-xten> Mar 21 09:56:50 HPZ440.attlocal.net libvirtd[10039]: operation failed: Multiple USB devices for 781:5581, use <> Mar 21 09:56:50 HPZ440.attlocal.net libvirtd[10039]: Unable to find device 000.000 in list of active USB devices Mar 21 09:57:54 HPZ440.attlocal.net libvirtd[10306]: 2024-03-21 13:57:54.273+: 10306: info : libvirt versio> Mar 21 09:57:54 HPZ440.attlocal.net libvirtd[10306]: 2024-03-21 13:57:54.273+: 10306: info : hostname: HPZ4> Mar 21 09:57:54 HPZ440.attlocal.net libvirtd[10306]: 2024-03-21 13:57:54.273+: 10306: warning : virSecurity> Mar 21 09:57:54 HPZ440.attlocal.net libvirtd[10307]: 2024-03-21 13:57:54.275+: 10307: info : libvirt versio> Mar 21 09:57:54 HPZ440.attlocal.net libvirtd[10307]: 2024-03-21 13:57:54.275+: 10307: info : hostname: HPZ4> Mar 21 09:57:54 HPZ440.attlocal.net libvirtd[10307]: 2024-03-21 13:57:54.275+: 10307: warning : virSecurity> Thought systemctl enable libvirtd would change the preset notation but it didn't -- ___ 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
Re: libvirtd.service start
> Am 20.03.2024 um 14:49 schrieb Robert McBroom via users > : > > Recently libvirtd.service is not starting on boot. I have to manually start > it with systemctl start libvirtd. You may have a look at https://docs.fedoraproject.org/en-US/fedora-server/virtualization/installation/ -- Peter Boy https://fedoraproject.org/wiki/User:Pboy p...@fedoraproject.org Timezone: CET (UTC+1) / CEST (UTC+2) Fedora Server Edition Working Group member Fedora Docs team contributor and board member Java developer and enthusiast -- ___ 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
Re: libvirtd.service start
On Wed, Mar 20, 2024 at 7:49 AM Robert McBroom via users wrote: > Recently libvirtd.service is not starting on boot. I have to manually > start it with systemctl start libvirtd. > > Do I need to put that command in a startup script? libvirtd.service is socket activated, so it should run automatically when needed. Does something not work if you don't start it manually? -- Jerry James http://www.jamezone.org/ -- ___ 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
libvirtd.service start
Recently libvirtd.service is not starting on boot. I have to manually start it with systemctl start libvirtd. Do I need to put that command in a startup script? -- ___ 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
