From owner-freebsd-emulation@FreeBSD.ORG Thu Apr 1 00:13:18 2004 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA4D316A4CE for ; Thu, 1 Apr 2004 00:13:18 -0800 (PST) Received: from oxyd.caraldi.com (caraldi.com [195.137.249.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5903F43D45 for ; Thu, 1 Apr 2004 00:13:18 -0800 (PST) (envelope-from jbq@anyware-tech.com) Received: from anyware12.anyware (unknown [217.112.237.100]) by oxyd.caraldi.com (Postfix) with ESMTP id 51E702107; Thu, 1 Apr 2004 10:13:16 +0200 (CEST) Received: by anyware12.anyware (Postfix, from userid 1001) id 4668F62E5; Thu, 1 Apr 2004 10:13:15 +0200 (CEST) Date: Thu, 1 Apr 2004 10:13:15 +0200 From: Jean-Baptiste Quenot To: Mike Silbersack Message-ID: <20040401081311.GA32457@anyware12.anyware> Mail-Followup-To: Jean-Baptiste Quenot , Mike Silbersack , orlando.bassotto@ieo-research.it, emulation@freebsd.org References: <20040324174618.GA18920@anyware12.anyware> <20040331214459.F657@odysseus.silby.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040331214459.F657@odysseus.silby.com> User-Agent: Mutt/1.5.6i cc: emulation@freebsd.org cc: orlando.bassotto@ieo-research.it Subject: Re: VMware3 on recent 5.2-CURRENT X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.1 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: Thu, 01 Apr 2004 08:13:18 -0000 * Mike Silbersack: > On Wed, 24 Mar 2004, Jean-Baptiste Quenot wrote: > > > I read your [1]problem report about VMWare crashing when starting a > > virtual machine on FreeBSD 5.2. I use FreeBSD 5.2.1-RELEASE with > > vmware3, and it keeps crashing the whole system as soon as I power > > the VM on, no matter the guest OS is. > > > > Have you been able to run VMWare successfully? Should I simply > > remove WITNESS from the kernel config? > > I just tested -current with WITNESS enabled, and the only witness > warning that vmware caused was a warning in the sound driver. VMWare > continued to run properly, I saw no lockup. > > My assumption is that there is some locking bug in 5.2.1 that has > since been fixed, so you may have to cvsup to -current in order to get > vmware to work better. Since I upgraded to 5.2-CURRENT, the system crashes as soon as the vmmon module is loaded, with or without WITNESS. Disabling ACPI by typing 2 at the boot prompt does not help either. Please find below some transcriptions of the panics. If you need complete stack traces, I can manage to do it... ------------------------------------------------------------------------ Booting with WITNESS disabled ------------------------------------------------------------------------ on pre-existing device (maj=0, min=0, name=console) at line 495 in file /usr/src/sys/kern/kern_conf.c cpuid=0; db> trace __panic make_dev +0x98 init_module +0x83 vmmon_modevent +0x2d module_register_init +0x5a linker_file_sysinit +0x7d linker_load_file +0xdd linker_load_module kldload syscall db> panic Fatal trap 3: breakpoint instruction fault while in kernel mode ------------------------------------------------------------------------ Booting with WITNESS enabled ------------------------------------------------------------------------ panic: _mtx_lock_sleep: recursed on non-recursive mutex at line 79 in file /usr/src/sys/kern/kern_conf.c Fatal trap 12: page fault while in kernel mode -- Jean-Baptiste Quenot http://caraldi.com/jbq/