From owner-freebsd-ports@FreeBSD.ORG Fri May 6 22:49:26 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB658106564A; Fri, 6 May 2011 22:49:26 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id EC35D8FC15; Fri, 6 May 2011 22:49:25 +0000 (UTC) Received: by ewy1 with SMTP id 1so1414646ewy.13 for ; Fri, 06 May 2011 15:49:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=HjQ1bXUf4gXMvd7AZjxiHVhuLUijBisNLXXK+pNubu4=; b=ll0MBwXlmV5cR67d51EhbO7VnSCgEA7LlcLv4MAwcvkcnW0dDV6VIqHsRWV0dQDn71 UVqbjMLkqDGTzxGA4vrDvOXflScrsQa5l3dfDv9nEhcJmLtDnqB9UoDtmlTeRniA4gin mJTj90EZoNm+hBi1Itf1rEUv74YRY7iJ4nZUU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=KbOlJAaS5tE+SdFZy2xxa8hai+4cexPlslYHJ9RIDkMp/qNTANtkQGMiQX3noNFirW EuLmXIUbo9WqDEKu3f2FTMnfOg8mWrLcBLfHijS0cjDD2u2zrSqdPrrJNVonbFloFRlg 3at19BOd12t1bGHGmy2sYp0/r1ff3kimPRi04= MIME-Version: 1.0 Received: by 10.213.108.147 with SMTP id f19mr61051ebp.9.1304722163575; Fri, 06 May 2011 15:49:23 -0700 (PDT) Received: by 10.213.25.139 with HTTP; Fri, 6 May 2011 15:49:23 -0700 (PDT) In-Reply-To: References: <430fcb25aefc374bf256e45e3151de15@bluelife.at> <9c0bedf7a0e9f131712e7c3bab754ecd@bluelife.at> Date: Fri, 6 May 2011 18:49:23 -0400 Message-ID: From: Ryan Stone To: Bernhard Froehlich Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: emulation@freebsd.org, ports@freebsd.org Subject: Re: Call for Testers: VirtualBox 4.0.6 (PBIs now available) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2011 22:49:26 -0000 On Fri, May 6, 2011 at 6:47 PM, Ryan Stone wrote: > On Wed, Apr 27, 2011 at 3:28 PM, Ryan Stone wrote: >> (Sorry for the noise earlier about the PBIs not working under PC-BSD; >> I'm not sure how I missed that had been already reported). >> >> I tried the new amd64 PBI and I am able to successfully start VMs now. >> =A0I had one VM(running some relatively recent version of amd64 HEAD) >> boot up fine, but a second one (also running amd64 HEAD, but maybe a >> different svn revision) gets a Guru Meditation during startup. =A0I'm >> not sure what is causing the crash. =A0In their original configurations >> the working VM booted off of an emulated IDE disk while the broken VM >> booted of an emulated SATA disk, however I just tried changing the >> SATA disk to instead be an IDE disk and it doesn't seems to have >> resolved the problem. >> >> I'm not getting a corefile for the crash(or I'm unable to find it). =A0I >> do have kern.sugid_coredump=3D1 and I'm running the PBI. =A0Is this >> expected for a Guru Meditation, or should it be putting a core >> somewhere? =A0I've put the VBox.log for the most recent crash here: >> >> http://people.freebsd.org/~rstone/vbox-4.0.6/VBox.log >> >> This seems to be easy to reproduce so let me know if there's any more >> information that I can gather. >> >> >> Also, the working VM was emulating uniprocessor machine. =A0I tried >> adding a second CPU and that VM started crashing, too. =A0I tried >> changing the broken VM to have only one core but it still crashes. >> I'm not sure if it's related to the first crash or not. >> > > To follow up, I tried playing around with the "working" VM > configuration. =A0I can only make it fail if I emulate a machine with > multiple processors and I leave SMP enabled in the kernel. =A0If I > either emulate a uniprocessor machine or disable SMP via tunable, the > VM is able to boot without crashing. > > To summarize, I believe that I am running into two separate issues > with VirtualBox 4.0.6: > - Booting off of an emulated SATA drive leads to crashes during boot: > http://people.freebsd.org/~rstone/vbox-4.0.6/VBox.log (Guru Meditation > -4001 (VERR_VMX_INVALID_VMCS_PTR) > ) > - Booting a VM with multiple virtual processors on a kernel with SMP > enabled crashes during boot: > http://people.freebsd.org/~rstone/vbox-4.0.6/VBox-SMP.log (Guru > Meditation -4002 (VERR_VMX_INVALID_VMXON_PTR)) > It occurs to me that I've left out a very important piece of information. I was previously able to boot the SATA, dual-core VM under VirtualBox 4.0.4, so this is a very recent regression.