All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Campbell <brad@wasp.net.au>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] kernel-kqemu and linux
Date: Tue, 21 Mar 2006 15:13:20 +0400	[thread overview]
Message-ID: <441FDFD0.9020706@wasp.net.au> (raw)
In-Reply-To: <441F999A.4060807@wasp.net.au>

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

  reply	other threads:[~2006-03-21 11:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-17  8:25 [Qemu-devel] kernel-kqemu and linux Kevin F. Quinn
2006-03-20 23:39 ` Fabrice Bellard
2006-03-21  6:13   ` Brad Campbell
2006-03-21 11:13     ` Brad Campbell [this message]
2006-03-21 17:10       ` Pascal Terjan
2006-03-21  7:48   ` Kevin F. Quinn

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=441FDFD0.9020706@wasp.net.au \
    --to=brad@wasp.net.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.