From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FLen3-0003Ez-0L for qemu-devel@nongnu.org; Tue, 21 Mar 2006 06:12:41 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FLen2-0003Eb-35 for qemu-devel@nongnu.org; Tue, 21 Mar 2006 06:12:40 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FLen2-0003EY-05 for qemu-devel@nongnu.org; Tue, 21 Mar 2006 06:12:40 -0500 Received: from [203.190.192.17] (helo=wasp.net.au) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FLen2-0007f3-Ug for qemu-devel@nongnu.org; Tue, 21 Mar 2006 06:12:41 -0500 Message-ID: <441FDFD0.9020706@wasp.net.au> Date: Tue, 21 Mar 2006 15:13:20 +0400 From: Brad Campbell MIME-Version: 1.0 Subject: Re: [Qemu-devel] kernel-kqemu and linux References: <20060317092540.20fd5e7a@c1358217.kevquinn.com> <441F3D23.8080008@bellard.org> <441F999A.4060807@wasp.net.au> In-Reply-To: <441F999A.4060807@wasp.net.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 Brad Campbell wrote: > Fabrice Bellard wrote: >> Try the following patch: >> >> diff -u -w -r1.39 helper2.c >> --- helper2.c 4 Dec 2005 18:46:06 -0000 1.39 >> +++ helper2.c 20 Mar 2006 23:38:51 -0000 >> @@ -110,6 +110,7 @@ >> env->pat = 0x0007040600070406ULL; >> env->cpuid_ext_features = 0; >> env->cpuid_features |= CPUID_FXSR | CPUID_MMX | CPUID_SSE | >> CPUID_SSE2 >> | CPUID_PAE | CPUID_SEP; >> + env->cpuid_features |= CPUID_APIC; /* TEST */ >> env->cpuid_xlevel = 0; >> { >> const char *model_id = "QEMU Virtual CPU version " >> QEMU_VERSION; >> >> If it works then APIC usage will become the default on i386... >> > > I'm afraid that makes no difference at all here.. > PIII-M linux host and both 2.4 compiled for i386 and 2.6 compiled for > PII linux guests More information here.. http://fnarfbargle.dyndns.org:81/qemu-oops/qemu.oops.log http://fnarfbargle.dyndns.org:81/qemu-oops/qemu.oops.log.2 Neat trick for capturing such groovy stuff.. In one console :- cat /dev/ptyzf | tee qemu.oops.log In another console :- qemu -hda vm-1.img -kernel /tracks/linux-2.6.15.6/arch/i386/boot/bzImage -serial /dev/ttyzf -append "console=ttyS0" -m 64 -kernel-kqemu Regards, Brad (who just learned about pseudo terminal devices) -- "Human beings, who are almost unique in having the ability to learn from the experience of others, are also remarkable for their apparent disinclination to do so." -- Douglas Adams