Displaying 3 results from an estimated 3 matches for "qemusetupimagepathcgroup".
2020 Jun 09
2
Permission to disk set wrong when restoring from memory snapshot?
...ed to run.
After looking in the debug logs (attached in the bug), I have seen this on
the first host:
2020-06-09 12:12:46.288+0000: 177879: debug :
qemuSetupImageCgroupInternal:139 : Not updating cgroups for disk path
'<null>', type: file
2020-06-09 12:12:46.288+0000: 177879: debug : qemuSetupImagePathCgroup:75 :
Allow path
/rhev/data-center/3b67fb92-906b-11ea-bb36-482ae35a5f83/4fd23357-6047-46c9-aa81-ba6a12a9e8bd/images/0191
384a-3e0a-472f-a889-d95622cb6916/7f553f44-db08-480e-8c86-cbdeccedfafe,
perms: rw
*2020-06-09 12:12:46.288+0000: 177879: debug : qemuSetupImagePathCgroup:75
: Allow path
/rhev/dat...
2020 Jun 09
2
Re: Permission to disk set wrong when restoring from memory snapshot?
On Tue, Jun 9, 2020 at 3:46 PM Peter Krempa <pkrempa@redhat.com> wrote:
> On Tue, Jun 09, 2020 at 15:38:53 +0300, Liran Rotenberg wrote:
> > Hi all,
> > Passing on Bug 1840609 <
> https://bugzilla.redhat.com/show_bug.cgi?id=1840609>
> > - Wake up from hibernation failed:internal error: unable to execute QEMU
> > command 'cont': Failed to get
2020 Jun 09
0
Re: Permission to disk set wrong when restoring from memory snapshot?
...remove the memory disk, but that doesn't
> happen in this case, since the VM wasn't up.
I'd speculate that it's timing. There's more time for the locks to
propagate or an offending process to terminate. The error message
definitely does not look like a permission issue, and
qemuSetupImagePathCgroup:75 is in the end a no-op on on non-device
paths (makes sense only for LVM logical volumes, partitions etc).