Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 14 Jun 2024 06:39:14 +0000
From:      bugzilla-noreply@freebsd.org
To:        virtualization@FreeBSD.org
Subject:   [Bug 279720] virtualization/bhyve: it does not boot from the slot where the parameter bootindex=1 is declared.
Message-ID:  <bug-279720-27103-ks4gSAvjkr@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-279720-27103@https.bugs.freebsd.org/bugzilla/>
References:  <bug-279720-27103@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=3D279720

Corvin K=C3=B6hne <corvink@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |corvink@FreeBSD.org

--- Comment #1 from Corvin K=C3=B6hne <corvink@FreeBSD.org> ---
>From https://man.freebsd.org/cgi/man.cgi?bhyve:

                   bootindex=3Dindex
                               Add  the  device  to the bootorder at index.=
  A
                               fwcfg file is used to  specify  the  bootord=
er.
                               The  guest  firmware may ignore or doesn't s=
up-
                               port this fwcfg file.  In that case, this  f=
ea-
                               ture doesn't work as expected.

EDK2 for bhyve currently doesn't support the bootorder fwcfg file. Therefor=
e,
it's ignored and uses it's default bootorder.

I'm going to send a patch to upstream EDK2.

--=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-279720-27103-ks4gSAvjkr>