Package: vagrant
Version: 1.7.4+dfsg-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
I installed the latest vagrant package from the Debian repositories on my
laptop running an up-to-date Debian unstable installation. I did this after
removing vagrant which I had installed from the .deb file available on Vagrant
website.
When I run vagrant up to provision and start a VM, it fails with the following
error:
<snip>
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'lgp171188/jessie64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'lgp171188/jessie64' is up to date...
==> default: Setting the name of the VM:
xpens-master_default_1443896094725_70453
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 8000 => 8000 (adapter 1)
default: 22 => 2222 (adapter 1)
==> default: Booting VM...
==> default: 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 primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue.
</snip>
I have installed the virtualbox-guest-utils, virtualbox-guest-x11 packages
and still I got this error.
But later when I installed virtualbox-ext-pack package from non-free, vagrant
worked fine without the above error. So if this is clearly reproducible,
vagrant package should depend on the virtualbox-ext-package which might
cause vagrant to be moved to non-free section.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages vagrant depends on:
ii bsdtar 3.1.2-11+b1
ii bundler 1.10.6-2
ii curl 7.44.0-2
ii openssh-client 1:6.9p1-2
ii ruby 1:2.1.5.1
ii ruby-childprocess 0.5.5-1
ii ruby-erubis 2.7.0-3
ii ruby-i18n 0.6.11-2
ii ruby-listen 3.0.3-2
ii ruby-log4r 1.1.10-4
ii ruby-net-scp 1.2.1-2
ii ruby-net-sftp 1:2.1.2-3
ii ruby-net-ssh 1:2.9.2-2
ii ruby-nokogiri 1.6.6.2+ds-2+b1
ii ruby-rb-inotify 0.9.5-1
ii ruby-rest-client 1.8.0-1
vagrant recommends no packages.
Versions of packages vagrant suggests:
ii virtualbox 5.0.4-dfsg-4
-- no debconf information
