From nobody Tue Jun 13 10:18:19 2023 X-Original-To: virtualization@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QgPdp709Nz4ckMR for ; Tue, 13 Jun 2023 10:18:22 +0000 (UTC) (envelope-from corvink@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QgPdp6My0z4kpt for ; Tue, 13 Jun 2023 10:18:22 +0000 (UTC) (envelope-from corvink@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1686651502; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=DU470Nj43FjaA2EU7RC+/RIvT1JaJsBe0TPbl0hQrUk=; b=kHC76vUCtZyCP/Fsp6+fMcCGuTlWJsotABnzOBinMTCXQ2yiloaRn+SOVPrFupig7vegp5 DNy4e/1tvTqMTDiFcsLABuSgblE2Wy4KFukLmieXvOinZm4xxBlqAY9CLcnzJ2ygwQ4TSv rW7gXWPRapHY7jl98IJpaP4yWcgtNmMqhUoqqcbMBaX+nl8XPoXS+472cyiWklNTIo0zG+ 2I65LVVry6+rHuxR7L4n1K9jrViyA6ryL3p7eOkPaqFua/Z8zI97MikZVNozr4n91b9O/a CBZHA117w5+LMCYjPfQA46sqJ8S0T5rpqrxuQPi8+px+M731n0BMvLXiJB5kDw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1686651502; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=DU470Nj43FjaA2EU7RC+/RIvT1JaJsBe0TPbl0hQrUk=; b=sO0/msMwVKc9GZQA0LFwyWgQRhTwok6zmSm8LlB9jNlEUaLVEGZv0tpaqKwNd335DINQe4 CbSxnHJuI4zG1wjtL6KNlj7ZmlL80SXuvGR9Cms4d4dnJAvKfu8EzCWjGNTUC/VcxkvbAn CoSy67fEcOewGrN+7PE93fH8M+DfACKeY3B+4XUlu56eABJ7UrWzuWGJmlOubLsNaF5B0F qJ4mrhdStqB0vvOJrV4fVC7x9GifLx8n/qD1nqpjYDIWDSMamLLJeH6zklWHeKeaLm2c7B cUisOWY2tsIAy+Q89COxwBhlibJJ3j5x9XiHO9Zpl4XNhqYSq0zlzgf510KWpA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1686651502; a=rsa-sha256; cv=none; b=OebKnp8QcsJ6WN1v7T0D8xkxxZ0PZmmIhiXnkVucpRfKo7ZKa1ph0Y/bIVYQAw8zAJcJul 9k6QUcZy63M7Y74NHN+LIbVpP9dYASUbRToce+wEyTik0l/wP4q0m9TF9k6M8ZTUjC1gNJ 2B/SMiw2t1+Y1Amwo/r9gH7KgptuJq1dGNEBYTDGbrcqJBIZYe1dOqVkPwrLgH3NHSjJXy j1VzwgCy2TOPFthY63EyZ82nFXoMnChDp84malGPykwf8Fy+3699XpwkVfXdX26IIydlo8 hu3x+F/5D/t3rGLumgfjq8GF/BVtX5tteOcnCrYYqPPPwbgONSNXdz09a8aqnA== Received: from [172.21.179.48] (unknown [195.226.174.194]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: corvink) by smtp.freebsd.org (Postfix) with ESMTPSA id 4QgPdp3Bh1znkK for ; Tue, 13 Jun 2023 10:18:22 +0000 (UTC) (envelope-from corvink@FreeBSD.org) Message-ID: <8f4207144eb5f020e840e3fe2aa3612e63792bc8.camel@FreeBSD.org> Subject: How to remove bhyve's fwctl device? From: Corvin =?ISO-8859-1?Q?K=F6hne?= To: virtualization@FreeBSD.org Date: Tue, 13 Jun 2023 12:18:19 +0200 Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-qtWotbAPq1B06jIHvtVE" User-Agent: Evolution 3.48.3 List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-virtualization List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N --=-qtWotbAPq1B06jIHvtVE Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, this is a request for some guidance on how to remove the fwctl device of bhyve. I've recently added support for qemu's fwcfg device as replacement for bhyve's fwctl device. As both devices are using the same io ports they can't coexist. For that reason, I'd like to remove the fwctl device from bhyve. However, this breaks old guest firmware because it doesn't support qemu's fwcfg. Old guest firmware won't be able to detect the number of vcpus. So, it'll report only a single vcpu to the guest OS. More recent guest firmware doesn't have this issue. Any advice would be appreciated. --=20 Kind regards, Corvin --=-qtWotbAPq1B06jIHvtVE Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgvRSla3m2t/H2U9G2FTaVjFeAmoFAmSIQmsACgkQ2FTaVjFe AmpFOw/9GHP+RSHmbsaJE4jjxuJFgshfqClY8CZdp0EXovFNRpH7vcAasqO5Srf3 fBcf0snRCV3YVfJr8GDC6T68qxSIa2kdKSfFfZSj4tjkFXzWaZJNlXz8f8fcmsxG dwK+FGpdAhSRNNpDrhMUf6RhHJ0SGV3S/61WPHZV4rUDGXbYhvv5J4X0rC706iiO v2rTQJfVwH6U8xernwVf09ac86GGm9M8u8VvHR10tLmI6dXOIc8l9PFmVW2/4SZU 614de2aiofT1arKTPUWGBNWiO6mzvmWY6qaHCT4trjaSuWSoVf/iEedliMIHiR+Z pduprqJqjo5gOrMTFEfqpIQH/PgqE4KwqZbQXMYCVKa8fB7AwpMpWdSLYoBSFWvN +qzIeZRhtrtAHWc7oiuHKURnV0VpF6Yf6y1WEmVixnfZeyDCGKB6tOlD9Q7taxhK XN1sMj4qcp+hs9WQuf6er2G4G2qDksNYysYdlpDtPy0aLnX21aST6wOoLW1XqfvL yTlA7tQQOBeyrzGMABAXVM/VFQgPyTJd1UsQZtSIegk/K3C0gbiipcX22ahseSnn xnLhsVtO4F34hhr4Th9m4L2HGn0Rw6JIzueYl2xmvgj9wOPFGUonEm62/TdOmftQ 3NBkTP9QLjWDUqbTfgUnFFyw8UEU1rfNk0wR8jNElL5GmZuPMBw= =1Oxa -----END PGP SIGNATURE----- --=-qtWotbAPq1B06jIHvtVE--