@xypron Thanks for looking into this! The relationship from the .json file to the .fd file that I can select in the virtual-manager interface are not completely clear to me, but I believe you are right and the "50-edk2-x86_64-secure.json" file matched my use case. I had it expected to force me to enroll this keys, but It should show me the keys present on the distro image, something like that. But I see no keys, on none of the 3 distros.
For the "40-edk2-x86_64-secure-enrolled.json case: Hm..I guess it matches "OVMF_CODE.4M.ms.fd" ? May be? I try it! Anyway- would that not be the Microsoft-Shim case ? Bazzite did work with that, that's prooven to work- the problem are custom certificates not published by microsoft. Anyway- with "OVMF_CODE.4M.ms.fd" it doesn't work either- after the install, some error on the MOK registration turns up, then full stop- It seems not to call the MOK enrollment as it should- may be this was not the right file or Mint doesn't want to enroll with Microsoft certificates. ** Attachment added: "mint-secureboot4.xml" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2113456/+attachment/6011899/+files/mint-secureboot4.xml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2113456 Title: libvirt fails to define UEFI KVM VMs with firmware compatibility error on Ubuntu 24.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2113456/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
