CODEWITHSUNDEEP
vagrantvagrant-plugin
user3536147
user3536147

Reputation: 33

Renaming the Windows guest failed. Most often this is because you've specified a FQDN instead of just a host name

I am running vagrant version,

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)

When I start a vagrant VM, windows 2012r2,

I get "Renaming the Windows guest failed. Most often this is because you've specified a FQDN instead of just a host name."

It used to work before on the same host(centos7, with Virtualbox) with version 1.4.

Upvotes: 1

Views: 711

Answers (2)

Brandon Hawbaker
Brandon Hawbaker

Reputation: 338

Another way you can resolve this issue is by setting the vm_hostname attribute to false like this:

platforms:
  - name: BPA-TEST
    driver_config:
      username: Tester
      password: [PASSWORD]
      vm_hostname: false
    driver:
      port: 55985
      customize:
        memory: 4048

https://github.com/test-kitchen/kitchen-vagrant

vm_hostname Sets the internal hostname for the instance. This is not used when connecting to the Vagrant virtual machine.

To prevent this value from being rendered in the default Vagrantfile, you can set this value to false.

The default will be computed from the name of the instance. For example, the instance was called "default-fuzz-9" will produce a default vm_hostname value of "default-fuzz-9". For Windows-based platforms, a default of nil is used to save on boot time and potential rebooting.

Upvotes: 0

rbanffy
rbanffy

Reputation: 2531

If you are (like me) experiencing this with Kitchen, in your .kitchen.yml, in the platform section, you can't have "name: mwrock/Windows2012R2". Instead, name it something like "windows2012R2" and, in platform's "driver_config" section, specify "box: mwrock/Windows2012R2".

Upvotes: 3

Related Questions