unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Christian Miller <miller.christian@proton.me>
Cc: 64073@debbugs.gnu.org
Subject: bug#64073: libvirtd requires restart to function
Date: Thu, 15 Jun 2023 14:37:57 +0200	[thread overview]
Message-ID: <87ttv8x5ne.fsf@gnu.org> (raw)
In-Reply-To: <4qRpCOZqo2dCWoe2W8nMf5XUDKSGU1z6Bzbk0o4V1AIE9buOePdVIXvQVbJD583fZMcSx_Tca37t-kuAG6todLdJAa5dLbayxVsnvebZSs0=@proton.me> (Christian Miller's message of "Wed, 14 Jun 2023 22:40:48 +0000")

Hi,

Christian Miller <miller.christian@proton.me> skribis:

> Currently libvirtd does not work without running "sudo herd restart
> libvirtd". Upon starting virt-manager I can't connect to the socket
> but if I restart libvirtd it works fine.
>
> I tested the 1.4.0 image in a VM and there is no issue. After that I
> did a guix pull and reconfigured the system and I have the same issue
> again in the VM.

Are there any hints in /var/log/messages as to what goes wrong with
libvirtd when it is first started?

I suspect it’s getting started “too early”.

Thanks,
Ludo’.




  reply	other threads:[~2023-06-15 12:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-14 22:40 bug#64073: libvirtd requires restart to function Christian Miller via Bug reports for GNU Guix
2023-06-15 12:37 ` Ludovic Courtès [this message]
2023-06-16 20:44 ` Christian Miller via Bug reports for GNU Guix
2023-06-17 16:02   ` Josselin Poiret via Bug reports for GNU Guix
2023-06-17 16:03     ` bug#64073: [PATCH] services: libvirt: Add requirement on dbus Josselin Poiret via Bug reports for GNU Guix
2023-06-19 19:29 ` bug#64073: libvirtd requires restart to function Christian Miller via Bug reports for GNU Guix
2023-06-20 12:21   ` Josselin Poiret via Bug reports for GNU Guix
2023-07-07 19:48     ` Josselin Poiret via Bug reports for GNU Guix

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ttv8x5ne.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=64073@debbugs.gnu.org \
    --cc=miller.christian@proton.me \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).