Hi @huygen, that's unfortunate. We have no idea what is happening to your instance.
Let's try to do some investigation. Could you run the following command inside the VM and see if the internet is configured?
Next, inside a terminal running directly in your Mac, run the same command. Do you see something like this? Note that the IP in "inet" should be the in the same network as the ethernet interface "eth0" in the VM (in our case 192.168.64.1/24 contains the VMs IP 192.168.64.10, and is assigned to bridge100):
bridge100: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.64.1 netmask 0xffffff00 broadcast 192.168.64.255
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 0x2
member: en5 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 18 priority 0 path cost 0
Also, since "en5" is a member (might be different in your case), run "sudo ifconfig en5" and you should see something like this:
en5: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
If so, it means it is connected to your Mac.
Next, we assume your Mac has internet access. Could you confirm this command works?