From: "Sven Köhler" <skoehler@upb.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] high CPU load / async IO?
Date: Mon, 24 Jul 2006 00:47:21 +0200 [thread overview]
Message-ID: <ea0u9u$gci$1@sea.gmane.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]
Hi,
sorry for bothering, but the last time i heard something about asyn IO
was on Feb 2nd. Fabrice said:
[quote]
I have at least 5 items on my TODO list :
1) New kqemu which virtualizes both user and kernel code (currently in
alpha stage but not released yet).
2) DMA block I/O (merged)
3) async block I/O (not merged yet)
4) Network adapter using DMA (not merged yet)
5) VGA acceleration (either improve Cirrus VGA or switch back to Bochs
VGA for Win 2000/XP or Linux)
[/quote]
so 1) and 2) are in HEAD. I saw something concerning 5) too, i think.
I'm not sure about 4) - but - well,
I'm very curious about 3) :-)
It's not in HEAD yet, isn't it?
Why i'm curious? Well, i'm curious about the improvement it causes. You
people once told me, that the boost will not be that significant. On the
other hand, i see my host CPU usage going towards 100% just because the
guest is doing some IO or ... or is it because of somethine else perhaps?
To be concrete: have you guys ever run windows-update inside qemu? Well,
my win2k guest consumes all CPU on the host for some reason. What might
be the reason?
(qemu is started with -kernel-kqemu -m 256 -soundhw es1370)
Also windows-update's green "progress bar" inside the guest is stopping
for let's say 3 or 5 seconds and not moving continuous.
Is anybody experiencing the same or knows the reason?
Thanks,
Sven
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
next reply other threads:[~2006-07-23 22:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-23 22:47 Sven Köhler [this message]
2006-07-24 18:46 ` [Qemu-devel] Re: high CPU load / async IO? Anthony Liguori
2006-07-24 22:51 ` Sven Köhler
2006-07-25 14:55 ` Anthony Liguori
2006-07-25 18:15 ` Sven Köhler
2006-07-25 19:43 ` Jens Axboe
2006-07-25 20:37 ` Fabrice Bellard
2006-07-26 7:45 ` Jens Axboe
2006-07-26 12:21 ` Paul Brook
2006-07-26 12:23 ` Jens Axboe
2006-07-26 12:27 ` Paul Brook
2006-07-26 12:46 ` Jens Axboe
2006-07-26 14:14 ` Sven Köhler
2006-07-26 17:54 ` Jens Axboe
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='ea0u9u$gci$1@sea.gmane.org' \
--to=skoehler@upb.de \
--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).