On Wed, Feb 13, 2019 at 09:01:27AM +0100, Ard Biesheuvel wrote: >On Wed, 13 Feb 2019 at 08:59, Chao Fan <fanc.f...@cn.fujitsu.com> wrote: >> >> On Wed, Feb 13, 2019 at 08:36:12AM +0100, Boris Petkov wrote: >> >On February 13, 2019 2:54:29 AM GMT+01:00, Chao Fan >> ><fanc.f...@cn.fujitsu.com> wrote: >> >>Yes, your PATCH really works well. I tried both efi32 OVMF and efi64 >> >>OVMF, all boot. >> > >> >What about the real hardware you are normally testing on? Boots there too? >> >> I testet it in a real EFI machine, it booted, but from command: >> > cat /sys/firmware/efi/fw_platform_size >> 64 >> >> We can see it's a 64-bit EFI firmware, and there is no 32-bit EFI firmware >> available. >> > >Did you try booting 32-bit OVMF from 64-bit QEMU?
Yes, I tried the 32-bit OVMF and rootfs from Guenter. Used as suggested by Boris: qemu-system-x86_64 -kernel /home/cfan/code/tip/arch/x86/boot/bzImage -M q35 -cpu SandyBridge \ -no-reboot -snapshot -smp 1 \ -bios OVMF-pure-efi-32.fd \ -net nic,model=rtl8139,macaddr=12:34:56:78:12:34 \ -usb -device usb-storage,drive=d0 \ -m 1G \ -drive file=rootfs.squashfs,if=none,id=d0,format=raw \ --append 'earlycon=uart8250,io,0x3f8,9600n8 root=/dev/sda rootwait panic=-1 earlyprintk=ttyS0,115200,keep console=ttyS0,115200' \ -monitor pty \ -serial stdio Since I used to watch the log, so I just change the "serial file:log" to "serial stdio". Thanks, Chao Fan > >
