From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: Custom BIOS supported size
Date: Mon, 04 May 2009 16:48:46 +0300
Message-ID: <49FEF23E.3020105@redhat.com>
References: <1241384925.26848.10.camel@hyperion>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: kvm@vger.kernel.org
To: Cristi Magherusan <Cristi.Magherusan@net.utcluj.ro>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx2.redhat.com ([66.187.237.31]:41405 "EHLO mx2.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1755561AbZEDNtd (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 4 May 2009 09:49:33 -0400
In-Reply-To: <1241384925.26848.10.camel@hyperion>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

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.




-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.