From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=43842 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PwfH0-0004tL-Tc for qemu-devel@nongnu.org; Mon, 07 Mar 2011 13:35:15 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PwfGz-0001ii-Ey for qemu-devel@nongnu.org; Mon, 07 Mar 2011 13:35:14 -0500 Received: from mail-wy0-f173.google.com ([74.125.82.173]:43323) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PwfGz-0001iX-Ak for qemu-devel@nongnu.org; Mon, 07 Mar 2011 13:35:13 -0500 Received: by wyb29 with SMTP id 29so4964415wyb.4 for ; Mon, 07 Mar 2011 10:35:12 -0800 (PST) Message-ID: <4D75255B.1020302@gmail.com> Date: Mon, 07 Mar 2011 20:35:07 +0200 From: vagran MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: EFI console stopped working in Qemu 0.14.0 References: <4D6EA921.60907@gmail.com> <4D6EB643.4030805@gmail.com> <20110303030353.GC1759@valinux.co.jp> <20110303030959.GD1759@valinux.co.jp> <4D6F387F.2000505@gmail.com> <0AC46461-5D0F-4B19-822D-C88B521E7DB0@adacore.com> <4D6FD79F.9000104@gmail.com> <4D735DA4.6050901@gmail.com> <4D73FC0D.9060807@gmail.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------020206080809060108070802" List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jordan Justen Cc: qemu-devel@nongnu.org This is a multi-part message in MIME format. --------------020206080809060108070802 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Yes, you are right, identity_base is 0xfffbc000 in my case and KVM_CAP_SET_IDENTITY_MAP_ADDR is not defined. So, as I understand, the problem is that BIOS size is too large and I have too old KVM module. Also I'm not sure if I can use KVM on 32-bit host for emulating 64-bit guests. Best regards, Artyom. Jordan Justen wrote: > On Sun, Mar 6, 2011 at 13:26, vagran wrote: > >>> Can you try disabling KVM? >>> >> Yes, it helped. Problem exists only when using KVM. Thanks. >> > > One thing I suspect is that the kernel side of kvm had an issue around > this time (Ubuntu 9.10) with a bios.bin larger than 256kb. > > With qemu 0.14.0, you could investigate what value is being used for > identity_base in target-i386/kvm.c:kvm_arch_init. > (Notice it will be a lower value if KVM_CAP_SET_IDENTITY_MAP_ADDR is > defined, and this will allow for a larger bios.bin.) > > I think I was able to use OVMF X64 with kvm on Ubuntu 10.04, but I > don't have a system set up right now to verify this. I am able to use > OVMF X64 with kvm on Ubuntu 10.10. > > -Jordan > --------------020206080809060108070802 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Yes, you are right, identity_base is 0xfffbc000 in my case and
KVM_CAP_SET_IDENTITY_MAP_ADDR is not defined. So,
as I understand, the problem is that BIOS size is too large
and I have too old KVM module.
Also I'm not sure if I can use KVM on 32-bit host for
emulating 64-bit guests.

Best regards,
Artyom.

Jordan Justen wrote:

On Sun, Mar 6, 2011 at 13:26, vagran <vagran.ast@gmail.com> wrote:

Can you try disabling KVM?

Yes, it helped. Problem exists only when using KVM. Thanks.


One thing I suspect is that the kernel side of kvm had an issue around
this time (Ubuntu 9.10) with a bios.bin larger than 256kb.

With qemu 0.14.0, you could investigate what value is being used for
identity_base in target-i386/kvm.c:kvm_arch_init.
(Notice it will be a lower value if KVM_CAP_SET_IDENTITY_MAP_ADDR is
defined, and this will allow for a larger bios.bin.)

I think I was able to use OVMF X64 with kvm on Ubuntu 10.04, but I
don't have a system set up right now to verify this.  I am able to use
OVMF X64 with kvm on Ubuntu 10.10.

-Jordan

--------------020206080809060108070802--