Re: [libvirt] [PATCH v3 4/5] qemu: Use predictable file names for memory-backend-file

2017-11-07 Thread John Ferlan
On 11/07/2017 10:51 AM, Michal Privoznik wrote: > In some cases management application needs to allocate memory for > qemu upfront and then just let qemu use that. Since we don't want > to expose path for memory-backend-file anywhere in the domain > XML, we can generate predictable paths. In

Re: [libvirt] [PATCH v3 4/5] qemu: Use predictable file names for memory-backend-file

2017-11-07 Thread Martin Kletzander
On Tue, Nov 07, 2017 at 03:57:45PM +, Daniel P. Berrange wrote: On Tue, Nov 07, 2017 at 04:51:03PM +0100, Michal Privoznik wrote: In some cases management application needs to allocate memory for qemu upfront and then just let qemu use that. Since we don't want to expose path for

Re: [libvirt] [PATCH v3 4/5] qemu: Use predictable file names for memory-backend-file

2017-11-07 Thread Michal Privoznik
On 11/07/2017 04:57 PM, Daniel P. Berrange wrote: > On Tue, Nov 07, 2017 at 04:51:03PM +0100, Michal Privoznik wrote: >> In some cases management application needs to allocate memory for >> qemu upfront and then just let qemu use that. Since we don't want >> to expose path for memory-backend-file

Re: [libvirt] [PATCH v3 4/5] qemu: Use predictable file names for memory-backend-file

2017-11-07 Thread Daniel P. Berrange
On Tue, Nov 07, 2017 at 04:51:03PM +0100, Michal Privoznik wrote: > In some cases management application needs to allocate memory for > qemu upfront and then just let qemu use that. Since we don't want > to expose path for memory-backend-file anywhere in the domain > XML, we can generate