With bug 1689 ("New OvmfXen platform with Xen PVH support") fixed, the current hypervisor support status is: - OvmfXen: - runs in Xen HVM guests - runs in Xen PVH guests - traditional OVMF - runs in Xen HVM guests - runs in QEMU/KVM guests The desired (and agreed upon) end-status is the following: - OvmfXen: - runs in Xen HVM guests - runs in Xen PVH guests - traditional OVMF - runs in QEMU/KVM guests Linked from bug 1689 comment 6, in message [1] (alternative link: [2]), Anthony wrote, > After this patch series, I'd like to wait a bit before removing Xen > support from the OvmfPkg*.dsc, to allow time to switch to the new Xen > only platform, maybe 1 year. [1] http://mid.mail-archive.com/20190813113119.14804-1-anthony.perard@citrix.com [2] https://edk2.groups.io/g/devel/message/45526
Confirming, based on earlier mailing list discussions, especially: http://mid.mail-archive.com/155492143006.23894.8253130602441997952@jljusten-skl https://edk2.groups.io/g/devel/message/38833
* [edk2-devel] deprecation notice: *dynamic* multi-VMM (QEMU vs. Xen) support in OvmfPkg msgid: <acf6161a-44f0-56cb-04de-8a81c1e4d93b@redhat.com> https://edk2.groups.io/g/devel/message/75498 https://listman.redhat.com/archives/edk2-devel-archive/2021-May/msg00814.html
* [edk2-devel] [PATCH 00/43] OvmfPkg: remove Xen support from OvmfPkg*.dsc, in favor of OvmfXen.dsc Message-Id: <20210526201446.12554-1-lersek@redhat.com> https://edk2.groups.io/g/devel/message/75669 https://listman.redhat.com/archives/edk2-devel-archive/2021-May/msg00962.html
Merged as commit range 924c2b847f0b..51adb689e1db, via <https://github.com/tianocore/edk2/pull/1689>.