Date: Thu, 02 Jun 2022 22:19:06 +0000 From: bugzilla-noreply@freebsd.org To: uboot@FreeBSD.org Subject: [Bug 264338] sysutils/edk2: vm_run error -1, errno 14 Message-ID: <bug-264338-39090-NKDbDru0Nl@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-264338-39090@https.bugs.freebsd.org/bugzilla/> References: <bug-264338-39090@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=3D264338 --- Comment #12 from Dries Michiels <driesm@freebsd.org> --- if use BHYVE_UEFI_CODE.fd vm start success =3D> Indeed! It seems that vm-bhyve script only uses this when setting loader=3D"uefi-de= vel" but than it also appends -devel to the firmware name so it wont work out of= the box. Right now I'm using "loader"=3D"uefi-custom", and created a symlink in vmdir/.config/ as such "BHYVE_UEFI.fd -> /usr/local/share/edk2-bhyve/BHYVE_UEFI_CODE.fd". This makes me wonder, maybe the edk2 port has caught up to the "devel versi= on intended in vm-bhyve script" back in the time, so now we should actually use BHYVE_UEFI_CODE.fd. https://github.com/churchers/vm-bhyve/blob/ec0e12e97465822d65ab32e791049d69= 791d49cb/lib/vm-run#L277 I have been thinking for a while to create a vm-bhyve-devel port, to actual= ly tracks commits of vm-bhyve upstream. Unfortunately the owner of the repo ha= sn't been so good in creating releases. --=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-264338-39090-NKDbDru0Nl>