From: Cristi Magherusan <Cristi.Magherusan@net.utcluj.ro>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: Custom BIOS supported size
Date: Mon, 04 May 2009 17:09:35 +0300 [thread overview]
Message-ID: <1241446175.30017.35.camel@hyperion> (raw)
In-Reply-To: <49FEF23E.3020105@redhat.com>
On Mon, 2009-05-04 at 16:48 +0300, Avi Kivity wrote:
> Cristi Magherusan wrote:
> > Hello,
> >
> > Which is the maximum size supported for a custom BIOS image(eg.
> > coreboot-based)? I tried some 256K coreboot BIOS images and seemed to
> > work fine, but it blowed up with a 3MB image (which by the way works on
> > qemu just fine).
> >
>
> 256K is the maximum with kvm. It can easily be increased, but we need a
> small kernel change on Intel to store the real-mode TSS.
>
>
Hi Avi,
Thanks for your answer. What would be the upper bound up to which we can
extend it? May I somehow help in getting this done?
Best regards,
Cristi
--
Ing. Cristi Măgherușan, System/Network Engineer
Technical University of Cluj-Napoca, Romania
http://cc.utcluj.ro +40264 401247
next prev parent reply other threads:[~2009-05-04 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-03 21:08 Custom BIOS supported size Cristi Magherusan
2009-05-04 13:48 ` Avi Kivity
2009-05-04 14:09 ` Cristi Magherusan [this message]
2009-05-04 14:31 ` 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=1241446175.30017.35.camel@hyperion \
--to=cristi.magherusan@net.utcluj.ro \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.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