Date: Mon, 23 Nov 2020 06:53:10 +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-TSjBgs96dc@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 #13 from Christian Ullrich <chris@chrullrich.net> --- I cannot reproduce the SCSI/NVMe behavior in 16.1; it fails with either configuration. Which type of SCSI controller did you use? However, I noticed something else potentially interesting. It has been mentioned elsewhere (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D244906#c8) that bootin= g from the ISO works, but then the reboot into the installed system fails. What I have not seen described yet is that rebooting into the ISO _also_ fa= ils, even on a VM that does not include any hard disk at all. Steps to reproduce: 1. Create VM. 2. Remove hard disk from VM. 3. Boot into 12.2-RELEASE disc1 ISO. 4. Select "Shell" at the first prompt. 5. # reboot The VM fails with the same firmware error message upon reboot. 6. Delete the VM's .nvram file. 7. Power on VM. The VM successfully boots into the installer image. I previously assumed there was a difference between the loader in the ISO a= nd what ends up on the virtual disk, but instead, the problem seems to persist= in EFI variables or something else in the NVRAM. --=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-TSjBgs96dc>