Ubuntu 16.04 current not booting in Vagrant (gurumeditation)

[Marvin R.]

I'm using OS X with current Vagrant 1.8.1 and VirtualBox 5.0.18.
Because today is the release of Ubuntu 16.04 I wanted to give it a try and failed. All other Ubuntu boxes from Canonical servers work here.

Here is the simple Vagrantfile: https://gist.github.com/therealmarv/555f7efc1c55ffa288bca09191e4e705
which is using the image from https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-vagrant.box

 $ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/xenial64'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: ubuntu-xenial-16.04-cloudimg
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: ubuntu
    default: SSH auth method: password
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'gurumeditation' 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 primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[domnulnopcea (domnulnopcea)]

the machine should be configured with a user and password: vagrant/vagrant

like all the other ubuntu boxes. then it should work

[Dan Watkins (oddbloke)]

Hi Marvin,

Thanks for reporting this issue. I believe you're seeing a Virtualbox bug (https://www.virtualbox.org/ticket/15317), rather than an Ubuntu Vagrant box issue.

We fixed this bug in the version of Virtualbox that shipped in xenial[0], but upstream have not yet released a patched version.

Thanks,

Dan

[0] https://launchpad.net/ubuntu/+source/virtualbox/5.0.18-dfsg-2build1

[Dan Watkins (oddbloke)]

(I was seeing a similar error message with the version of Virtualbox in Ubuntu before the fix I mentioned above was applied; after installing a version with the fix applied, the issue went away)

[Adam Israel (aisrael)]

This appears to be come sort of compatibility issue with Virtualbox 5.0.18. I was able to boot the ubuntu/xenial64 image on Virtualbox 5.0.16. It failed with an identical error after upgrading to 5.0.18, and worked again after downgrading back to 5.0.16.

[Marvin R. (therealmarv)]

Thanks for all the information!
Very upsetting (the timing and coincidence) with this not working VirtualBox version.

I'm currently running successfully Ubuntu 16.04 Vagrant Box together with VirtualBox 5.0.19 Test build:
https://www.virtualbox.org/wiki/Testbuilds

Everything works as expected. Really bad timing... I hope not many Vagrant users will be upset with this.

[Miguel (miguelsmuller)]

I'm the same problem using the 5.1.2 version of the virtual box and vagrant 1.8.5

If I put to the virtualbox display the VM screen appears this message:
[ 79.214766] sd 2:0:0:0: rejecting I/O to offline devide.

the return of the command 'vagrant up' is this:
Bringing machine 'test' up with 'virtualbox' provider...
==> test: Importing base box 'ubuntu/xenial64'...
==> test: Matching MAC address for NAT networking...
==> test: Checking if box 'ubuntu/xenial64' is up to date...
==> test: Setting the name of the VM: test
==> test: Clearing any previously set network interfaces...
==> test: Preparing network interfaces based on configuration...
    test: Adapter 1: nat
    test: Adapter 2: hostonly
==> test: Forwarding ports...
    test: 22 (guest) => 2299 (host) (adapter 1)
    test: 80 (guest) => 8099 (host) (adapter 1)
==> test: Running 'pre-boot' VM customizations...
==> test: Booting VM...
==> test: Waiting for machine to boot. This may take a few minutes...
    test: SSH address: 127.0.0.1:2299
    test: SSH username: ubuntu
    test: SSH auth method: password
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

[Marvin R. (therealmarv)]

I also experienced this time out issues from time to time. Something is hanging there. You should try booting again.

Waiting after the ssh auth method password takes without time out 1 minute and 18 seconds here and with former Ubuntu 14.04 Vagrant image it goes nearly instantly. This step needs definitely optimization. For what reason is Ubuntu 16.04 waiting over 1 minute after "SSH auth method: password" ?
Usually I'm spinning Vagrant boxes up and down for quick testing but Ubuntu 16.04 steals minimum 1m18s of waiting time for nothing and it's not fun to use Vagrant with it.

My configuration:
VirtualBox 5.1.2 r108956
Vagrant 1.8.5
Box: Ubuntu/Xenial64 20160805.0.0

[Miguel (miguelsmuller)]

Now virtual machine is booting. What bothers me is the fact that the User and default password not be vagrant/vagrant.

Another mistake came ... he can not create shared folders.

C:\Users\Miguel\Documents\vagrant>vagrant up test
Bringing machine 'test' up with 'virtualbox' provider...
==> test: Checking if box 'ubuntu/xenial64' is up to date...
==> test: A newer version of the box 'ubuntu/xenial64' is available! You currently
==> test: have version '20160805.0.0'. The latest is version '20160811.0.0'. Run
==> test: `vagrant box update` to update.
==> test: Clearing any previously set forwarded ports...
==> test: Clearing any previously set network interfaces...
==> test: Preparing network interfaces based on configuration...
    test: Adapter 1: nat
    test: Adapter 2: hostonly
==> test: Forwarding ports...
    test: 22 (guest) => 2299 (host) (adapter 1)
    test: 80 (guest) => 8099 (host) (adapter 1)
==> test: Running 'pre-boot' VM customizations...
==> test: Booting VM...
==> test: Waiting for machine to boot. This may take a few minutes...
    test: SSH address: 127.0.0.1:2299
    test: SSH username: ubuntu
    test: SSH auth method: password
==> test: Machine booted and ready!
==> test: Checking for guest additions in VM...
    test: The guest additions on this VM do not match the installed version of
    test: VirtualBox! In most cases this is fine, but in rare cases it can
    test: prevent things such as shared folders from working properly. If you see
    test: shared folder errors, please make sure the guest additions within the
    test: virtual machine match the version of VirtualBox you have installed on
    test: your host and reload your VM.
    test:
    test: Guest Additions Version: 5.0.18_Ubuntu r106667
    test: VirtualBox Version: 5.1
==> test: Setting hostname...
==> test: Configuring and enabling network interfaces...
==> test: Mounting shared folders...
    test: /projects => C:/Users/Miguel/Documents/projects
Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attemped was:

set -e
mount -t vboxsf -o uid=`id -u ubuntu`,gid=`getent group ubuntu | cut -d: -f3`,dmode=755,fmode=644 projects /projects
mount -t vboxsf -o uid=`id -u ubuntu`,gid=`id -g ubuntu`,dmode=755,fmode=644 projects /projects

The error output from the command was:

mount: unknown filesystem type 'vboxsf'

[Hagen Kuehn (hag-k)]

As a workaround I suggest to use the Bento boxes. As of https://www.vagrantup.com/docs/boxes.html Bento is one of the two officially-recommended box sets. They are open source too. For Ubuntu Xenial you would use the "bento/ubuntu-16.04" box.