From: Werner Dittmann <Werner.Dittmann@t-online.de>
To: balrogg@gmail.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu / KQemu on 64-bit (x86_64) host systems
Date: Tue, 17 Apr 2007 20:34:09 +0200 [thread overview]
Message-ID: <46251321.5050803@t-online.de> (raw)
In-Reply-To: <fb249edb0704162205xa0133a7m5e48cadfbecf065c@mail.gmail.com>
andrzej zaborowski wrote:
> Hi,
>
> On 16/04/07, Werner Dittmann <Werner.Dittmann@t-online.de> wrote:
>> During several tests with Qemu / Kqemu it seems that Qemu
>> has problems with x86_64 host systems. My system is an
>> AMD 64 X2 (Dual Core), running openSUSE 10.2, 2GB memory.
>>
Indeed it is a dual CPU. Adding notsc as an additional parameter to
the kernel commandline (the guest system uses Lilo). Using this
parameter the kernel was able to start INIT and the init.d startup
scripts (not always, but most of the time). After a short time
the kernel starts to loop again, e.g. during hotplug handling.
Using th same technique as before (gdb) it's the same picture:
mainly in compute_c_subl or compute_c_addl.
>
> Does your host happen to be dual-core? If so, please try adding
> "notsc" to the guest kernel commandline and report if it makes a
> difference.
>
>>
I thought qemu's gdb server is used to debug kernels running
inside Qemu but not to debug Qemu itself. IMHO the problem is not
in the kernel (the kernel works perfectly on a real HW processor)
but in Qemu.
>
> Use qemu's gdb server, it's documented.
>
>>
>>
>>
>
> Regards,
> Andrzej
>
Regards,
Werner
next prev parent reply other threads:[~2007-04-17 18:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-16 6:47 [Qemu-devel] Qemu / KQemu on 64-bit (x86_64) host systems Werner Dittmann
2007-04-17 5:05 ` andrzej zaborowski
2007-04-17 18:34 ` Werner Dittmann [this message]
2007-04-17 20:02 ` andrzej zaborowski
2007-04-18 19:26 ` Werner Dittmann
2007-04-18 19:44 ` Werner Dittmann
2007-04-18 20:05 ` andrzej zaborowski
2007-04-19 15:25 ` Werner Dittmann
2007-04-19 17:08 ` andrzej zaborowski
2007-04-20 14:28 ` Werner Dittmann
2007-04-22 10:18 ` Werner Dittmann
2007-04-17 11:26 ` Bernhard Kauer
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=46251321.5050803@t-online.de \
--to=werner.dittmann@t-online.de \
--cc=balrogg@gmail.com \
--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).