Re: [libvirt] [PATCH] qemuDomainRemoveMemoryDevice: unlink() memory backing file

2018-02-02 Thread Michal Privoznik
On 02/02/2018 11:01 AM, Jiri Denemark wrote: > On Thu, Jan 11, 2018 at 13:24:57 +0100, Michal Privoznik wrote: >> https://bugzilla.redhat.com/show_bug.cgi?id=1461214 >> >> Since fec8f9c49af we try to use predictable file names for >> 'memory-backend-file' objects. But that made us provide full

Re: [libvirt] [PATCH] qemuDomainRemoveMemoryDevice: unlink() memory backing file

2018-02-02 Thread Jiri Denemark
On Thu, Jan 11, 2018 at 13:24:57 +0100, Michal Privoznik wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=1461214 > > Since fec8f9c49af we try to use predictable file names for > 'memory-backend-file' objects. But that made us provide full path > to qemu when hot plugging the object while

Re: [libvirt] [PATCH] qemuDomainRemoveMemoryDevice: unlink() memory backing file

2018-01-30 Thread Michal Privoznik
On 01/11/2018 01:24 PM, Michal Privoznik wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=1461214 > > Since fec8f9c49af we try to use predictable file names for > 'memory-backend-file' objects. But that made us provide full path > to qemu when hot plugging the object while previously we

Re: [libvirt] [PATCH] qemuDomainRemoveMemoryDevice: unlink() memory backing file

2018-01-11 Thread Zack Cornelius
- Original Message - > From: "Michal Privoznik" > To: libvir-list@redhat.com > Cc: "Zack Cornelius" > Sent: Thursday, January 11, 2018 6:24:57 AM > Subject: [PATCH] qemuDomainRemoveMemoryDevice: unlink() memory backing file > > Zack, can

Re: [libvirt] [PATCH] qemuDomainRemoveMemoryDevice: unlink() memory backing file

2018-01-11 Thread Michal Privoznik
On 01/11/2018 01:36 PM, Peter Krempa wrote: > On Thu, Jan 11, 2018 at 13:24:57 +0100, Michal Privoznik wrote: >> https://bugzilla.redhat.com/show_bug.cgi?id=1461214 >> >> Since fec8f9c49af we try to use predictable file names for >> 'memory-backend-file' objects. But that made us provide full path

Re: [libvirt] [PATCH] qemuDomainRemoveMemoryDevice: unlink() memory backing file

2018-01-11 Thread Michal Privoznik
On 01/11/2018 01:32 PM, Daniel P. Berrange wrote: > On Thu, Jan 11, 2018 at 01:24:57PM +0100, Michal Privoznik wrote: >> https://bugzilla.redhat.com/show_bug.cgi?id=1461214 >> >> Since fec8f9c49af we try to use predictable file names for >> 'memory-backend-file' objects. But that made us provide

Re: [libvirt] [PATCH] qemuDomainRemoveMemoryDevice: unlink() memory backing file

2018-01-11 Thread Peter Krempa
On Thu, Jan 11, 2018 at 13:24:57 +0100, Michal Privoznik wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=1461214 > > Since fec8f9c49af we try to use predictable file names for > 'memory-backend-file' objects. But that made us provide full path > to qemu when hot plugging the object while

Re: [libvirt] [PATCH] qemuDomainRemoveMemoryDevice: unlink() memory backing file

2018-01-11 Thread Daniel P. Berrange
On Thu, Jan 11, 2018 at 01:24:57PM +0100, Michal Privoznik wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=1461214 > > Since fec8f9c49af we try to use predictable file names for > 'memory-backend-file' objects. But that made us provide full path > to qemu when hot plugging the object while

[libvirt] [PATCH] qemuDomainRemoveMemoryDevice: unlink() memory backing file

2018-01-11 Thread Michal Privoznik
https://bugzilla.redhat.com/show_bug.cgi?id=1461214 Since fec8f9c49af we try to use predictable file names for 'memory-backend-file' objects. But that made us provide full path to qemu when hot plugging the object while previously we provided merely a directory. But this makes qemu behave