search

Parallels / vagrant-parallels

Vagrant Parallels Provider
https://parallels.github.io/vagrant-parallels
MIT License
996 stars 87 forks source link

vagrant-parallels and Parallels 17 issue ? #408

Closed AnatomicJC closed 3 years ago

AnatomicJC commented 3 years ago

Hi 👋 ,

I'm using a MacBook pro 2020 with Intel chip.

$ vagrant --version
Vagrant 2.2.18
$ vagrant plugin list
vagrant-parallels (2.2.4, global)

With Parallels 16, I have this interface with 10.211.55.0/24 network when I launch ifconfig:

bridge100: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        options=3<RXCSUM,TXCSUM>
        ether 16:7d:da:2a:3c:64
        inet 10.211.55.2 netmask 0xffffff00 broadcast 10.211.55.255
        inet6 fe80::147d:daff:fe2a:3c64%bridge100 prefixlen 64 scopeid 0x13
        Configuration:
                id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
                maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
                root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
                ipfilter disabled flags 0x0
        member: vmenet0 flags=3<LEARNING,DISCOVER>
                ifmaxaddr 0 port 18 priority 0 path cost 0
        nd6 options=201<PERFORMNUD,DAD>
        media: autoselect
        status: active

When I upgrade to Parallels 17, this interface is missing and vagrant is no more able to configure the VM.

==> vm: Running 'pre-boot' VM customizations...
==> vm: Booting VM...
==> vm: Waiting for machine to boot. This may take a few minutes...
    vm: SSH address: :22
    vm: SSH username: vagrant
    vm: SSH auth method: private key
    vm: Warning: Connection refused. Retrying...
    vm: Warning: Connection refused. Retrying...
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'stopping' state. Please verify everything is configured
properly and try again.

If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.

The primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue.

I switched back to Parallels 16 to use vagrant. Is it a know issue ?

Thanks !

legal90 commented 3 years ago

@AnatomicJC I don't see that issue in my case with Parallels Desktop 17.1.0 on macOS 11.5.2. It works just fine.

I remember that after the upgrade to Parallels Desktop 17 it ask to reboot the Mac. Did you try rebooting after the upgrade? If not - please try to reboot and then also check the output of prlsrvctl net info Shared. Normally it would look like this:

$ prlsrvctl net info Shared
Network ID: Shared
Type: shared
Parallels adapter:
    IPv4 address: 10.211.55.2
    IPv4 subnet mask: 255.255.255.0
    Host assign IP v6: off
    IPv6 address: fdb2:2c26:f4e4::1
    IPv6 subnet mask: ffff:ffff:ffff:ffff::
DHCPv4 server:
    Server address: 10.211.55.1
    IP scope start address: 10.211.55.1
    IP scope end address: 10.211.55.254
DHCPv6 server:
    Server address: fdb2:2c26:f4e4::
    IP scope start address: fdb2:2c26:f4e4::
    IP scope end address: fdb2:2c26:f4e4:0:ffff:ffff:ffff:ffff

NAT server:
AnatomicJC commented 3 years ago

Hi @legal90 thanks for reply me. I forgot to say in the description of the issue I am using MacOS 12.0.1 Monterey, and I opened this issue after upgrading MacOS to 12.0.1. By the way, I upgraded again Parallels to version 17.1.0 just now and I no longer encounter this issue :) So I will close this issue as all is working as expected.

Thanks !