I post this problem in the 'linux hosts' group but this is only partially correct.
So here is my setup:
- I am running windows 10
- VMware workstation with super-up-to-date arch linux
- virtualization enabled for vm (vt-x)
- in arch linux, I run vagrant to provision a virtualbox vm
Short version:
When I start the box from virtual box, it works. When I use vagrant with nothing but the box, it crashes.
This crashes every single time. Tried it with different boxes, e.g. trusty64 and centos. This happens with a pretty much empty Vagrantfile, naming only the box.
Immediately when the machine is starting up, it goes into gurumeditation. Attached is a log file.
The crash happens pretty much immediately. WAY WAY WAY before the machine is ready for login. Basically before the virtual box screen shows even anything of the bootup sequence. The status of the machine is 'Guru Meditation'.
The crash happens at timestamp 00:00:00.177733, that is after 177 ms.
Now here is the thing: When I use the virtualbox gui and select the machine that has just been added by vagrant and start it up manually, it just starts. When I now go back to vagrant I can use vagrant up / vagrant provision and it is fine.
When I stop vagrant from trying to tunnel into the machine it also seems to work. The crash occurrs way before the network drivers are ready on the guest. It looks as if vagrant is hindering the machine to properly boot.
When I shutdown the machine and then use vagrant up again, I get the same crash.
I also attach a log file of the exact same machine booting up correctly. You can compare the two files, and the occurs at line 885 in the log file.
I am in need of some help here. I tried many things with the vagrant file, including one that looks just like this:
Code: Select all
Vagrant.require_version ">= 1.5"
Vagrant.configure("2") do |config|
config.vm.box = "ubuntu/trusty64"
end
Super short summary:
- use vagrant and virutalbox => guru meditation immediately. Tested several boxes, super simple Vagrantfile.
- use virtualbox gui to boot machine => works always. Vagrant up / vagrant provision then seems to work against the already running machine.
- Shutting down the guest and using vagrant up => same crash.