I just upgraded my Ubuntu 20.04 VM to v22.04, and notice that the VM losts network connection after the Mac host wakes up from sleep. The only way to bring it back is to reboot the VM. The problem does not repro with the original Ubuntu c20.04 VM. I have another Ubuntu 20.04 VM and it does not have the networking problem. Could it be caused by a change in the v22.04 kernel? Thank you.
Parallels Desktop 17: Ubuntu 22.04 VM losts networking after Mac host wakes up
- Thread starter HongL1
- Start date
Hello, did you check the same issue with Bridged network mode (or Shared network mode)?
You can refer to this KB Article to change the network mode.
You can refer to this KB Article to change the network mode.
Hello, Please change the network in the Configuration > bridged mode > select "Default adaptor" and check.
Same here. Parallels Desktop Version 18.1.1 (53328) on macOS 12.6.2 running Ubuntu 22.04 LTS Server as a guest. As soon as the Mac (Macmini9,1 with Apple Silicon) goes to sleep and wakes up again the VM becomes unreachable. It's already using Bridged Networking with the adapter set to "Default Adapter" so this advice is of no use to me.
Any help would be appreciated
Any help would be appreciated
A quick fix is to sudo dhclient which will renew your lease and get you connected, restore samba/filesharing etc without further irk (assuming you have a static assignment to the h/w address set at the router/dhcp server) - but for me the only solution is to reboot (the guest) every time the mac sleeps as so much else is borked (I'm running Plesk/DNS etc) - I don't think Parallels is really intended for serious dev purposes, just simple app compatibility and such
sudo dhclient works just fine on my end, but I wouldn't have a clue how to automate this from within the VM. The only automatable "solution" I came up so far was to whip up a command line tool running in the background (on the host) which reboots the VM every time the Mac wakes up 
GuruunoFlob
Bit poster
I'm in the very same boat, and resolve as of yet?
Parallels 20 and Ubuntu 5.10 also suffers from this.
dhclient restores the IP, but all underlying stuff died in the meantime time, so having to reboot every time.
Running in bridged mode to wifi (which is the only active interface on my mac)
A real solution would be appreciated, also considering the wide spread of this years old issue.
dhclient restores the IP, but all underlying stuff died in the meantime time, so having to reboot every time.
Running in bridged mode to wifi (which is the only active interface on my mac)
A real solution would be appreciated, also considering the wide spread of this years old issue.
I share your problem. But I tried to set up a vanilla Ubuntu and weren't able to reproduce the issue.
So I assume that some other things done to the Ubuntu setup seem to cause the issue. That's why it is NOT that easy to reproduce.
Me, I've installed paperlessngx in a docker container. To access the service, I set up a docker network and Caddy to support https access to paperless. It's just a vague idea, but maybe that causes the problem?
BTW: After waking up and calling "ip a", I can see IPv6 adresses on the interface, but no IPv4 anymore.
BTW*2: For me, calling "sudo netplan apply" solves the issue. Unfortunately, I haven't found a way to do this automatically on wakeup.
So I assume that some other things done to the Ubuntu setup seem to cause the issue. That's why it is NOT that easy to reproduce.
Me, I've installed paperlessngx in a docker container. To access the service, I set up a docker network and Caddy to support https access to paperless. It's just a vague idea, but maybe that causes the problem?
BTW: After waking up and calling "ip a", I can see IPv6 adresses on the interface, but no IPv4 anymore.
BTW*2: For me, calling "sudo netplan apply" solves the issue. Unfortunately, I haven't found a way to do this automatically on wakeup.