Pawel Stolowski

Ah, it's great the fix already landed, I missed the first report about this problem because it got addressed so fast and closed... Might make sense to keep this issue...

> I would feel safer if the extra snippets were not manually written by the user, but came with the snap itself, and installed in a way that even non...

> @stolowski I'll be looking to reproduce this behavior today and hopefully identify and resolve the issue fairly quickly. Thank you! To be honest, I'm a little skeptical when it...

This just happened again, so 5 days from previous occurence. After restarting the system I took a look at the processes with pstree and under normal conditions I see this:...

@chrisroberts I had a hunch and checked Mac's Console app and found two crash reports for vagrant-vmware-utility that match the times where vmrest wouldn't work anymore; attached below. [crash1.txt](https://github.com/hashicorp/vagrant/files/5421347/crash1.txt) [crash2.txt](https://github.com/hashicorp/vagrant/files/5421348/crash2.txt)

This just happened again. I was hoping `sudo launchctl start com.vagrant.vagrant-vmware-utility` would work around the problem, but it didn't help (the service would start, but vmrest does not respond). @chrisroberts...

I know recent update to vagrant/vagrant-vmware-utility was aimed at fixing the issue of zombie vmrest process and I think it indeed fixed it, but I just experienced the problem again...

@chrisroberts No, I didn't put the machine to sleep around the time the issue occurred. I woke it in the morning around 9:00, started a vm with `vagrant up` followed...

FWTW I haven't experienced this problem with vagrant 2.2.14 for good 3 weeks, but I've also upgraded to Big Sur on the day it was officially released (on a side...

Hi, thanks for another contribution and I apologize for the delay with looking at it... I've just been reviewing the project preparing the new release and tested your changes, but...