VMs don't work at all on non-VT-x CPUs #138

Closed
CoJaBo opened this Issue Mar 31, 2013 · 2 comments

Projects

None yet

2 participants

CoJaBo commented Mar 31, 2013

The created VM images appear to have VT-x turned on; there is no way to turn this off, as the setting to do so is disabled unless the CPU supports VT-x (this seems like a VBox bug, but it apparently dates back at least 2 years). The command line tool does not appear to work either. There is no way to use the VMs at all, as the setting cannot be turned off by any means I could find; if theres a workaround, I'd love to hear it.

CoJaBo commented Mar 31, 2013

The only workaround I could find was to simply delete the VMs, create them again (using the existing disk images), then create new snapshots for each.

Owner

Latest version requires VirtualBox 5.0. Reopen if this issue persists.

@xdissent xdissent closed this Aug 24, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment