andrewdeandrade
commented
11 years ago Furthermore, when I add asecond provisioner after my main shell script:
"provisioners": [{
"type": "shell",
"script": "./configs/packer-bootstrap.sh",
"execute_command" : "echo {{user `ssh_pass`}} | sudo -S sh '{{ .Path }}'"
},{
"type": "shell",
"script": "./configs/temp.sh",
"execute_command" : "echo {{user `ssh_pass`}} | sudo -S sh '{{ .Path }}'"
}],and add the following two lines to it:
sleep 10
lsmod | grep vbox > /home/vagrant/36_vbox_system_modules.logIt sits and appears stuck with almost 100% CPU across 4 processor cores on my Macbook Air 13" (kernel_task)
2013/10/15 20:28:09 /Users/me/go/bin/packer-builder-virtualbox: 2013/10/15 20:28:09 remote command exited with '0': echo vagrant | sudo -S sh '/tmp/script.sh'
2013/10/15 20:28:09 127374 bytes written for 'stdout'
2013/10/15 20:28:09 0 bytes written for 'stderr'
2013/10/15 20:28:09 127374 bytes written for 'stdout'
2013/10/15 20:28:09 0 bytes written for 'stderr'
2013/10/15 20:28:09 /Users/me/go/bin/packer-command-build: 2013/10/15 20:28:09 127374 bytes written for 'stdout'
2013/10/15 20:28:09 /Users/me/go/bin/packer-command-build: 2013/10/15 20:28:09 0 bytes written for 'stderr'
2013/10/15 20:28:09 /Users/me/go/bin/packer-provisioner-shell: 2013/10/15 20:28:09 0 bytes written for 'stderr'
2013/10/15 20:28:09 /Users/me/go/bin/packer-provisioner-shell: 2013/10/15 20:28:09 127374 bytes written for 'stdout'
==> vagrant-precise64: Provisioning with shell script: ./configs/temp.sh
2013/10/15 20:28:09 ui: ==> vagrant-precise64: Provisioning with shell script: ./configs/temp.sh
2013/10/15 20:28:09 /Users/me/go/bin/packer-provisioner-shell: 2013/10/15 20:28:09 Opening ./configs/temp.sh for reading
2013/10/15 20:28:09 /Users/me/go/bin/packer-builder-virtualbox: 2013/10/15 20:28:09 opening new ssh session
2013/10/15 20:28:10 /Users/me/go/bin/packer-builder-virtualbox: 2013/10/15 20:28:10 Starting remote scp process: scp -vt /tmp
2013/10/15 20:28:11 /Users/me/go/bin/packer-builder-virtualbox: 2013/10/15 20:28:11 Started SCP session, beginning transfers...
2013/10/15 20:28:11 /Users/me/go/bin/packer-builder-virtualbox: 2013/10/15 20:28:11 Copying input data into in-memory buffer so we can get the length
2013/10/15 20:28:12 /Users/me/go/bin/packer-builder-virtualbox: 2013/10/15 20:28:12 Opening conn for SSH to tcp 127.0.0.1:3213That last log entry is at 20:28:12 and it is now ~20:49:00.
I don't know if this is or is not related to the problem above. I was hoping to check for the presence of vboxsf in a second provisioning shell script.
mitchellh
dindinoh
benissimo
mhamrah
I'm using packer to build a Vagrant box for use in VirtualBox. I have an error that could be a Packer or VirtualBox problem, but I am not sure since I haven't seen this error with previous VirtualBoxes used with Vagrant (but my prior experience is admittedly limited). Below are the details. FWIW, my suspicion is that one of the Packer scripts or a tool it calls is kicking off some sort of kernel recompile when packaging up the vmdk, causing the loss of
vboxsf.When building the VM, I know that installation of VBoxAdditions via my shell provisioning script is working perfectly (no errors, log below. All dependencies like build-essentials, dkms and linux-headers-generic--
uname -rare available as is X and XFree86). After installing, I write the result oflsmod | grep vboxto a log file:I then install Chef, do a bunch of cleanup and right before returning
exit 0at the end of the script, I write at the result oflsmod | grep vboxto a second log and get the same exact value as before, confirming that the linux kernel extensions are there before Packer takes over and passes the virtual machine through the Vagrant post-processor.Despite all this, when I add the Vagrant box and try to boot it with the
--no-provisionflag to keep things simple, I get the following error:In order to triage this, I've first tried the
"keep_input_artifact": trueflag on the vagrant post-processor and loaded theovf/vmdkdirectly in VirtualBox and after logging and runninglsmod | grep vboxI get back nothing. I then tried adding a second shell provisioning after the first that does nothing but log the output oflsmod | grep vboxto another log to see where this kernel extension modules are getting lost.When in the vm
modprobe vboxdrvreturnsFATAL: Module vboxdrv not found.When I look in
/etc/init.d/for thevboxdrvbinary, it is not there.When I try to run the
VirtualBoxcommand at the$prompt I get:The kernel ring buffer returns nothing when I pipe
dmesgthrough agrepwithvboxdrv,vboxor even justvb.FWIW, the only vbox related items in
/etc/init.d/arevboxadd,vboxadd-serviceandvboxadd-x11FWIW, I installed VirtualBox Guest additions with the following snippet:
I also found the source of
vboxsfin/usr/src/vboxguest-4.2.18/vboxsf