On Sat, Jan 7, 2017, at 03:48 PM, Mike Latimer wrote:
42.1 or 42.2?
42.2
Do you remember accepting the certificate on this guest prior to the update to 4.8?
no, never.
Were you able to say 'Yes' to that prompt during the startup under 4.8?
Yes, I am *able* to select 'Yes'. Unfortunately, it simply then pops up the 'Error' screen, as above.
Are you continuing to see the following errors during every (failed) boot?
Yes
I'll reach out to a bootloader guy to see if we can figure out what those are related to.
I have a strong, sneaking suspicion that it's OVMF The fact that I can chroot, re-grub, then reboot -- and *see* that 'new' NvVars file suggests, to me anyway, that "a BIOS" is touching that Guest. And there's the staring-me-in-the-face message it hangs at in the serial console (d2) [2017-01-07 21:55:36] Invoking OVMF ... Obviously that^ has to be OVMF. I don't know why the strings in the NvVars file are all Microsoft-laden. The only thing I can imaging is that it's the SecureBoot stuff. I've tried echo "fs0:\EFI\opensuse\shim.efi" > /boot/efi/startup.nsh instead of echo "fs0:\EFI\opensuse\grubx64.efi" > /boot/efi/startup.nsh but that doesn't seem to have any effect.
You've gathered some great information on the problem so far. Can you enter this into an official bug on this at bugzilla.opensuse.org?
https://bugzilla.opensuse.org/show_bug.cgi?id=1018741 -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org