Hello Marc,
> On Sep 27, 2016, at 08:13, Marc-André Lureau wrote:
>
>>> On Tue, Sep 27, 2016 at 03:06:21AM +, Rafael David Tinoco wrote:
>>> We should not have QEMU creating unpredictabile filenames in the
>>> first place - any filenames should be determined by libvirt
>>> explicitly.
>>
>
Hi
- Original Message -
> On Tue, Sep 27, 2016 at 07:13:55AM -0400, Marc-André Lureau wrote:
> > Hi
> >
> > - Original Message -
> > >
> > > > On Sep 27, 2016, at 05:36, Daniel P. Berrange
> > > > wrote:
> > > >
> > > > On Tue, Sep 27, 2016 at 03:06:21AM +, Rafael David Tin
On Tue, Sep 27, 2016 at 07:13:55AM -0400, Marc-André Lureau wrote:
> Hi
>
> - Original Message -
> >
> > > On Sep 27, 2016, at 05:36, Daniel P. Berrange wrote:
> > >
> > > On Tue, Sep 27, 2016 at 03:06:21AM +, Rafael David Tinoco wrote:
> > > We should not have QEMU creating unpredi
Hello!
> On Sep 27, 2016, at 08:13, Marc-André Lureau wrote:
>
>> Note that the filename, per se, is not as important as other files,
>> since qemu won't provide it for being accessed by external programs, and,
>> deletes the file, while keeping the descriptor, right after its creation
>> (due t
Hi
- Original Message -
>
> > On Sep 27, 2016, at 05:36, Daniel P. Berrange wrote:
> >
> > On Tue, Sep 27, 2016 at 03:06:21AM +, Rafael David Tinoco wrote:
> > We should not have QEMU creating unpredictabile filenames in the
> > first place - any filenames should be determined by li
> On Sep 27, 2016, at 05:36, Daniel P. Berrange wrote:
>
> On Tue, Sep 27, 2016 at 03:06:21AM +, Rafael David Tinoco wrote:
>> Commit: 35f9b6ef3acc9d0546c395a566b04e63ca84e302 added a fallback
>> mechanism for systems not supporting memfd_create syscall (started
>> being supported since 3.17
On Tue, Sep 27, 2016 at 03:06:21AM +, Rafael David Tinoco wrote:
> Commit: 35f9b6ef3acc9d0546c395a566b04e63ca84e302 added a fallback
> mechanism for systems not supporting memfd_create syscall (started
> being supported since 3.17).
This is really dubious code in general and IMHO should just
b
Commit: 35f9b6ef3acc9d0546c395a566b04e63ca84e302 added a fallback
mechanism for systems not supporting memfd_create syscall (started
being supported since 3.17).
Backporting memfd_create might not be accepted for distros relying
on older kernels. Nowadays there is no way for security driver
to dis
Commit: 35f9b6ef3acc9d0546c395a566b04e63ca84e302 added a fallback
mechanism for systems not supporting memfd_create syscall (started
being supported since 3.17).
Backporting memfd_create might not be accepted for distros relying
on older kernels. Nowadays there is no way for security driver
to dis
