ARM (M1,M3) issues after wakeup from sleep.

[akrizs]

I experience som issues with socket_vmnet and qemu when my macbook's come back from sleep, then it seems like some tools (minikube & kubectl) aren't capable of finding a route to host, I have scraped the entire internet to try to find a solution and tested everything.

if i check netstat -rn | grep 192.168.105 after wakeup it seems like the routing records for 192.168.105 have been cleared, but as soon as i ping the instance or use regular ssh to connect then they get reinstated and everything presumably seems to work OK, but something with "higher order" tools seems like they aren't able to resolve the route. (Normal SSH works and the instance has connection to the internet).

Is this something that anyone else has experienced and perhaps found a solution to?, i have tried to restart the socket_vmnet launchd daemon, i have tried to ifconfig down/up the bridge, tried both, it seems like sometimes it kicks in and works, sometimes i have to spend bunch of time trying to kick it into gear.

Hope that someone has a clue or this is something that can be solved.

[AkihiroSuda]

ARM (M1,M3) issues after wakeup from sleep.

Is this issue specific to those ARM chips?
i.e., this issue doesn't happen on Intel and M2?

[akrizs]

ARM (M1,M3) issues after wakeup from sleep.

Is this issue specific to those ARM chips? i.e., this issue doesn't happen on Intel and M2?

Hard for me to say since i do not have access to those devices, thats why i specified what i had access to and have tested on.

[dharsanb]

Same issue here

Lima / socker_vmnet version: v1.2.1
MacOS 15.6
MacBook Pro M4 Max
vz VM with bridged network

When using bridged network on top of socket_vmnet, if the network interface reconnects for any reason (physical disconnection of interface, restarting of router or system going to sleep), the network interface stops working inside the VM . It does not work even if I restart the interface inside the VM or the entire VM. Only restarting the host machine fixes the issue.

[dharsanb]

@AkihiroSuda @jandubois ,
Could you take a look when you get a chance?

[nirs]

@dharsanb this sounds like an issue in macOS, not in in socket_vmnet or lima, since you tested restarting the vm. If this was an issue in lima restarting the vm would fix the issue.

You can try to restart the socket_vmnet service to check if this is an issue in socket_vment.

Check socket_vment logs for errors: /var/log/socket_vmnet/bridged.*.stderr

I did not see any issue in socket_vment for long time.

[nirs]

@akrizs

I experience som issues with socket_vmnet and qemu when my macbook's come back from sleep, then it seems like some tools (minikube & kubectl) aren't capable of finding a route to host, I have scraped the entire internet to try to find a solution and tested everything.

Minikube has the vfkit driver (since 1.36) using native virtualization and better network support (--network vmnet-shared). Check if you see the same issue there.