From: Lonnie Mendez <lmendez19@austin.rr.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu speed vs vmplayer?
Date: Fri, 15 Dec 2006 15:33:03 -0600 [thread overview]
Message-ID: <1166218383.22784.10.camel@vaio> (raw)
In-Reply-To: <45831FB1.4030907@tidetamerboatlifts.com>
On Fri, 2006-12-15 at 17:20 -0500, Joseph Miller wrote:
> I've got a copy of today's CVS, I was just assuming, since this is the
> qemu-devel mailing list, that someone on the list who regularly works on
> the qemu code would probably know more about this than I do. I have
> some assembly background, and I'm not afraid to start digging into x86
> cpu internals, but I would like a starting point. I'm really trying to
> figure out something specific about qemu. When running Qemu+KQEMU for
> linux-x86 host on WinXP x86 guest, top shows that 70% or more of my cpu
> is being use in the system portion. When using vmplayer (free), top
> shows less than 5% of my cpu in the system portion. vmplayer seems to
> be a LOT faster than Qemu, however I would prefer to use Qemu. I have a
> P4 2.6GHz host system with 1.5G RAM and 512MB RAM allocated to my guest
> OS's. Does anyone know the reason behind the slowdown? Is anyone
> familiar with what Qemu is so busy doing whilst sitting idle? I should
> note that I have compiled the KQemu into my 2.6 kernel instead of
> loading it as a module. I have found better performance with it this
> way. Any insight from a developer would be most appreciated.
Are you using the -kernel-kqemu switch? I see idle usage of 6-10% with
kqemu using -kernel-kqemu on windows xp guest. kqemu is closed source
software. If you want a starting point for improving the acceleration
portion then start by improving qvm86 (the GPL'ed accelerator).
next prev parent reply other threads:[~2006-12-15 21:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 8:09 [Qemu-devel] About performance of qemu-system-arm PianoPan
2006-12-13 10:32 ` [Qemu-devel] " Ross Burton
2006-12-13 11:22 ` [Qemu-devel] " Màrius Montón
2006-12-13 14:17 ` PianoPan
2006-12-13 15:23 ` Màrius Montón
2006-12-13 13:26 ` Martin Guy
2006-12-13 14:40 ` [Qemu-devel] qemu-system-* using mmap? Tim Olson
2006-12-13 15:32 ` Paul Brook
2006-12-13 16:04 ` Joseph Miller
2006-12-14 14:50 ` Tim Olson
2006-12-14 17:01 ` [Qemu-devel] " Joseph Miller
2006-12-14 16:45 ` Paul Brook
2006-12-15 16:21 ` [Qemu-devel] Qemu speed vs vmplayer? Joseph Miller
2006-12-15 16:13 ` Paul Brook
2006-12-15 22:20 ` Joseph Miller
2006-12-15 21:33 ` Lonnie Mendez [this message]
2006-12-15 21:38 ` Paul Brook
2006-12-15 21:48 ` Christian MICHON
2006-12-15 21:57 ` Lonnie Mendez
2006-12-15 22:18 ` Paul Brook
2006-12-15 22:34 ` Christian MICHON
2006-12-15 22:47 ` Paul Brook
[not found] ` <Pine.LNX.4.64.0612160028590.758@home.oyster.ru>
[not found] ` <25199.71.51.225.120.1166272989.squirrel@secure.emarketingnc.com>
[not found] ` <Pine.LNX.4.64.0612161732560.630@home.oyster.ru>
2006-12-17 4:37 ` it
2006-12-17 5:18 ` Lonnie Mendez
2006-12-19 16:00 ` [Qemu-devel] Qemu speed w/ USB tablet emulation Joseph Miller
2006-12-16 5:27 ` [Qemu-devel] Qemu speed vs vmplayer? Jamie Lokier
2006-12-15 16:32 ` [Qemu-devel] using mmap? Mark Williamson
2006-12-15 21:22 ` [Qemu-devel] " Anthony Liguori
2006-12-13 15:10 ` [Qemu-devel] About performance of qemu-system-arm Martin Guy
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=1166218383.22784.10.camel@vaio \
--to=lmendez19@austin.rr.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).