-
-
Notifications
You must be signed in to change notification settings - Fork 304
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
Fixes #13: errors with Machine not booting for VMWare Ubuntu 16.04 #17
Conversation
Will review, thanks! |
Ah, I was wondering why the fix wasn't working... then realized I didn't apply this branch :P |
This got it further, but I'm now getting:
|
After a
|
Somewhat related? hashicorp/vagrant#7070 |
That's weird. I have this fix up and running over for the development team right now. I don't think issue 7070 is related. I wouldn't also like to waste time on this, virtualbox does a great job even though it is slower for file syncing. |
@zaiddabaeen - I typically either use NFS or rsync, so the performance is close to identical (in terms of file access) on VirtualBox. If using native shared folders, then it's a pretty vast difference (in VMware's favor)—but I can't support a box that doesn't offer NFS support out of the box, and that seems to be one of the main difficulties for VMware and the Vagrant plugin right now :/ |
See: #42 |
No description provided.