From nobody Fri May 3 12:04:26 2024 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 170.10.133.124 as permitted sender) client-ip=170.10.133.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.133.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=1677595778; cv=none; d=zohomail.com; s=zohoarc; b=glEs2rvXgfiNsO09A/v08uFw6ZBtCaZ+xC9gaKk0S0vvxc/gmtbPKR1OXsCsDjaACNLcJhzYD01Tvzt4NgMh0IOLrRtSnetYfOBKwEgFxnzGkbVKAhbwDSfh0bZA1gPfgPoeOXaFIzr51vIR1NO/k6Ge/Xx3ntOsivkdgsKvewc= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1677595778; 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=vwVpM/EIcGpF8+9t/IYjNPlivPWMxPHvi76Lpwq2fAI=; b=GfgZRgiIWL0Q6u/xCROwgvkE+/9GAtzFNl2+7NI1BqPkkVg5IcqN6BekhrO3nZNpRzcGSoBM3Q3BXHzIKouMQAEKxdeoGJB6BIwLfbkbtHeWQC9Lr0gqADQzmPukpOd+I396GYa4oowIfyN4TDXxL818mIUF+roC1NsLwtvjQno= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.133.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.133.124]) by mx.zohomail.com with SMTPS id 1677595778563308.0991951546953; Tue, 28 Feb 2023 06:49:38 -0800 (PST) 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-158-Joi7etC_PNCnf1TDiWeufA-1; Tue, 28 Feb 2023 09:49:33 -0500 Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com [10.11.54.10]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 1E16285A5A3; Tue, 28 Feb 2023 14:49:31 +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 C792B492B12; Tue, 28 Feb 2023 14:49:28 +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 732FB194658D; Tue, 28 Feb 2023 14:49:28 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 9D5C8194658C for ; Tue, 28 Feb 2023 14:49:26 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id 6BD712166B2B; Tue, 28 Feb 2023 14:49:26 +0000 (UTC) Received: from vhost3.router.laine.org (unknown [10.2.16.231]) by smtp.corp.redhat.com (Postfix) with ESMTP id 53CB62166B26 for ; Tue, 28 Feb 2023 14:49:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1677595775; 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=vwVpM/EIcGpF8+9t/IYjNPlivPWMxPHvi76Lpwq2fAI=; b=d1aQQWMchc4W9XX1Af4lpAFZrv9W4KhcQa04ksJMS4y9YhhBgoL6LYKbtoWV1Xn7l/KfqE dI49jg4MNXBKr+E4MBHk6Ts1ZqZhzOSRp2fPX+vheodZME86l8ESa+DQHRem/9UreBBFPn IfHpSJpWSNLkG1PqgvpjaLy03YPKT9M= X-MC-Unique: Joi7etC_PNCnf1TDiWeufA-1 X-Original-To: libvir-list@listman.corp.redhat.com From: Laine Stump To: libvir-list@redhat.com Subject: [PATCH] NEWS: note new passt feature & bugfix for 9.1.0 release Date: Tue, 28 Feb 2023 09:49:26 -0500 Message-Id: <20230228144926.452029-1-laine@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.6 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.10 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: 1677595779874100001 Content-Type: text/plain; charset="utf-8"; x-default="true" At Stefano's suggestion, this also adds a sentence pointing out that SELinux must be disabled in order for passt support to work. I didn't think to put this info in the NEWS file last month. Signed-off-by: Laine Stump Reviewed-by: Peter Krempa --- I've noticed that in some places, QEMU related points are marked with "QEMU:" and in other places they are marked with "qemu:". In the 9.1.0 sections, the new features all use "qemu:" while the bugfixes all use "QEMU:". I just went along with the flow in both cases, but we should probably do a patch to standardize on one or the other (and then try to stick to it). So which is more appropriate? using the capitalization the way the QEMU project prefers it? Or the capitalization the way the subdirectory in libvirt is named? NEWS.rst | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/NEWS.rst b/NEWS.rst index 1180d75310..df613abc69 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -38,6 +38,13 @@ v9.1.0 (unreleased) A pvpanic device can be now defined as a PCI device (the original is a= n ISA device) with ````. =20 + * qemu: support automatic restart of inadvertantly terminated passt proc= ess=20 + + If the passt process that is serving as the backend of a -netdev + stream is terminated unexpectedly, libvirt now listens to QEMU's + notification of this, and starts up a new passt instance, thus + preserving network connectivity. + * **Improvements** =20 * RPM packaging changes @@ -63,6 +70,15 @@ v9.1.0 (unreleased) snapshot when it existed. In addition when external memory only snapsh= ot was created libvirt failed without producing any error. =20 + * QEMU: properly report passt startup errors + + Due to how the child passt process was started, the initial + support for passt (added in 9.0.0) would not see errors + encountered during startup, so libvirt would continue to setup and + start the guest; this led to a running guest with no network + connectivity. This issue has be corrected. + + (NB: it is still necessary to disable SELinux to start passt.) =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