Skip to content

Instantly share code, notes, and snippets.

@mwarkentin
Created July 29, 2011 11:58
Show Gist options
  • Save mwarkentin/1113680 to your computer and use it in GitHub Desktop.
Save mwarkentin/1113680 to your computer and use it in GitHub Desktop.
Vagrant Error
vagrant@lucid32:~$ sudo apt-get install build-essential module-assistant linux-headers-$(uname -r) dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
build-essential is already the newest version.
module-assistant is already the newest version.
The following extra packages will be installed:
linux-headers-2.6.32-28
Recommended packages:
linux-headers-2.6-686 linux-headers-2.6-amd64 linux-headers-generic linux-headers
The following NEW packages will be installed:
dkms linux-headers-2.6.32-28 linux-headers-2.6.32-28-generic
0 upgraded, 3 newly installed, 0 to remove and 2 not upgraded.
Need to get 10.7MB of archives.
After this operation, 85.9MB of additional disk space will be used.
Do you want to continue [Y/n]? Y
Get:1 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main dkms 2.1.1.2-2ubuntu1 [70.8kB]
Get:2 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main linux-headers-2.6.32-28 2.6.32-28.55 [9,907kB]
Get:3 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main linux-headers-2.6.32-28-generic 2.6.32-28.55 [764kB]
Fetched 10.7MB in 26s (401kB/s)
Selecting previously deselected package dkms.
(Reading database ... 28178 files and directories currently installed.)
Unpacking dkms (from .../dkms_2.1.1.2-2ubuntu1_all.deb) ...
Selecting previously deselected package linux-headers-2.6.32-28.
Unpacking linux-headers-2.6.32-28 (from .../linux-headers-2.6.32-28_2.6.32-28.55_all.deb) ...
Selecting previously deselected package linux-headers-2.6.32-28-generic.
Unpacking linux-headers-2.6.32-28-generic (from .../linux-headers-2.6.32-28-generic_2.6.32-28.55_i386.deb) ...
Processing triggers for man-db ...
Setting up dkms (2.1.1.2-2ubuntu1) ...
Setting up linux-headers-2.6.32-28 (2.6.32-28.55) ...
Setting up linux-headers-2.6.32-28-generic (2.6.32-28.55) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 2.6.32-28-generic /boot/vmlinuz-2.6.32-28-generic
vagrant@lucid32:~$ sudo sh /mnt/VBoxLinuxAdditions.run --nox11
Verifying archive integrity... All good.
Uncompressing VirtualBox 4.1.0 Guest Additions for Linux..........
VirtualBox Guest Additions installer
Removing installed version 4.1.0 of VirtualBox Guest Additions...
tar: Record size = 8 blocks
Removing existing VirtualBox DKMS kernel modules ...done.
Removing existing VirtualBox non-DKMS kernel modules ...done.
Building the VirtualBox Guest Additions kernel modules ...done.
Doing non-kernel setup of the Guest Additions ...done.
You should restart your guest to make sure the new modules are actually used
Installing the Window System drivers ...fail!
(Could not find the X.Org or XFree86 Window System.)
vagrant@lucid32:~$ exit
logout
Connection to 127.0.0.1 closed.
mwarkentin@imac vagrant_guide $ vagrant reload
[default] Attempting graceful shutdown of linux...
[default] Clearing any previously set forwarded ports...
[default] Forwarding ports...
[default] -- ssh: 22 => 2222 (adapter 1)
[default] Cleaning previously set shared folders...
[default] Creating shared folders metadata...
[default] Running any VM customizations...
[default] Booting VM...
[default] Waiting for VM to boot. This can take a few minutes.
[default] VM booted and ready for use!
[default] Mounting shared folders...
[default] -- v-root: /vagrant
[default] -- v-csc-2: /tmp/vagrant-chef-4/chef-solo-1
[default] Running provisioner: Vagrant::Provisioners::ChefSolo...
[default] Generating chef JSON and uploading...
[default] Running chef-solo...
[default] stdin: is not a tty
: stderr
[default] /opt/ruby/lib/ruby/gems/1.8/gems/chef-0.10.2/bin/../lib/chef/application/solo.rb:159:in `join': stderr
[default] : : stderr
[default] can't convert nil into String: stderr
[default] (: stderr
[default] TypeError: stderr
[default] )
: stderr
[default] from /opt/ruby/lib/ruby/gems/1.8/gems/chef-0.10.2/bin/../lib/chef/application/solo.rb:159:in `reconfigure'
: stderr
[default] from /opt/ruby/lib/ruby/gems/1.8/gems/chef-0.10.2/bin/../lib/chef/application.rb:64:in `run'
: stderr
[default] from /opt/ruby/lib/ruby/gems/1.8/gems/chef-0.10.2/bin/chef-solo:25
: stderr
[default] from /opt/ruby/bin/chef-solo:19:in `load'
: stderr
[default] from /opt/ruby/bin/chef-solo:19
: stderr
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
chef-solo -c /tmp/vagrant-chef-4/solo.rb -j /tmp/vagrant-chef-4/dna.json
The output of the command prior to failing is outputted below:
[no output]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment