From: Chris Marusich <cmmarusich@gmail.com>
To: Christopher Baines <mail@cbaines.net>
Cc: 36634@debbugs.gnu.org, rvgn@disroot.org
Subject: bug#36634: Virtual Machine Manager (virt-manager)
Date: Sun, 22 Sep 2019 21:14:31 -0700 [thread overview]
Message-ID: <87wodzir88.fsf@gmail.com> (raw)
In-Reply-To: <87sgqze1yq.fsf@cbaines.net> (Christopher Baines's message of "Sun, 21 Jul 2019 18:23:25 +0100")
[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]
Christopher Baines <mail@cbaines.net> writes:
> Raghav Gururajan <rvgn@disroot.org> writes:
>
>> libvirt.libvirtError: Unable to read from
>> '/sys/fs/cgroup/unified/machine/cgroup.controllers': No such file or
>> directory
>
> So, I've experienced this too. Even though this is a cgroup thing, I'm
> pretty sure this isn't an issue with Linux.
>
> I've tried reverting the changes in [1], and that seems to solve the
> issue. Unfortunately, I don't have any insight in to what's different
> between the problematic 5.5.0 release, and the working 5.4.0 release.
>
> 1: 458fe419232844d2021608d20dcd8f6e095eb2b4
> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=458fe419232844d2021608d20dcd8f6e095eb2b4
This bug is consistently reproducible. I've found an upstream bug
report that is very similar to what we're seeing here, so I've left a
comment telling the libvirt maintainers that Guix is also seeing a
similar issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1751120
In the meantime, should we revert to version 5.4.0 in Guix? I'm not
sure if there are any security vulnerabilities between 5.4.0 and the
most recent release, but this bug is currently preventing me from
creating any VMs at all in Guix using virt-manager, which is pretty bad.
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-09-23 4:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-13 5:06 bug#36634: Virtual Machine Manager (virt-manager) Raghav Gururajan
2019-07-14 12:42 ` Efraim Flashner
2019-07-14 21:21 ` Raghav Gururajan
2019-07-21 17:23 ` Christopher Baines
2019-07-21 21:42 ` Raghav Gururajan
2019-09-23 4:14 ` Chris Marusich [this message]
2019-09-23 4:30 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-10-05 5:41 ` Chris Marusich
2019-10-10 8:55 ` Chris Marusich
2019-07-25 9:46 ` bug#36634: ATTENTION REQUIRED Raghav Gururajan
2019-07-25 19:36 ` Tobias Geerinckx-Rice
2019-07-25 20:01 ` Tobias Geerinckx-Rice
2019-07-26 3:51 ` bug#36634: Raghav Gururajan
2019-07-26 3:47 ` bug#36634: Raghav Gururajan
2019-09-08 18:14 ` bug#36634: Virtual Machine Manager (virt-manager) Christopher Baines
2019-10-21 14:46 ` Miguel Arruga Vivas
2019-10-27 9:37 ` Miguel Arruga Vivas
2019-11-07 8:44 ` Chris Marusich
2019-11-08 0:53 ` Miguel Arruga Vivas
2020-03-19 10:06 ` bug#36634: (no subject) Brice Waegeneire
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=87wodzir88.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=36634@debbugs.gnu.org \
--cc=mail@cbaines.net \
--cc=rvgn@disroot.org \
/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).