HELP: Qemu not able to load Duet image

HELP: Qemu not able to load Duet image

[david moheban]

Just wanted to followup on my experimentation with Qemu and EDK2's DuetPkg.
So far I have successfully been able to load the Duet image in Qemu after
refining my image making skills. Though having an issue with UDK2010 NOT
being able to load the 'Bootx64' or 'BootIa32' efi boot loader. I also
compiled 2010-SR1 and this problem is not present and works with 2010-SR1.
Using DDK3790 and VS2010 to compile both packages in DEBUG mode. Should
also mention was able to load the EDK-2010 standard Duet Image inside
Virtualbox as well HOWEVER need to turn on 'EFI' mode inside Virtualbox
settings for the bootx64 or bootia32 efi loader to load!

You might ask why using such an old version of EDK? Well I have noticed
that UDK-2010 compiles with the smallest file size and I am planing to
insert the final image into my firmware with limited space so every KB
counts!

So if anyone can offer some advice I would very much appreciate it..




Thank you.

David.

Re: HELP: Qemu not able to load Duet image

[Richardson, Brian]

David:

DUET has a number of legacy dependencies, since it's designed to boot a UEFI environment over 16-bit BIOS. We don't recommend DUET for current development, since it's not actively under test. https://github.com/tianocore/tianocore.github.io/wiki/DuetPkg  

Is there some reason you're using DUET rather than building a native UEFI image for QEMU using the EDK II OvmfPkg? https://github.com/tianocore/tianocore.github.io/wiki/OVMF 

Thanks ... br
---
Brian Richardson, Senior Technical Marketing Engineer, Intel Software
brian.richardson@intel.com -- @intel_brian (Twitter & WeChat)
https://software.intel.com/en-us/meet-the-developers/evangelists/team/brian-richardson 

-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of david moheban
Sent: Sunday, March 11, 2018 11:22 AM
To: edk2-devel@lists.01.org
Subject: [edk2] HELP: Qemu not able to load Duet image

Just wanted to followup on my experimentation with Qemu and EDK2's DuetPkg.
So far I have successfully been able to load the Duet image in Qemu after refining my image making skills. Though having an issue with UDK2010 NOT being able to load the 'Bootx64' or 'BootIa32' efi boot loader. I also compiled 2010-SR1 and this problem is not present and works with 2010-SR1.
Using DDK3790 and VS2010 to compile both packages in DEBUG mode. Should also mention was able to load the EDK-2010 standard Duet Image inside Virtualbox as well HOWEVER need to turn on 'EFI' mode inside Virtualbox settings for the bootx64 or bootia32 efi loader to load!

You might ask why using such an old version of EDK? Well I have noticed that UDK-2010 compiles with the smallest file size and I am planing to insert the final image into my firmware with limited space so every KB counts!

So if anyone can offer some advice I would very much appreciate it..




Thank you.

David.
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel

HELP: Qemu not able to load Duet image

[david moheban]

Hi,

I am having difficulty loading Duet image via Qemu x86-64 or Bochs in Windows 10-64. Command line I type ‘Qemu -fda floppy.img’ and does not get past ‘Welcome to Efi World’ but if I burn the image to a flash usb drive it will boot up just fine. Are there any settings or drivers that need to be included in the compilation process? 

Thank you

Re: HELP: Qemu not able to load Duet image

[Laszlo Ersek]

Hello David,

On 03/08/18 02:08, david moheban wrote:
> 
> Hi,
> 
> I am having difficulty loading Duet image via Qemu x86-64 or Bochs in
> Windows 10-64. Command line I type ‘Qemu -fda floppy.img’ and does
> not get past ‘Welcome to Efi World’ but if I burn the image to a
> flash usb drive it will boot up just fine. Are there any settings or
> drivers that need to be included in the compilation process?

I saw your last query too on the mailing list:

  [edk2] How load Duet Floppy.IMG File in Bochs or Quemu?
  https://lists.01.org/pipermail/edk2-devel/2018-March/022313.html

I could have followed up there, but I decided not to, because (a) I
didn't want to appear as questioning your use case, and (b) I really
cannot help with the DUET firmware platform of edk2. I assumed what you
really cared about was running DUET on physical machines, and meant to
use QEMU only as a testbed of sorts.

However, seeing how this may be important to you, I can no longer avoid
questioning your use case -- are you perhaps targeting QEMU as your main
platform? Because, in that case, I certainly recommend that you drop
DUET and use OVMF instead.

So what's your ultimate goal here? For example, if you have individual
UEFI_DRIVER modules (not upstreamed to edk2) that you'd like to test on
QEMU first, and then use "for real" on physical machines, you could
build the driver into both OVMF and DUET. For testing, you can use OVMF
on QEMU, and DUET on physical machines with traditional BIOS firmware.

With regard to running OVMF on QEMU, I personally recommend a wrapper
script like the following (this example will launch a UEFI-bootable ISO
image):

  ISO=/.../xxxx.iso
  CODE=Build/OvmfX64/.../FV/OVMF_CODE.fd
  TMPL=Build/OvmfX64/.../FV/OVMF_VARS.fd
  DEBUG=ovmf.debug.log

  cp $TMPL varstore.fd

  qemu-system-x86_64 \
    -m 2048 \
    -drive if=pflash,format=raw,file=$CODE,readonly \
    -drive if=pflash,format=raw,file=varstore.fd \
    -drive if=none,format=raw,file=$ISO,readonly,id=cdrom \
    -device ide-cd,drive=cdrom,bootindex=0 \
    -debugcon file:$DEBUG \
    -global isa-debugcon.iobase=0x402 \
    -monitor stdio

Laszlo