[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v6 06/10] migration: move only_migratable to Mig
From: |
Peter Xu |
Subject: |
Re: [Qemu-devel] [PATCH v6 06/10] migration: move only_migratable to MigrationState |
Date: |
Wed, 28 Jun 2017 14:54:34 +0800 |
User-agent: |
Mutt/1.5.24 (2015-08-30) |
On Tue, Jun 27, 2017 at 10:36:44AM -0300, Eduardo Habkost wrote:
> On Tue, Jun 27, 2017 at 06:15:37AM -0500, Eric Blake wrote:
> > On 06/26/2017 11:10 PM, Peter Xu wrote:
> > > One less global variable, and it does only matter with migration.
> > >
> > > We keep the old "--only-migratable" option, but also now we support:
> > >
> > > -global migration.only-migratable=true
> >
> > Does command line introspection work to see that this new spelling is
> > available? If not, what else can we do to let libvirt learn that the
> > new form is preferred?
>
> "only-migratable" will appear on the output of
> "device-list-properties typename=migration". But although I think
> implementing this using global properties internally is nice, I'm unsure
> about making -global the recommended interface to configure this.
Could I ask why it may not good to use "-global" to configure it?
Actually if we can merge this series, there is planned work to expose
more migration parameters to the user, like: migration.postcopy,
migration.compression, migration.speed, etc. So before I post similar
patches like this to export more things, I would like to know whether
there is possible issue with it in general. Thanks,
--
Peter Xu
[Qemu-devel] [PATCH v6 07/10] migration: move skip_configuration out, Peter Xu, 2017/06/27
[Qemu-devel] [PATCH v6 08/10] migration: move skip_section_footers, Peter Xu, 2017/06/27
[Qemu-devel] [PATCH v6 09/10] migration: merge enforce_config_section somewhat, Peter Xu, 2017/06/27