From owner-freebsd-emulation@FreeBSD.ORG Tue Jun 8 22:14:13 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 A0A461065670 for ; Tue, 8 Jun 2010 22:14:13 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id 7E0FA8FC17 for ; Tue, 8 Jun 2010 22:14:13 +0000 (UTC) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1OM73l-0007IV-3L for freebsd-emulation@freebsd.org; Tue, 08 Jun 2010 15:14:13 -0700 Message-ID: <28823754.post@talk.nabble.com> Date: Tue, 8 Jun 2010 15:14:13 -0700 (PDT) From: Hubert Tournier To: freebsd-emulation@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: hubert@frbsd.org Subject: Panic with FreeBSD Guest in FreeBSD VirtualBox host 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: Tue, 08 Jun 2010 22:14:13 -0000 Hello, I noticed that FreeBSD guests (either i386 or amd64, release 7.x or 8.x, even freshly installed from the install CD) running in VirtualBox (3.1.4 to 3.2.2) on FreeBSD hosts (only tested on 8.0pX amd64, but on 4 machines with different hardware) panic during the boot sequence, just after the "Starting cron" message, and enter an endless loop of reboots: http://old.nabble.com/file/p28823754/panic1.png The same VMs work fine on VirtualBox (any version) on a Windows XP guest, and used to work on VirtualBox 3.1.2 on a FreeBSD host. I can boot a blank VM with the FreeBSD install CD and proceed with installation, but the problem occurs during the first reboot of the installed system. I've no troubles with VM guests using Linuxes (CentOS, Ubuntu, Red Hat) or Windows (XP, 2008). With some additional debug messages, i've seen that the problem happens in /etc/rc.d/mixer: http://old.nabble.com/file/p28823754/panic2.png So, i put a mixer_enable="NO" in /etc/rc.conf and was able to complete the boot sequence. Unfortunately, a few commands later, even doing a simple "ls", the VM panics again. I tried with a generic kernel instead of a custom one, and an unmodified VirtualBox port, but got the same results. Any idea? Are there other people encountering this? Best regards, Hubert PS: if needed, i can provide root access to an Internet server where the problem happens, to the vbox team. PPS: i haven't filed a PR for this, but can do if wanted. -- View this message in context: http://old.nabble.com/Panic-with-FreeBSD-Guest-in-FreeBSD-VirtualBox-host-tp28823754p28823754.html Sent from the freebsd-emulation mailing list archive at Nabble.com.