On Wed, 19 Sep 2012 14:57:30 -0700, Garrett Cooper 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.. VMware (as well as KVM and Xen) provides reliable way to detect its presence by checking "hypervisor present" CPUID's bit or accessing its I/O port, while VirtualBox doesn't do that, and matching SMBios ident doesn't seem to be really useful. Are there better and reliable ways of detecting VirtualBox?Received on Wed Sep 19 2012 - 20:24:03 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:30 UTC