From owner-freebsd-emulation@FreeBSD.ORG Sun May 11 19:27:46 2008 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B0181065675 for ; Sun, 11 May 2008 19:27:46 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from mail.bitblocks.com (bitblocks.com [64.142.15.60]) by mx1.freebsd.org (Postfix) with ESMTP id 2D24C8FC12 for ; Sun, 11 May 2008 19:27:46 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from bitblocks.com (localhost.bitblocks.com [127.0.0.1]) by mail.bitblocks.com (Postfix) with ESMTP id 6F3625B4D; Sun, 11 May 2008 12:27:45 -0700 (PDT) To: Juergen Lock In-reply-to: Your message of "Sun, 11 May 2008 18:07:48 +0200." <20080511160748.GA38480@saturn.kn-bremen.de> Date: Sun, 11 May 2008 12:27:45 -0700 From: Bakul Shah Message-Id: <20080511192745.6F3625B4D@mail.bitblocks.com> Cc: freebsd-emulation@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: seems I finally found what upset kqemu on amd64 SMP... shared gdt! (please test new patch :) X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 May 2008 19:27:46 -0000 Juergen, With your latest patch things are looking pretty good! - Multiple qemus on a MP FreeBSD amd64 works with kqemu enabled for user code. Some running 64 bit kernels (freebsd), some running 32 bit kernels (freebsd and plan9). - Nested qemus work! That is, qemu*x86_64 under qemu*x86_64, both with user mode kqemu. A 32 bit 7.0 kernel under it ran fine. Ideally qemus should nest as long as there is enough memory (a torture test for emulation fidelity). - As mentioned in another thread netbooting works well enough but you have to use pxeboot from -current and append a byte to it to work around an etherboot tftp bug. Now the bugs (probably most having to do with qemu/kqemu, not the freebsd port): 1. kernel mode kqemu seems to cause crashes. Generally this happens right after the guest freebsd kernel comes up. 2. After the above crash VM reboots automatically but now it can't find the root device so it hangs at the root selection prompt. 3. Ocassionally plan9 and (less often FreeBSD) crashes on boot. Looks like a race condition of some sort. If they boot, there are no further problems traceable to qemu/kqemu. 4. "calcru: runtime went backwards from usec to for pid ()" is back! Also, ntpd seems to get very confused and after syncing with another clock shifts mostly correct time by a few hours. 5. An initial getty gets killed as it "exceeded maximum CPU limit" This could an emulation bug or related to time issues. Random thoughts: - If qemu is made scriptable we can automate a lot of testing. For qemu/kqemu and freebsd. - We need to add a section on qemu in the handbook.