From: Avi Kivity <avi@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: Anthony Liguori <aliguori@us.ibm.com>, beth kon <eak@us.ibm.com>,
Alexander Graf <agraf@suse.de>, Gleb Natapov <gleb@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] PC machine types switched to SeaBIOS/gPXE
Date: Mon, 02 Nov 2009 15:56:08 +0200 [thread overview]
Message-ID: <4AEEE4F8.1020409@redhat.com> (raw)
In-Reply-To: <20091102135107.GA9856@morn.localdomain>
On 11/02/2009 03:51 PM, Kevin O'Connor wrote:
> On Mon, Nov 02, 2009 at 03:32:54PM +0200, Avi Kivity wrote:
>
>> On 11/02/2009 03:15 PM, Alexander Graf wrote:
>>
>>> They are taken with -d in_asm,cpu,int after doing:
>>>
>>> $ ./x86_64-softmmu/qemu-system-x86_64 -kernel ../kvm/arch/x86/boot/bzImage
>>>
>>> with a fresh checkout from your kvm kernel tree (make defconfig) and a
>>> fresh git checkout of qemu (./configure --target-list=x86_64-softmmu)
>>>
>>>
>>> They basically mean that with SeaBIOS the Linux loading code is trying
>>> to jump off to zeros while at the same place there is useful data using
>>> pcbios.bin.
>>>
>>>
>> Is seabios clobbering memory? Gleb/Kevin?
>>
> I have not tested with the -kernel option before. I believe you may
> be running into the clearing of memory that PMM does - see
> malloc_finalize() in src/pmm.c. The PMM spec requires that low memory
> be cleared before starting the boot process.
>
>
Likely. Alex, does -kernel use memory below 1MB? Can it be moved
elsewhere?
If not, we probably need a protocol where the option rom loads the
kernel from qemu, rather than qemu poking the kernel into memory.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-11-02 13:56 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 14:54 [Qemu-devel] PC machine types switched to SeaBIOS/gPXE Anthony Liguori
2009-10-30 19:37 ` [Qemu-devel] " Jan Kiszka
2009-10-30 19:45 ` Anthony Liguori
2009-10-31 12:42 ` Stefan Weil
2009-10-31 13:10 ` Jan Kiszka
2009-11-02 23:09 ` Beth Kon
2009-11-02 23:22 ` Anthony Liguori
2009-11-03 4:16 ` Kevin O'Connor
2009-11-03 14:11 ` Beth Kon
2009-11-04 1:38 ` Kevin O'Connor
2009-11-04 1:55 ` Anthony Liguori
2009-10-31 11:07 ` [Qemu-devel] " Stefan Weil
2009-10-31 12:02 ` [Qemu-devel] " Jan Kiszka
2009-11-02 12:51 ` [Qemu-devel] " Alexander Graf
2009-11-02 13:08 ` Avi Kivity
2009-11-02 13:15 ` Alexander Graf
2009-11-02 13:32 ` Avi Kivity
2009-11-02 13:51 ` Kevin O'Connor
2009-11-02 13:56 ` Avi Kivity [this message]
2009-11-02 14:06 ` Alexander Graf
2009-11-02 14:39 ` Avi Kivity
2009-11-09 18:41 ` Glauber Costa
2009-11-10 13:02 ` Avi Kivity
2009-11-10 13:03 ` Alexander Graf
2009-11-10 13:07 ` Avi Kivity
2009-11-10 13:09 ` Alexander Graf
2009-11-03 4:50 ` Kevin O'Connor
2009-11-03 4:57 ` Alexander Graf
2009-11-03 5:01 ` Avi Kivity
2009-11-03 6:02 ` Kevin O'Connor
2009-11-03 6:08 ` Avi Kivity
2009-11-03 13:42 ` Kevin O'Connor
2009-11-03 4:58 ` Avi Kivity
2009-11-02 14:51 ` Gleb Natapov
2009-11-02 14:54 ` Gleb Natapov
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=4AEEE4F8.1020409@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=eak@us.ibm.com \
--cc=gleb@redhat.com \
--cc=kevin@koconnor.net \
--cc=qemu-devel@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).