Date: Mon, 02 Nov 2020 06:25:40 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 250580] VMware UEFI guests crash in virtual hardware after r366691 Message-ID: <bug-250580-227-Qvb5YvRAam@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-250580-227@https.bugs.freebsd.org/bugzilla/> References: <bug-250580-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D250580 hehongbo@mail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hehongbo@mail.com --- Comment #5 from hehongbo@mail.com --- Yes, this bug is not AMD-specific. I'm running FreeBSD 12.1 on an ESXi Serv= er with an Intel Xeon E3-1230v3 CPU and after upgrading to 12.2 it failed to b= oot. Also, another virtual machine which is a FreeNAS 11.3 also breaks after upgrading to TrueNAS 12, which under the hood is also FreeBSD 12.2. Recently I found I can boot these 2 virtual machines by entering the EFI sh= ell of VMware UEFI firmware before booting FreeBSD, just: i. Power ON the VM and immediately press the ESC button. ii. On the boot menu screen of VMware VM's firmware, press the arrow key to select "EFI Internal Shell (Unsupported option)" and press enter to confirm. iii. After seeing "Press ESC in 5 seconds to skip startup.nsh, any other ke= y to continue." press a key other than ESC or just wait for the countdown. iv. Continue to boot FreeBSD as normal. May this detail helps to investigate the issue. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-250580-227-Qvb5YvRAam>