bug#36634: (no subject)

2020-03-19 Thread Brice Waegeneire
Hello, Chris Marusich writes: I see the patch was incorporated into Guix master in commit aa1f0896fb15a0bdcc5474839c8afdbb2520d603. That is good, and I think this issue can be resolved. If nobody follows up in a few days' time, let's close the bug report. I created 38032 on guix-patches an

bug#36634: Virtual Machine Manager (virt-manager)

2019-11-07 Thread Miguel Arruga Vivas
Hi Chris, Chris Marusich writes: > With the patch you submitted upstream (not the patches you attached to > your previous email here), I can confirm the issue is fixed for me, > and that I do NOT observe the errors you mentioned above. Sorry, I did not send the email here. > I see the patch was

bug#36634: Virtual Machine Manager (virt-manager)

2019-11-07 Thread Chris Marusich
Hi Miguel, Miguel Arruga Vivas writes: > Hello again, > > The two patches attached create the cgroup directory needed and remove > the warning for the ip binary missing. Still the following errors > are emitted to the log. > > 8<--- > error : virConnectGetCP

bug#36634: Virtual Machine Manager (virt-manager)

2019-10-27 Thread Miguel Arruga Vivas
Hello again, The two patches attached create the cgroup directory needed and remove the warning for the ip binary missing. Still the following errors are emitted to the log. 8<--- error : virConnectGetCPUModelNames:1109 : this function is not supported by the

bug#36634: Virtual Machine Manager (virt-manager)

2019-10-21 Thread Miguel Arruga Vivas
Hi, This bug can be easier to fix than we thought. :-D As a workaround, you only have to execute: $ sudo mkdir /sys/fs/cgroup/unified/{machine,system,user} The folders should be created at libvirtd start, probably manually with some extra cgroup magic that I don't understand yet, but this works

bug#36634: Virtual Machine Manager (virt-manager)

2019-10-10 Thread Chris Marusich
Chris Marusich writes: > I've updated the upstream bug report with information that hopefully > will be useful to them. We'll see how it goes. The original upstream bug report has been closed, but it seems likely it was for a different issue, since it didn't fix the issue in Guix. At upstream'

bug#36634: Virtual Machine Manager (virt-manager)

2019-10-04 Thread Chris Marusich
Chris Marusich writes: > 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

bug#36634: Virtual Machine Manager (virt-manager)

2019-09-22 Thread Tobias Geerinckx-Rice via Bug reports for GNU Guix
Chrisen, Chris Marusich 写道: 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

bug#36634: Virtual Machine Manager (virt-manager)

2019-09-22 Thread Chris Marusich
Christopher Baines writes: > Raghav Gururajan 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 w

bug#36634: Virtual Machine Manager (virt-manager)

2019-09-08 Thread Christopher Baines
As version 5.7.0 has been released, I tried updating to that. There seems to be some issue with the configuration for the socket file, but even avoiding that, it doesn't seem to resolve the issue with the cgroups. For now, I've switched more permanently back to 5.4.0. signature.asc Description:

bug#36634:

2019-07-25 Thread Raghav Gururajan
> I have applied ‘your’ patch in > 41097b2dee9367974c6dd16ac1ba2ee945457237. > > I'm closing this bug for now. However, could you update and > confirm that this actually solves the problem? Oh Shoot! I just saw your previous reply and replied to it. Sorry for the delay. Anyway that patch fixe

bug#36634:

2019-07-25 Thread Raghav Gururajan
> I will do so swiftly since I updated libvirt to the 'broken' version > (although I never had any troubles like yours). Thank you for > reporting this upstream. About that, it appears I misunderstood the patch. That recent build was not to fix the bug I reported. Anyway, I have been told by o

bug#36634: ATTENTION REQUIRED

2019-07-25 Thread Tobias Geerinckx-Rice
Tobias Geerinckx-Rice 写道: Could anyone please update the libvirt package/service to this latest build? I will do so swiftly since I updated libvirt to the 'broken' version (although I never had any troubles like yours). Thank you for reporting this upstream. I have applied ‘your’ patch in

bug#36634: ATTENTION REQUIRED

2019-07-25 Thread Tobias Geerinckx-Rice
Raghav, On Thu, Jul 25, 2019 at 11:46 AM, Raghav Gururajan wrote: Hello Guix! I posted the bug on libvirt mail list few days ago (https://www.redhat. com/archives/libvir-list/2019-July/msg01309.html). It appears the bug has now been fixed (https://github.com/libvirt/libvirt/commit/759bf903

bug#36634: ATTENTION REQUIRED

2019-07-25 Thread Raghav Gururajan
Hello Guix! I posted the bug on libvirt mail list few days ago (https://www.redhat. com/archives/libvir-list/2019-July/msg01309.html). It appears the bug has now been fixed (https://github.com/libvirt/libvirt/commit/759bf903a 6c24a8efa25c7cf4b099d952eda9bd3). Could anyone please update the libvir

bug#36634: Virtual Machine Manager (virt-manager)

2019-07-21 Thread Raghav Gururajan
> 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 see. > 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 problemati

bug#36634: Virtual Machine Manager (virt-manager)

2019-07-21 Thread Christopher Baines
Raghav Gururajan 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 ch

bug#36634: Virtual Machine Manager (virt-manager)

2019-07-14 Thread Raghav Gururajan
> Checking my machine: > $ ls /sys/fs/cgroup/unified/ > cgroup.controllers cgroup.max.depth cgroup.max.descendants cgroup. > procs cgroup.stat cgroup.subtree_control cgroup.threads I get the same output for `ls /sys/fs/cgroup/unified/`. But as shown in the error, the virt-manager is search

bug#36634: Virtual Machine Manager (virt-manager)

2019-07-14 Thread Efraim Flashner
On Sat, Jul 13, 2019 at 01:06:55AM -0400, Raghav Gururajan wrote: > Hello Guix! > > Unable to create any VMs by installing from any ISO file. > > The virt-manager gives out the following error: > > Unable to complete install: 'Unable to read from > '/sys/fs/cgroup/unified/machine/cgroup.controll

bug#36634: Virtual Machine Manager (virt-manager)

2019-07-12 Thread Raghav Gururajan
Hello Guix! Unable to create any VMs by installing from any ISO file. The virt-manager gives out the following error: Unable to complete install: 'Unable to read from '/sys/fs/cgroup/unified/machine/cgroup.controllers': No such file or directory' Traceback (most recent call last): File "/gnu/