linux guest doesn't support configure_networks

[Robert A Ensink]

vagrant 1.7.4

host: Windows 7

guest: Ubuntu Mate 14.04

provider: VirtualBox 4.3.30

Seeing this error when creating a new VM with a bridged network interface:

vagrant up

Bringing machine 'SDL-VM-UbuntuMate1404B' up with 'virtualbox' provider...

==> SDL-VM-UbuntuMate1404B: Importing base box 'UbuntuMate1404LTS-pristineB'...

==> SDL-VM-UbuntuMate1404B: Matching MAC address for NAT networking...

==> SDL-VM-UbuntuMate1404B: Setting the name of the VM: SDL-VM-UbuntuMate1404B

==> SDL-VM-UbuntuMate1404B: Clearing any previously set network interfaces...

==> SDL-VM-UbuntuMate1404B: Preparing network interfaces based on configuration...

    SDL-VM-UbuntuMate1404B: Adapter 1: nat

    SDL-VM-UbuntuMate1404B: Adapter 2: bridged

==> SDL-VM-UbuntuMate1404B: Forwarding ports...

    SDL-VM-UbuntuMate1404B: 22 => 2222 (adapter 1)

==> SDL-VM-UbuntuMate1404B: Booting VM...

==> SDL-VM-UbuntuMate1404B: Waiting for machine to boot. This may take a few minutes...

    SDL-VM-UbuntuMate1404B: SSH address: 127.0.0.1:2222

    SDL-VM-UbuntuMate1404B: SSH username: vagrant

    SDL-VM-UbuntuMate1404B: SSH auth method: private key

    SDL-VM-UbuntuMate1404B: Warning: Connection timeout. Retrying...

    SDL-VM-UbuntuMate1404B: Warning: Connection timeout. Retrying...

    SDL-VM-UbuntuMate1404B:

    SDL-VM-UbuntuMate1404B: Vagrant insecure key detected. Vagrant will automatically replace

    SDL-VM-UbuntuMate1404B: this with a newly generated keypair for better security.

    SDL-VM-UbuntuMate1404B:

    SDL-VM-UbuntuMate1404B: Inserting generated public key within guest...

    SDL-VM-UbuntuMate1404B: Removing insecure key from the guest if it's present...

    SDL-VM-UbuntuMate1404B: Key inserted! Disconnecting and reconnecting using new SSH key...

==> SDL-VM-UbuntuMate1404B: Machine booted and ready!

==> SDL-VM-UbuntuMate1404B: Checking for guest additions in VM...

==> SDL-VM-UbuntuMate1404B: Configuring and enabling network interfaces...

Vagrant attempted to execute the capability 'configure_networks'

on the detect guest OS 'linux', but the guest doesn't

support that capability. This capability is required for your

configuration of Vagrant. Please either reconfigure Vagrant to

avoid this capability or fix the issue by creating the capability.

Vagrant File: 

Vagrant.configure(2) do |config|

  config.vm.box   = 'UbuntuMate1404LTS-pristineB'

  config.vm.guest = :linux

  config.vm.define  'SDL-VM-UbuntuMate1404B'

  config.vm.provider :virtualbox do |vb|

    vb.name = 'SDL-VM-UbuntuMate1404B'

    vb.gui  = true

  end

  config.vm.network :public_network

end

The VM is created successfully, and the two network interfaces are configured correctly and functioning.

Yet vagrant fails with the error message shown above.

I need this to be successful because I also need to add some Chef provisioning to the Vagrant file.

[Alvaro Miranda Aguilera]

On Wed, Jul 29, 2015 at 3:53 AM, Robert A Ensink <raen...@gmail.com> wrote:
> Vagrant File:
> Vagrant.configure(2) do |config|
>
> config.vm.box = 'UbuntuMate1404LTS-pristineB'
> config.vm.guest = :linux
> config.vm.define 'SDL-VM-UbuntuMate1404B'
>
> config.vm.provider :virtualbox do |vb|
> vb.name = 'SDL-VM-UbuntuMate1404B'
> vb.gui = true
> end
>
> config.vm.network :public_network
>
> end

Hello

what happen if you don't specify the config.vm.guest part?

Vagrant File:
Vagrant.configure(2) do |config|

config.vm.box = 'UbuntuMate1404LTS-pristineB'

#config.vm.guest = :linux

[Robert A Ensink]

Removing config.vm.guest = :linux

from my Vagrantfile made the problem go away.

I was able to add my Chef provisioning and everything seems fine.

This looks like a bug somewhere in Vagrant - especially considering that :linux is the default value.

Possibly something with the auto-detection mechanism?

I am hoping, for now, that I don't encounter a future situation where the guest config parameter is required.

In any case, thanks very much for your suggestion!

[Alvaro Miranda Aguilera]

On Thu, Jul 30, 2015 at 5:19 AM, Robert A Ensink <raen...@gmail.com> wrote:
> This looks like a bug somewhere in Vagrant - especially considering that
> :linux is the default value.

Hello Robert,

Vagrant provide guest discovery, so in my particular case I have never
been in the need to specify that parameter.

For vagrant tasks, if the OS is well known, vagrant will identify
correctly and execute the code its' required. which is nice.

When this doesn't work, I think the best is open an issue on Vagrant
if the code is on the core, and add what's required ..

ie: a new linux guest require new discover, or because RedHat 7 use
different XYZ the command is different, etc

in that way, everyone benefit of the addition.

Even when your ruby-fu or vagrant-core-fu is low, having the issue on
the radar with a reproductible case, helps, since someone else can
finish that

Thanks!
Alvaro.