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 B19BDEB64DD for ; Thu, 17 Aug 2023 10:50:38 +0000 (UTC) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qWaZg-0008Dy-4L; Thu, 17 Aug 2023 06:49:57 -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 1qWaZe-0008De-4D for qemu-devel@nongnu.org; Thu, 17 Aug 2023 06:49:54 -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 1qWaZa-0001Ta-Ha for qemu-devel@nongnu.org; Thu, 17 Aug 2023 06:49:53 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1692269389; 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:in-reply-to:in-reply-to: references:references; bh=X0v7Me8rgYKDAf6VTKVckm9++IXMVHXMSa/puah3VSU=; b=YpbD3W39MJkqpMQxIOnmngqmZy68Xu/ZyZJWI38EPXaahCkZL2Zf95wY3sGty6br8Kg1bN vPtUZ7JDa0E+lZbRMWSDvGC4J7o//5hmdhLT/fj9+OXKS0xi7DGH6RjLsdoIhbVPMQuWcE w0l7SgX3+o5783IUz0+k+hNI9sVR35w= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-534-RAEyWhGSNxKuiMpkgzSr4A-1; Thu, 17 Aug 2023 06:49:46 -0400 X-MC-Unique: RAEyWhGSNxKuiMpkgzSr4A-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id C2D3785CCE2; Thu, 17 Aug 2023 10:49:45 +0000 (UTC) Received: from redhat.com (unknown [10.42.28.120]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 2B27540C6F4E; Thu, 17 Aug 2023 10:49:45 +0000 (UTC) Date: Thu, 17 Aug 2023 11:49:43 +0100 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= To: Yu Zhang Cc: qemu-devel , Jinpu Wang , Elmar Gerdes Subject: Re: about QEMU TLS Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/2.2.9 (2022-11-12) X-Scanned-By: MIMEDefang 3.1 on 10.11.54.2 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_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=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 Mon, Aug 07, 2023 at 12:07:31AM +0200, Yu Zhang wrote: > Hi all, > > According to qemu docs [1], TLS parameters are specified as an object in > the QEMU command line: > > -object tls-creds-x509,id=id,endpoint=endpoint,dir=/path/to/cred/dir ... > > of which "endpoint" is a type of "QCryptoTLSCredsEndpoint" and can be > either a "server" or a "client". > > I'd like to know: > > - When a VM is started with this config, is there a way (e.g. QMP) to > change the value of "endpoint"? > If possible, how to do this? or else after the first migration of a VM, > the VM has "endpoint=server", > which can't be migrated without stop / start. Use object_del + object_add to delete the old credentials and create new ones. > - In which case does the QEMU reload its TLS certificate, e.g. when a QEMU > VM has been run longer > than the valid period of its TLS certificate? The certs are loaded at the time the incoming/outgoing migration operation is initiated, so they are always fresh. > - The migration is done by using HMP monitor on both source and target > side. Is it possible to do it > by using QMP commands? Almost everything in HMP has an equivalent QMP command. 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 :|