From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Andrea Bolognani <abologna@redhat.com>,
David Gibson <david@gibson.dropbear.id.au>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH qemu v5] spapr: Kill SLOF
Date: Thu, 30 Jan 2020 16:57:10 +1100 [thread overview]
Message-ID: <e9ce0b0b-2edf-ddd8-c05e-2556d1bff0cc@ozlabs.ru> (raw)
In-Reply-To: <f8c6e5cccc0dfc6a02cc6746808c023a4a4ff238.camel@redhat.com>
On 28/01/2020 22:31, Andrea Bolognani wrote:
> On Thu, 2020-01-23 at 16:11 +1100, David Gibson wrote:
>> On Wed, Jan 22, 2020 at 06:14:37PM +1100, Alexey Kardashevskiy wrote:
>>> On 22/01/2020 17:32, David Gibson wrote:
>>>> I'm not thinking of "grub" as a separate option - that would be the
>>>> same as "vof". Using vof + no -kernel we'd need to scan the disks in
>>>> the same way SLOF does, and look for a boot partition, which will
>>>> probably contain a GRUB image.
>>>
>>> I was hoping we can avoid that by allowing
>>> "-kernel grub" and let grub do filesystems and MBR/GPT.
>>
>> I don't want that to be the only way, because I want the GRUB
>> installed by the OS installer to be the GRUB we use.
>
> Agreed, the bootloader and the kernel should live inside the guest
> image and not on the host's filesystem.
Well, I tried. Added simple MBR+GPT parser, loaded ELF and discovered
that load_elf32/64 does not parse ELFs from memory, only from files.
Anyone keen on fixing that? :) My current workaround is to load grub
from the disk, then store it /tmp and load this as it was passed via
-kernel which is ugly..
--
Alexey
prev parent reply other threads:[~2020-01-30 5:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 2:09 [PATCH qemu v5] spapr: Kill SLOF Alexey Kardashevskiy
2020-01-21 5:11 ` David Gibson
2020-01-21 7:25 ` Alexey Kardashevskiy
2020-01-22 6:32 ` David Gibson
2020-01-22 7:14 ` Alexey Kardashevskiy
2020-01-23 5:11 ` David Gibson
2020-01-23 8:43 ` Alexey Kardashevskiy
2020-01-28 11:31 ` Andrea Bolognani
2020-01-30 5:57 ` Alexey Kardashevskiy [this message]
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-all 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=e9ce0b0b-2edf-ddd8-c05e-2556d1bff0cc@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=abologna@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).