On Mon, 2 Dec 2024, Mario Marietto wrote:
Hello to everyone.
Recently I've upgraded one of my FreeBSD systems and I see a strange
error when I try to boot Android 7.1.1. I have never seen this error
before and I also have another system where I haven't applied the
latest pkg upgrades where Android is still able to boot.
The bhyve parameters that I use in both systems are the following:
/usr/sbin/./bhyve -S -c sockets=2,cores=2,threads=2 -m 8G -w -H -A \
-s 0,hostbridge \
-s
1,ahci-hd,/mnt/zroot-133/bhyve/img/Android/DarkMatter-qemu.img,bootindex=1 \
-s 8:0,passthru,4/0/0 \
-s 11,hda,play=/dev/dsp,rec=/dev/dsp \
-s 13,virtio-net,tap13 \
-s 29,fbuf,tcp=0.0.0.0:5913,w=1440,h=900,wait \
-s 30,xhci,tablet \
-s 31,lpc \
-l
bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI_CODE.fd,/usr/local/share/uefi-firmware/BHYVE_UEFI_VARS.fd
\
vm0:13 < /dev/null & sleep 5 && vncviewer 0:13 && echo vncviewer 0:13 &
Do you actually want the UEFI variables to be written to
/usr/local/share/uefi-firmware/BHYVE_UEFI_VARS.fd? That file is
actually installed by edk2-bhyve. You should pick a different location
for the variables file to be written. Plus, reinstall edk2-bhyve to
make sure nothing unexpected happens, especially if you have had
multiple bhyve instances using that same file. Probably, save it just
in case there are any values you need to keep first.
$ pkg which /usr/local/share/uefi-firmware/BHYVE_UEFI_VARS.fd
/usr/local/share/uefi-firmware/BHYVE_UEFI_VARS.fd was installed by package
edk2-bhyve-g202308_5
$ ls -l /usr/local/share/uefi-firmware/BHYVE_UEFI_VARS.fd
lrwxr-xr-x 1 root wheel 32 Nov 29 03:28
/usr/local/share/uefi-firmware/BHYVE_UEFI_VARS.fd@ ->
../edk2-bhyve/BHYVE_UEFI_VARS.fd
$ pkg which /usr/local/share/edk2-bhyve/BHYVE_UEFI_VARS.fd
/usr/local/share/edk2-bhyve/BHYVE_UEFI_VARS.fd was installed by package
edk2-bhyve-g202308_5
$ pkg check -s edk2-bhyve-g202308_5
Checking edk2-bhyve-g202308_5: 100%
I would run that check to make sure it is still valid.
When I first ran into the error, I just replaced the UEFI vars file with
an old one from a ZFS snapshot to see what was happening, which worked
until the next time I rebooted the VM.
Sean
--
s...@freebsd.org
