qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: vagran <vagran.ast@gmail.com>
To: Jordan Justen <jljusten@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: EFI console stopped working in Qemu 0.14.0
Date: Mon, 07 Mar 2011 20:35:07 +0200	[thread overview]
Message-ID: <4D75255B.1020302@gmail.com> (raw)
In-Reply-To: <AANLkTik=rM31QdjzNUjTXZL6mqzWy+adUvgEkteOMdgO@mail.gmail.com>

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

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
>   

[-- Attachment #2: Type: text/html, Size: 1717 bytes --]

      reply	other threads:[~2011-03-07 18:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-02 20:31 [Qemu-devel] EFI console stopped working in Qemu 0.14.0 vagran
2011-03-02 21:27 ` [Qemu-devel] " vagran
2011-03-03  3:03   ` Isaku Yamahata
2011-03-03  3:09     ` Isaku Yamahata
2011-03-03  6:43       ` vagran
2011-03-03  7:38         ` Isaku Yamahata
2011-03-03  7:46         ` Isaku Yamahata
2011-03-03  7:48           ` Isaku Yamahata
2011-03-03  8:20         ` Tristan Gingold
2011-03-03 18:02           ` vagran
2011-03-06  3:35             ` Jordan Justen
2011-03-06 10:10               ` vagran
     [not found]                 ` <AANLkTik968MQ9K+DGqrLDsse04BPMep9mQpXT55TCUnn@mail.gmail.com>
2011-03-06 21:26                   ` vagran
2011-03-06 23:36                     ` Jordan Justen
2011-03-07 18:35                       ` vagran [this message]

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=4D75255B.1020302@gmail.com \
    --to=vagran.ast@gmail.com \
    --cc=jljusten@gmail.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).