Date: Wed, 28 Oct 2020 01:53:31 +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-cOwfWm5AUD@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 --- Comment #2 from Phillip R. Jaenke <prj@rootwyrm.com> --- (In reply to Warner Losh from comment #1) Unfortunately, this is in a restricted environment, so no luck this time. *Fortunately*, the reproduction is relatively easy. 1) Needs AMD Ryzen, Threadripper, or EPYC in non-EVC with or without SEV 2) Needs vSphere 7.0 build 16324942 or later (7.0b or 7.0U1) - 16321839 and lower will not boot UEFI cleanly.=20 3) Create a guest with the following properties: - Hardware Version 17 (must be 17; 16 and below will not boot UEFI) - Any number of CPUs - At least 1GB of RAM; 512MB didn't behave consistently - Any disk configuration - 1 or more VMXnet3 adapter - Boot Options must be EFI, Secure Boot disabled - Do NOT disable acceleration or enable debug under advanced 4) Install FreeBSD 12.1-RELEASE amd64 from ISO. Don't make any adjustments, just leave everything defaults. open-vm-tools-nox11 is optional but recomme= nded for snapshots. 5) Confirm reboot. Update to 12.1-p10, confirm reboot. SNAPSHOT HERE! 6) Perform `freebsd-update -r 12.2-RELEASE` and reboot 7) Guest will now crash as described including power off behavior. The snapshot in step 5 is critical. If you revert to this snapshot, the gue= st will go right back to working normally. Either a live or powered down snaps= hot, doesn't matter. The base and snapshot are both clone and template safe as w= ell, for spinning up more VMs if needed. I forgot to note, this also reproduced using -CURRENT after the r366422 and r366588 commits. -CURRENT VMs do NOT appear recoverable with live snapshots though. You'll see the behavior through the initial branch of 12.2 until you hit r366691. Every step between 12.2 initial branch up to that commit will work just fine. After that commit, you will receive the EFI frame buffer loading message and then an immediate console disconnect (within probably 500ms. It= 's fast.) The only event you will get is a guest error, "The firmware encountered an unexpected exception. The virtual machine cannot boot. An error message lis= ting a collection of observations has been reported by the virtual machine". Whi= ch indicates that the kernel reported an EFI error upward. --=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-cOwfWm5AUD>