[Bug 1573058] Re: Ubuntu 16.04 current not booting in Vagrant (gurumeditation)

[Launchpad Bug Tracker]

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

** Changed in: livecd-rootfs (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1573058

Title:
  Ubuntu 16.04 current not booting in Vagrant (gurumeditation)

Status in livecd-rootfs package in Ubuntu:
  Confirmed

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1573058/+subscriptions