Open jensdeweerdt opened 1 year ago
I tried uninstalling vagrant, restarting my mac, installing vagrant, unloading and then loading and that didnt work.
@jensdeweerdt @fonsambrooskbc Can you please try installing the latest release of the utility and see if that resolves your issue?
Internal
Hey Chris
The incident has been resolved, I manually deleted the vagrant vmware utility driver and re installed it again and that seems to have fixed it.
Thanks for the answer
Fons Ambroos Developer AEM WEBSITES
KBC Global Services NVhttps://www.kbc.be/bedrijfsgegevens-groep, LEUbrust - DCU Brusselstesteenweg 100, 3000 Leuven
[Logo]
From: Chris Roberts @.> Date: Wednesday, 17 May 2023 at 00:46 To: hashicorp/vagrant-vmware-desktop @.> Cc: Fons Ambroos @.>, Mention @.> Subject: Re: [hashicorp/vagrant-vmware-desktop] VMware Utility driver causes issues when starting VM (Issue #71)
The real sender of this external email is @.***
@fonsambrooskbchttps://github.com/fonsambrooskbc Can you please try installing the latest release of the utilityhttps://developer.hashicorp.com/vagrant/downloads/vmware and see if that resolves your issue?
— Reply to this email directly, view it on GitHubhttps://github.com/hashicorp/vagrant-vmware-desktop/issues/71#issuecomment-1550453472, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZQWPQFXQXTTFSL7PNQX7DLXGP7T7ANCNFSM6AAAAAAXTCPD2Q. You are receiving this because you were mentioned.Message ID: @.***>
Disclaimer https://www.kbc.com/KBCmailDisclaimer
Vagrant version
Vagrant 2.3.4
Vagrant VMware plugin version
vagrant-vmware-desktop 3.0.1 vagrant-vmware-utility 1.0.21
Host operating system
Occuring on both Apple M1 Pro and Apple M2 Pro with MacOS Monteray and MacOS Ventura
Guest operating system
CentOS Stream 9
Expected behaviour
A VM is started
Actual behaviour
I am receiving the following errors on a regular basis:
and
Vagrant encountered an unexpected communications error with the Vagrant VMware Utility driver. Please try to run the command again. If this error persists, please contact support@hashicorp.com
Temporary fix
We have a temporary fix for this by doing the following two commands:
I have seen this issue a couple of times already but seems there is not a solution yet. I am having to do this workaround on a regular basis and would be nice to see this fixed permanently.