Problem with vagrant halt

[Jakub Sekera]

I am using Vagrant version 1.8.5 and VMware_workstation as provider with licence and vagrant-vmware-workstation (4.0.10) plugin with license too. I created my own box (vmware_workstation) provider, all is working ok, but unfortunately, when command: vagrant halt, this process stuck forever (but in GUI I can see, that virtual machine was shutdown gracefully). Vagrant ssh, vagrant destroy, vagrant suspend commands are working! 

[Alvaro Miranda Aguilera]

Hello,

Please send an email to sup...@hashicorp.com as you are entitled to paid support.

Not sure at this stage where the error is, so if you could share the output of

(for windows)

set VAGRANT_LOG=debug

(for linux)

export VAGRANT_LOG=debug

vagrant halt

that will generate a lot of verbose log, that should help.

Thanks

Alvaro

On Thu, Jul 28, 2016 at 12:17 AM, Jakub Sekera <jakub....@gmail.com> wrote:

I am using Vagrant version 1.8.5 and VMware_workstation as provider with licence and vagrant-vmware-workstation (4.0.10) plugin with license too. I created my own box (vmware_workstation) provider, all is working ok, but unfortunately, when command: vagrant halt, this process stuck forever (but in GUI I can see, that virtual machine was shutdown gracefully). Vagrant ssh, vagrant destroy, vagrant suspend commands are working! 

--
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/b0d6d4b3-714f-4b8a-909f-84573d78e6fc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jakub Sekera]

DEBUG ssh: stderr: sudo: unable to resolve host TESThostname

DEBUG ssh: Sending SSH keep-alive...

I think, the problem is, that I changed the hostname via ansible and vagrant cant reconnect via ssh to my virtual machine? It is possible to solve this problem?

Thank you in advance.

[Alvaro Miranda Aguilera]

On Thu, Jul 28, 2016 at 2:07 AM, Jakub Sekera <jakub....@gmail.com> wrote:

DEBUG ssh: Sending SSH keep-alive...

Hello,

It may be that.

If you need to set a hostname, please use  config.vm.hostname = "newname"

Alvaro.