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

Hang at Configuring and enabling network interfaces... #8295

Closed
340515991 opened this issue Feb 19, 2017 · 4 comments
Closed

Hang at Configuring and enabling network interfaces... #8295

340515991 opened this issue Feb 19, 2017 · 4 comments

Comments

@340515991
Copy link

340515991 commented Feb 19, 2017

The box is custom by myself use centos 7

Vagrant version

Vagrant 1.9.1

Host operating system

windows10

Guest operating system

centos 7

Vagrantfile

# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure(2) do |config|
    config.vm.define "vbox1" do | dev |
        dev.vm.box = "vbox1"
	dev.ssh.insert_key = false
        dev.ssh.username = "root"
        dev.ssh.password = "123456"
	dev.vm.network "public_network", ip: "192.168.0.100"
        dev.vm.synced_folder "../wwwroot", "/data/wwwroot/"
        dev.vm.provider "virtualbox" do | vb |
            vb.name = "vbox1"
            vb.gui = false
            vb.memory = "256"
        end
    end
end

Debug output

https://github.com/340515991/vagrant/blob/master/debug.log

Expected behavior

What should have happened?

Actual behavior

What actually happened?

Steps to reproduce

1.execute vagrant up vbox1
2.hung at Configuring and enabling network interfaces

@340515991 340515991 changed the title vagrant stuck in Waiting for process to exit. Remaining to timeout: 32000 Hang at Configuring and enabling network interfaces... Feb 19, 2017
@chrisroberts
Copy link
Member

Hi! The debug log shows the machine successfully being transitioned to the up state. Does the error only show up on the initial up when the machine is created? If so, can you please provide the debug log for that? Thanks!

@340515991
Copy link
Author

@famod
Copy link

famod commented Feb 27, 2017

Sounds like #8148. Have you tried reverting to 1.9.0?

@chrisroberts
Copy link
Member

#8148 should be the fix for this and is included in the 1.9.2 release. If you are still encountering the error please feel free to reopen this issue.

Cheers!

@ghost ghost locked and limited conversation to collaborators Apr 4, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants