english?
On Thu, Apr 24, 2014 at 4:36 AM, Sudamar Cerqueira <[email protected]>wrote: > Caros, > > Eu tinha uma máquina vagrant funcionando (não conseguia apenas instalar > o meteor), mas atualizei pro vbox 4.3.10 e vagrant 1.5.4 e estou levando > muito erro. > > Mesmo fazendo downgrade, não consigo mais levantar a maquina. Estou > buscando ajuda aqui com a esperança de que não vcs já tenham passado por > algo parecido e não precise formatar a máquina. > > Eu usei o VagrantFile original, gerado pelo vagrant init (vagrant init > hashicorp/precise32). não modifiquei mais nada. Tenho o paralells instalado > na minha máquina, mas no momento ele está desligado em todas as tentativas! > :( > > Vamos aos erros: > > Situação 1) Vagrant 1.5.3 e vbox 4.3.10 SEM SUDO (vagrant up): > > *Could not find the X.Org or XFree86 Window System, skipping.* > > *An error occurred during installation of VirtualBox Guest Additions > 4.3.10. Some functionality may not work as intended.* > > *In most cases it is OK that the "Window System drivers" installation > failed.* > > *stdin: is not a tty* > > *==> default: Checking for guest additions in VM...* > > *==> default: Mounting shared folders...* > > * default: /vagrant => /Users/sudamar/Desktop/DESENVOLVIMENTO/vagrant* > > *Failed to mount folders in Linux guest. This is usually because* > > *the "vboxsf" file system is not available. Please verify that* > > *the guest additions are properly installed in the guest and* > > *can work properly. The command attempted was:* > > *mount -t vboxsf -o uid=`id -u vagrant`,gid=`getent group vagrant | cut > -d: -f3` /vagrant /vagrant* > > *mount -t vboxsf -o uid=`id -u vagrant`,gid=`id -g vagrant` /vagrant > /vagrant* > > > *Situação 2) Vagrant 1.5.4 (e 1.5.3 tbm) e vbox 4.3.10 - COM SUDO (sudo > vagrant up):* > > > *==> default: Importing base box 'hashicorp/precise32'...* > > *==> default: Matching MAC address for NAT networking...* > > *==> default: Checking if box 'hashicorp/precise32' is up to date...* > > *==> 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 <http://127.0.0.1:2222>* > > * default: SSH username: vagrant* > > * default: SSH auth method: private key* > > *Timed out while waiting for the machine to boot. This means that* > > *Vagrant was unable to communicate with the guest machine within* > > *the configured ("config.vm.boot_timeout" value) time period.* > > > *If you look above, you should be able to see the error(s) that* > > *Vagrant had when attempting to connect to the machine. These errors* > > *are usually good hints as to what may be wrong.* > > > *If you're using a custom box, make sure that networking is properly* > > *working and you're able to connect to the machine. It is a common* > > *problem that networking isn't setup properly in these boxes.* > > *Verify that authentication configurations are also setup properly,* > > *as well.* > > > *If the box appears to be booting properly, you may want to increase* > > *the timeout ("config.vm.boot_timeout") value.* > > *Já não sei o que fazer para tentar arrumar isso!* > > > > -- > 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. > -- 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.
