From: Jason Brittain <jason@brittainweb.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] kqemu vs Standard
Date: Tue, 15 Feb 2005 09:55:57 -0800 [thread overview]
Message-ID: <421237AD.1090401@brittainweb.org> (raw)
Hi Qemu developers & users!
I'm reporting in to say that I've lightly tested Qemu/kqemu, and found it
to be significantly faster with both XP and Linux guest OSs.
I tested with the following setup:
Real Hardware: IBM Thinkpad T42p, pentium M 1.80GHz, 1GB RAM, 60G IDE HD
Host OS: Fedora Core 3 "everything" installation, very slight kernel
reconfig changes.
Guest OS: XP Corp. SP1
----------------------
This feels noticeably faster. Double clicking on icons works a bit better,
although it doesn't work all that well still. Instead, I right click on
icons and select "Open". :) The programs run faster as well, but I'm not
sure yet how I could test how much faster. Plus, I'm happy with it, so I
may not spend much time figuring that out.
XP boot, all the way to the desktop:
65 seconds regular
45 seconds kqemu
Also, due to other changes that were checked in either at the same time as
kqemu, or just before, I believe some bugs were fixed because some errors
I used to get running some of the software I run are now gone.
Guest OS: RedHat Linux 9, modified to run a 2.6 kernel
------------------------------------------------
This boots much faster now, as the numbers below show.
Linux boot, all the way to the text (non-graphical) login prompt:
86 seconds regular
36 seconds kqemu
Probably also due to numberous bug fixes checked in recently, my Java VM/Tomcat
installation now runs inside qemu without crashing with a HotSpot VM error.
It used to run for a bit, then crash, and there wasn't anything I could do
about it other than run a newer version of Sun's JVM. Now, it just works. :)
I'm not yet sure if it works in the unaccelerated mode. I'm about to test that.
Also, in unaccelerated mode, the Java VM runs very slow versus natively. But,
using kqemu, it's decently fast. Fast enough to develop with it running inside
qemu. Excellent!
A Little More About How I Tested
--------------------------------
This was all done with qemu source from CVS as of the day Fabrice
checked in kqemu. I compiled it on FC3 like:
# ./configure
# make
# make install
So, nothing fancy there.
To switch between kqemu-accelerated, and standard (unaccelerated), all
I did was load or unload the kqemu module. Yes, when I ran qemu with
it unloaded I did get the output warning saying the acceleration was
disabled.
Here's my real (laptop) hardware's CPU info:
# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 13
model name : Intel(R) Pentium(R) M processor 1.80GHz
stepping : 6
cpu MHz : 599.679
cache size : 2048 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr mce cx8 mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe est tm2
bogomips : 1187.84
--
Jason Brittain
next reply other threads:[~2005-02-15 18:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 17:55 Jason Brittain [this message]
2005-02-15 18:28 ` [Qemu-devel] kqemu vs Standard Karel Gardas
2005-02-15 18:55 ` Jason Brittain
2005-02-15 19:43 ` Thomas Petazzoni
2005-02-15 20:05 ` Magnus Damm
2005-02-15 20:59 ` Jason Brittain
2005-02-15 20:18 ` Darryl Dixon
2005-02-15 19:43 ` James Mastros
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=421237AD.1090401@brittainweb.org \
--to=jason@brittainweb.org \
--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).