From nobody Tue Feb 10 01:16:03 2026 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=1649061358; cv=none; d=zohomail.com; s=zohoarc; b=OgRwoX6SQCAFWMmb4tX6V7IzW4i9ZXfiZZiAye8BQU3O2SisDOTVAviDZ9xPqMNFHXCUx0wgp7aqRWOruUzlAhmls2Pz/UPgIZzoC7zG7cud/D70DxiB0zwT1YwD7i4zcNDZeMgesLb4N4wu3irrh0EIpPvyVkwmw6QNHTvBj/8= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1649061358; h=Content-Type:Content-Transfer-Encoding:Date:From:In-Reply-To:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:References:Sender:Subject:To; bh=4J9NX2zwUdupdf515YvLx7xee7YjtYOdf0yTEqeRLyQ=; b=S5JijkUTcWv3DjVRM9JApaB2aa+mQWmRQtwvshnZ6TdTN1/Vrt9WWHf3RMBxb4fOPXtOusxxzr7VcJIXFKQaTBxhKigfegpNap1iGwrMbDnzngmyQStdjPb5i2td4aRyXxUlWCkTr2U3+1jxl6DMOq8WyBovltgvjgyFTyIkqsc= 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 1649061358303554.1031613536217; Mon, 4 Apr 2022 01:35:58 -0700 (PDT) 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-171-XOWdI7eaOnuE_HH1rZ1dDQ-1; Mon, 04 Apr 2022 04:35:53 -0400 Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 09D12802803; Mon, 4 Apr 2022 08:35:52 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com [10.30.29.100]) by smtp.corp.redhat.com (Postfix) with ESMTP id E1E174229B8; Mon, 4 Apr 2022 08:35:51 +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 B76321940374; Mon, 4 Apr 2022 08:35:48 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com [10.11.54.10]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 243FC1940367 for ; Mon, 4 Apr 2022 08:35:44 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id 09EF5535D3D; Mon, 4 Apr 2022 08:35:44 +0000 (UTC) Received: from speedmetal.lan (unknown [10.40.208.35]) by smtp.corp.redhat.com (Postfix) with ESMTP id 8D48B401DAC for ; Mon, 4 Apr 2022 08:35:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1649061357; 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: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=4J9NX2zwUdupdf515YvLx7xee7YjtYOdf0yTEqeRLyQ=; b=TPRS2AFv4rYZIRckQHaGChSBGdHjp8kLoeVOeCtsdZPl2sLHux9RxUdFnz1o2caHj625b3 mtQrwrboYmfBRwJxzpDQyGsHqVKmJWOO+SAN0s3nLqG0EYQKPlGxKq2JQtPQoGyXWaqEIA krh09TTanGmEG7es3QTeUR6kcp3YATU= X-MC-Unique: XOWdI7eaOnuE_HH1rZ1dDQ-1 X-Original-To: libvir-list@listman.corp.redhat.com From: Peter Krempa To: libvir-list@redhat.com Subject: [PATCH 08/17] qemu: Formally deprecate support for qemu < 3.1 Date: Mon, 4 Apr 2022 10:35:25 +0200 Message-Id: In-Reply-To: References: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.85 on 10.11.54.10 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 2.85 on 10.11.54.9 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=libvir-list-bounces@redhat.com 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: 1649061359245100001 Content-Type: text/plain; charset="utf-8"; x-default="true" As of April 23 2022, Ubuntu 20.04 will be out for two years, which means we no longer have to support Ubuntu 18.04 along with qemu-2.11 shipped with it. This then brings the minimum qemu version we have to support to qemu-3.1: Debian 10/Stable: 3.1 OpenSUSE Leap 15.3: 5.2 Ubuntu 20.04: 4.2 RHEL/Centos 8.4: 4.2 Next event in this space will be 2023/07/06 when Debian 11 will be out for two years. Signed-off-by: Peter Krempa --- docs/drvqemu.rst | 6 +++--- src/qemu/qemu_capabilities.c | 4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/drvqemu.rst b/docs/drvqemu.rst index cfe4473951..6368a91fb9 100644 --- a/docs/drvqemu.rst +++ b/docs/drvqemu.rst @@ -5,7 +5,7 @@ QEMU/KVM/HVF hypervisor driver =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D -The libvirt KVM/QEMU driver can manage any QEMU emulator from version 2.11= .0 or +The libvirt KVM/QEMU driver can manage any QEMU emulator from version 3.1.= 0 or later. It supports multiple QEMU accelerators: software @@ -34,8 +34,8 @@ Deployment pre-requisites ``qemu-kvm`` and ``/dev/kvm`` device node. If both are found, then KVM = fully virtualized, hardware accelerated guests will be available. - **Hypervisor.framework (HVF)**: The driver will probe ``sysctl`` for the - presence of ``Hypervisor.framework``. If it is found and QEMU is newer = than - 2.12, then it will be possible to create hardware accelerated guests. + presence of ``Hypervisor.framework``. If it is found it will be possibl= e to + create hardware accelerated guests. Connections to QEMU driver -------------------------- diff --git a/src/qemu/qemu_capabilities.c b/src/qemu/qemu_capabilities.c index 25d029d0cc..e10035ee13 100644 --- a/src/qemu/qemu_capabilities.c +++ b/src/qemu/qemu_capabilities.c @@ -5371,8 +5371,8 @@ virQEMUCapsProbeQMPSchemaCapabilities(virQEMUCaps *qe= muCaps, return 0; } -#define QEMU_MIN_MAJOR 2 -#define QEMU_MIN_MINOR 11 +#define QEMU_MIN_MAJOR 3 +#define QEMU_MIN_MINOR 1 #define QEMU_MIN_MICRO 0 virDomainVirtType --=20 2.35.1