"vagrant up" failed after disabling DHCPv4 server for Host-Only

[legal90]

This issue affects only Parallels Desktop 10.1.2 and higher.

If we disable DHCPv4 server for "Host-Only" network (using GUI or prlsrvctl utility), then vagrant up will fail:

With "vagrant-parallels" v1.3.6

==> dev: Fixed port collision for 22 => 2222. Now on port 2200.
==> dev: Available bridged network interfaces:
1) en0
2) awdl0
    dev: What interface should the network bridge to? Enter a number: 1
/Users/username/.vagrant.d/gems/gems/vagrant-parallels-1.3.6/lib/vagrant-parallels/driver/pd_10.rb:149:in `block in read_host_only_interfaces': undefined method `[]' for nil:NilClass (NoMethodError)
  from /Users/username/.vagrant.d/gems/gems/vagrant-parallels-1.3.6/lib/vagrant-parallels/driver/pd_10.rb:133:in `each'
  from /Users/username/.vagrant.d/gems/gems/vagrant-parallels-1.3.6/lib/vagrant-parallels/driver/pd_10.rb:133:in `read_host_only_interfaces'
  from /Users/username/.vagrant.d/gems/gems/vagrant-parallels-1.3.6/lib/vagrant-parallels/action/network.rb:443:in `hostonly_find_matching_network'
  from /Users/username/.vagrant.d/gems/gems/vagrant-parallels-1.3.6/lib/vagrant-parallels/action/network.rb:318:in `hostonly_adapter'
  from /Users/username/.vagrant.d/gems/gems/vagrant-parallels-1.3.6/lib/vagrant-parallels/action/network.rb:95:in `block (3 levels) in call'
  from /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/lib/vagrant/environment.rb:516:in `lock'

Pretty the same with "vagrant-parallels" v1.3.5 and lower:

==> dev: Fixed port collision for 22 => 2222. Now on port 2200.
==> dev: Available bridged network interfaces:
1) en0
2) awdl0
    dev: What interface should the network bridge to? Enter a number: 1
/Users/username/.vagrant.d/gems/gems/vagrant-parallels-1.3.5/lib/vagrant-parallels/driver/pd_8.rb:290:in `block in read_host_only_interfaces': undefined method `[]' for nil:NilClass (NoMethodError)
  from /Users/username/.vagrant.d/gems/gems/vagrant-parallels-1.3.5/lib/vagrant-parallels/driver/pd_8.rb:278:in `each'
  from /Users/username/.vagrant.d/gems/gems/vagrant-parallels-1.3.5/lib/vagrant-parallels/driver/pd_8.rb:278:in `read_host_only_interfaces'
  from /Users/username/.vagrant.d/gems/gems/vagrant-parallels-1.3.5/lib/vagrant-parallels/action/network.rb:443:in `hostonly_find_matching_network'
  from /Users/username/.vagrant.d/gems/gems/vagrant-parallels-1.3.5/lib/vagrant-parallels/action/network.rb:318:in `hostonly_adapter'
  from /Users/username/.vagrant.d/gems/gems/vagrant-parallels-1.3.5/lib/vagrant-parallels/action/network.rb:95:in `block (3 levels) in call'
  from /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/lib/vagrant/environment.rb:516:in `lock'

Temporary workaround: Enable DHCPv4 server for "Host-Only" network:
"Parallels Desktop -> Preferences -> Advanced -> Network -> Host-Only -> Restore Defaults - Enable IPv4 DHCP"

[legal90]

Fixed in v1.3.7