Re: [libvirt] [RFC] test_driver: Thoughts on the implementation of some FS-related APIs

2019-07-04 Thread Pavel Hrdina
On Thu, Jul 04, 2019 at 01:28:36PM +0200, Ilias Stamatis wrote: > On Thu, Jul 4, 2019 at 12:58 PM Pavel Hrdina wrote: > > > > On Wed, Jun 26, 2019 at 06:36:28PM +0200, Ilias Stamatis wrote: > > > Hello, > > > > > > I was thinking about how to implement the following APIs in the test > > >

Re: [libvirt] [RFC] test_driver: Thoughts on the implementation of some FS-related APIs

2019-07-04 Thread Ilias Stamatis
On Thu, Jul 4, 2019 at 12:58 PM Pavel Hrdina wrote: > > On Wed, Jun 26, 2019 at 06:36:28PM +0200, Ilias Stamatis wrote: > > Hello, > > > > I was thinking about how to implement the following APIs in the test driver: > > -virDomainFSFreeze > > -virDomainFSThaw > > -virDomainFSTrim > > > > The

Re: [libvirt] [RFC] test_driver: Thoughts on the implementation of some FS-related APIs

2019-07-04 Thread Pavel Hrdina
On Wed, Jun 26, 2019 at 06:36:28PM +0200, Ilias Stamatis wrote: > Hello, > > I was thinking about how to implement the following APIs in the test driver: > -virDomainFSFreeze > -virDomainFSThaw > -virDomainFSTrim > > The first two are conceptually paired. They both get a mountpoints > argument.

[libvirt] [RFC] test_driver: Thoughts on the implementation of some FS-related APIs

2019-06-26 Thread Ilias Stamatis
Hello, I was thinking about how to implement the following APIs in the test driver: -virDomainFSFreeze -virDomainFSThaw -virDomainFSTrim The first two are conceptually paired. They both get a mountpoints argument. The QEMU driver (which is the only driver implementing this currently) ignores