From: Mikhail Ramendik <mr@ramendik.ru>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] win98 slow with kqemu
Date: Sat, 30 Dec 2006 18:09:30 +0000 [thread overview]
Message-ID: <200612301809.30656.mr@ramendik.ru> (raw)
Hello,
Some time ago I reported win98 slowness with kqemu, see
http://lists.gnu.org/archive/html/qemu-devel/2006-05/msg00295.html
I have tried again, this time on a Pentium 4 (Prescott) 3 GHz system, with
Debian sarge and backports.org 2.6.18 kernel; qemu 0.8.2 and kqemu 1.3.0pre9
are locally compiled, not packaged.
Still I see visible slowness with win98 guest and kqemu; it is slower than
win98 guest without kqemu. The amnhld.vxd idlesness driver is installed.
The problem is mentioned in forums periodically, i.e. the last reply in
http://qemu-forum.ipi.fi/viewtopic.php?t=2015 .
I would really like to have this fixed; I am somewhat experienced and will do
what is needed for testing etc. I would try some CPU "mark" tests for a more
objective check - but which of them will work without DirectX?
--
Yours, Mikhail Ramendik
next reply other threads:[~2006-12-30 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-30 18:09 Mikhail Ramendik [this message]
2007-01-02 12:54 ` [Qemu-devel] win98 slow with kqemu Dan Sandberg
2007-01-06 17:43 ` Mikhail Ramendik
2007-01-08 10:11 ` Dan Sandberg
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=200612301809.30656.mr@ramendik.ru \
--to=mr@ramendik.ru \
--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).