From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cristi Magherusan Subject: Re: Custom BIOS supported size Date: Mon, 04 May 2009 17:09:35 +0300 Message-ID: <1241446175.30017.35.camel@hyperion> References: <1241384925.26848.10.camel@hyperion> <49FEF23E.3020105@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: kvm@vger.kernel.org To: Avi Kivity Return-path: Received: from bavaria.utcluj.ro ([193.226.5.35]:60371 "EHLO bavaria.utcluj.ro" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752617AbZEDOJt (ORCPT ); Mon, 4 May 2009 10:09:49 -0400 In-Reply-To: <49FEF23E.3020105@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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 work= s on > > qemu just fine).=20 > > =20 >=20 > 256K is the maximum with kvm. It can easily be increased, but we nee= d a=20 > small kernel change on Intel to store the real-mode TSS. >=20 >=20 Hi Avi, Thanks for your answer. What would be the upper bound up to which we ca= n extend it? May I somehow help in getting this done? Best regards, Cristi --=20 Ing. Cristi M=C4=83gheru=C8=99an, System/Network Engineer Technical University of Cluj-Napoca, Romania http://cc.utcluj.ro +40264 401247