Why does "vagrant up" trigger the installation of linux-headers-3.2.0-4-486 and Guest Additions?

[Jason Hsu]

I've created a fork of Pierre Mavro's packer-wheezy project at https://github.com/jhsu802701/packer-debian-wheezy-rvm .  What I'm working on is providing a Debian Stable Vagrant box with RVM for Ruby on Rails development.

So far, the Vagrant boxes that I've been able to create must take the time to install Guest Additions and linux-headers-3.2.0-4-486.  Why wasn't this taken care of during the packer build phase?  I thought I took out the parts of the provisioning scripts that remove the Guest Additions and Linux headers package.  Is there a way to get Packer to just leave the Guest Additions and Linux headers alone so that it doesn't have to reinstall them later?

The relevant part of the screen output is:
No installation found.
stdin: is not a tty
Reading package lists...
Building dependency tree...
Reading state information...
dkms is already the newest version.
The following NEW packages will be installed:
  linux-headers-3.2.0-4-486
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 588 kB of archives.
After this operation, 2,358 kB of additional disk space will be used.
Get:1 http://mirrors.kernel.org/debian/ wheezy/main linux-headers-3.2.0-4-486 i386 3.2.63-2 [588 kB]
dpkg-preconfigure: unable to re-open stdin: No such file or directory
Fetched 588 kB in 5s (101 kB/s)
Selecting previously unselected package linux-headers-3.2.0-4-486.
(Reading database ... 53180 files and directories currently installed.)
Unpacking linux-headers-3.2.0-4-486 (from .../linux-headers-3.2.0-4-486_3.2.63-2_i386.deb) ...
Setting up linux-headers-3.2.0-4-486 (3.2.63-2) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 3.2.0-4-486
Error! Could not locate dkms.conf file.
File:  does not exist.
Copy iso file /usr/share/virtualbox/VBoxGuestAdditions.iso into the box /tmp/VBoxGuestAdditions.iso
stdin: is not a tty
mount: block device /tmp/VBoxGuestAdditions.iso is write-protected, mounting read-only
Installing Virtualbox Guest Additions 4.1.18 - guest version is
stdin: is not a tty
Verifying archive integrity... All good.
Uncompressing VirtualBox 4.1.18 Guest Additions for Linux.........
VirtualBox Guest Additions installer
Removing installed version 4.1.18 of VirtualBox Guest Additions...
Removing existing VirtualBox DKMS kernel modules ...done.
Removing existing VirtualBox non-DKMS kernel modules ...done.
Building the VirtualBox Guest Additions kernel modules
The headers for the current running kernel were not found. If the following
module compilation fails then this could be the reason.

Building the main Guest Additions module ...done.
Building the shared folder support module ...done.
Building the OpenGL support module ...fail!
(Look at /var/log/vboxadd-install.log to find out what went wrong)
Doing non-kernel setup of the Guest Additions ...done.
Installing the Window System drivers ...fail!
(Could not find the X.Org or XFree86 Window System.)
An error occurred during installation of VirtualBox Guest Additions 4.1.18. Some functionality may not work as intended.
In most cases it is OK that the "Window System drivers" installation failed.
stdin: is not a tty

[Alvaro Miranda Aguilera]

Do you have a vagrant plugin called vbguest or similar?

--
You received this message because you are subscribed to the Google Groups "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jason Hsu]

No, I don't.  I need to familiarize myself with Vagrant plugins.

Would having this plugin allow me to get to work in the virtual environment immediately, WITHOUT having to wait for the Guest Additions to install?

[Alvaro Miranda Aguilera]

no, actually that plugin install vbguest .

Not sure if there is something on this particular OS that cause himself to install but I doubt it.

what's the ouput of  vagrant plugin list ?

[Jason Hsu]

It turns out that vagrant-vbguest is installed after all.  The output of "vagrant plugin list" is:
vagrant-login (1.0.1, system)
vagrant-share (1.1.2, system)
vagrant-vbguest (0.10.0)

[Alvaro Miranda Aguilera]

That is what is installiing virtualbox guest.

--