On Wed, 22 May 2019 at 15:22, Laszlo Ersek <ler...@redhat.com> wrote: > This is very interesting. I had obviously tested booting > "bios-tables-test.aarch64.iso.qcow2" against "edk2-aarch64-code.fd", > using TCG, on my x86_64 laptop. (And, I've run the above exact command > just now, at commit a4f667b67149 -- it works 100% fine.) > > However, I've never been *near* a 32-bit ARM host. Therefore my > suspicion is that the AARCH64 UEFI guest code tickles something in the > 32-bit ARM code generator. It could be a bug in 32-bit ARM TCG, or it > could be a bug in edk2 that is exposed by 32-bit ARM TCG.
Does it repro in a 32-bit-chroot in an aarch64 host ? I don't know if that might be easier for you to set up than getting access to real 32-bit hardware. thanks -- PMM
