Installation via Vagrant requires GUI

Question

UPDATE (5 Feb, 2014) : This error comes up when machine is restarted without proper shutdown

I am trying to install EdX's open source Learning Management System, through their development vagrant box on a remote machine. However, I get an error related to virtual machine GUI. Is there anything that can be done via CLI/ssh ? This is the exact error.

The guest machine entered an invalid state while waiting for it       
to boot. Valid states are 'starting, running'. The machine is in the  
'poweroff' state. Please verify everything is configured              
properly and try again.                                               

If the provider you're using has a GUI that comes with it,            
it is often helpful to open that and watch the machine, since the     
GUI often has more helpful error messages than Vagrant can retrieve.  
For example, if you're using VirtualBox, run `vagrant up` while the   
VirtualBox GUI is open.

Below are the contents of VagrantFile

# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure("2") do |config|
  config.vm.box = "precise32"
  config.vm.box_url = "http://files.vagrantup.com/precise32.box"

  config.vm.network :forwarded_port, guest: 8000, host: 9000
  config.vm.network :forwarded_port, guest: 8001, host: 9001

  # Create a private network, which allows host-only access to the machine
  # using a specific IP.
  config.vm.network :private_network, ip: "192.168.20.40"

  nfs_setting = RUBY_PLATFORM =~ /darwin/ || RUBY_PLATFORM =~ /linux/
  config.vm.synced_folder ".", "/opt/edx/edx-platform", id: "vagrant-root", :nfs => nfs_setting

  # Make it so that network access from the vagrant guest is able to
  # use SSH private keys that are present on the host without copying
  # them into the VM.
  config.ssh.forward_agent = true

  config.vm.provider :virtualbox do |vb|
    # Use VBoxManage to customize the VM. For example to change memory:
    vb.customize ["modifyvm", :id, "--memory", "2048"]

    # This setting makes it so that network access from inside the vagrant guest
    # is able to resolve DNS using the hosts VPN connection.
    vb.customize ["modifyvm", :id, "--natdnshostresolver1", "on"]
  end

  config.vm.provision :shell, :path => "scripts/install-acceptance-req.sh"
  config.vm.provision :shell, :path => "scripts/vagrant-provisioning.sh"
end

please, show you Vagrantfile configuration. – Robert Jan 22 '14 at 12:56 — Robert, Jan 22 '14 at 12:56
added the vagrant configuration. – iankit Oct 30 '14 at 17:31 — iankit, Oct 30 '14 at 17:31

score 1 · Accepted Answer · edited Apr 13 '17 at 12:36

No, there's not much you can do/diagnose using CLI or Ssh at this stage, because the VM fails to initialize properly and is not in a "working" state.

You should follow the advice contained in the error message.

Destroy your current VM:

vagrant destroy

then open VirtualBox GUI, and restart the Vagrant setup with :

vagrant up

You can then watch in the VM Console/Window (from Virtualbox GUI) what fails and prevents the setup from running.

An alternative way to start the VM with a console GUI would be to modify your Vagrantfile:

# You will find this line in the Vagrantfile
Vagrant.configure("2") do |config|

  #Add this directive
  config.vm.provider "virtualbox" do |v|
    v.gui = true
  end


end

(destroy your existing and failing VM with vagrant destroyand then run vagrant up)

If the remote machine (where VirtualBox runs) is a Unix box accessed using SSH, you may be able to export the GUI to your local machine using the -Xoption when SSHing to it. See this answer for more details about ssh -X

destroy and again up is not helping. Same error is repeated. Yet to try the alternative method. — iankit, Jan 22 '14 at 10:49
Thanks for this answer! I had trouble with a similar issue, and had already found the `v.gui = true` solution, but could not get it to work until I found your answer saying I should put it in the `Vagrant.configure("2") do |config|` block — Energya, Apr 11 '15 at 14:47

score -1 · Answer 2 · answered Mar 09 '14 at 00:22

-1

This message occured with my environment because 2 things:

1 - If your VirtualBox Software GUI have is closed, just open it. Ps.: Try vagrant destroy then vagrant up again

2 - If the problem persist, just update your VirtualBox GUI. VirtualBox Downloads

Let me know if it's done.

answered Mar 09 '14 at 00:22

Helder Robalo

1,827
2
13
16

1

I dont have access to GUI in the machine. It is a VPS with only shell access – iankit Mar 09 '14 at 09:01

Installation via Vagrant requires GUI

2 Answers2