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

From: Adrian Chadd <adrian_at_freebsd.org>
Date: Wed, 19 Sep 2012 15:10:38 -0700
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?". :-)


Adrian
Received on Wed Sep 19 2012 - 20:10:39 UTC

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