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

errors starting vm on windows 7 #7

Closed
fractal76 opened this issue Aug 10, 2015 · 1 comment
Closed

errors starting vm on windows 7 #7

fractal76 opened this issue Aug 10, 2015 · 1 comment
Assignees

Comments

@fractal76
Copy link

c:> .\VBoxHeadless.exe --startvm playground-vm

Error:

Error: failed to start machine. 
Error message: NamedPipe#0 failed to create named pipe 
\home\brandon\.boot2docker\boot2docker-vm.sock (VERR_INVALID_NAME)
@brandon-rhodes
Copy link
Owner

All right!

After months of trying to work around this problem — and after several conversations with people who have more experience with virtualization than I do — I have deprecated my original scheme of distributing a bare VirtualBox image and expecting it to run across multiple operating systems correctly, especially with network forwarding turned on.

I have just rebuilt, repackaged, and re-uploaded the Playground as a Vagrant box, because Vagrant had a reputation for doing a better job of supporting cross-platform image support than do any of the raw native back-end mechanisms for virtualization like VirtualBox.

I have amended the Playground instructions to explain starting up a Vagrant box:

https://github.com/brandon-rhodes/fopnp/tree/m/playground

Could you try out the instructions and let me know if they work on your platform and, if not, at which step they fail? Thanks so much!

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

2 participants