From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38777) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cOkk8-0006UL-0e for qemu-devel@nongnu.org; Wed, 04 Jan 2017 07:32:37 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cOkk4-0002Ki-Sa for qemu-devel@nongnu.org; Wed, 04 Jan 2017 07:32:35 -0500 Received: from mail-pf0-x244.google.com ([2607:f8b0:400e:c00::244]:36166) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cOkk4-0002Ke-MV for qemu-devel@nongnu.org; Wed, 04 Jan 2017 07:32:32 -0500 Received: by mail-pf0-x244.google.com with SMTP id b22so696620pfd.3 for ; Wed, 04 Jan 2017 04:32:32 -0800 (PST) From: Ashijeet Acharya Date: Wed, 4 Jan 2017 18:02:25 +0530 Message-Id: <1483533149-12807-1-git-send-email-ashijeetacharya@gmail.com> Subject: [Qemu-devel] [PATCH v3 0/4] Introduce a new --only-migratable option List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dgilbert@redhat.com Cc: jsnow@redhat.com, amit.shah@redhat.com, pbonzini@redhat.com, kwolf@redhat.com, armbru@redhat.com, quintela@redhat.com, mst@redhat.com, marcandre.lureau@redhat.com, groug@kaod.org, aneesh.kumar@linux.vnet.ibm.com, peter.maydell@linaro.org, qemu-devel@nongnu.org, Ashijeet Acharya Previously posted series patches: http://lists.nongnu.org/archive/html/qemu-devel/2016-12/msg02391.html http://lists.nongnu.org/archive/html/qemu-devel/2016-12/msg02062.html 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 helps to fail the migration blocker if the migration is already in progress and thus cannot be blocked. Note: This patch was originally written by John Snow and I have only made few changes. Patch 4 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. Note: I have not been able to test and compile the ARM drivers for KVM. They are: hw/intc/arm_gic_kvm.c hw/intc/arm_gicv3_its_kvm.c hw/intc/arm_gicv3_kvm.c Changes in v3: - set s->root_fid after migrate_add_blocker - free migration_blocker inside v9fs_attach() - change back ret<0 to just ret - free local_err Changes in v2: - change the documentation for the new option - add a NULL check for ObjectClass - break patch 3 into patch 3 and 4 - use error_append_hint - return -EACCES for only-migratable - fix the error messages Ashijeet Acharya (4): 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 migration: Fail migration blocker for --only-migratble block/qcow.c | 9 ++++++++- block/vdi.c | 9 ++++++++- block/vhdx.c | 18 ++++++++++++------ block/vmdk.c | 10 +++++++++- block/vpc.c | 13 ++++++++++--- block/vvfat.c | 22 ++++++++++++++-------- hw/9pfs/9p.c | 26 +++++++++++++++++++++----- hw/display/virtio-gpu.c | 34 +++++++++++++++++++++------------- hw/intc/arm_gic_kvm.c | 19 +++++++++++++------ 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 | 18 ++++++++++++++++++ hw/virtio/vhost.c | 10 +++++++++- include/migration/migration.h | 9 ++++++++- migration/migration.c | 42 ++++++++++++++++++++++++++++++++++++++++-- qdev-monitor.c | 9 +++++++++ qemu-options.hx | 9 +++++++++ stubs/migr-blocker.c | 3 ++- target-i386/kvm.c | 19 ++++++++++++++++--- vl.c | 4 ++++ 22 files changed, 294 insertions(+), 76 deletions(-) -- 2.6.2