hashicorp / vagrant

Vagrant is a tool for building and distributing development environments.
https://www.vagrantup.com
Other
26.28k stars 4.43k forks source link

Vagrant on OSX (HighSierra) getting VERR_PERMISSION_DENIED when creating virtualbox__intnet #9235

Closed mightywomble closed 4 years ago

mightywomble commented 6 years ago

Please note that the Vagrant issue tracker is reserved for bug reports and enhancements. For general usage questions, please use the Vagrant mailing list: https://groups.google.com/forum/#!forum/vagrant-up. Thank you!

Vagrant version

Vagrant 2.0.1

Host operating system

OSX High Sierra

Guest operating system

CentOS 7.3

Vagrantfile

Vagrant.configure(2) do |config|
  config.vm.box = "bento/centos-7.3"
  config.vm.provider "virtualbox" do |v|
    v.memory = 2048
    v.cpus = 1
  #config.vm.network "public_network", use_dhcp_assigned_default_route: true, bridge: "en0: Wi-Fi (AirPort)"
 config.vm.network "private_network", ip: "10.100.100.211", virtualbox__intnet: "puppetlan"
  #config.vm.network "private_network", ip: "10.100.100.211"

  end
    config.vm.provision "shell", inline: <<-SHELL

    rpm -Uvh https://yum.puppetlabs.com/puppet5/puppet5-release-el-7.noarch.rpm
    yum install -y puppet-agent

cat << EOF1 > /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4                                                                                        
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6                                                                                        
10.100.100.10   puppet   
EOF1

cat << EOF2 > /etc/puppetlabs/puppet/puppet.conf 
[main]                                                                                                                                                                
certname = client                                                                                                                                                     
server = puppet                                                                                                                                                       
environment = production                                                                                                                                              
runinterval = 24h  
EOF2

mkdir -p /etc/facter/facts.d/
touch /etc/facter/facts.d/instance_role.txt
echo "instance_role=base" > /etc/facter/facts.d/instance_role.txt

/opt/puppetlabs/bin/puppet resource service puppet ensure=running enable=true
service puppet restart

  SHELL
end

Please note, if you are using Homestead or a different Vagrantfile format, we may be unable to assist with your issue. Try to reproduce the issue using a vanilla Vagrantfile first.

Debug output

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

Was expecting the line config.vm.network "private_network", ip: "10.100.100.211", virtualbox__intnet: "puppetlan" to add the Virtualbox machine to the internal lan puppetlan

Actual behavior

I got the error Stderr: VBoxManage: error: Failed to open/create the internal network 'puppetlan' (VERR_PERMISSION_DENIED).

VBoxManage: error: Failed to attach the network LUN (VERR_PERMISSION_DENIED)

VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole

Steps to reproduce

  1. Run vagrant up

References

Are there any other GitHub issues (open or closed) that should be linked here? For example:

mightywomble commented 6 years ago

I noted if this happens on Windows, you ned to ad the NDIS Driver to the Physical NIC

briancain commented 6 years ago

What version of virtualbox are you using @mightywomble ?

briancain commented 6 years ago

I couldn't reproduce this using macOS sierra with virtualbox 5.1.26r117224

mightywomble commented 6 years ago

OK, I'm using the latest 5.2.2.r119230

David Field
03330115650 [https://si.gnatu.re/#fieldymac@gmail.com] fieldymac@gmail.com [fieldymac@gmail.com] [https://si.gnatu.re/#http://www.photowalktheworld.com] www.photowalktheworld.com [http://www.photowalktheworld.com/]
United Kingdom[https://facebook.com/mightywomble] [https://twitter.com/mightywomble] [https://linkedin.com/in/mightywomble] [https://instagram.com/mightywomble]
Warning: Spelling errors in this message are the product of a poor school system. Pay teachers more than athletes.

On Fri, Dec 01, 2017 at 9:44pm, Brian Cain < notifications@github.com [notifications@github.com] > wrote: I couldn't reproduce this using macOS sierra with virtualbox 5.1.26r117224

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub [https://github.com/hashicorp/vagrant/issues/9235#issuecomment-348622232] , or mute the thread [https://github.com/notifications/unsubscribe-auth/AUGwRPnTNW0RHQQJv5zJxZhlgf2VWbPbks5s8HMngaJpZM4QxS9f] .

mightywomble commented 6 years ago

And the same thing happens on high sierra with the version you listed.

On Fri, Dec 01, 2017 at 9:44pm, Brian Cain < notifications@github.com [notifications@github.com] > wrote: I couldn't reproduce this using macOS sierra with virtualbox 5.1.26r117224

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub [https://github.com/hashicorp/vagrant/issues/9235#issuecomment-348622232] , or mute the thread [https://github.com/notifications/unsubscribe-auth/AUGwRPnTNW0RHQQJv5zJxZhlgf2VWbPbks5s8HMngaJpZM4QxS9f] .

soapy1 commented 4 years ago

Hi there,

Thanks for reporting this bug. I'm sure this was a real issue when originally reported (our fault for not looking sooner!) but there have been multiple Vagrant releases since the original report. I'm going to close this issue now and request you reopen the issue if you're still experiencing this problem. I'm sorry this wasn't looked at earlier ☹️

Cheers!

ghost commented 4 years ago

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.