search

GetValkyrie / valkyrie

Valkyrie is an opinionated local dev stack that makes features/git based Drupal development easy.
http://www.getvalkyrie.com
GNU General Public License v3.0
45 stars 11 forks source link

Could not resolve hostname valkyrie.local #23

Closed gboudrias closed 9 years ago

gboudrias commented 9 years ago

I'm getting this error while trying to create a new vm. I'm guessing it's something to do with avahi, although my avahi-deamon service is running.

guigui@turbowarp:~/dev$ drush vnew valkyrie
Valkyrie project initialized at: valkyrie                                                                                                          [ok]
Bringing machine 'valkyrie' up with 'virtualbox' provider...
==> valkyrie: Importing base box 'ubuntu/trusty64'...
==> valkyrie: Matching MAC address for NAT networking...
==> valkyrie: Checking if box 'ubuntu/trusty64' is up to date...
==> valkyrie: Setting the name of the VM: valkyrie_valkyrie_1425482534729_38881
==> valkyrie: Clearing any previously set forwarded ports...
==> valkyrie: Clearing any previously set network interfaces...
==> valkyrie: Preparing network interfaces based on configuration...
    valkyrie: Adapter 1: nat
    valkyrie: Adapter 2: hostonly
==> valkyrie: Forwarding ports...
    valkyrie: 22 => 2222 (adapter 1)
==> valkyrie: Running 'pre-boot' VM customizations...
==> valkyrie: Booting VM...
==> valkyrie: Waiting for machine to boot. This may take a few minutes...
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'poweroff' state. Please verify everything is configured
properly and try again.

If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.
The external command could not be executed due to an application     error.                                                                            [error]
Illegal string offset 'site' backend.inc:1017                                                                                                      [warning]
[error]be executed successfully (returned: ssh: Could not resolve hostname valkyrie.local: Name or service not known
, code: 255)
ergonlogic commented 9 years ago

The error happened earlier:

The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'poweroff' state. Please verify everything is configured
properly and try again.
gboudrias commented 9 years ago

Oh yeah, I thought the error caused the crash but I guess it could be the other way around.

gboudrias commented 9 years ago

Any ideas on how to debug this?

ergonlogic commented 9 years ago

Check vagrant global-status, and make sure there isn't name collision perhaps.

Also, I believe we need to install avahi-daemon in the VM, which I believe got dropped somewhere in the conversion to Ansible.

gboudrias commented 9 years ago

Apparently I had VT-x disabled in the BIOS. (Don't know how this is possible but oh well.)

To future readers trying to debug a similar problem, just launch the VM in VirtualBox, it'll tell you. You then have to restart and go into the BIOS to activate VT-x (and sometimes restart again).

I have the NFS issue now but I'll check out the open issue.