public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: nahim.souza@fit-tecnologia.org.br
To: devel@edk2.groups.io
Subject: Cannot boot ISO on RamDisk
Date: Thu, 26 Nov 2020 11:53:49 -0800	[thread overview]
Message-ID: <MH9w.1606420429710701772.eQsI@groups.io> (raw)

[-- Attachment #1: Type: text/plain, Size: 1394 bytes --]

Greetings!

We are trying to implement an .efi application that receives an ISO file from an Android device, loads it into a buffer and try to boot an Operating System. To do this, we tested some implementations using Ram Disk but after creating the virtual disk and running BOOTX64.efi and found on the FAT32 partition, but some problems occur after boot, as if I did not find the other files in the ISO. To solve this problem, we tried some approaches:

* Change the parameters when calling RamDiskProtocol->Register() function (GUID and DevicePath)
* Tried with different OS (Xubuntu, Windows 10, Windows 7, Ubuntu and OpenSuse)
* Compared with HttpBoot implementation from EDK2, where we saw that an ISO file could be loaded into memory to boot an OS, but the RamDisk implementation in HttpBootRegisterRamDisk was very similar to ours
Based on this, I have some questions:

* In our understanding, HttpBoot downloads the ISO and boots the OS using the RamDisk. Is that correct?
* We saw that RamDiskDxe has some dependencies from ACPI tables, since it uses NFIT (NVDIMM Firmware Interface Table) to save some persistent information. Is there some hardware/driver requirement to make the OS boot through RamDisk? Did we need to have this NVDIMM to support ACPI feature from RamDiskDxe?
* Would you have any other suggestions for solving this scenario?

Best regards!
Nahim.

[-- Attachment #2: Type: text/html, Size: 1547 bytes --]

             reply	other threads:[~2020-11-26 19:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-26 19:53 nahim.souza [this message]
2020-11-27 17:08 ` [edk2-devel] Cannot boot ISO on RamDisk Laszlo Ersek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=MH9w.1606420429710701772.eQsI@groups.io \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox