I will give new Vagrant 1.5.4 a try, wonder if it changes anything. I guess 
you're running Vagrant with VirtualBox locally, right? Most probably me 
trying to run them "in a cloud" is what makes it different from a typical 
use. EC2 was not an option right away 
- https://forums.virtualbox.org/viewtopic.php?f=1&t=51584.


On Monday, April 21, 2014 2:51:41 PM UTC+2, 谢美龙 wrote:
>
> I am using the same version vagrant and virtualbox,  ubuntu 12.04 can 
> start up , but ubuntu 14.04 can't start up in my computer。
>
> 在 2014年4月20日星期日UTC+8下午10时00分46秒,Evgeny Goldin写道:
>>
>> Hi,
>>
>> I'm sorry if this is a duplicate but I can't see my previous message has 
>> made it to the mailing list.
>>
>> The problem I'm facing is Vagrant / VirtualBox fails to start on 
>> DigitalOcean / Google Compute Engine Ubuntu instances:
>>
>> $ uname -a
>> Linux boxer 3.8.0-29-generic #42~precise1-Ubuntu SMP Wed Aug 14 16:19:23 
>> UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
>>
>> $ lsb_release -a
>> No LSB modules are available.
>> Distributor ID: Ubuntu
>> Description:    Ubuntu 12.04.4 LTS
>> Release:    12.04
>> Codename:   precise
>>
>> $ sudo apt-get update  -y
>> $ sudo apt-get upgrade -y
>> $ echo "deb http://download.virtualbox.org/virtualbox/debian$(lsb_release 
>> -sc) contrib" | sudo tee 
>> /etc/apt/sources.list.d/virtualbox.list
>> $ wget -q 
>> http://download.virtualbox.org/virtualbox/debian/oracle_vbox.asc -O- | 
>> sudo apt-key add -
>> $ sudo apt-get update -y
>> $ sudo apt-get install -y virtualbox-4.3
>> $ wget https://dl.bintray.com/mitchellh/vagrant/vagrant_1.5.3_x86_64.deb
>> $ sudo dpkg -i vagrant_1.5.3_x86_64.deb
>> $ rm -rf       vagrant_1.5.3_x86_64.deb
>>
>> $ vagrant --version
>> Vagrant 1.5.3
>>
>> $ VBoxManage --version
>> 4.3.10r93012
>>
>> $ vagrant init hashicorp/precise64
>> A `Vagrantfile` has been placed in this directory. You are now
>> ready to `vagrant up` your first virtual environment! Please read
>> the comments in the Vagrantfile as well as documentation on
>> `vagrantup.com` for more information on using Vagrant.
>>
>> $ vagrant up
>> Bringing machine 'default' up with 'virtualbox' provider...
>> ==> default: Box 'hashicorp/precise64' could not be found. Attempting to 
>> find and install...
>>     default: Box Provider: virtualbox
>>     default: Box Version: >= 0
>> ==> default: Loading metadata for box 'hashicorp/precise64'
>>     default: URL: https://vagrantcloud.com/hashicorp/precise64
>> ==> default: Adding box 'hashicorp/precise64' (v1.1.0) for provider: 
>> virtualbox
>>     default: Downloading: 
>> https://vagrantcloud.com/hashicorp/precise64/version/2/provider/virtualbox.box
>> ==> default: Successfully added box 'hashicorp/precise64' (v1.1.0) for 
>> 'virtualbox'!
>> ==> default: Importing base box 'hashicorp/precise64'...
>> ==> default: Matching MAC address for NAT networking...
>> ==> default: Checking if box 'hashicorp/precise64' is up to date...
>> ==> default: Setting the name of the VM: root_default_1398002051745_45539
>> ==> default: Clearing any previously set network interfaces...
>> ==> default: Preparing network interfaces based on configuration...
>>     default: Adapter 1: nat
>> ==> default: Forwarding ports...
>>     default: 22 => 2222 (adapter 1)
>> ==> default: Booting VM...
>> ==> default: Waiting for machine to boot. This may take a few minutes...
>>     default: SSH address: 127.0.0.1:2222
>>     default: SSH username: vagrant
>>     default: SSH auth method: private key
>>     default: Warning: Connection refused. Retrying...
>> 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.
>> $
>>
>>

-- 
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to