From: Stefan Hajnoczi <stefanha@gmail.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: kvm@vger.kernel.org, mst@redhat.com, mtosatti@redhat.com,
qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>,
blauwirbel@gmail.com, alex.williamson@redhat.com, avi@redhat.com
Subject: [Qemu-devel] Re: Slow PXE boot in qemu.git (fast in qemu-kvm.git)
Date: Sat, 9 Apr 2011 13:03:43 +0100 [thread overview]
Message-ID: <BANLkTinZoMr1by8M14nhqHqnsj_9j3dvcw@mail.gmail.com> (raw)
In-Reply-To: <4D9FAD71.5020503@codemonkey.ws>
On Sat, Apr 9, 2011 at 1:50 AM, Anthony Liguori <anthony@codemonkey.ws> wrote:
> On 04/08/2011 06:25 PM, Luiz Capitulino wrote:
>>
>> Hi there,
>>
>> Summary:
>>
>> - PXE boot in qemu.git (HEAD f124a41) is quite slow, more than 5 minutes.
>> Got
>> the problem with e1000, virtio and rtl8139. However, pcnet *works*
>> (it's
>> as fast as qemu-kvm.git)
>>
>> - PXE boot in qemu-kvm.git (HEAD df85c051) is fast, less than a minute.
>> Tried
>> with e1000, virtio and rtl8139 (I don't remember if I tried with pcnet)
>>
>> I tried with qemu.git v0.13.0 in order to check if this was a regression,
>> but
>> I got the same problem...
>>
>> Then I inspected qemu-kvm.git under the assumption that it could have a
>> fix
>> that wasn't commited to qemu.git. Found this:
>>
>> - commit 0836b77f0f65d56d08bdeffbac25cd6d78267dc9 which is merge, works
>>
>> - commit cc015e9a5dde2f03f123357fa060acbdfcd570a4 does not work (it's
>> slow)
>>
>> I tried a bisect, but it brakes due to gcc4 vs. gcc3 changes. Then I
>> inspected
>> commits manually, and found out that commit 64d7e9a4 doesn't work, which
>> makes
>> me think that the fix could be in the conflict resolution of 0836b77f,
>> which
>> makes me remember that I'm late for diner, so my conclusions at this point
>> are
>> not reliable :)
>
> Can you run kvm_stat to see what the exit rates are?
>
> Maybe we're missing a coalesced io in qemu.git? It's also possible that
> gpxe is hitting the apic or pit quite a lot.
In gPXE's main loop it will do real <-> protected mode switches and
poll hardware. It doesn't handle interrupts itself but sets up the
8254 timer chip.
I once found that polling the keyboard only every couple of gPXE main
loop iterations significantly speeds up network throughput under KVM.
I never got around to auditing the entire main loop and implementing a
clean patch.
Anyway, kvm_stat is a good idea. It may be tickling qemu in a way
that qemu-kvm is immune to.
Stefan
next prev parent reply other threads:[~2011-04-09 12:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 23:25 [Qemu-devel] Slow PXE boot in qemu.git (fast in qemu-kvm.git) Luiz Capitulino
2011-04-09 0:50 ` [Qemu-devel] " Anthony Liguori
2011-04-09 12:03 ` Stefan Hajnoczi [this message]
2011-04-10 8:19 ` Avi Kivity
2011-04-11 18:35 ` [Qemu-devel] " Luiz Capitulino
2011-04-11 19:00 ` Alex Williamson
2011-04-11 19:15 ` Luiz Capitulino
2011-04-11 20:04 ` Jan Kiszka
2011-04-11 20:14 ` Alex Williamson
2011-04-11 20:18 ` Jan Kiszka
2011-04-11 20:29 ` Jan Kiszka
2011-04-12 8:09 ` Paolo Bonzini
2011-04-11 21:05 ` Luiz Capitulino
2011-04-11 21:18 ` Jan Kiszka
2011-04-12 0:39 ` Anthony Liguori
2011-04-12 7:42 ` Avi Kivity
2011-04-09 10:34 ` [Qemu-devel] " Blue Swirl
2011-04-11 12:51 ` Luiz Capitulino
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=BANLkTinZoMr1by8M14nhqHqnsj_9j3dvcw@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=alex.williamson@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=lcapitulino@redhat.com \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.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).