Re: [libvirt] [PATCH RFC 0/3] Add mechanisms to force QEMU capabilities refetches

2018-11-15 Thread Daniel P . Berrangé
On Wed, Nov 14, 2018 at 02:22:12PM -0500, John Ferlan wrote: > > > On 11/14/18 4:25 AM, Daniel P. Berrangé wrote: > > On Tue, Nov 13, 2018 at 03:21:03PM -0500, John Ferlan wrote: > >> Sending as an RFC primarily because I'm looking for whether either > >> or both mechanisms in the series is more

Re: [libvirt] [PATCH RFC 0/3] Add mechanisms to force QEMU capabilities refetches

2018-11-14 Thread John Ferlan
On 11/14/18 4:25 AM, Daniel P. Berrangé wrote: > On Tue, Nov 13, 2018 at 03:21:03PM -0500, John Ferlan wrote: >> Sending as an RFC primarily because I'm looking for whether either >> or both mechanisms in the series is more or less desired. Likewise, >> if it's felt that the current process of

Re: [libvirt] [PATCH RFC 0/3] Add mechanisms to force QEMU capabilities refetches

2018-11-14 Thread Daniel P . Berrangé
On Tue, Nov 13, 2018 at 03:21:03PM -0500, John Ferlan wrote: > Sending as an RFC primarily because I'm looking for whether either > or both mechanisms in the series is more or less desired. Likewise, > if it's felt that the current process of telling customers to just > delete the cache is

[libvirt] [PATCH RFC 0/3] Add mechanisms to force QEMU capabilities refetches

2018-11-13 Thread John Ferlan
Sending as an RFC primarily because I'm looking for whether either or both mechanisms in the series is more or less desired. Likewise, if it's felt that the current process of telling customers to just delete the cache is acceptible, then so be it. If there's other ideas I'm willing to give them a