From: Jordan Justen <jljusten@gmail.com>
To: vagran <vagran.ast@gmail.com>
Cc: Isaku Yamahata <yamahata@valinux.co.jp>,
Tristan Gingold <gingold@adacore.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: EFI console stopped working in Qemu 0.14.0
Date: Sat, 5 Mar 2011 19:35:12 -0800 [thread overview]
Message-ID: <AANLkTinvqBgV2ZNzXHo9WH312oz+v1jqHi-sYKkb+vvq@mail.gmail.com> (raw)
In-Reply-To: <4D6FD79F.9000104@gmail.com>
On Thu, Mar 3, 2011 at 10:02, vagran <vagran.ast@gmail.com> wrote:
> I have taken EFI BIOS image from
> http://sourceforge.net/apps/mediawiki/tianocore/index.php?title=OVMF
> 32-bit version works perfectly. However 64-bit version for some reason
> doesn't work on
> qemu-system-x86_64.
Hi. I was wondering if you could describe the OVMF issue you saw with
qemu-system-x86_64.
I tried 0.14.0 with OVMF X64 (r11337), and it was able to boot to the EFI shell.
I did see an issue while booting the 64-bit Ubuntu 10.10 live-cd, but
occurred on both the legacy (seabios) and uefi (ovmf) firmware. With
kvm 0.14.0, in both cases the OS boots most of the way, but the
graphics do not start properly when X starts.
Thanks,
-Jordan
next prev parent reply other threads:[~2011-03-06 3: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 [this message]
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
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=AANLkTinvqBgV2ZNzXHo9WH312oz+v1jqHi-sYKkb+vvq@mail.gmail.com \
--to=jljusten@gmail.com \
--cc=gingold@adacore.com \
--cc=qemu-devel@nongnu.org \
--cc=vagran.ast@gmail.com \
--cc=yamahata@valinux.co.jp \
/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).