3 ms·
Vagrant is absolutely fantastic. But I have an issue with the default precise64 box. If the vm is shut down abnormally (manual power off from virtualbox, unexp
by neurostimulant 13y ago
Vagrant is absolutely fantastic. But I have an issue with the default precise64 box.
If the vm is shut down abnormally (manual power off from virtualbox, unexpected power outage, etc), next time I run `vagrant up`, the vm would be stuck on grub. It appear to be a problem with ubuntu and I need to start the vm in gui mode (as opposed to vagrant's default headless mode) to resolve this (changed timeout=-1 to timeout=0 in /etc/grub.d/00_header and run update-grub).
- beagle3 13y agoYes, this is a known problem with precise. The discussion on https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/669481 https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/669481 indicates that a fix has been released, although one wasn't - a 12.04 default server install will STILL happily hang after a boot problem until you press "enter" on your keyboard. Additional reboots will not help. And given that 12.04 is still the LTS version, it makes Ubuntu unusable for long term remote servers unless you have an IPKVM. Of course, after 12.04.03 you can update your /etc/default/grub to include: GRUB_RECORDFAIL_TIMEOUT=0 and then do grub-update (and some people say you should also do: DEBIAN_FRONTEND=noninteractive dpkg-reconfigure grub-pc Although I can't figure out why that would be needed)
- jcastro 13y agoWhich exact precise64 box are you using? Ubuntu now publishes regularly updated Vagrant images, do you have this problem with this box? - http://cloud-images.ubuntu.com/vagrant/precise/current/ http://cloud-images.ubuntu.com/vagrant/precise/current/
- neurostimulant 13y agoThanks for the info. I was using the default precise64 box from fresh vagrant init. I'll try that box see if the problem persist.