From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Juan Quintela <quintela@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH RFC] migration: warn about non-migratable configurations unless '--no-migration' was specified
Date: Mon, 19 Apr 2021 18:17:19 +0100 [thread overview]
Message-ID: <YH27H6VmKGXdA4H7@redhat.com> (raw)
In-Reply-To: <YH26x8TkpT5zsgst@redhat.com>
On Mon, Apr 19, 2021 at 06:15:56PM +0100, Daniel P. Berrangé wrote:
> On Mon, Apr 19, 2021 at 06:11:47PM +0100, Dr. David Alan Gilbert wrote:
> > * Eduardo Habkost (ehabkost@redhat.com) wrote:
> > > I would make live migration policy an enum, just to make sure
> > > we are explicit about the requirements:
> > >
> > > - UNKNOWN: this is the current state in QEMU 6.0, where we don't
> > > really know what the user expects.
> > > This can be the default on existing versioned machine types,
> > > just for compatibility.
> > > I suggest making this print warnings for every migration
> > > blocker (like this patch does).
> > > I suggest deprecating this behavior as soon as we can.
> > >
> > > - PREFERRED: try to make the VM migratable when possible, but
> > > don't print a warning or error out if migration is blocked.
> > > This seems to be the behavior expected by libvirt today.
> > >
> > > - NOT_NEEDED: live migration is not needed, and QEMU is free to
> > > enable features that block live migration or change guest ABI.
> > > We can probably make this the default on machine types that
> > > never supported live migration.
> >
> > I suggest you could do this by adding:
> > -warn-none-migratable
> > -no-warn-none-migratable
> >
> > and then argue about defaults another time.
>
> If we're going to add new args, lets at least future proof our
> approach with an extensible option that we can wire into QMP
> too later
>
> -migratable none|preferred|required
>
> and letting us add extra key/value pairs to tune it if desired.
Having said that, we potentially don't need a dedicated arg if we
just make 'migratable=none|preferred|required' be a property of
the machine type and hook everything off that
>
> > > - REQUIRED: live migration is required, and adding a migration
> > > blocker would be a fatal error.
> > > This is already implemented by --only-migratable.
> > > I suggest making this the default on versioned machine types
> > > after a few releases, and after deprecating UNKNOWN.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2021-04-19 17:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 15:44 [PATCH RFC] migration: warn about non-migratable configurations unless '--no-migration' was specified Vitaly Kuznetsov
2021-04-15 16:04 ` Daniel P. Berrangé
2021-04-15 16:30 ` Eduardo Habkost
2021-04-15 16:40 ` Daniel P. Berrangé
2021-04-15 17:07 ` Daniel P. Berrangé
2021-04-15 17:28 ` Dr. David Alan Gilbert
2021-04-16 7:33 ` Vitaly Kuznetsov
2021-04-16 16:28 ` Eduardo Habkost
2021-04-17 9:33 ` Markus Armbruster
2021-04-19 16:42 ` Daniel P. Berrangé
2021-04-19 16:48 ` Eduardo Habkost
2021-04-19 17:11 ` Dr. David Alan Gilbert
2021-04-19 17:15 ` Daniel P. Berrangé
2021-04-19 17:17 ` Daniel P. Berrangé [this message]
2021-04-19 18:47 ` Dr. David Alan Gilbert
2021-04-19 19:32 ` Eduardo Habkost
2021-04-20 11:51 ` Dr. David Alan Gilbert
2021-04-20 13:48 ` Eduardo Habkost
2021-04-20 14:10 ` Dr. David Alan Gilbert
2021-04-20 14:15 ` Daniel P. Berrangé
2021-04-20 15:20 ` Eduardo Habkost
2021-04-17 9:35 ` Markus Armbruster
2021-04-19 7:26 ` Markus Armbruster
2021-04-19 15:46 ` Markus Armbruster
2021-04-18 15:53 ` Peter Maydell
2021-04-19 16:28 ` Eduardo Habkost
2021-04-19 16:37 ` Daniel P. Berrangé
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YH27H6VmKGXdA4H7@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=vkuznets@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.