From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LdUgE-00009V-EA for qemu-devel@nongnu.org; Sat, 28 Feb 2009 14:16:58 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LdUgC-00008u-JO for qemu-devel@nongnu.org; Sat, 28 Feb 2009 14:16:57 -0500 Received: from [199.232.76.173] (port=50896 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LdUgC-00008r-HQ for qemu-devel@nongnu.org; Sat, 28 Feb 2009 14:16:56 -0500 Received: from mout5.freenet.de ([195.4.92.95]:57638) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LdUgC-000239-7c for qemu-devel@nongnu.org; Sat, 28 Feb 2009 14:16:56 -0500 Date: Sat, 28 Feb 2009 20:16:50 +0100 From: Gary Jennejohn Message-ID: <20090228201650.064c0ee4@ernst.jennejohn.org> In-Reply-To: <20090228171520.GA56888@saturn.kn-bremen.de> References: <20090225201550.3d3032b5@ernst.jennejohn.org> <20090228171520.GA56888@saturn.kn-bremen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: testing qemu svn r6636 on FreeBSD; future of qemu on FreeBSD... Reply-To: gary.jennejohn@freenet.de, qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Juergen Lock Cc: freebsd-emulation@FreeBSD.org, freebsd-current@FreeBSD.org, qemu-devel@nongnu.org On Sat, 28 Feb 2009 18:15:20 +0100 Juergen Lock wrote: > On Wed, Feb 25, 2009 at 08:15:50PM +0100, Gary Jennejohn wrote: > > On Mon, 23 Feb 2009 22:19:33 +0100 > > Juergen Lock wrote: > > > > > You could try a few things: > > > a) the same with kqemu (userland), in case its a tcg bug (or indeed a > > > timeout; remember to rebuild qemu in case you built it without the > > > kqemu knob enabled or otherwise kqemu won't get used), and also > > > b) another time with -kernel-kqemu in case its a tcg bug affecting > > > guest kernel code (altho of course in both cases kqemu can cause its > > > own kind of failures, even more so with amd64 guests...) > > > > > > > Neither of these work. The only way I can get past loading the kernel > > is with -no-kqemu. > > > > I still see the segmentation fault in Yast.call. Now I know that it's > > in line 486, if that's of any interest. > > > > Sorry, I'm not going to invest any more time in this. > > Thanx. Can someone else verify that kqemu still works on FreeBSD-current? > I went back to openSUSE with the standard qemu-devel. I found that I could (usually) boot w/o problems if I put -no-acpi on the CL. Right now I have openSUSE runngin pretty well. It's nearly as fast as on my old (genuine) IBM X31 laptop :) > It is possible that you got hit by the kqemu tsc vs smp problem, i.e. > passing `notsc' to the guest kernel or forcing qemu onto one cpu > (cpuset -l 0 qemu ...) may have helped there, sorry I should have thought > of that earlier... > I just tried these suggestions (with the standard qemu-devel) and they don't seem to do any harm :-P > Also, did I get that right that this opensuse 10.3 install worked with > the original qemu-devel port (without kqemu)? So we do seem to have a > regression here... (thats a 20080620 qemu svn snapshot, for the folks > on the qemu list.) > See above. Now I'm thinking about giving the patched qemu-devel another try, since I've found some workarounds for booting. I'll see whether I can at least boot into the installed openSUSE using it. --- Gary Jennejohn