[Vagrant 2.2.5] [Hyper-V] Guest-specific operations were attempted on a machine that is not ready for guest communication.

[Jacqueline Costa]

Well,

I am using vagrant 2.2.5 and also provider is HyperV, I am using Stefan's Windows 10 box 

But when one of my shell scripts start to working vagrant return:

Bringing machine 'hyperv' up with 'hyperv' provider... 

==> hyperv: Verifying Hyper-V is enabled... 

==> hyperv: Verifying Hyper-V is accessible... 

==> hyperv: Machine already provisioned. 

Run `vagrant provision` or use the `--provision` 

==> hyperv: flag to force provisioning. 

Provisioners marked to run always will still run. 

==> hyperv: Running provisioner: shell... 

Guest-specific operations were attempted on a machine that is not ready for guest communication. This should not happen and a bug should be reported

I tried install the plugin vagrant-vbguest and also without it, but the both ways returns the message of Guest-specific.

Any idea of what is happening?

[Alvaro Miranda Aguilera]

hello

vagrant-vbguest is for virtualbox guest additions

i would suggest remove this and other plugins if not using virtualbox

the vm seems already was provisioned, so maybe did work at some point

you could try

vagrant destroy

vagrant up

if still fails, check hyper v console of this vm to check what may be happening

alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/5318a3c5-df79-40b5-805a-0d7e791b794d%40googlegroups.com.

--

Alvaro