From owner-freebsd-current@FreeBSD.ORG  Wed Sep 19 22:17:03 2012
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id E3CAD106564A;
	Wed, 19 Sep 2012 22:17:03 +0000 (UTC)
	(envelope-from freebsd@damnhippie.dyndns.org)
Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214])
	by mx1.freebsd.org (Postfix) with ESMTP id 9F5D08FC14;
	Wed, 19 Sep 2012 22:17:03 +0000 (UTC)
Received: from damnhippie.dyndns.org (daffy.symmetricom.us [206.168.13.218])
	by duck.symmetricom.us (8.14.5/8.14.5) with ESMTP id q8JMH2oS061644;
	Wed, 19 Sep 2012 16:17:02 -0600 (MDT)
	(envelope-from freebsd@damnhippie.dyndns.org)
Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240])
	by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id q8JMGxcp059174; 
	Wed, 19 Sep 2012 16:16:59 -0600 (MDT)
	(envelope-from freebsd@damnhippie.dyndns.org)
From: Ian Lepore <freebsd@damnhippie.dyndns.org>
To: Adrian Chadd <adrian@freebsd.org>
In-Reply-To: <CAJ-Vmo=oHti=F8a=kaX=HZFyUjKwg-NaoRE=Ke_ezbVd7iauPQ@mail.gmail.com>
References: <80840563.20120920002200@serebryakov.spb.ru>
	<1252171344.20120920003724@serebryakov.spb.ru>
	<1348087584.95562.55.camel@revolution.hippie.lan>
	<CAGH67wS0pKmEjbHMH3dFPqkzTbEx6tFgBOKzWxGXHfDtap=iGw@mail.gmail.com>
	<CAJ-Vmo=oHti=F8a=kaX=HZFyUjKwg-NaoRE=Ke_ezbVd7iauPQ@mail.gmail.com>
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 19 Sep 2012 16:16:59 -0600
Message-ID: <1348093019.95562.73.camel@revolution.hippie.lan>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port 
Content-Transfer-Encoding: 7bit
Cc: Garrett Cooper <yanegomi@gmail.com>, lev@freebsd.org,
	freebsd-current@freebsd.org
Subject: Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18
 and 4.2 (Windows host): hangs up after atrtc0 detection
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Sep 2012 22:17:04 -0000

On Wed, 2012-09-19 at 15:10 -0700, Adrian Chadd wrote:
> On 19 September 2012 14:57, Garrett Cooper <yanegomi@gmail.com> wrote:
> > On Wed, Sep 19, 2012 at 1:46 PM, Ian Lepore
> > <freebsd@damnhippie.dyndns.org> wrote:
> >
> > ...
> >
> >> Yes, exactly.  I updated the PR to request that my patch not get
> >> committed because it locks up virtualbox.  I hope to find time soon to
> >> learn enough about installing/configuring virtualbox to figure out what
> >> the problem is (offhand,I suspect it hangs in the loop that probes for
> >> the need to re-index, because vbox doesn't quite emulate the hardware
> >> behavior fully).
> >
> >     Why not just detect VBox and disable that functionality? VMware at
> > least has a sane way of determining whether or not you're running it
> > based on the SMBios ident..
> 
> Sure, but that doens't answer the underlying reason(s) of "why is it
> failing?". :-)

Yeah, I'd much rather understand a problem than tap dance around it, at
least for starters.  Figuring out what's really going on may lead to a
discovery that it would fail in other circumstances as well, or it may
lead to a bugfix in vbox if that's where the problem lies.  I'm just a
bit too busy with $work right now to dig into it.

-- Ian