Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 14 Mar 2021 15:42:39 +0100
From:      Ruben van Staveren <ruben@verweg.com>
To:        FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Subject:   Re: FreeBSD 13.0 RC1 UEFI RAID-10 boot problems under VMware Fusion
Message-ID:  <F43DCA46-5CE7-40F4-B19D-C29AB4C75705@verweg.com>
In-Reply-To: <B492E2EA-2F7C-4DAA-986C-7CCC53FB44CA@verweg.com>
References:  <58352200-C53A-4B8F-9498-316FC852BD95@verweg.com> <B492E2EA-2F7C-4DAA-986C-7CCC53FB44CA@verweg.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--Apple-Mail=_B5046A8B-C7BB-4009-BF52-3CF38DE8A16A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I=E2=80=99ve updated the installation to RC2, the behaviour has changed =
in vmware fusion to when I installed one of the  BETA releases.

The initial boot fails, the system will reboot again and then it =
succeeds, though more predictable than with the BETAs

I=E2=80=99m trying to see the differences in screen recording I made, =
and I can only see the =E2=80=9CImage base=E2=80=9D is changed.
Load path, load device, bootcurrent, bootinfo path, currdev (disk0p1, =
EFI)) has not changed.

Either something in the loader(s) was changed, or the RC1 to RC2 update =
placed contents on more =E2=80=9Cfavourable" places on disk that made it =
possible to boot again.

But I do not understand how the loader interacts with the (Vmware) EFI =
firmware to make sense out of it.

> On 10 Mar 2021, at 12:22, Ruben van Staveren <ruben@verweg.com> wrote:
>=20
> To continue on the subject of UEFI booting weirdness
>=20
>> On 9 Mar 2021, at 16:57, Ruben van Staveren <ruben@verweg.com> wrote:
>>=20
>> If I press escape and end up in VMWare=E2=80=99s UEFI setup screen I =
can boot from any ada*p1 drive and continue as normal.
>> Is UEFI with OpenZFS too new, or is this an issue in VMWare?
>=20
> I got an off list tip to see whether this was also the case in bhyve, =
so I also created the setup in there, using UEFI boot, and no problems =
even with the special/log/cache NVMe vdevs attached to the pool.
>=20
> So I=E2=80=99m starting to wonder whether the loader  / VMware UEFI =
firmware (??) interaction is a bug in VMware or an edge case that needs =
to be supported too.
>=20
> Btw, bhyve is looking nice these days!
>=20
> Cheers,
>    Ruben
>=20


--Apple-Mail=_B5046A8B-C7BB-4009-BF52-3CF38DE8A16A
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBAgAdFiEEJ5YXTZtFY5bgSLwXiG9r7NR3qT8FAmBOIOAACgkQiG9r7NR3
qT9YzA/9Fm9eCYKxyvpBPHwlr2aW9r13YZGqx4IJYHB8LBh/5KyzLMaJOOMJqe5y
/yCdjvj4+NjIW0gk5qAidcXsI8d6YuwH1185rErTgJ0evOMqnpyI7ZxEbpi1tV4/
XIZZo1asK+SSlwz/XXQEgj8MXdDOAnvSW4AtFoXeI7glXhfKC5x230Cd3fUTTFwF
sTtQlRbTzo+v0wO67za3RZE3Lp3rBFbnsSbgLlp+eY9880ht3ScvGXYpGqK8naBr
u8tWU9TLcpZGBum0MlmOsvnTl5S2VNvWRAAsEGkJHg11+MKgGPZFb8IydMf8uGQY
PQR60t8mkSJTBOqYO8k1r5ciFNeNfNH+OgPtFy/yvToXOGHAcYAbeWbIc2LJraBa
1YPv08RYh9Ehgr7e+zjpms/DZLpg4LT6PGYvVN5qZEch5sqgXlLLtiRaHsgvWxld
lREY0BxrGqGR55eqn4KkJKCwHUNW3ok9lQoPobpYTb9OpBkiDorT43JMVmdm7vf/
PHAYKyjGS3b2khFsmRdLS4LGmPwF1Oup/rt4sv+SC6VaBlRrYGfiQSVzYUUa6jsm
hkgbIomM5v5mFTG5UdvSD8BN9Ed6iMhSY6352YVEgX+qYaClM0CLkEmz5QqUQ3CN
l0NHr9yb7HJST35C7C5KrxjMRGBfuMtXkD3v+rz9goi6AULMm7s=
=Nv/2
-----END PGP SIGNATURE-----

--Apple-Mail=_B5046A8B-C7BB-4009-BF52-3CF38DE8A16A--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F43DCA46-5CE7-40F4-B19D-C29AB4C75705>