public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Cristi Magherusan <Cristi.Magherusan@net.utcluj.ro>
To: Jordan Justen <jljusten@gmail.com>
Cc: Sheng Yang <sheng@linux.intel.com>,
	kvm@vger.kernel.org, Jordan Justen <jordan.l.justen@intel.com>,
	Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH] Update qemu-kvm to allow a larger BIOS image.
Date: Wed, 22 Jul 2009 22:04:33 +0300	[thread overview]
Message-ID: <1248289473.12578.5.camel@hyperion> (raw)
In-Reply-To: <2a50f7880907161057u58802061xc472e9b8c9ec4f1a@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]

On Thu, 2009-07-16 at 10:57 -0700, Jordan Justen wrote:
> On Wed, Jul 15, 2009 at 10:37 PM, Sheng Yang<sheng@linux.intel.com> wrote:
> > Make sense to me. So what's mattered here is not bios, but qemu-kvm and kvm
> > code. The user can replace bios binary by UEFI binary easily, but not with kvm
> > related part.
> >
> > I realized you still need separate the qemu-kvm patch into two: one for bios
> > and another for qemu.
> 
> Okay, I will split this change apart.
> 
> > And I just hope this modification won't break some old
> > OS(any OS got assumption about bios size? I think Tiano team should have idea
> > on it)...
> 
> I don't think the OS should care about the bios size, but it is
> important to update the INT15-E820 memory ranges to help
> make sure the OS knows which regions are in use.
> 
> Even without the E820 change, I think it would be unlikely
> for an OS to try utilize these memory regions, but it is
> definitely better to properly describe it.
Hello,

I don't know if I get this right, but is it enough to apply this patch
to KVM-userspace, or do I also need to have a patched kernel in order to
get large images (my image is 4MB) to work in KVM? 

Thanks,
Cristi

-- 
Ing. Cristi Măgherușan, System/Network Engineer
Technical University of Cluj-Napoca, Romania
http://cc.utcluj.ro  +40264 401247

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-07-22 19:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-16  0:12 [PATCH] Update KVM kernel module to allow a larger BIOS image Jordan Justen
2009-07-16  0:12 ` [PATCH] Update qemu-kvm " Jordan Justen
2009-07-16  1:34   ` Sheng Yang
2009-07-16  2:58     ` Jordan Justen
2009-07-16  3:08       ` Sheng Yang
2009-07-16  4:57         ` Jordan Justen
2009-07-16  5:37           ` Sheng Yang
2009-07-16 17:57             ` Jordan Justen
2009-07-22 19:04               ` Cristi Magherusan [this message]
2009-07-23  1:42                 ` Sheng Yang

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=1248289473.12578.5.camel@hyperion \
    --to=cristi.magherusan@net.utcluj.ro \
    --cc=jljusten@gmail.com \
    --cc=jordan.l.justen@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=sheng@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox