Known issue?: Shared Network IP address conflicts

Discussion in 'General Questions' started by meermanr, Jul 14, 2023.

  1. meermanr

    meermanr Bit poster

    Messages:
    8
    I often find the networking on my VMs doesn't seem to work after I reboot my MacBook. I mostly run headless Linux VMs via vagrant and vagrant-parallels.

    The running VMs are auto-suspended as part of shutdown. When I manually resume two or more of them I often find they are all given the *same* IP address.

    Suppose I have two headless Linux VMs, alpha and bravo. When I resume alpha /etc/hosts gains an entry for the IP 192.168.111.30:
    192.168.111.30 alpha.shared alpha #prl_hostonly shared
    When I then resume the second VM, bravo, it gets the same IP and overwrites the entry in /etc/hosts:
    192.168.111.30 bravo.shared bravo #prl_hostonly shared
    The result is that I cannot SSH into alpha anymore. Using the GUI of the VM I can see that both VM do indeed have this IP address, in _addition_ to the IP address they had before I shutdown my MacBook.

    For now I can work around this by toggling the networking - in the GUI I change it from "Shared Network" -> "Disconnect" and then back -> "Shared Network". That seems to get everything back to a sane state with each VM having a distinct IP address and entry in /etc/hosts. It also seems to restore the original IPs from before the reboot, but that may be confirmation bias on my part.

    Is this a known issue?
     

Share This Page