On 10/09/2018 11:27 AM, Bin Meng wrote: > Hi Heinrich, > > Did you ever get 'bootefi selftest' pass on qemu-x86_64? I got: > > => bootefi selftest > WARNING: booting without device tree > lib/efi_selftest/efi_selftest.c(242): > ERROR: Cannot open loaded image protocol > > Regards, > Bin > Hello Bin,
when running qemu-x86_64_defconfig with qemu-system-x86_64 -bios denx/u-boot.rom -machine pc-i440fx-2.5 --nographic it hangs in an endless loop: U-Boot 2018.11-rc1-00130-g0a60a81ba3 (Oct 09 2018 - 18:23:16 +0200) QEMU Virtual CPU version 2.5+DRAM: 128 MiB U-Boot SPL 2018.11-rc1-00130-g0a60a81ba3 (Oct 09 2018 - 18:23:16 +0200) CPU: x86_64, vendor AMD, device 663h Trying to boot from SPI Jumping to 64-bit U-Boot: Note many features are missing U-Boot 2018.11-rc1-00130-g0a60a81ba3 (Oct 09 2018 - 18:23:16 +0200) QEMU Virtual CPU version 2.5+DRAM: 128 MiB U-Boot SPL 2018.11-rc1-00130-g0a60a81ba3 (Oct 09 2018 - 18:23:16 +0200) CPU: x86_64, vendor AMD, device 663h Trying to boot from SPI Jumping to 64-bit U-Boot: Note many features are missing U-Boot 2018.11-rc1-00130-g0a60a81ba3 (Oct 09 2018 - 18:23:16 +0200) QEMU Virtual CPU version 2.5+DRAM: 128 MiB .... How did you succeed to reach the console? There is a doc/README.x86 but nothing on x86_64. Could you, please, add the missing information in said README.x86. I could not find qemu-x86_64_defconfig in .travis.yml. Shouldn't we try to run the target there too? I am using Debian Buster: gcc 8.2.0 qemu 2.12.0 Best regards Heinrich _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
