From: "Kazu" <kazoo@r3.dion.ne.jp>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] -kernel-kqemu
Date: Sat, 11 Feb 2006 12:02:23 +0900 [thread overview]
Message-ID: <002a01c62eb7$95234f90$0464a8c0@athlon> (raw)
In-Reply-To: 43EBBBC1.1070508@bellard.org
Sent: Friday, February 10, 2006 7:01 AM Fabrice Bellard wrote:
> Hi,
>
> I will update the documentation about "-kernel-kqemu" soon.
>
> To be short: as some people already noticed, this option allows to run
> user code and most of the kernel code on "bare metal". The result is
> usually a noticable speed up. Only the following guest OSes are
> supported: Linux, Windows 2000 or XP. The installation of Windows
> 2000/XP must be run without the -kernel-kqemu option.
>
> I did not test the win32 and x86_64 versions of kqemu yet, but the i386
> version is usable.
>
I tested it on Windows XP host. But linux.img in linux-test package and
Win2k don't boot.
A strange thing is that when I used RedHat 7.2 guest, user-kqemu is much
slower than no-kqemu.
On Fedora Core 4 host, Win2k boots fine and is faster than user-kqemu and
no-kqemu. Great!
linux.img from linux-test package also works fine with kernel-kqemu,
user-kqemu on FC4 host.
But FC4-i386-rescuecd.iso guest doesn't boot with kernel-kqemu. It works
with user-kqemu and no-kqemu.
I can see about TSC error messages.
Morphix.iso doesn't boot with kernel-kqemu. It works with user-kqemu and
no-kqemu.
I couldn't see booting logo.
And a strange thing is that when I used Redhat 7.2 guest, user-kqemu is much
slower than no-kqemu. And kernel-kqemu is much slower than user-kqemu.
It is the same result as on WinXP host.
I seems that Linux guest doesn't work well.
PS. user-kqemu means no option.
Regards,
Kazu
next prev parent reply other threads:[~2006-02-11 3:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 23:04 [Qemu-devel] -kernel-kqemu Jim C. Brown
2006-02-09 1:27 ` Jim C. Brown
2006-02-09 8:46 ` Hetz Ben Hamo
2006-02-09 18:05 ` Jim C. Brown
2006-02-09 22:01 ` Anthony Liguori
2006-02-09 23:32 ` Phil Krylov
2006-02-10 14:24 ` G Portokalidis
2006-04-19 17:31 ` Troy Benjegerdes
2006-04-21 21:09 ` Brad Campbell
2006-04-24 8:38 ` [Qemu-devel] -kernel-kqemu - bug with -m 256 Dan Sandberg
2006-04-24 13:28 ` [Qemu-devel] -kernel-kqemu - bug with -m 256 <-please disregard Dan Sandberg
2006-04-24 22:31 ` [Qemu-devel] -kernel-kqemu Fabrice Bellard
2006-02-09 18:35 ` Anthony Liguori
2006-02-09 22:01 ` Fabrice Bellard
2006-02-11 3:02 ` Kazu [this message]
2006-02-09 16:27 ` Brad Campbell
2006-02-10 13:29 ` Christian MICHON
2006-02-10 16:18 ` Jim C. Brown
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='002a01c62eb7$95234f90$0464a8c0@athlon' \
--to=kazoo@r3.dion.ne.jp \
--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).