From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Is39x-0006Id-Vx for qemu-devel@nongnu.org; Tue, 13 Nov 2007 16:19:02 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Is39w-0006Fm-B8 for qemu-devel@nongnu.org; Tue, 13 Nov 2007 16:19:00 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Is39v-0006F9-SR for qemu-devel@nongnu.org; Tue, 13 Nov 2007 16:18:59 -0500 Received: from mail62.opentransfer.com ([76.162.254.62]) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1Is39v-0005GR-6r for qemu-devel@nongnu.org; Tue, 13 Nov 2007 16:18:59 -0500 Received: from [127.0.0.1] (localhost [127.0.0.1]) by gateway.localdomain (Postfix) with ESMTP id 75ECB269757 for ; Tue, 13 Nov 2007 16:18:50 -0500 (EST) Message-ID: <473A14B9.4080606@mmri.us> Date: Tue, 13 Nov 2007 16:18:49 -0500 From: "admin@mmri.us" MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: KQemu require Intel VT or AMD-V processors ? References: <4739F007.50301@mmri.us> <473A0C49.3070209@mmri.us> <200711131455.39062.rickv@hobi.com> In-Reply-To: <200711131455.39062.rickv@hobi.com> Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Hi Rick, I did that
$]qemu -hda WinXP_Home.img -kernel-kqemu -net nic,model=rtl8139 -net user -cdrom software.iso
Still the same.
Maybe the Macs do not reneder fast enough but I doubt it.

It is no sweat really, it is usable for one BIG reason.
Since Win4Lin does not support ntdll.dll newdev.dll etc it just dont work with custom device drivers.
Qemu has no problems and custom drivers works great which was a surprise.
Win4Lin has blazing speed, but Vmware is not much faster than qemu anyway, so it is unfair for me to critisize.

Rick Vernam wrote:

On Tuesday 13 November 2007 02:42:49 pm admin@mmri.us wrote:

Ok I see what went wrong.
I accidentally had a XEN kernel still running so insmod did not work.
Now it works and the message disappeared.

But, kqemu is not much faster than qemu. I perceive about 1.5x over a
1gbit network  to a terminal through an x session.
It is much much slower than win4lin, but it is free and
I can live with it under most applications except streaming.
Is there something I could have done wrong?

not necessarily wrong, but try qemu with the -kernel-kqemu command line 
option - ie, qemu -kernel-kqemu -hda WinXP_Home.img