GNU bug report logs - #64073
libvirtd requires restart to function

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Josselin Poiret <dev <at> jpoiret.xyz>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#64073: closed (libvirtd requires restart to function)
Date: Fri, 07 Jul 2023 19:49:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Fri, 07 Jul 2023 21:48:15 +0200
with message-id <87fs5z7bb4.fsf <at> jpoiret.xyz>
and subject line Re: bug#64073: libvirtd requires restart to function
has caused the debbugs.gnu.org bug report #64073,
regarding libvirtd requires restart to function
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
64073: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=64073
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Christian Miller <miller.christian <at> proton.me>
To: "bug-guix <at> gnu.org" <bug-guix <at> gnu.org>
Subject: libvirtd requires restart to function
Date: Wed, 14 Jun 2023 22:40:48 +0000

[Message part 3 (text/plain, inline)]

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.

[Message part 4 (text/html, inline)]

[Message part 5 (message/rfc822, inline)]

From: Josselin Poiret <dev <at> jpoiret.xyz>
To: Christian Miller <miller.christian <at> proton.me>, 64073-done <at> debbugs.gnu.org
Subject: Re: bug#64073: libvirtd requires restart to function
Date: Fri, 07 Jul 2023 21:48:15 +0200

[Message part 6 (text/plain, inline)]

Hi Christian,

Josselin Poiret <dev <at> jpoiret.xyz> writes:

> Great!  Thanks for going the extra mile testing this, I didn't know how
> familiar you were with the Guix development process.  We could also
> advertise the simpler `guix time-machine` with the branches from [1],
> although processing the new patch is not instantaneous (and I don't
> think bug reports are scanned for patches).
>
> In any case, I'll try to push it ASAP with some other changes!

Pushed as 612399df3edcbe4d1b1da784bd23440398d27454, closing.

Best,
-- 
Josselin Poiret

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.