From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 1B8311A1DED for ; Thu, 6 Oct 2016 00:47:33 -0700 (PDT) Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 9AC5A624A2; Thu, 6 Oct 2016 07:47:32 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-116-80.phx2.redhat.com [10.3.116.80]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u967lUwQ005139; Thu, 6 Oct 2016 03:47:31 -0400 To: spam collector References: <1825038664.87486514.1475464584880.JavaMail.zimbra@cableone.net> <9f2b0b8c-9bfb-dd73-f7cb-cd6df775c237@redhat.com> <812341546.91963700.1475549145141.JavaMail.zimbra@cableone.net> <5c54ce38-9f0c-ac8d-c926-570ebc3dd720@redhat.com> <1747186652.93714260.1475599157436.JavaMail.zimbra@cableone.net> <94a76bd7-732c-c8f6-b8be-8175dd061b86@redhat.com> <1410853764.96270806.1475635626572.JavaMail.zimbra@cableone.net> <280e3403-1821-396e-5243-54b770dcb01a@redhat.com> <360734730.99846163.1475732718290.JavaMail.zimbra@cableone.net> Cc: edk2-devel@ml01.01.org From: Laszlo Ersek Message-ID: Date: Thu, 6 Oct 2016 09:47:30 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <360734730.99846163.1475732718290.JavaMail.zimbra@cableone.net> X-Scanned-By: MIMEDefang 2.68 on 10.5.11.27 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.39]); Thu, 06 Oct 2016 07:47:32 +0000 (UTC) Subject: Re: OVMF.fd and placement of EfiBootServicesData X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Oct 2016 07:47:33 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit On 10/06/16 07:45, spam collector wrote: > ----- Original Message ----- >> From: "Laszlo Ersek" >> To: "spam collector" >> Cc: edk2-devel@ml01.01.org >> Sent: Wednesday, October 5, 2016 8:28:46 AM >> Subject: Re: [edk2] OVMF.fd and placement of EfiBootServicesData >> >> I recommend trying the following (32-bit command line), with Gerd's package: >> >> FW_BIN=/usr/share/edk2.git/ovmf-ia32/OVMF_CODE-pure-efi.fd >> VARS_TMPL=/usr/share/edk2.git/ovmf-ia32/OVMF_VARS-pure-efi.fd >> VARS=myvars.fd >> SHELL_ISO=/usr/share/edk2.git/ovmf-ia32/UefiShell.iso >> if ! [ -e "$VARS" ]; then >> cp -v -- "$VARS_TMPL" "$VARS" >> fi >> >> qemu-system-i386 \ >> -m 2048 \ >> -machine accel=kvm \ >> \ >> -drive if=pflash,format=raw,unit=0,readonly,file="$FW_BIN" \ >> -drive if=pflash,format=raw,unit=1,file="$VARS" \ >> \ >> -device virtio-scsi-pci,id=scsi0 \ >> -drive if=none,format=raw,readonly,file="$SHELL_ISO",id=shell \ >> -device scsi-cd,bus=scsi0.0,drive=shell,bootindex=1 \ >> \ >> -chardev file,id=debugfile,path=ovmf.log \ >> -device isa-debugcon,iobase=0x402,chardev=debugfile >> >> This will boot the shell for you, and even save the OVMF debug log in >> the file "ovmf.log". > > I used the following command line (again, a WinXP DOS Session .BAT file): > > "..\qemu-system-i386w.exe" -m 256 -drive if=pflash,format=raw,unit=0,readonly,file=..\OVMF_CODE.fd -drive > if=pflash,format=raw,unit=1,file=..\OVMF_VARS.fd -device virtio-scsi-pci,id=scsi0 -drive > if=none,format=raw,readonly,file=..\UefiShell.iso,id=shell -device scsi-cd,bus=scsi0.0,drive=shell,bootindex=1 > -chardev file,id=debugfile,path=ovmf.log -device isa-debugcon,iobase=0x402,chardev=debugfile -drive > file=uefi.bin.vhd,format=raw,if=ide,media=disk,index=0 > > The shell booted up as expected. However, my BOOT.efi file is now a: > > "image is not an application" > > I don't think I mentioned before, my BOOT.efi is an OS loader, not > a UEFI driver or other type application. (A UEFI_DRIVER module is *not* an application.) > Sorry, I should have mentioned > that earlier, hope that did not confuse you. > > My BOOT.efi file has a value of 0x0B as the Subsystem value. > > PE Optional Header: Subsystem: 0x000B > > I removed the UefiShell.iso part: > > "..\qemu-system-i386w.exe" -m 256 -drive if=pflash,format=raw,unit=0,readonly,file=..\OVMF_CODE.fd -drive > if=pflash,format=raw,unit=1,file=..\OVMF_VARS.fd -device virtio-scsi-pci,id=scsi0 -chardev > file,id=debugfile,path=ovmf.log -device isa-debugcon,iobase=0x402,chardev=debugfile -drive > file=uefi.bin.vhd,format=raw,if=ide,media=disk,index=0 > > and the shell was loaded, with the same result, "not an application". Based on "MdePkg/Include/IndustryStandard/PeImage.h": - Subsystem type 0xb (11 decimal) seems to correspond to EFI_IMAGE_SUBSYSTEM_EFI_BOOT_SERVICE_DRIVER. If your module is an application however (and a boot loader is usually an application), it should have EFI_IMAGE_SUBSYSTEM_EFI_APPLICATION (= 0xa, 10 decimal). - You might want to double-check if the bitnesses match (you can't launch an IMAGE_FILE_MACHINE_I386 (0x014c) image on the X64 and Ia32X64 builds of OVMF, nor an IMAGE_FILE_MACHINE_X64 (0x8664) image on the Ia32 build). Laszlo