From nobody Wed May 1 08:27:26 2024 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as permitted sender) client-ip=170.10.129.124; envelope-from=libvir-list-bounces@redhat.com; helo=us-smtp-delivery-124.mimecast.com; Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass(p=none dis=none) header.from=redhat.com ARC-Seal: i=1; a=rsa-sha256; t=1677663693; cv=none; d=zohomail.com; s=zohoarc; b=f/AsjO/sK/yUdTz+xitVXY5mq8k/MyIgAReODVCxOtdIR5zpM8wbwKoD8SdKxZQgc1Ycso0eUoevotZyADQ1FmM9H2JENxe8XQcWuiXmSvqZjJka81ioFO8YSdNiVJop53tNq95pL9MFm+qZgzIG4B6sQ/k6KZo8QJE9kABLuXQ= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1677663693; h=Content-Type:Content-Transfer-Encoding:Date:From:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:Sender:Subject:To; bh=zUzcJ3bv1M+B/LvvKq3CQzEMYm6oL1inuvkWMy6xo0I=; b=DyxHUhaFHoZ6574h4BF8EglttQpLmdmr5U5ozK86M3ko9DzGELR7iSIv/BoOutHm1pU0H4NaEc8Bptr5ezjr92fosGyqe9T+7mvwjp0CbmMIBqNZ4ew1z2/upNtONJpaHEvaGh1w4unvZ4hWAnAv0/eGgF8uAZavu87JWP9rjlw= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass header.from= (p=none dis=none) Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mx.zohomail.com with SMTPS id 1677663693478214.80766971781065; Wed, 1 Mar 2023 01:41:33 -0800 (PST) Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-145-OP-yEHfsNyyLHXcOLeKkMA-1; Wed, 01 Mar 2023 04:41:20 -0500 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id EE8C229AB3F3; Wed, 1 Mar 2023 09:41:16 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (unknown [10.30.29.100]) by smtp.corp.redhat.com (Postfix) with ESMTP id 4CB012026D4B; Wed, 1 Mar 2023 09:41:16 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (localhost [IPv6:::1]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 21ECF19465BB; Wed, 1 Mar 2023 09:41:16 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 7188F19465B9 for ; Wed, 1 Mar 2023 09:41:15 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id 544F0492C18; Wed, 1 Mar 2023 09:41:15 +0000 (UTC) Received: from localhost.localdomain (unknown [10.43.2.39]) by smtp.corp.redhat.com (Postfix) with ESMTP id EF786492C14 for ; Wed, 1 Mar 2023 09:41:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1677663692; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=zUzcJ3bv1M+B/LvvKq3CQzEMYm6oL1inuvkWMy6xo0I=; b=CjKEjOfFD6f3ZtW+Hxqznxvrp4giqu6P51KhgwQXzx0/b4DVmq3CnxWUwNp3WZ17yEsq71 JCh7HxFCT/ZBJtj3/zI3Ce+3YDVejHGUkgwEwuzZHNEoSqwf5tfjcxcJfrd4nCUcMiCKJo 7gAaXTNhsDmFzVIObbLn3OdDR7U3nDc= X-MC-Unique: OP-yEHfsNyyLHXcOLeKkMA-1 X-Original-To: libvir-list@listman.corp.redhat.com From: Michal Privoznik To: libvir-list@redhat.com Subject: [PATCH] NEWS: Document my contributions for upcoming release Date: Wed, 1 Mar 2023 10:41:12 +0100 Message-Id: <2d5dee21fdb718d0f5011d2f766e577f7db7fa05.1677663672.git.mprivozn@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.9 X-BeenThere: libvir-list@redhat.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development discussions about the libvirt library & tools List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: libvir-list-bounces@redhat.com Sender: "libvir-list" X-Scanned-By: MIMEDefang 3.1 on 10.11.54.4 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable X-ZohoMail-DKIM: pass (identity @redhat.com) X-ZM-MESSAGEID: 1677663694591100001 Content-Type: text/plain; charset="utf-8"; x-default="true" Signed-off-by: Michal Privoznik Reviewed-by: Jiri Denemark --- NEWS.rst | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) diff --git a/NEWS.rst b/NEWS.rst index 683c147af0..ab43d40f16 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -93,6 +93,39 @@ v9.1.0 (unreleased) properly terminated. This could cause problems such as errors when detaching a disk after snapshot. =20 + * virsh: Make domif-setlink work more than once + + There was a bug introduced in the previous release which made ``virsh + domif-setlink`` work exactly once over given domain. The bug was fixed= and + now the command can be run multiple times. + + * qemu: Make domain startup fail if NIC already exists + + When starting a domain with an ```` that's supposed to be + managed by libvirt (``managed=3D'yes'``) but corresponding TAP device = already + exists, report an error and make the startup process fail. + + * qemu: Deal with nested mounts when umount()-ing /dev + + When setting up private ``/dev`` for a domain (also known as ``namespa= ces`` + in ``qemu.conf``), libvirt preserves mount points nested under ``/dev`` + (e.g. ``/dev/shm``, ``/dev/pts`` and so on). But there was a bug which + resulted in inability to construct the namespace when there were two or + more filesystems mounted on the same path. This is common scenario with + containers and thus the bug was fixed. + + * remote: Pass ``mode`` and ``socket`` URI parameters to virt-ssh-helper + + When connecting to a remote host using SSH transport, ``?mode=3D`` and + ``?socket=3D`` URI parameters were ignored. This prevented users from + connecting to a monolithic daemon running on a remote host. + + * qemu: Various ``swtpm`` related fixes + + There are more cleanups and small bug fixes with regards to emulated + ````. For instance with migration when the ``swtpm`` state is on= a + shared volume, or seclabel setting/restoring. + =20 v9.0.0 (2023-01-16) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --=20 2.39.2