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

ubuntu1604/vmware_fusion - Startup timesout #60

Closed
yogendra opened this issue Apr 27, 2016 · 3 comments
Closed

ubuntu1604/vmware_fusion - Startup timesout #60

yogendra opened this issue Apr 27, 2016 · 3 comments

Comments

@yogendra
Copy link

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 of ens32.

VAGRANT_INFO=info vagrant up
....
....

 INFO vmware_driver: Reading VMX data...
 INFO vmware_driver: Reading DHCP lease for '00:0c:29:2f:98:43' on 'vmnet8'
 INFO vmware_driver: DHCP leases file: [#<Pathname:/var/db/vmware/vmnet-dhcpd-vmnet8.leases>, #<Pathname:/var/db/vmware/vmnet-dhcpd-vmnet8.leases~>]
 INFO dhcp_lease_file: Initialized DHCP helper: /var/db/vmware/vmnet-dhcpd-vmnet8.leases
 INFO dhcp_lease_file: Looking for IP for MAC: 00:0c:29:2f:98:43
 INFO dhcp_lease_file:   - IP:
 INFO dhcp_lease_file: Initialized DHCP helper: /var/db/vmware/vmnet-dhcpd-vmnet8.leases~
 INFO dhcp_lease_file: Looking for IP for MAC: 00:0c:29:2f:98:43
 INFO dhcp_lease_file:   - IP:
....

I manually updated file /etc/network/interfaces and change ens33 to ens32.
Then I brought up interface using sudo ifup ens32

So, question is how to make this change permanent? Of is my VMware messed up?

@rickard-von-essen
Copy link
Contributor

See chef/bento#554 and related PR.

@hmahmood
Copy link

Any updates on this?

@cbednarski
Copy link

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.

gtrafimenkov pushed a commit to gtrafimenkov/vagrant-boxes that referenced this issue Mar 19, 2018
Debian 9 new image and some corrections
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

5 participants