[Vagrant] Guest Machine State Management (Provider: VirtualBox)

[Smit Jain]

Team,

Big thanks to the community and hashicorp or building awesome tools.

Issue :

I see when we restart guest within from CLI terminal, the vagrant process is not able to figure out correct state of the Guest Machines. 

Even if I execute  $ vagrant global-status this will still show the vm state as  "running" .Therefore, any plugin being used is also not able to make changes accordingly.

For eg: landrush plugin would not refresh the DNS record for vagrant the VM is still running .

Is there any way or feature to make aware vagrant about the guest state.

Note: This issue occur only if the VM is restarted or poweroff from within the guest machine and NOT from the host.

Please share your feedback and inputs, if anybody encountered same issue.

Vagrant : 2.0

VirtualBox : 5.1

[tamal bhattacharjee]

I faced the similar issue. Where vagrant global-status showing me up message against vm's,but login in that vm not happening through putty(putty config ed there and works fine in general case). 

--
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/61bab69e-0345-4a72-aef1-28333cc773a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Denislav Denov]

Hello,

Your vagrant seems to be out of date from what is written.

Have you tried with the latest version?

https://www.vagrantup.com/downloads.html

There is also newer version of Virtualbox.

[Alvaro Miranda Aguilera]

IF you have VMs created and managed by Vagrant, the best is to use vagrant to halt/stop/pause/start

otherwise, if you will start/stop the vm outside vagrant, then go back to vagrant and expect vagrant to do the right thing.

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/61bab69e-0345-4a72-aef1-28333cc773a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Smit Jain]

Thanks Alvaro and rest for the feedback, but I think its a way vagrant is desgined to manage the state of the VMs.

I checked with newer version as well, vagrant cannot identify the state of the VM , if there are any changes made from within in the guest machine.

Thanks & Regards,

------------------------------------------------

Smit Jain
Contact no.-9582921008

Email: smitj...@gmail.com

 

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ex2mn2SmQuV_ShLAGStY-E--M%2BJpTNytDHh1EZwWT-7ng%40mail.gmail.com.