From owner-freebsd-emulation@FreeBSD.ORG Fri Jun 18 17:47:19 2010 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 46D2A106568F for ; Fri, 18 Jun 2010 17:47:19 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 8F5D48FC14 for ; Fri, 18 Jun 2010 17:47:18 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id UAA23863; Fri, 18 Jun 2010 20:47:13 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4C1BB121.8070409@icyb.net.ua> Date: Fri, 18 Jun 2010 20:47:13 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.24 (X11/20100517) MIME-Version: 1.0 To: Kris Moore References: <4C1BA8A9.5050504@pcbsd.org> In-Reply-To: <4C1BA8A9.5050504@pcbsd.org> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-emulation@freebsd.org Subject: Re: VirtualBox 3.2.4 Kernel Panic at Boot 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: Fri, 18 Jun 2010 17:47:19 -0000 on 18/06/2010 20:11 Kris Moore said the following: > > Running VirtualBox 3.2.4 here on 8.1-Beta1 - amd64: > > FreeBSD pcbsd-5315 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #1: Tue Jun 1 > 22:41:58 UTC 2010 > root@build8x64.pcbsd.org:/usr/obj/storage/builds/pcbsd-build81-x64/fbsd-source/8.1/sys/PCBSD > amd64 > > Got the new VB 3.2.4 built, and installed. Works just fine when I first > load and kldload the modules. However when I go to reboot, the vbox > modules are causing a kernel panic almost immediately after ZFS inits: > > http://www.pcbsd.org/~kris/VBoxCrash3.2.4.jpg [snip] > > > Any ideas? Yes. Try to obtain a crash dump by configuring a dump device. At the very least add KDB_TRACE and its dependencies to your kernel config. Otherwise we would mostly be shooting in the dark. -- Andriy Gapon