Re: Latest -CURRENT/i386 could not start under VirutalBox 4.1.18

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
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"