[Pkg-virtualbox-devel] Bug#800800: vagrant: Running vagrant up to start a VM fails with error

[Antonio Terceiro]

Control: severity -1 normal

On Sat, Oct 03, 2015 at 11:57:23PM +0530, L. Guruprasad wrote:
> 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.

Those packages need to be installed on Debian guests, not on Debian
hosts.

> 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.

vagrant does not depend on virtualbox (it can use other virtualization
providers -- e.g. I do not use virtuabox myself), so it does not make
any sense for it to depend on something that virtualbox needs to work.

I am copying the virtualbox maintainers to see if they have some input.
Maybe virtualbox should recommend virtualbox-ext-pack of something like
that.

-- 
Antonio Terceiro <terceiro at debian.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-virtualbox-devel/attachments/20151003/71ef0d01/attachment.sig>