From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: extboot.bin required in git
Date: Wed, 02 Sep 2009 17:26:16 +0200 [thread overview]
Message-ID: <4A9E8E98.6040201@siemens.com> (raw)
In-Reply-To: <4A9E8D56.3080102@redhat.com>
Avi Kivity wrote:
> On 09/02/2009 05:51 PM, Jan Kiszka wrote:
>> Avi Kivity wrote:
>>
>>> On 09/02/2009 05:34 PM, Jan Kiszka wrote:
>>>
>>>> Hi Marcelo,
>>>>
>>>> qemu-kvm's installation (0.11-rc as well as git head) is currently
>>>> broken /wrt extboot.bin. Please check some proper binary in as
>>>> pc-bios/extboot.bin.
>>>>
>>>>
>>> It's built at runtime. Why check in a binary?
>>>
>> First of all, it's a qemu policy (AFAIK): try to build the rom, use
>> shipped version if that doesn't work.
>
> Right, but this is qemu-kvm, which doesn't have the same issues
> (building an i386 target on non-i386). When extboot is merged into
> qemu.git, they can add the build-if-possible-otherwise-use-shipped thing.
Well, people may expect qemu-kvm's source tree to build properly also
for non-kvm usage. But this is not that important for now.
>
>> And second, we (more precisely
>> qemu) does not seem to use the optionrom output for installation yet.
>> The latter is likely subject to change, but the former is expected to stay.
>>
>
> We do, see 321b6ef91.
Ah, I see: some out-of-tree build bug. Will fix.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2009-09-02 15:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 14:34 extboot.bin required in git Jan Kiszka
2009-09-02 14:38 ` Avi Kivity
2009-09-02 14:51 ` Jan Kiszka
2009-09-02 15:20 ` Avi Kivity
2009-09-02 15:26 ` Jan Kiszka [this message]
2009-09-02 15:31 ` Jan Kiszka
2009-09-02 15:40 ` Avi Kivity
2009-09-02 16:17 ` Jan Kiszka
2009-09-02 16:20 ` Avi Kivity
2009-09-02 15:40 ` Avi Kivity
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=4A9E8E98.6040201@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.