From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HeFso-0006ot-A6 for qemu-devel@nongnu.org; Wed, 18 Apr 2007 15:32:02 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HeFsn-0006oS-N2 for qemu-devel@nongnu.org; Wed, 18 Apr 2007 15:32:01 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HeFsn-0006oE-Is for qemu-devel@nongnu.org; Wed, 18 Apr 2007 15:32:01 -0400 Received: from mailout06.sul.t-online.com ([194.25.134.19]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HeFnv-0006SK-3g for qemu-devel@nongnu.org; Wed, 18 Apr 2007 15:26:59 -0400 Message-ID: <462670E9.40100@t-online.de> Date: Wed, 18 Apr 2007 21:26:33 +0200 From: Werner Dittmann MIME-Version: 1.0 Subject: Re: [Qemu-devel] Qemu / KQemu on 64-bit (x86_64) host systems References: <46231BEB.5070402@t-online.de> <46251321.5050803@t-online.de> In-Reply-To: Content-Type: text/plain; charset=UTF-8 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: balrogg@gmail.com, qemu-devel@nongnu.org Andrzej, setting "notsc" makes the difference (yesterday I forgot to start lilo after modifying /etc/lilo.conf to include notsc"). Now it work even with -kernel-kqemu. Not fully tested though, but much better than before. Thanks, Werner andrzej zaborowski wrote: > Hi, > > On 17/04/07, Werner Dittmann wrote: >> andrzej zaborowski wrote: >> > Hi, >> > >> > On 16/04/07, Werner Dittmann 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. > > Hmm, I was thinking that it may be the same problem as I described in > http://lists.gnu.org/archive/html/qemu-devel/2007-03/msg00652.html but > if the lockup is happening anyway then I'm not sure. On the other hand > "notsc" does make a difference, right? > >> >> 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. > > That's right, qemu's gdb server is for debugging the guest. However, > it's often much easier to debug qemu knowing what guest code is > causing the qemu bug, especially C code in case of opensource guests, > and especially a guest lockup or guest crash. > > Other than that I think there's only the -d. > > Regards, > Andrzej > > >