-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Vagrant Up failing to apply network configuration #12553
Comments
Downgrading to VirtualBox version v6.1.26 fixed the problem for me. |
I open a ticket on Oracle VirtualBox bug tracker because of the main problem is when following command is run:
Virtualbox 2.1.28 imposes additional control on the addresses that can be set for host-only interfaces. According to the VirtualBox docs you can fix it running the following command (the folder /etc/vbox must already exist):
Anyway, is it possible to setup Vagrant (currently version or a new one) to create new private_networks within the CIDR 192.68.56.0/21? CIDR allowed by default on VirtualBox 2.1.28 regarding on VirtualBox docs Regards. |
This unfortunate typo is at least limited to the VirtualBox documentation, should be |
Yes, a small mistake :P, and that's correct, the CIDR is 192.168.56.0/21 regarding on Virtualbox docs Thanks to clarificate it Anyway, any response from Vagrant team about the question? |
Linked PR addresses this issue. We won't automatically modify the configuration file on the host, but we can validate the configured address, and if it's not within the allowed ranges found it will kick out an error and provide information on how to enable more ranges. |
hashicorp/vagrant#12553 (comment) > Anyway, is it possible to setup Vagrant (currently version or a new > one) to create new private_networks within the CIDR 192.68.56.0/21? > CIDR allowed by default on VirtualBox 2.1.28 regarding on VirtualBox > docs This unfortunate typo is at least limited to the VirtualBox documentation, should be 192.168.56.0/21. https://www.virtualbox.org/manual/ch06.html#network_hostonly > On Linux, Mac OS X and Solaris Oracle VM VirtualBox will only allow IP > addresses in 192.68.56.0/21 range to be assigned to host-only > adapters.
Vagrant version: Vagrant 2.2.18
Host operating system: Garuda Linux, kernel 5.10.75-1-lts
Guest operating system: Ubuntu Xenial ceph/ubuntu-xenial
Provider: virtualbox
VirtualBox version: v6.1.28
Vagrantfile:
Debug output: attached to issue
Provide a link to a GitHub Gist containing the complete debug output:
https://www.vagrantup.com/docs/other/debugging.html. The debug output should
be very long. Do NOT paste the debug output in the issue, just paste the
link to the Gist.
Expected behavior:
6x Ubuntu Xenials guests should populate into VirtualBox
Actual behavior:
vboxmanage fails to apply network configuration.
Steps to reproduce
vagrant-debug.txt
For brevity, the exact error encountered is:
─$ vagrant up
Bringing machine 'mon0' up with 'virtualbox' provider...
Bringing machine 'mon1' up with 'virtualbox' provider...
Bringing machine 'mon2' up with 'virtualbox' provider...
Bringing machine 'osd0' up with 'virtualbox' provider...
Bringing machine 'osd1' up with 'virtualbox' provider...
Bringing machine 'osd2' up with 'virtualbox' provider...
==> mon0: Checking if box 'ceph/ubuntu-xenial' version '0.0.1' is up to date...
==> mon0: Clearing any previously set network interfaces...
There was an error while executing
VBoxManage
, a CLI used by Vagrantfor controlling VirtualBox. The command and stderr is shown below.
Command: ["hostonlyif", "ipconfig", "vboxnet6", "--ip", "192.168.100.1", "--netmask", "255.255.255.0"]
Stderr: VBoxManage: error: Code E_ACCESSDENIED (0x80070005) - Access denied (extended info not available)
VBoxManage: error: Context: "EnableStaticIPConfig(Bstr(pszIp).raw(), Bstr(pszNetmask).raw())" at line 242 of file VBoxManageHostonly.cpp
The text was updated successfully, but these errors were encountered: