Hacker News Reader

Comment by fideloper | Hacker News Reader

This doesn't work for me, because of this issue: https://github.com/mitchellh/vagrant/issues/6871

Sadly even the most recent one still has the private_network issue (and the missing line in hosts), it just stops during vagrant up with this error:

> sudo: unable to resolve host ubuntu-xenial

> mesg: ttyname failed: Inappropriate ioctl for device

I hope this PR (https://github.com/mitchellh/vagrant/pull/7241) gets merged because the private_network issue has been around since 15.04

Does it work for you? For me VirtualBox gets stuck into the 'gurumeditation' state when booting.

Same Problem. Newest VirtualBox newest vagtant 1.8.1

Also same, but have heard better reports from those on Virtuabox 4 instead of latest Virtuabox 5 :(

I had better luck with https://atlas.hashicorp.com/gbarbieru/boxes/xenial which just got updated a few hours ago.

This is a virtualbox regression because the box is packaged with the LsiLogic controller: https://www.virtualbox.org/ticket/15317

You can downgrade VirtualBox, dropping to 5.0.16 worked for me: http://download.virtualbox.org/virtualbox/5.0.16/

I'm not sure as there's no description, so I'll ask. That's the desktop version, not the server one ?

Ummm I assumed it was the server one, perhaps I'm mistaken. Ubuntu/*64 have typically been headless.