The VM failed to remain in the "running" state while attempting to boot -- for seemingly no good reason

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

The VM failed to remain in the "running" state while attempting to boot -- for seemingly no good reason

Steven Emmerson
I can't create a VM for the reason in the subject line:

$ vagrant destroy
[default] VM not created. Moving on...
$ egrep -v '^ *(#|$)' Vagrantfile
VAGRANTFILE_API_VERSION = "2"
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
  config.vm.box = "precise32"
end
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
[default] Importing base box 'precise32'...
[default] Matching MAC address for NAT networking...
[default] Setting the name of the VM...
[default] Clearing any previously set forwarded ports...
[default] Creating shared folders metadata...
[default] Clearing any previously set network interfaces...
[default] Preparing network interfaces based on configuration...
[default] Forwarding ports...
[default] -- 22 => 2222 (adapter 1)
[default] Booting VM...
[default] Waiting for VM to boot. This can take a few minutes.
The VM failed to remain in the "running" state while attempting to boot.
This is normally caused by a misconfiguration or host system incompatibilities.
Please open the VirtualBox GUI and attempt to boot the virtual machine
manually to get a more informative error message.

The info-level messages from Vagrant and the log messages from VirtualBox are attached. Note that there is no mention of the BIOS in the messages from VirtualBox.

Any advice would be greatly appreciated.

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

vagrantup.log (60K) Download Attachment
VBoxSVC.log (22K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: The VM failed to remain in the "running" state while attempting to boot -- for seemingly no good reason

Steven Emmerson
The problems appears to have been that I was not a member of the "vboxusers" group, which was created by the installation of VirtualBox.

On Tuesday, August 13, 2013 12:01:49 PM UTC-6, Steven Emmerson wrote:
I can't create a VM for the reason in the subject line:

$ vagrant destroy
[default] VM not created. Moving on...
$ egrep -v '^ *(#|$)' Vagrantfile
VAGRANTFILE_API_VERSION = "2"
Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
  config.vm.box = "precise32"
end
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
[default] Importing base box 'precise32'...
[default] Matching MAC address for NAT networking...
[default] Setting the name of the VM...
[default] Clearing any previously set forwarded ports...
[default] Creating shared folders metadata...
[default] Clearing any previously set network interfaces...
[default] Preparing network interfaces based on configuration...
[default] Forwarding ports...
[default] -- 22 => 2222 (adapter 1)
[default] Booting VM...
[default] Waiting for VM to boot. This can take a few minutes.
The VM failed to remain in the "running" state while attempting to boot.
This is normally caused by a misconfiguration or host system incompatibilities.
Please open the VirtualBox GUI and attempt to boot the virtual machine
manually to get a more informative error message.

The info-level messages from Vagrant and the log messages from VirtualBox are attached. Note that there is no mention of the BIOS in the messages from VirtualBox.

Any advice would be greatly appreciated.

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.