Date: Wed, 19 Sep 2012 14:57:30 -0700 From: Garrett Cooper <yanegomi@gmail.com> To: Ian Lepore <freebsd@damnhippie.dyndns.org> Cc: 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 Message-ID: <CAGH67wS0pKmEjbHMH3dFPqkzTbEx6tFgBOKzWxGXHfDtap=iGw@mail.gmail.com> In-Reply-To: <1348087584.95562.55.camel@revolution.hippie.lan> References: <80840563.20120920002200@serebryakov.spb.ru> <1252171344.20120920003724@serebryakov.spb.ru> <1348087584.95562.55.camel@revolution.hippie.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
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..
Thanks!
-Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGH67wS0pKmEjbHMH3dFPqkzTbEx6tFgBOKzWxGXHfDtap=iGw>