On Mon, Jun 03, 2019 at 08:27:29PM +0200, Ilias Stamatis wrote:
> On Mon, Jun 3, 2019 at 1:50 PM Pavel Hrdina wrote:
> >
> > On Mon, Jun 03, 2019 at 10:36:58AM +0200, Erik Skultety wrote:
> > > On Wed, May 29, 2019 at 02:22:55PM +0200, Ilias Stamatis wrote:
> > > > While implementing virDomainSave
On Mon, Jun 3, 2019 at 1:50 PM Pavel Hrdina wrote:
>
> On Mon, Jun 03, 2019 at 10:36:58AM +0200, Erik Skultety wrote:
> > On Wed, May 29, 2019 at 02:22:55PM +0200, Ilias Stamatis wrote:
> > > While implementing virDomainSaveImageGetXMLDesc and
> > > virDomainSaveImageDefineXML for the test driver,
On Mon, Jun 03, 2019 at 10:36:58AM +0200, Erik Skultety wrote:
> On Wed, May 29, 2019 at 02:22:55PM +0200, Ilias Stamatis wrote:
> > While implementing virDomainSaveImageGetXMLDesc and
> > virDomainSaveImageDefineXML for the test driver, I realized that there
> > exists already code for saving and
On Wed, May 29, 2019 at 02:22:55PM +0200, Ilias Stamatis wrote:
> While implementing virDomainSaveImageGetXMLDesc and
> virDomainSaveImageDefineXML for the test driver, I realized that there
> exists already code for saving and loading test images which can be
> reused. However, it needed to be ext
While implementing virDomainSaveImageGetXMLDesc and
virDomainSaveImageDefineXML for the test driver, I realized that there
exists already code for saving and loading test images which can be
reused. However, it needed to be extracted from testDomainSaveFlags and
testDomainRestoreFlags into separate
