Date: Wed, 4 Dec 2024 10:02:44 +0100 From: Mario Marietto <marietto2008@gmail.com> To: "Sean C. Farley" <scf@freebsd.org> Cc: FreeBSD virtualization <freebsd-virtualization@freebsd.org> Subject: Re: Failed to emulate instruction sequence [ 41f646040874064c017d88eb144c89 ] at 0xbea5fcf9 Message-ID: <CA%2B1FSigSwUmM-W4TxrCmvXChxE0STBb_Ap4Omy7%2BjTmU58Qt%2Bw@mail.gmail.com> In-Reply-To: <7905a2e7-3107-bf4d-10f7-2547a2af8df3@FreeBSD.org> References: <CA%2B1FSijzwf6xHOv7-CfmdFPmxD46vFEdaJ4V6xy29G4BYEetWA@mail.gmail.com> <7905a2e7-3107-bf4d-10f7-2547a2af8df3@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] The first thing I did has been to exchange all the BHYVE_UEFI* files between the working system and the not working system. Unfortunately the error is not gone. On Wed, Dec 4, 2024 at 6:16 AM Sean C. Farley <scf@freebsd.org> wrote: > 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 > -- > scf@FreeBSD.org > -- Mario. [-- Attachment #2 --] <div dir="ltr">The first thing I did has been to exchange all the BHYVE_UEFI* files between the working system and the not working system. Unfortunately the error is not gone. <br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Dec 4, 2024 at 6:16 AM Sean C. Farley <<a href="mailto:scf@freebsd.org" target="_blank">scf@freebsd.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Mon, 2 Dec 2024, Mario Marietto wrote:<br> <br> > Hello to everyone.<br> ><br> > Recently I've upgraded one of my FreeBSD systems and I see a strange <br> > error when I try to boot Android 7.1.1. I have never seen this error <br> > before and I also have another system where I haven't applied the <br> > latest pkg upgrades where Android is still able to boot.<br> > The bhyve parameters that I use in both systems are the following:<br> ><br> > /usr/sbin/./bhyve -S -c sockets=2,cores=2,threads=2 -m 8G -w -H -A \<br> > -s 0,hostbridge \<br> > -s<br> > 1,ahci-hd,/mnt/zroot-133/bhyve/img/Android/DarkMatter-qemu.img,bootindex=1 \<br> > -s 8:0,passthru,4/0/0 \<br> > -s 11,hda,play=/dev/dsp,rec=/dev/dsp \<br> > -s 13,virtio-net,tap13 \<br> > -s 29,fbuf,tcp=<a href="http://0.0.0.0:5913" rel="noreferrer" target="_blank">0.0.0.0:5913</a>,w=1440,h=900,wait \<br> > -s 30,xhci,tablet \<br> > -s 31,lpc \<br> > -l<br> > bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI_CODE.fd,/usr/local/share/uefi-firmware/BHYVE_UEFI_VARS.fd<br> > \<br> > vm0:13 < /dev/null & sleep 5 && vncviewer 0:13 && echo vncviewer 0:13 &<br> <br> Do you actually want the UEFI variables to be written to <br> /usr/local/share/uefi-firmware/BHYVE_UEFI_VARS.fd? That file is <br> actually installed by edk2-bhyve. You should pick a different location <br> for the variables file to be written. Plus, reinstall edk2-bhyve to <br> make sure nothing unexpected happens, especially if you have had <br> multiple bhyve instances using that same file. Probably, save it just <br> in case there are any values you need to keep first.<br> <br> $ pkg which /usr/local/share/uefi-firmware/BHYVE_UEFI_VARS.fd<br> /usr/local/share/uefi-firmware/BHYVE_UEFI_VARS.fd was installed by package edk2-bhyve-g202308_5<br> $ ls -l /usr/local/share/uefi-firmware/BHYVE_UEFI_VARS.fd<br> 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<br> $ pkg which /usr/local/share/edk2-bhyve/BHYVE_UEFI_VARS.fd<br> /usr/local/share/edk2-bhyve/BHYVE_UEFI_VARS.fd was installed by package edk2-bhyve-g202308_5<br> $ pkg check -s edk2-bhyve-g202308_5<br> Checking edk2-bhyve-g202308_5: 100%<br> <br> I would run that check to make sure it is still valid.<br> <br> When I first ran into the error, I just replaced the UEFI vars file with <br> an old one from a ZFS snapshot to see what was happening, which worked <br> until the next time I rebooted the VM.<br> <br> Sean<br> -- <br> scf@FreeBSD.org<br> </blockquote></div><div><br clear="all"></div><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature">Mario.<br></div>help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2B1FSigSwUmM-W4TxrCmvXChxE0STBb_Ap4Omy7%2BjTmU58Qt%2Bw>