public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: Aaron Young <aaron.young@oracle.com>,
	Anthony Perard <anthony.perard@citrix.com>,
	Ard Biesheuvel <ardb+tianocore@kernel.org>,
	Dann Frazier <dannf@debian.org>, Gary Lin <glin@suse.com>,
	Jordan Justen <jordan.l.justen@intel.com>,
	Julien Grall <julien@xen.org>,
	edk2-devel-groups-io <devel@edk2.groups.io>
Subject: deprecation notice: *dynamic* multi-VMM (QEMU vs. Xen) support in OvmfPkg
Date: Mon, 24 May 2021 10:42:42 +0200	[thread overview]
Message-ID: <acf6161a-44f0-56cb-04de-8a81c1e4d93b@redhat.com> (raw)

Hi,

the "OvmfXen.dsc" platform supports not only HVM guests, but also PVH
guests. This platform does not run on QEMU.

The historical "OvmfPkgIa32.dsc", "OvmfPkgIa32X64.dsc", "OvmfPkgX64.dsc"
platforms support Xen guests, HVM only. They dynamically adapt to QEMU
vs. Xen HVM.

This dynamism has been a *huge* development and maintenance complication
over the years. Another issue (which has been becoming ever more acute)
is the NOOPT binary size, which certainly matters for debugging.

With the introduction of OvmfXen in August 2019
<https://bugzilla.tianocore.org/show_bug.cgi?id=1689>, we formed a plan
to remove the dynamism. Xen guests would only be targeted with the
OvmfXen platform, while the "historical three" would only target QEMU.
See <https://bugzilla.tianocore.org/show_bug.cgi?id=2122>.

The incompatibility is that an existing Xen guest that uses one of the
"OvmfPkgIa32.dsc", "OvmfPkgIa32X64.dsc", "OvmfPkgX64.dsc" firmware
binaries will have to be reconfigured on the host to switch to the
"OvmfXen.dsc" binary, after an edk2 package upgrade brings the above
change to the host.

Anthony originally proposed a 1 year grace period; we're now at 23
months. I've got 20 patches thus far, and those only take us about one
third, or maybe one half, of the way. It's a very intrusive patch
series, not one to revert after it's applied.

My intent / hope is to get this merged into the (presumed)
edk2-stable202108 tag. If you find that too early, please speak up.

If you have another distro with LTS in mind whose package maintainer I
should have put on the address list, please don't hesitate to add them.

Please note that my question is not *if* we should do this, the question
is *when* you can tolerate it, in your respective distros.

Thanks,
Laszlo


             reply	other threads:[~2021-05-24  8:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-24  8:42 Laszlo Ersek [this message]
2021-05-24  8:51 ` [edk2-devel] deprecation notice: *dynamic* multi-VMM (QEMU vs. Xen) support in OvmfPkg Ard Biesheuvel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=acf6161a-44f0-56cb-04de-8a81c1e4d93b@redhat.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox