Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dvm starts but times out trying to communicate with box #14

Closed
binaryphile opened this issue Feb 1, 2014 · 1 comment
Closed

dvm starts but times out trying to communicate with box #14

binaryphile opened this issue Feb 1, 2014 · 1 comment

Comments

@binaryphile
Copy link

I'm on Ubuntu 13.10, Vagrant 1.4.3 and Docker 0.7.6.

I did the install, which btw created the .dvm directory as root and prevented me from running dvm up as a regular user.

After chmod -R me:me .dvm, I was able to run dvm up, but I just get the long "Timed out while waiting for the machine to boot" message.

dvm status shows the machine as up, but dvm ssh doesn't work either. dvm destroy seems to work ok though.

Separate question: does dvm work in windows?

@binaryphile
Copy link
Author

I now believe this is due to my machine not supporting vt-x extensions. Running the native boot2docker script directly and this error message came up:

VBoxManage: error: VT-x is not available. (VERR_VMX_NO_VMX)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component Console, interface IConsole

I believe this was happening here as well but the error message wasn't coming up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant