From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Ashijeet Acharya <ashijeetacharya@gmail.com>,
jsnow@redhat.com, amit.shah@redhat.com, pbonzini@redhat.com,
kwolf@redhat.com, armbru@redhat.com, quintela@redhat.com,
marcandre.lureau@redhat.com, groug@kaod.org,
aneesh.kumar@linux.vnet.ibm.com, peter.maydell@linaro.org,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] Introduce a new --only-migratable option
Date: Thu, 15 Dec 2016 19:03:56 +0000 [thread overview]
Message-ID: <20161215190355.GA16467@work-vm> (raw)
In-Reply-To: <20161215205122-mutt-send-email-mst@kernel.org>
* Michael S. Tsirkin (mst@redhat.com) wrote:
> On Thu, Dec 15, 2016 at 04:07:41PM +0000, Dr. David Alan Gilbert wrote:
> > * Michael S. Tsirkin (mst@redhat.com) wrote:
> > > On Thu, Dec 15, 2016 at 12:36:59AM +0530, Ashijeet Acharya wrote:
> > > > This series adds a new command line option "--only-migratable" which will only
> > > > allow addition of those devices to a QEMU instance which are migratable and do
> > > > not abruptly fail QEMU after migration.
> > > >
> > > > Patch 1 adds the new option "-only-migratable".
> > > >
> > > > Patch 2 adds compatibility for various "device adding" options for both via
> > > > command line and hotplug methods.
> > > >
> > > > Patch 3 handles the special case of devices which become unmigratable dynamically
> > > > by making call to "migrate_add_blocker". Here we fail the particular action of the
> > > > device which results in an unmigratable VM.
> > > > Eg: 9pfs fails to mount the filesystem.
> > >
> > > I guess that's possible but wouldn't it be cleaner to add introspection
> > > so management can find out what can migrate?
> > > Further, what should be removed (e.g. by hotplug) if you do want
> > > to migrate.
> > >
> > > As it is, you get a failure but no easy way for tools to
> > > find out what was the failure reason.
> >
> > You get the device name of the device that's failed don't you?
>
> As a string but I'm not sure it's machine readable.
>
> > Where would you add introspection?
> >
> > Dave
>
> monitor and command line.
OK; that's not a bad idea if you or a libvirt person could
specifiy how they want that to appear - but it's really
a separate problem.
One thing we'd have to do if we did that would be to
add another flag to devices to declare that they might
sometime in the future call the migrate_add_blocker.
Dave
> > >
> > > > Ashijeet Acharya (3):
> > > > migration: Add a new option to enable only-migratable
> > > > migration: Allow "device add" options to only add migratable devices
> > > > migration: disallow migrate_add_blocker during migration
> > > >
> > > > block/qcow.c | 11 ++++++++++-
> > > > block/vdi.c | 11 ++++++++++-
> > > > block/vhdx.c | 20 ++++++++++++++------
> > > > block/vmdk.c | 12 +++++++++++-
> > > > block/vpc.c | 15 ++++++++++++---
> > > > block/vvfat.c | 24 ++++++++++++++++--------
> > > > hw/9pfs/9p.c | 22 ++++++++++++++++++----
> > > > hw/display/virtio-gpu.c | 35 ++++++++++++++++++++++-------------
> > > > hw/intc/arm_gic_kvm.c | 20 ++++++++++++++------
> > > > hw/intc/arm_gicv3_its_kvm.c | 21 ++++++++++++++-------
> > > > hw/intc/arm_gicv3_kvm.c | 22 +++++++++++++++-------
> > > > hw/misc/ivshmem.c | 17 +++++++++++++----
> > > > hw/scsi/vhost-scsi.c | 27 +++++++++++++++++++++------
> > > > hw/usb/bus.c | 15 +++++++++++++++
> > > > hw/virtio/vhost.c | 11 ++++++++++-
> > > > include/migration/migration.h | 9 ++++++++-
> > > > migration/migration.c | 42 ++++++++++++++++++++++++++++++++++++++++--
> > > > qdev-monitor.c | 9 +++++++++
> > > > qemu-options.hx | 10 ++++++++++
> > > > stubs/migr-blocker.c | 3 ++-
> > > > target-i386/kvm.c | 19 ++++++++++++++++---
> > > > vl.c | 4 ++++
> > > > 22 files changed, 304 insertions(+), 75 deletions(-)
> > > >
> > > > --
> > > > 2.6.2
> > --
> > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2016-12-15 19:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 19:06 [Qemu-devel] [PATCH 0/3] Introduce a new --only-migratable option Ashijeet Acharya
2016-12-14 19:07 ` [Qemu-devel] [PATCH 1/3] migration: Add a new option to enable only-migratable Ashijeet Acharya
2016-12-15 15:29 ` Dr. David Alan Gilbert
2016-12-15 16:48 ` Ashijeet Acharya
2016-12-15 16:50 ` Dr. David Alan Gilbert
2016-12-14 19:07 ` [Qemu-devel] [PATCH 2/3] migration: Allow "device add" options to only add migratable devices Ashijeet Acharya
2016-12-15 16:05 ` Dr. David Alan Gilbert
2016-12-15 16:10 ` Ashijeet Acharya
2016-12-15 16:19 ` Dr. David Alan Gilbert
2016-12-15 16:36 ` Ashijeet Acharya
2016-12-14 19:07 ` [Qemu-devel] [PATCH 3/3] migration: disallow migrate_add_blocker during migration Ashijeet Acharya
2016-12-15 17:11 ` Dr. David Alan Gilbert
2016-12-15 17:51 ` John Snow
2016-12-15 18:12 ` Ashijeet Acharya
2016-12-15 15:57 ` [Qemu-devel] [PATCH 0/3] Introduce a new --only-migratable option Michael S. Tsirkin
2016-12-15 16:07 ` Dr. David Alan Gilbert
2016-12-15 16:16 ` Ashijeet Acharya
2016-12-15 18:53 ` Michael S. Tsirkin
2016-12-15 19:03 ` Dr. David Alan Gilbert [this message]
2016-12-15 19:16 ` Peter Maydell
2016-12-15 19:39 ` Dr. David Alan Gilbert
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=20161215190355.GA16467@work-vm \
--to=dgilbert@redhat.com \
--cc=amit.shah@redhat.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=armbru@redhat.com \
--cc=ashijeetacharya@gmail.com \
--cc=groug@kaod.org \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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.