vagrant-parallels broken on Big Sur / v16.1.0, network initialization fails on subsequent vagrant up

L

LudwigG3

Bit poster
Hi,

I followed the instructions how to reset the network when the initialization error occurs, and it does actually work the first time setting up another machine using vagrant. However if you stop the virtual machine and do another "vagrant up" it fails to recognize the existing vagrant-vnet and creates another one at which point it shows the error again "network could not be initialized".

So there are 2 potential problems here:
  1. why can't vagrant recognize and reuse the existing network
  2. why is parallels failing to just use the second network as it did the first one?
The problems are probably related and I hope there is a fix just within Parallels Desktop to provide its APIs within Big Sur for vagrant just as it did on Catalina.

kind regards
 
Some more Info:
  • vagrant: 2.2.13
  • vagrant-parallels: 2.0.1
  • Parallels Desktop: 16.1.0
Sample Vagrantfile used:

Vagrant.configure(2) do |config|
config.vm.box = "bento/centos-7"
config.vm.hostname = "test"
config.vm.network "private_network", ip: "192.168.221.20", netmask: "255.255.255.0"
config.vm.provider "parallels" do |v|
v.memory = "2048"
v.cpus = "4"
end
end
 
You must log in or register to reply here.
Back
Top