Chef kitchen with vagrant hangs using Fusion 12.2

I have been having trouble for some time now with Fusion 12 and Chef kitchen and vagrant. When I attempt to destroy a vagrant box using “kitchen destroy”, vagrant is unable to communicate with Fusion and it will time-out. I have to reboot for it to work again.

I upgraded to Fusion 12.2 in the hopes this would be fixed. Unfortunately, I am now unable to stand up a kitchen instance using “kitchen create”. It hangs without a time-out. I have deleted the .kitchen directory without a change in behavior.

-----> Creating …
Bringing machine ‘default’ up with ‘vmware_desktop’ provider…
==> default: Checking if box ‘bento/centos-7’ version ‘202109.07.0’ is up to date…
==> default: Verifying vmnet devices are healthy…
==> default: Preparing network adapters…
==> default: Starting the VMware VM…
==> default: Waiting for the VM to receive an address…

I have uninstalled Fusion and vagrant and then reinstalled them. No change.

Downgrading to Fusion 12.1.2 allows me to create a kitchen instance.

I needed to upgrade VMWare Fusion Pro 12.1.2 to 12.2.1 since I upgraded my other VMs. I also upgrade all Vagrant resources:
Vagrant 2.2.19
vagrant-vmware-desktop (3.0.1, global)
vagrant-vmware-utility 1.0.21

Ultimately (or in part), the final piece was deleting the cached box and allowing Vagrant to download the latest. I think this was key now that I realized 12.1.2 VMs are not compatible with 12.2.1.