From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.4 required=3.0 tests=FROM_EXCESS_BASE64, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4D4D3C04AAF for ; Tue, 21 May 2019 09:49:35 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 237F821479 for ; Tue, 21 May 2019 09:49:35 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 237F821479 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([127.0.0.1]:50307 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hT1Oo-0002U7-E6 for qemu-devel@archiver.kernel.org; Tue, 21 May 2019 05:49:34 -0400 Received: from eggs.gnu.org ([209.51.188.92]:42399) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hT1NI-0001r4-3B for qemu-devel@nongnu.org; Tue, 21 May 2019 05:48:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hT1NF-0004A5-Qe for qemu-devel@nongnu.org; Tue, 21 May 2019 05:47:59 -0400 Received: from mx1.redhat.com ([209.132.183.28]:36038) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hT1NF-0003RV-Jm for qemu-devel@nongnu.org; Tue, 21 May 2019 05:47:57 -0400 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id D3345F74CE for ; Tue, 21 May 2019 09:47:14 +0000 (UTC) Received: from redhat.com (ovpn-112-26.ams2.redhat.com [10.36.112.26]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 5A00E176B9; Tue, 21 May 2019 09:47:05 +0000 (UTC) Date: Tue, 21 May 2019 10:47:02 +0100 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= To: "Dr. David Alan Gilbert" Message-ID: <20190521094702.GH25835@redhat.com> References: <20190517125820.2885-1-jfreimann@redhat.com> <20190517125820.2885-2-jfreimann@redhat.com> <20190521093336.GA2915@work-vm> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190521093336.GA2915@work-vm> User-Agent: Mutt/1.11.4 (2019-03-13) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Tue, 21 May 2019 09:47:14 +0000 (UTC) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.132.183.28 Subject: Re: [Qemu-devel] [PATCH 1/4] migration: allow unplug during migration for failover devices X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= Cc: pkrempa@redhat.com, ehabkost@redhat.com, mst@redhat.com, aadam@redhat.com, qemu-devel@nongnu.org, laine@redhat.com, Jens Freimann , ailan@redhat.com Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On Tue, May 21, 2019 at 10:33:36AM +0100, Dr. David Alan Gilbert wrote: > * Jens Freimann (jfreimann@redhat.com) wrote: > > In "b06424de62 migration: Disable hotplug/unplug during migration" we > > added a check to disable unplug for all devices until we have figured > > out what works. For failover primary devices qdev_unplug() is called > > from the migration handler, i.e. during migration. > > > > This patch adds a flag to DeviceState which is set to false for all > > devices and makes an exception for vfio-pci devices that are also > > primary devices in a failover pair. > > > > Signed-off-by: Jens Freimann > > So I think this is safe in your case, because you trigger the unplug > right at the start of migration during setup and plug after failure; > however it's not generally safe - I can't unplug a device while the > migration is actually in progress. Libvirt will also block any attempt to hotplug/unplug device during migration. 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 :|