-
Notifications
You must be signed in to change notification settings - Fork 374
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
ubuntu1604/vmware_fusion - Startup timesout #60
Comments
See chef/bento#554 and related PR. |
Any updates on this? |
Hey folks, I hacked around this inside the OS: https://github.com/cbednarski/packer-ubuntu/blob/master/scripts-1604/vm_cleanup.sh#L9-L15 There seems to be some idiosyncrasy between packer, vagrant, and the guest OS version. I'm not really sure if there's a way to magically fix this without some OS-specific switching in Vagrant or Packer, so for now I've worked around it in the provisioning process. |
Debian 9 new image and some corrections
I was trying to start a vm with ubuntu1604 box. I don't have anything else in Vagrantfile, except config.vm.box line. When I start vm using vagrant up, I gets stuck on "Waiting for machine to boot." message for a while, and then just throws an error stating increase timeout.
After a bit of trial and error with following command, I found that in the interfaces file,
ens33
interface is configured instead ofens32
.I manually updated file
/etc/network/interfaces
and changeens33
toens32
.Then I brought up interface using
sudo ifup ens32
So, question is how to make this change permanent? Of is my VMware messed up?
The text was updated successfully, but these errors were encountered: