qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 0/3] hw/arm/virt: boot with -kernel -initrd -app


From: Laszlo Ersek
Subject: Re: [Qemu-devel] [PATCH 0/3] hw/arm/virt: boot with -kernel -initrd -append on top of UEFI
Date: Tue, 09 Dec 2014 01:07:20 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0

On 12/05/14 19:55, Peter Maydell wrote:
> On 5 December 2014 at 18:36, Laszlo Ersek <address@hidden> wrote:
>> A number of tools depend on passing the kernel image, the initial
>> ramdisk, and the kernel command line to the guest on the QEMU command
>> line (options -kernel, -initrd, -append, respectively). At the moment,
>> these QEMU options work, but the guest kernel loaded this way is
>> launched by a minimal binary firmware that is dynamically composed by
>> QEMU. As a consequence, such a kernel has no UEFI environment.
>>
>> In this patchset the kernel, initrd and cmdline blobs are passed to the
>> guest firmware to process & load. This mode is activated when both
>> -kernel and -pflash unit#0 (or -bios) are specified.
> 
> ...so we avoid back-compat problems on the assumption that
> nobody was previously trying to provide both -bios and
> -kernel at once. I *think* that's probably a reasonable
> assumption...

I'm including these three too in the new patchset that I'll post soon,
so no need to keep these queued.

Thanks
Laszlo




reply via email to

[Prev in Thread] Current Thread [Next in Thread]