https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580
ru...@verweg.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ru...@verweg.com
--- Comment #22 from ru...@verweg.com ---
Chiming in on a similar observation (that removing the VM's nvram file
alleviates the issue)
Installed FreeBSD 11.2 with Auto ZFS in vmware fusion 12.1.0 (as RAID1)
Upgraded it to 12.2. gpart bootcode was used to update both boot1.efifat and
gptzfsboot
UEFI boot doesn't work anymore, unless when the system is reset from the boot
loader and choose "boot from file" chosing BOOTx64.efi from either EFI
partition.
Creating it as a boot entry using the VMWare EFI setup screen made no
difference with auto booting, but it would works when dropping again in the
vmware EFI firmware and select one of the entries that where created.
It not, any automated (re)boot lets VMWare stop with "The firmware encountered
an unexpected exception."
Removing the nvram file lets the system boot normally once.
After that it will run into the "The firmware encountered an unexpected
exception" again.
However, replacing BOOTx64.efi with /boot/loader.efi instead of /boot/boot1.efi
lets the system reliably reboot into multi user mode.
keeping BOOTx64.efi as boot1.efi and creating boot entries for
\EFISYS\FreeBSD\loader.efi doesn't work.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
