From: "Richardson, Brian" <brian.richardson@intel.com>
To: "Justen, Jordan L" <jordan.l.justen@intel.com>,
"Prakhya, Sai Praneeth" <sai.praneeth.prakhya@intel.com>,
Laszlo Ersek <lersek@redhat.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: Unable to boot OVMF on qemu-x86_64
Date: Tue, 25 Apr 2017 19:13:14 +0000 [thread overview]
Message-ID: <80AC2BAA3152784F98F581129E5CF5AF8DF224CE@ORSMSX109.amr.corp.intel.com> (raw)
In-Reply-To: <149307459156.29807.2877695759233240338@jljusten-skl>
The Ubuntu wiki info isn't quite up to date. We're maintaining updated build instructions on the TianoCore Wiki:
https://github.com/tianocore/tianocore.github.io/wiki/Using-EDK-II-with-Native-GCC#Ubuntu_1604_LTS__Ubuntu_1610
https://github.com/tianocore/tianocore.github.io/wiki/How-to-build-OVMF
The README in OvmfPkg is going to be more up to date for OVMF specific info, but the wiki will have more general build info for different OS/compiler configurations.
Please let us know if you see issues with the wiki info so we can make updates.
Thanks ... br
---
Brian Richardson, Senior Technical Marketing Engineer, Intel Software
brian.richardson@intel.com -- @intel_brian (Twitter & WeChat)
https://software.intel.com/en-us/meet-the-developers/evangelists/team/brian-richardson
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Jordan Justen
Sent: Monday, April 24, 2017 6:57 PM
To: Prakhya, Sai Praneeth <sai.praneeth.prakhya@intel.com>; Laszlo Ersek <lersek@redhat.com>
Cc: edk2-devel@lists.01.org
Subject: Re: [edk2] Unable to boot OVMF on qemu-x86_64
On 2017-04-24 13:41:50, Laszlo Ersek wrote:
> On 04/18/17 07:29, Prakhya, Sai Praneeth wrote:
> > Hi All,
> >
> > I am facing an issue booting OVMF on qemu, could you please help me?
> > I have cloned EDKII, and built OVMF for X64 using GCC5. I have
> > followed the steps given at https://wiki.ubuntu.com/UEFI/EDK2.
>
> "last edited 2012-11-16 20:22:59"
>
> > Then I
> > have used qemu-system-x86_64 to boot OVMF, but it fails, I don't see
> > anything on tty0 of qemu.
Did you build with "-DDEBUG_ON_SERIAL_PORT=TRUE" to enable the debug to go to the serial port?
Personally, I'd recommend *not* using DEBUG_ON_SERIAL_PORT, and instead of looking at tty0, add this to the qemu command line:
-debugcon file:debug.log -global isa-debugcon.iobase=0x402
Then debug.log will contain the debug messages.
(BTW, thanks Laszlo for implementing this! :)
> > When I tried the same by changing to IA32 it seems working. So,
> > could anyone please let me know what I am missing or maybe someone
> > give it a try and see it it's reproducible or not...
> > I am using Ubuntu 15.04 as my build system.
>
> Please try the instructions given under "Build Scripts" in
> "OvmfPkg/README". (CC Jordan)
Yeah. This is more up to date than the Ubuntu wiki. It also has the debugcon info...
-Jordan
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2017-04-25 19:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 5:29 Unable to boot OVMF on qemu-x86_64 Prakhya, Sai Praneeth
2017-04-24 20:41 ` Laszlo Ersek
2017-04-24 22:56 ` Jordan Justen
2017-04-25 19:13 ` Richardson, Brian [this message]
2017-04-26 19:17 ` Sai Praneeth Prakhya
2017-04-26 19:12 ` Sai Praneeth Prakhya
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-list 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=80AC2BAA3152784F98F581129E5CF5AF8DF224CE@ORSMSX109.amr.corp.intel.com \
--to=devel@edk2.groups.io \
/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