2017-11-08 23:57 GMT+03:00 Alexander Graf <[email protected]>: > > > On 08.11.17 21:24, Matwey V. Kornilov wrote: >> On 08.11.2017 23:22, Alexander Graf wrote: >>> >>> >>> On 08.11.17 21:17, Matwey V. Kornilov wrote: >>>> On 08.11.2017 23:07, Alexander Graf wrote: >>>>> >>>>> >>>>> On 08.11.17 21:00, Matwey V. Kornilov wrote: >>>>>> Hi, >>>>>> >>>>>> I am trying to run >>>>>> openSUSE-Tumbleweed-ARM-JeOS-efi.armv7l-2017.10.29-Build1.7.raw >>>>>> using qemu. >>>>>> >>>>>> When I use qemu-system-aarch64 with 64-bit UEFI code >>>>>> aavmf-aarch64-code.bin then the only I see is the EFI console: >>>>>> >>>>>> UEFI Interactive Shell v2.287477C2-69C7-11D2-8E39-00A0C969723B B8F1C820 >>>>>> >>>>>> EDK IIlProtocolInterface: 752F3136-4E16-4FDC-A22A-E5F46812F4CA B8F1FF18 >>>>>> >>>>>> UEFI v2.60 (EDK II, 0x00010000)008-7F9B-4F30-87AC-60C9FEF5DA4E B8348710 >>>>>> >>>>>> Mapping table >>>>>> FS0: Alias(s):HD1a0b:;BLK2: >>>>>> >>>>>> VenHw(837DCA9E-E874-4D82-B29A-23FE0E23D1E2,003E000A00000000)/Scsi(0x0,0x0)/HD(1,GPT,E30D92E4-F475-4D50-9D3D-DF05DA812008,0x800,0x64004) >>>>>> BLK5: Alias(s): >>>>>> VenHw(F9B94AE2-8BA6-409B-9D56-B9B417F53CB3) >>>>>> BLK0: Alias(s): >>>>>> VenHw(8047DB4B-7E9C-4C0C-8EBC-DFBBAACACE8F) >>>>>> BLK1: Alias(s): >>>>>> >>>>>> VenHw(837DCA9E-E874-4D82-B29A-23FE0E23D1E2,003E000A00000000)/Scsi(0x0,0x0) >>>>>> BLK3: Alias(s): >>>>>> >>>>>> VenHw(837DCA9E-E874-4D82-B29A-23FE0E23D1E2,003E000A00000000)/Scsi(0x0,0x0)/HD(2,GPT,3DF8DD35-94BC-4FF0-B74C-12853D4B1811,0x65000,0x83004) >>>>>> BLK4: Alias(s): >>>>>> >>>>>> VenHw(837DCA9E-E874-4D82-B29A-23FE0E23D1E2,003E000A00000000)/Scsi(0x0,0x0)/HD(3,GPT,38C4AA8C-4A7F-49C4-BCFD-6C2C755496BD,0xE8800,0x3DE781) >>>>>> >>>>>> Press ESC in 1 seconds to skip startup.nsh or any other key to continue. >>>>>> FSOpen: Open '\startup.nsh' Success >>>>>> FSOpen: Open '\startup.nsh' Success >>>>>> FSOpen: Open '\startup.nsh' Success >>>>>> Shell> bootarm >>>>>> FSOpen: Open '\efi\boot\bootarm.EFI' Success >>>>>> FSOpen: Open '\efi\boot\bootarm.EFI' Success >>>>>> FSOpen: Open '\efi\boot\bootarm.EFI' Success >>>>>> FSOpen: Open '\efi\boot\bootarm.EFI' Success >>>>>> [Security] 3rd party image[0] can be loaded after EndOfDxe: >>>>>> VenHw(837DCA9E-E874-4D82-B29A-23FE0E23D1E2,003E000A00000000)/Scsi(0x0,0x0)/HD(1,GPT,E30D92E4-F475-4D50-9D3D-DF05DA812008,0x800,0x64004)/\efi\boot\bootarm.EFI. >>>>>> InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B B8EDE440 >>>>>> Unloading driver at 0x00000000000 >>>>>> Shell> Error Status: Unsupported (line number 1) >>>>>> >>>>>> >>>>>> As far as I understand, 64-bit Qemu UEFI code doesn't expect to see and >>>>>> run 32-bit EFI executable. >>>>> >>>>> Correct, as far as UEFI is concerned, a 32bit ARM binary could as well >>>>> be a MIPS one ;). It's a different, unsupported platform for it. >>>>> >>>>>> When I try to use qemu-uefi-aarch32.bin as firmware, then I see the >>>>>> following: >>>>>> >>>>>> Initialization of device cfi.pflash01 failed: failed to read the initial >>>>>> flash content >>>>>> >>>>>> As far as I understand, qemu-uefi-aarch32.bin is in wrong format, but >>>>>> there are no other files in ovfm rpm package. >>>>> >>>>> Which ovmf package are you looking at? I'm not sure we properly package >>>>> OVMF for AArch32. But you can always try with the Linaro built ones :) >>>>> >>>>> http://snapshots.linaro.org/components/kernel/leg-virt-tianocore-edk2-upstream/latest/QEMU-ARM/RELEASE_GCC5/ >>>> >>>> Well, the last thing I see using linaro's DEBUG build is the following: >>>> >>>> SetUefiImageMemoryAttributes - 0x00000000BBA48000 - 0x0000000000002000 >>>> (0x0000000000004000) >>>> Found Timer interrupts 29, 30, 27, 26 >>>> InstallProtocolInterface: 26BACCB3-6F42-11D4-BCE7-0080C73C8881 BBA48010 >>>> Loading driver E660EA85-058E-4B55-A54B-F02F83A24707 >>>> InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B BAF790A8 >>>> add-symbol-file >>>> /home/buildslave/workspace/leg-virt-tianocore-edk2-upstream/edk2/Build/ArmVirtQemu-ARM/DEBUG_GCC5/ARM/MdeModulePkg/Universal/DisplayEngineDxe/DisplayEngineDxe/DEBUG/DisplayEngine.dll >>>> 0xBBA26000 >>>> Loading driver at 0x000BBA25000 EntryPoint=0x000BBA26031 DisplayEngine.efi >>>> InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF BAF79990 >>>> ProtectUefiImageCommon - 0xBAF790A8 >>>> - 0x00000000BBA25000 - 0x000000000001C000 >>>> SetUefiImageMemoryAttributes - 0x00000000BBA25000 - 0x0000000000001000 >>>> (0x0000000000004000) >>>> SetUefiImageMemoryAttributes - 0x00000000BBA26000 - 0x0000000000017000 >>>> (0x0000000000020000) >>>> SetUefiImageMemoryAttributes - 0x00000000BBA3D000 - 0x0000000000004000 >>>> (0x0000000000004000) >>>> >>>> Then happens nothing but 100% CPU load. >>> >>> The file on the link I provided works just fine for me: >>> >>> $ qemu-system-arm -nographic -M virt -cpu cortex-a15 -bios QEMU_EFI.fd >>> >> >> What is your qemu version? >> Mine is >> >>> qemu-system-arm --version >> QEMU emulator version 2.9.1(openSUSE Leap 42.3) > > $ qemu-system-arm --version > QEMU emulator version 2.10.1(Virtualization / SLE_12) > > > Alex
Thanks, now it almost works. I managed to run with 2.9.1 and Linaro's DEBUG UEFI image. However, I only Grub works well. The kernel seems to be not booted. I set loglevel=8 and console=ttyS0,115200 manually in grub config, but still don't see any info from the kernel. Booting a command list Loading linux.vmx... Loading initrd.vmx... PciBus: Disable Bus Master of all devices... Bus# Device# Function# NewCommand SetUefiImageMemoryAttributes - 0x00000000BBDBE000 - 0x0000000000009000 (0x0000000000000000) SetUefiImageMemoryAttributes - 0x00000000BBDB1000 - 0x000000000000D000 (0x0000000000000000) SetUefiImageMemoryAttributes - 0x00000000BBD36000 - 0x000000000007B000 (0x0000000000000000) SetUefiImageMemoryAttributes - 0x00000000BBD2D000 - 0x0000000000009000 (0x0000000000000000) SetUefiImageMemoryAttributes - 0x00000000BBD23000 - 0x000000000000A000 (0x0000000000000000) SetUefiImageMemoryAttributes - 0x00000000BBD1A000 - 0x0000000000009000 (0x0000000000000000) SetUefiImageMemoryAttributes - 0x00000000BBD11000 - 0x0000000000009000 (0x0000000000000000) -- With best regards, Matwey V. Kornilov -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
