We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
chmod -R me:me .dvm
dvm up
dvm status shows the machine as up, but dvm ssh doesn't work either. dvm destroy seems to work ok though.
dvm status
dvm ssh
dvm destroy
Separate question: does dvm work in windows?
The text was updated successfully, but these errors were encountered:
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.
Sorry, something went wrong.
No branches or pull requests
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 rundvm up
, but I just get the long "Timed out while waiting for the machine to boot" message.dvm status
shows the machine as up, butdvm ssh
doesn't work either.dvm destroy
seems to work ok though.Separate question: does dvm work in windows?
The text was updated successfully, but these errors were encountered: