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 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id CB1EBCCD18E for ; Wed, 15 Oct 2025 07:13:15 +0000 (UTC) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1v8vfz-0002d4-PZ; Wed, 15 Oct 2025 03:11:59 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1v8vfy-0002cw-AJ for qemu-devel@nongnu.org; Wed, 15 Oct 2025 03:11:58 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1v8vfq-0000NE-GW for qemu-devel@nongnu.org; Wed, 15 Oct 2025 03:11:57 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1760512306; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=EINVuQNLcrWvoqQs7o3wwbhGgD5M+fyWyFY9MPkf0/A=; b=DcNuAgFPtrmILIVfhjP/cFA3ZwMPy93nZ9E4qos976YTN45Rq3EL1phe2d/BM5g/AKt/R3 ayShPB7Ozq1fXE9OYkVgG6qHLDpjAur9QQqQESsdkNIHuV4hBk27gTGdnmHu75mWes/sKW EIpf1s0lsvsN/Vnx5BSqVACx2JNmdo8= Received: from mx-prod-mc-03.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-638-9gFMvhTQMYmyk72DsUBh9Q-1; Wed, 15 Oct 2025 03:11:43 -0400 X-MC-Unique: 9gFMvhTQMYmyk72DsUBh9Q-1 X-Mimecast-MFC-AGG-ID: 9gFMvhTQMYmyk72DsUBh9Q_1760512301 Received: from mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.93]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-03.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 4FA151956052; Wed, 15 Oct 2025 07:11:41 +0000 (UTC) Received: from redhat.com (unknown [10.42.28.51]) by mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 7B3E518003FC; Wed, 15 Oct 2025 07:11:36 +0000 (UTC) Date: Wed, 15 Oct 2025 08:11:33 +0100 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= To: Vladimir Sementsov-Ogievskiy Cc: Peter Xu , mst@redhat.com, jasowang@redhat.com, farosas@suse.de, sw@weilnetz.de, eblake@redhat.com, armbru@redhat.com, thuth@redhat.com, philmd@linaro.org, qemu-devel@nongnu.org, michael.roth@amd.com, steven.sistare@oracle.com, leiyang@redhat.com, davydov-max@yandex-team.ru, yc-core@yandex-team.ru, raphael.s.norwitz@gmail.com Subject: Re: [PATCH v7 16/19] qapi: add interface for backend-transfer virtio-net/tap migration Message-ID: References: <20251010173957.166759-1-vsementsov@yandex-team.ru> <20251010173957.166759-17-vsementsov@yandex-team.ru> <6da192b9-7609-4cc8-82a9-1a445ecb10c9@yandex-team.ru> <9a9ced95-583e-4c1e-84f0-af12a5800193@yandex-team.ru> <5b9a466f-19c2-41a0-86b0-aa8ce7c98443@yandex-team.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <5b9a466f-19c2-41a0-86b0-aa8ce7c98443@yandex-team.ru> User-Agent: Mutt/2.2.14 (2025-02-20) X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.93 Received-SPF: pass client-ip=170.10.133.124; envelope-from=berrange@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org On Wed, Oct 15, 2025 at 12:54:21AM +0300, Vladimir Sementsov-Ogievskiy wrote: > On 15.10.25 00:46, Vladimir Sementsov-Ogievskiy wrote: > > > > > > And then, developing similar migration for vhost-user-blk, found > > > that I can't use on boolean capability for such features, the reason > > > in commit message, which we discuss now. > > > > Why a bool isn't enough?  Could you share a link to that discussion? > > I mean, one boolean is not enough for different devices, when not assisted > by per-device options. So, I came to idea of "list of backend targets" > in migration parameter. If we need to identify backends or frontends, surely we should be using the "id" that the mgmt app used when creating the object, that gets set in the QOM tree. With 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 :|