==> testwin: Waiting for machine to boot. This may take a few minutes...
testwin: WinRM address: 127.0.0.1:2202
testwin: WinRM username: localadmin
testwin: WinRM execution_time_limit: PT2H
testwin: WinRM transport: negotiate
==> testwin: Machine booted and ready!
==> testwin: Checking for guest additions in VM...
==> testwin: Setting hostname...
==> testwin: Saved client key to
/home/testlab/testlab/lab/.vagrant/butcher/testwin-client.pem
After this I get the Error
On Wednesday, 12 April 2017 18:04:31 UTC+1, athreya vc wrote:
>
> Hi,
> I am trying setup a vagrant machine windows 2012r2. I am using
>
> vagrant -v
> Vagrant 1.9.3
>
> vagrant plugin list
> vagrant-butcher (2.2.1)
> vagrant-cachier (1.2.1)
> vagrant-omnibus (1.5.0)
> vagrant-share (1.1.7, system)
> vagrant-vbguest (0.13.0)
>
> Virtualbox version is 5.
>
> the vagrant up <windows box> fails at
>
> "Renaming the Windows guest failed. Most often this is because you've
> specified a FQDN instead of just a host name."
>
> the whole setup is, after the machine is setup it should integrate with chef.
>
> I have setup the "winrm" as a communicator.
>
> Regards,
>
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/1ee18733-371d-440f-86fe-28685fd5febb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
