-
Notifications
You must be signed in to change notification settings - Fork 31
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
public_network not being configured for DHCP or default route #26
Comments
Thanks for the report! I don't quite know how those guest setup bits and pieces are supposed to work, so I'll need to investigate that. We're probably just missing a call to some vagrant library function during the 'up' action. I'll investigate a bit more and see what I can find. |
Actually this might be a problem with XenServer needing some extra configuration. Could you try executing the following on your xenserver then recreating your vagrant box: net=`xe network-list other-config:is_host_internal_management_network=true --minimal`
xe network-param-set uuid=$net other-config:ip_disable_gw=true This should prevent the internal network from advertising itself as a gateway. If this works, I'll add it to the README, or possibly even detect it in the plugin. |
After executing those commands and destroying/upping the VM, the situation is different but
|
I'm not well versed in the responsibilities of vagrant providers vs. vagrant itself, but it appears that the xenserver provider is missing something to make
public_network
s work correctly. Vagrant's documentation says the following configuration will add a public network interface to the VM, and allow its DHCP configuration to set the default route for the system:With Virtualbox
In my case I am using an ubuntu box file. When I up the VM using the virtualbox provider, the
eth1
interface is correctly configured for DHCP, and its route is the default route for the system. As such, from the VM I can ping hosts on the Internet.With XenServer
When I up the VM with the xenserver provider, the VM does have a second interface (
eth1
). However,eth1
is unconfigured. The result is that the VM cannot access the Internet, because its default route is through the private NAT interface that Vagrant uses.In the guest, I found the configuration difference in
/etc/network/interfaces
. When the VM is upped using the virtualbox provider, the file contains a block with#VAGRANT-BEGIN
/#VAGRANT-END
, which I believe comes from https://github.com/mitchellh/vagrant/blob/master/templates/guests/debian/network_dhcp.erb. When the VM is upped using the xenserver provider, the file contains nothing from Vagrant.I'm using vagrant 1.8.1 on Mac OS 10.10.
The text was updated successfully, but these errors were encountered: