From: Jan Kiszka <jan.kiszka@web.de>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: kvm@vger.kernel.org, mst@redhat.com, mtosatti@redhat.com,
qemu-devel@nongnu.org, blauwirbel@gmail.com,
Alex Williamson <alex.williamson@redhat.com>,
avi@redhat.com
Subject: Re: [Qemu-devel] Slow PXE boot in qemu.git (fast in qemu-kvm.git)
Date: Mon, 11 Apr 2011 23:18:06 +0200 [thread overview]
Message-ID: <4DA3700E.6010006@web.de> (raw)
In-Reply-To: <20110411180523.219530d7@doriath>
[-- Attachment #1: Type: text/plain, Size: 1936 bytes --]
On 2011-04-11 23:05, Luiz Capitulino wrote:
> On Mon, 11 Apr 2011 22:04:52 +0200
> Jan Kiszka <jan.kiszka@web.de> wrote:
>
>> On 2011-04-11 21:15, Luiz Capitulino wrote:
>>> On Mon, 11 Apr 2011 13:00:32 -0600
>>> Alex Williamson <alex.williamson@redhat.com> wrote:
>>>
>>>> On Mon, 2011-04-11 at 15:35 -0300, Luiz Capitulino wrote:
>>>>> On Fri, 08 Apr 2011 19:50:57 -0500
>>>>> 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 was having this problem too, but I think it's because I forgot to
>>>> build qemu with --enable-io-thread, which is the default for qemu-kvm.
>>>> Can you re-configure and build with that and see if it's fast? Thanks,
>>>
>>> Yes, nice catch, it's faster with I/O thread enabled, even seem faster
>>> than qemu-kvm.git.
>>
>> What's the performance under qemu-kvm with -no-kvm-irqchip?
>
> Still fast,
I meant: is it even faster with unaccelerated userspace irqchip? I've
seen such effects with emulated NICs before.
> but just realized that qemu-kvm's configure says that I/O thread
> is disabled:
>
> IO thread no
>
> And it's fast..
That only means (so far) that the upstream io-thread code is disabled.
Qemu-kvm's own solution is enabled all the time, and you can't switch to
upstream anyway as both are incompatible. That's going to change soon
(hopefully) when we migrate qemu-kvm to the upstream version.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2011-04-12 1:33 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
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 [this message]
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=4DA3700E.6010006@web.de \
--to=jan.kiszka@web.de \
--cc=alex.williamson@redhat.com \
--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).