Date: Wed, 18 Sep 2019 18:30:50 +0300 From: Toomas Soome <tsoome@me.com> To: freebsd-current <freebsd-current@freebsd.org> Subject: Re: ESXi VM does not boot in UEFI mode from 20190906 snapshot ISO Message-ID: <3978E5B5-CAB1-4214-AF9B-757BE1BEA923@me.com> In-Reply-To: <dffffb7e-1ec8-59ca-e312-47551ab23e94@yuripv.net> References: <dffffb7e-1ec8-59ca-e312-47551ab23e94@yuripv.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 18 Sep 2019, at 18:01, Yuri Pankov <yuripv@yuripv.net> wrote: >=20 > I have tested several snapshot ISOs available for download: >=20 > FreeBSD-13.0-CURRENT-amd64-20190822-r351363-disc1.iso - OK > FreeBSD-13.0-CURRENT-amd64-20190829-r351591-disc1.iso - OK > FreeBSD-13.0-CURRENT-amd64-20190906-r351901-disc1.iso - FAIL > FreeBSD-13.0-CURRENT-amd64-20190913-r352265-disc1.iso - FAIL >=20 > FAIL being VM shutdown after loading kernel/modules and displaying = "EFI framebuffer information". Relevant messages in the VM log are = rather unhelpful: >=20 > 2019-09-18T14:47:12.397Z| vcpu-0| I125: Guest: Firmware has = transitioned to runtime. > 2019-09-18T14:47:12.434Z| vcpu-0| I125: Msg_Post: Error > 2019-09-18T14:47:12.434Z| vcpu-0| I125: [msg.efi.exception] The = firmware encountered an unexpected exception. The virtual machine cannot = boot. >=20 > Any hints on debugging this further? Im not really sure about debugging; I can not tell about early kernel, = but I=E2=80=99d check if the kernel/module locations conflict with efi = memory map items=E2=80=A6=20 The same issue can be seen with vmware fusion, it is not 100% repeatable = but I=E2=80=99d say, 95%, starting grab_faults, perhaps ls or some other = random command, and boot -v may actually start the system up.=20 rgds, toomas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3978E5B5-CAB1-4214-AF9B-757BE1BEA923>