From: Laszlo Ersek <lersek@redhat.com>
To: Oleksii Shevchuk <alxchk@alxchk.me>
Cc: "edk2-devel@lists.sourceforge.net"
<edk2-devel@lists.sourceforge.net>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [edk2] OVMF and qemu 1.5.2 (git trunk)
Date: Mon, 15 Jul 2013 14:08:58 +0200 [thread overview]
Message-ID: <51E3E65A.1060802@redhat.com> (raw)
In-Reply-To: <87ip0cf7f3.fsf@alxchk.me>
On 07/15/13 12:23, Oleksii Shevchuk wrote:
> I managed to run it from edk2:
> qemu-system-x86_64 -L /opt/edk2/Build/OvmfX64/DEBUG_GCC46/QEMU -hda
> fat:/opt/edk2/Build/OvmfX64/DEBUG_GCC46/X64
>
> But with enabled kvm it doesn't work and boots veeeeeeeery slow.
>
> It successfully runned with KVM in qemu 1.4.2, and looking to your
> launching command looks like you can run it with KVM too
Can you please bisect qemu from 1.4.2 to current master? (And we should
probably take the discussion to qemu-devel -- I'm CC'ing both lists now,
but your answer should probably go to qemu-devel only.)
Thanks,
Laszlo
parent reply other threads:[~2013-07-15 12:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <87ip0cf7f3.fsf@alxchk.me>]
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=51E3E65A.1060802@redhat.com \
--to=lersek@redhat.com \
--cc=alxchk@alxchk.me \
--cc=edk2-devel@lists.sourceforge.net \
--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).