Hi again, now all puzzle pieces fit together - thank you, no further questions needed.
This is not a bug as in "this has broken" it is a "feature request" in regard to qemu and edk2 at the versions they've been available at the time of Ubuntu Noble. Yet, despite being a feature request it is still something that is generally useful/demanded. I've done other small fixes where possible towards that and I know some Ubuntu folks work on SNP support in general. Clearly on new the releases all has come together - EDK2 is good since Oracular (as you confirmed) - QEMU has it since 9.1 (see https://wiki.qemu.org/ChangeLog/9.1) and Plucky comes very soon with QEMU 9.2 We can't just upgrade EDK2 for the associated regression risk, but I'd right now not spend the effort to isolate the fix either as with the qemu in Noble it won't work. But that does not mean no, it means this has different timelines: Time: Immediately For cases like yours where you already build qemu yourself I'd suggest using the unofficial, but often very helpful gap closer PPA with server backports [1]. That currently has what is in 25.04 (and therefore the OVMF you want) and will soon get what is then released in 25.10 (including qemu and an even newer edk2). This is not a one-shot, but rebuilt automatically when the source release gets an update. Timeline: short term If someone can isolate the change to EDK2 that makes this work, that change is rather uncontroversial and one can make a case why this helps at all if people using it need to build their own qemu already - then this might be an SRU. But right now I do not see that fit nicely given the alternatives. Time: mid-term 25.04 Plucky is soon released and has all you need. Time: mid-term but on LTS I know people are working on what can be done for SNP in Noble, including all components (more invasive on qemu than on edk2 I assume) needed. If that ends up as something that can pass the "do not regress existing users" SRU rules has to be seen. But they will find a way eventually. Time: long-term LTS Well, the next 26.04 is not too far away, if the backporting is not working out or ends up with a solution you do not want to use (e.g. because it might need opt-in to not regress other users) then that isn't too far off either. [1]: https://launchpad.net/~canonical-server/+archive/ubuntu/server- backports?field.series_filter=noble ** Changed in: edk2 (Ubuntu) Status: Triaged => Fix Released ** Also affects: edk2 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: edk2 (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: edk2 (Ubuntu Plucky) Importance: Undecided Status: Fix Released ** Changed in: edk2 (Ubuntu Oracular) Status: New => Fix Committed ** Changed in: edk2 (Ubuntu Oracular) Status: Fix Committed => Fix Released ** Changed in: edk2 (Ubuntu Noble) Status: New => Triaged ** Changed in: edk2 (Ubuntu Noble) Importance: Undecided => Wishlist ** Tags removed: server-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2104069 Title: OVMF.fd file doesn't support SNP QEMU Guest Launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/2104069/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
