Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18 and 4.2 (Windows host): hangs up after atrtc0 detection

From: Ian Lepore <freebsd_at_damnhippie.dyndns.org>
Date: Wed, 19 Sep 2012 16:16:59 -0600
On Wed, 2012-09-19 at 15:10 -0700, Adrian Chadd wrote:
> On 19 September 2012 14:57, Garrett Cooper <yanegomi_at_gmail.com> wrote:
> > On Wed, Sep 19, 2012 at 1:46 PM, Ian Lepore
> > <freebsd_at_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
Received on Wed Sep 19 2012 - 20:17:03 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:30 UTC