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

Vagrant not working with VMWare on Apple Silicon Macbook #13378

Open
Patsch36 opened this issue Apr 5, 2024 · 0 comments
Open

Vagrant not working with VMWare on Apple Silicon Macbook #13378

Patsch36 opened this issue Apr 5, 2024 · 0 comments

Comments

@Patsch36
Copy link

Patsch36 commented Apr 5, 2024

Debug output

2024-04-05T15:40:30.341+0200 [INFO] vagrant-vmware-utility.api: created: vmx=
2024-04-05T15:40:30.341+0200 [TRACE] vagrant-vmware-utility.api.settings: building nat settings: path=/opt/vagrant-vmware-desktop/settings/nat.json
2024-04-05T15:40:30.341+0200 [ERROR] vagrant-vmware-utility.api.settings.nat: failed to read nat file: error="open /opt/vagrant-vmware-desktop/settings/nat.json: permission denied" path=/opt/vagrant-vmware-desktop/settings/nat.json
2024-04-05T15:40:30.341+0200 [ERROR] vagrant-vmware-utility.api: settings setup failure: error="open /opt/vagrant-vmware-desktop/settings/nat.json: permission denied"
2024-04-05T15:40:30.341+0200 [ERROR] vagrant-vmware-utility.api: base driver setup failure: error="open /opt/vagrant-vmware-desktop/settings/nat.json: permission denied"
Failed to setup Vagrant VMWare API service - open /opt/vagrant-vmware-desktop/settings/nat.json: permission denied

Expected behavior

Show VM in VMWARE-Fusion Client

Actual behavior

VM not shown in VMWARE-Fusion Client. But can be started with Vagrant ssh

Reproduction information

Createt VM with following commands:

/usr/sbin/softwareupdate --install-rosetta --agree-to-license
brew install vagrant
ln -s /Applications/VMWare\ Fusion\ Tech\ Preview.app /Applications/VMWare\ Fusion.app
brew install --cask vagrant-vmware-utility
vagrant plugin install vagrant-vmware-desktop
vagrant init gyptazy/ubuntu22.04-arm64
vagrant up

Vagrant version

Host operating system

Guest operating system

macOS 14.4 (23E214)

Steps to reproduce

Vagrantfile

# Copy-paste your Vagrantfile here. Remove any sensitive information such as passwords, authentication tokens, or email addresses.
# -*- mode: ruby -*-
# vi: set ft=ruby :

# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure("2") do |config|
  # The most common configuration options are documented and commented below.
  # For a complete reference, please see the online documentation at
  # https://docs.vagrantup.com.

  # Every Vagrant development environment requires a box. You can search for
  # boxes at https://vagrantcloud.com/search.
  config.vm.box = "archlinux/archlinux"

  # Disable automatic box update checking. If you disable this, then
  # boxes will only be checked for updates when the user runs
  # `vagrant box outdated`. This is not recommended.
  # config.vm.box_check_update = false

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine. In the example below,
  # accessing "localhost:8080" will access port 80 on the guest machine.
  # NOTE: This will enable public access to the opened port
  # config.vm.network "forwarded_port", guest: 80, host: 8080

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine and only allow access
  # via 127.0.0.1 to disable public access
  # config.vm.network "forwarded_port", guest: 80, host: 8080, host_ip: "127.0.0.1"

  # Create a private network, which allows host-only access to the machine
  # using a specific IP.
  # config.vm.network "private_network", ip: "192.168.33.10"

  # Create a public network, which generally matched to bridged network.
  # Bridged networks make the machine appear as another physical device on
  # your network.
  # config.vm.network "public_network"

  # Share an additional folder to the guest VM. The first argument is
  # the path on the host to the actual folder. The second argument is
  # the path on the guest to mount the folder. And the optional third
  # argument is a set of non-required options.
  # config.vm.synced_folder "../data", "/vagrant_data"

  # Disable the default share of the current code directory. Doing this
  # provides improved isolation between the vagrant box and your host
  # by making sure your Vagrantfile isn't accessible to the vagrant box.
  # If you use this you may want to enable additional shared subfolders as
  # shown above.
  # config.vm.synced_folder ".", "/vagrant", disabled: true

  # Provider-specific configuration so you can fine-tune various
  # backing providers for Vagrant. These expose provider-specific options.
  # Example for VirtualBox:
  #
  # config.vm.provider "virtualbox" do |vb|
  #   # Display the VirtualBox GUI when booting the machine
  #   vb.gui = true
  #
  #   # Customize the amount of memory on the VM:
  #   vb.memory = "1024"
  # end
  #
  # View the documentation for the provider you are using for more
  # information on available options.

  # Enable provisioning with a shell script. Additional provisioners such as
  # Ansible, Chef, Docker, Puppet and Salt are also available. Please see the
  # documentation for more information about their specific syntax and use.
  # config.vm.provision "shell", inline: <<-SHELL
  #   apt-get update
  #   apt-get install -y apache2
  # SHELL
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant