unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Christian Miller via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "64073@debbugs.gnu.org" <64073@debbugs.gnu.org>
Subject: bug#64073: libvirtd requires restart to function
Date: Mon, 19 Jun 2023 19:29:07 +0000	[thread overview]
Message-ID: <JdQy7-V_gSWNJoZgCkIbK0dGEtavs4nd0PrTAMSkvTAMAjaQ1B5epY94jpz0RXcq1I4VYmY73FWN9S4mBUgBcBTjjySKcg8nzMsFmhtsnSI=@proton.me> (raw)
In-Reply-To: <4qRpCOZqo2dCWoe2W8nMf5XUDKSGU1z6Bzbk0o4V1AIE9buOePdVIXvQVbJD583fZMcSx_Tca37t-kuAG6todLdJAa5dLbayxVsnvebZSs0=@proton.me>

Hello,

I tested your patch and it works.  With the patch virt-manager does instantly connect without any manual interference.

Since this is the first time I did this, just to be sure I did everything correctly, I list how I tested it.

I cloned the git repository
I created a file called libvirtd.patch with your contents
git apply libvirtd.patch
guix shell -D guix --pure
./bootstrap
./configure --localstatedir=/var
make
make check (had 2 errors, authenticate and something else)
after that I executed "sudo -E ./pre-inst-env guix system reconfigure ~/guix/system.cm"
I rebooted the system and launched virt-manager which directly connected.

Best Regards,
Christian Miller




  parent reply	other threads:[~2023-06-19 19:30 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
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 ` Christian Miller via Bug reports for GNU Guix [this message]
2023-06-20 12:21   ` bug#64073: libvirtd requires restart to function 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='JdQy7-V_gSWNJoZgCkIbK0dGEtavs4nd0PrTAMSkvTAMAjaQ1B5epY94jpz0RXcq1I4VYmY73FWN9S4mBUgBcBTjjySKcg8nzMsFmhtsnSI=@proton.me' \
    --to=bug-guix@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).