From nobody Sat Feb 7 06:35:25 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=1678092435; cv=none; d=zohomail.com; s=zohoarc; b=ZA/WrBig4VhjKxiKTRlivYne2JcUuGkBcMjjwgR57U6zBf6wFsWlumbGtwLLbLq4oZrUC1EZ+d3l7uTvOh06/Yxpgg1TRiQgutNyrd+B/k82/PsRjaoI1jK1lPP5tERgiLTNo72P2vQXI7gB6STthq/WdtGB881bB2fUBPxTl3g= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1678092435; h=Content-Type:Content-Transfer-Encoding:Cc: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=37MyqIGrJ8NDqQYDY+IFgkqLJhkh+Oz/+/sGdhCxVu4=; b=UN9t9HpCCoM5bNJU56JA09coCk78oF36+tYMSrgS+77iC8YP8KIdgTjv1DQ+3pgDku/vJjFmfJGrmjVup+nSYifNXTrvibe0SeYQfMjRQqHI7BltcO7+/aDm8YMIvVZxG9MWJiFLiOSVjhXDIW13PdIt/rUa/Rd6cs4Sh/GThkw= 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 1678092435681574.4385587331711; Mon, 6 Mar 2023 00:47:15 -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-13-j3bZMeawNLmNLsiTr4bWeA-1; Mon, 06 Mar 2023 03:47:13 -0500 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id B99083813F23; Mon, 6 Mar 2023 08:47:09 +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 A4BEF1400AFC; Mon, 6 Mar 2023 08:47:09 +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 7487B194658C; Mon, 6 Mar 2023 08:47:09 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 1FA9A1946586 for ; Mon, 6 Mar 2023 08:47:08 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id 0571B440E0; Mon, 6 Mar 2023 08:47:08 +0000 (UTC) Received: from thuth.com (unknown [10.39.193.101]) by smtp.corp.redhat.com (Postfix) with ESMTP id AC35A175AD; Mon, 6 Mar 2023 08:47:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1678092434; h=from:from:sender:sender: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:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=37MyqIGrJ8NDqQYDY+IFgkqLJhkh+Oz/+/sGdhCxVu4=; b=eAA6po5VprUJaRkXp8hn9SsJ1ru7FQST0qBQDJJ1te4Zfdb4hXSdqTHo9dXKa/uRjRZQMV v2n4UyAB9QuovCBUYLXBCyScIHZLG45crnPskwm+uLMjEgpNwc8L+khF+ZbfXupcKIT7P2 V/fsDPjMSLzwbxNxCzRRyebjlUuxNgo= X-MC-Unique: j3bZMeawNLmNLsiTr4bWeA-1 X-Original-To: libvir-list@listman.corp.redhat.com From: Thomas Huth To: qemu-devel@nongnu.org, Peter Maydell , Daniel Berrange , Paolo Bonzini Subject: [PATCH v4 2/5] docs/about/deprecated: Deprecate the qemu-system-i386 binary Date: Mon, 6 Mar 2023 09:46:55 +0100 Message-Id: <20230306084658.29709-3-thuth@redhat.com> In-Reply-To: <20230306084658.29709-1-thuth@redhat.com> References: <20230306084658.29709-1-thuth@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.5 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: , Cc: libvir-list@redhat.com, Richard Henderson , Markus Armbruster , Maxim Levitsky , Wilfred Mallawa , qemu-arm@nongnu.org, Reinoud Zandijk , John Paul Adrian Glaubitz , xen-devel@lists.xenproject.org, =?UTF-8?q?Alex=20Benn=C3=A9e?= Errors-To: libvir-list-bounces@redhat.com Sender: "libvir-list" X-Scanned-By: MIMEDefang 3.1 on 10.11.54.7 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-ZohoMail-DKIM: pass (identity @redhat.com) X-ZM-MESSAGEID: 1678092436223100003 Aside from not supporting KVM on 32-bit hosts, the qemu-system-x86_64 binary is a proper superset of the qemu-system-i386 binary. With the 32-bit host support being deprecated, it is now also possible to deprecate the qemu-system-i386 binary. With regards to 32-bit KVM support in the x86 Linux kernel, the developers confirmed that they do not need a recent qemu-system-i386 binary here: https://lore.kernel.org/kvm/Y%2ffkTs5ajFy0hP1U@google.com/ Reviewed-by: Daniel P. Berrang=C3=A9 Reviewed-by: Wilfred Mallawa Signed-off-by: Thomas Huth --- docs/about/deprecated.rst | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docs/about/deprecated.rst b/docs/about/deprecated.rst index 1ca9dc33d6..c4fcc6b33c 100644 --- a/docs/about/deprecated.rst +++ b/docs/about/deprecated.rst @@ -34,6 +34,20 @@ deprecating the build option and no longer defend it in = CI. The ``--enable-gcov`` build option remains for analysis test case coverage. =20 +``qemu-system-i386`` binary (since 8.0) +''''''''''''''''''''''''''''''''''''''' + +The ``qemu-system-i386`` binary was mainly useful for running with KVM +on 32-bit x86 hosts, but most Linux distributions already removed their +support for 32-bit x86 kernels, so hardly anybody still needs this. The +``qemu-system-x86_64`` binary is a proper superset and can be used to +run 32-bit guests by selecting a 32-bit CPU model, including KVM support +on x86_64 hosts. Thus users are recommended to reconfigure their systems +to use the ``qemu-system-x86_64`` binary instead. If a 32-bit CPU guest +environment should be enforced, you can switch off the "long mode" CPU +flag, e.g. with ``-cpu max,lm=3Doff``. + + System emulator command line arguments -------------------------------------- =20 --=20 2.31.1