the guest network doesn't come up

Question

the guest network doesn't come up

Closed this issue 8 years ago · 8 comments

Hi,

I tried this, and the RHEL image has some problems. Like you mention, the network doesn't come up, no matter how many times I try. The RHEL keeps saying "no suitable device found for this connection.", when I login as vagrant/vagrant and try sudo ifup eth0 or systemctl restart network.

I'm on mac Sierra, Virtualbox is version 5.0.30 r112061, and Vagrant 1.8.7.

I tried with another RHEL box, and it does bring the network up, so likely not vagrant issue. But it fails to restart the network while vagrant tries to bring up eth1 (host only), which again might be vagrant issue with rhel.

I also tried changing the virtio-net drivers for virtual nic, but no help.

Answer 1 · 2016-11-28T10:52:46.000Z

Are you using libvirt when you get these issues? The libvirt config for this VM is mostly untested right now, so if you are using that, give me a few days to test and fix these issues.

If you are using virtualbox and get these errors, check that your vagrant version is 1.8.7. There are issues with network devices on 1.8.6 and earlier that might impact this issue.

Answer 2 · 2016-11-28T12:59:14.000Z

Thanks, I'm on mac, so using virtualbox, and my vagrant is 1.8.7. Any other ideas?

Answer 3 · 2016-11-28T13:40:40.000Z

Same here - was on 1.8.5 hung with the SSH step, same now that I have upgraded to 1.8.7.
reviewed the vbox log and now trying to run vagrant with debug_log - any other ideas on how to troubleshoot?

Answer 4 · 2016-11-28T16:12:30.000Z

@ccustine were we able to get this resolved?

Answer 5 · 2016-11-29T18:14:25.000Z

I can't reproduce this and as far as I know, several others are using this without any issues, so I am trying to figure out what could cause the issue.

Answer 6 · 2016-12-03T03:14:31.000Z

To see what's causing the error for the VM to boot up, you need to enable the vbox GUI: http://stackoverflow.com/questions/22575261/vagrant-stuck-connection-timeout-retrying

For my setup, the underlying issue was that Parallel VM I'm using on Mac creates a 32-bit system w/o VTx support that VBox is looking for. This means, the issue is not the private key or network that I originally thought.

When you enable the VBox gui in the vagrant file, you can at least see the underlying reason for the VM boot failure.

Answer 7 · 2016-12-06T16:57:40.000Z

I was able to fix my ssh key issue and then ran vagrant provision after updating vagrant to 1.8.7 and now I've got the demo running. But need to see a happy path demo here... thanks Ishu

Answer 8 · 2017-02-02T15:38:31.000Z

Thanks, I tested this again and it worked now from that part.