[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Minutes from the "Stuttgart block Gipfele"
From: |
Stefan Hajnoczi |
Subject: |
Re: [Qemu-devel] Minutes from the "Stuttgart block Gipfele" |
Date: |
Thu, 14 Jan 2016 11:25:35 +0000 |
User-agent: |
Mutt/1.5.24 (2015-08-30) |
On Mon, Jan 11, 2016 at 04:10:12PM +0100, Kevin Wolf wrote:
> Am 23.12.2015 um 09:33 hat Stefan Hajnoczi geschrieben:
> > On Fri, Dec 18, 2015 at 02:15:38PM +0100, Markus Armbruster wrote:
> > Another problem is that the backup block job and other operations that
> > require a single command today could require sequences of low-level
> > setup commands to create filter nodes. The QMP client would need to
> > first create a write notifier filter and then start the backup block job
> > with the write notifier node name. It's clumsy.
>
> I don't think splitting it up into several low-level commands is
> necessary. We don't expect the user to set any options for the filter
> (and if we did, they would probably have to match the same options for
> the block job), so we can keep the BDS creation as a part of starting
> the block job.
>
> The important part is that the management tool knows that a filter is
> going to be inserted and how to address it. In order to achieve that, we
> could simply add a 'filter-node-name' option to the QMP command starting
> the job.
That sounds like a good approach.
Stefan
signature.asc
Description: PGP signature