date:20171206

Re: [vagrant-up] Trying to set up a virtual box with vagrant

2017-12-06 Thread Alvaro Miranda Aguilera

hello

please use your normal user, no need to use run-ad-admin

Alvaro.


On Wed, Dec 6, 2017 at 10:40 PM, Carlos Morales <
carlosmoralesdi...@gmail.com> wrote:

> I'm working with the admin  user and I'm working on  cmd.exe. Thanks
>
> El miércoles, 6 de diciembre de 2017, 22:35:32 (UTC+1), Alvaro Miranda
> Aguilera escribió:
>>
>> Hello
>>
>> There is this error:
>>
>>
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:333:in
>> `unlink': Permission denied @ unlink_internal - C:/Users/Carlos/Desktop/
>> Vagrant_base/.vagrant/machines/default/virtualbox/id (Errno::EACCES)
>>
>> what user are you using?
>>
>> are you in Windows over cmd.exe, powershell, wsl, some bash?
>>
>> Alvaro
>>
>> On Wed, Dec 6, 2017 at 12:40 PM, Carlos Morales 
>> wrote:
>>
>>> I have a virtualbox 5.1.30 and I have vagrant 2.0.1 and I have this
>>> error after doing a vagrant up --provider=virtualbox:
>>>
>>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:333:in
>>> `unlink': Permission denied @ unlink_internal -
>>> C:/Users/Carlos/Desktop/Vagrant_base/.vagrant/machines/default/virtualbox/id
>>> (Errno::EACCES)
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:333:in `delete'
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:333:in `id='
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:146:in `initialize'
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/lib/vagrant/vagrantfile.rb:79:in `new'
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/lib/vagrant/vagrantfile.rb:79:in `machine'
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:733:in `machine'
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/lib/vagrant/plugin/v2/command.rb:180:in `block
>>> in with_target_vms'
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/lib/vagrant/plugin/v2/command.rb:204:in `block
>>> in with_target_vms'
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/lib/vagrant/plugin/v2/command.rb:186:in `each'
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/lib/vagrant/plugin/v2/command.rb:186:in
>>> `with_target_vms'
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/plugins/commands/up/command.rb:87:in `execute'
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/lib/vagrant/cli.rb:42:in `execute'
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:308:in `cli'
>>> from C:/HashiCorp/Vagrant/embedded/
>>> gems/gems/vagrant-2.0.1/bin/vagrant:138:in `'
>>>
>>>
>>> How can I solve it?. Thanks in advance
>>>
>>>
>>> --
>>> This mailing list is governed under the HashiCorp Community Guidelines -
>>> https://www.hashicorp.com/community-guidelines.html. Behavior in
>>> violation of those guidelines may result in your removal from this mailing
>>> list.
>>>
>>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>>> IRC: #vagrant on Freenode
>>> ---
>>> 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 vagrant-up+...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/vagrant-up/5cbeee61-6b10-4fdd-ba08-1039ca622ac1%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Alvaro
>>
>> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> 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 vagrant-up+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/vagrant-up/4b80eaac-69ec-4c1e-b386-1061cbabb6cd%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Alvaro

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those

Re: [vagrant-up] Trying to set up a virtual box with vagrant

2017-12-06 Thread Carlos Morales

I'm working with the admin  user and I'm working on  cmd.exe. Thanks

El miércoles, 6 de diciembre de 2017, 22:35:32 (UTC+1), Alvaro Miranda 
Aguilera escribió:
>
> Hello
>
> There is this error:
>
>
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:333:in
>  
> `unlink': Permission denied @ unlink_internal - C:/Users/Carlos/Desktop/
> Vagrant_base/.vagrant/machines/default/virtualbox/id (Errno::EACCES)
>
> what user are you using?
>
> are you in Windows over cmd.exe, powershell, wsl, some bash?
>
> Alvaro
>
> On Wed, Dec 6, 2017 at 12:40 PM, Carlos Morales  > wrote:
>
>> I have a virtualbox 5.1.30 and I have vagrant 2.0.1 and I have this error 
>> after doing a vagrant up --provider=virtualbox:
>>
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:333:in
>>  
>> `unlink': Permission denied @ unlink_internal - 
>> C:/Users/Carlos/Desktop/Vagrant_base/.vagrant/machines/default/virtualbox/id 
>> (Errno::EACCES)
>> from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:333:in
>>  
>> `delete'
>> from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:333:in
>>  
>> `id='
>> from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:146:in
>>  
>> `initialize'
>> from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/vagrantfile.rb:79:in
>>  
>> `new'
>> from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/vagrantfile.rb:79:in
>>  
>> `machine'
>> from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:733:in
>>  
>> `machine'
>> from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/plugin/v2/command.rb:180:in
>>  
>> `block in with_target_vms'
>> from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/plugin/v2/command.rb:204:in
>>  
>> `block in with_target_vms'
>> from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/plugin/v2/command.rb:186:in
>>  
>> `each'
>> from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/plugin/v2/command.rb:186:in
>>  
>> `with_target_vms'
>> from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/plugins/commands/up/command.rb:87:in
>>  
>> `execute'
>> from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/cli.rb:42:in
>>  
>> `execute'
>> from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:308:in
>>  
>> `cli'
>> from 
>> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/bin/vagrant:138:in 
>> `'
>>
>>
>> How can I solve it?. Thanks in advance
>>
>>
>> -- 
>> This mailing list is governed under the HashiCorp Community Guidelines - 
>> https://www.hashicorp.com/community-guidelines.html. Behavior in 
>> violation of those guidelines may result in your removal from this mailing 
>> list.
>>  
>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>> IRC: #vagrant on Freenode
>> --- 
>> 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 vagrant-up+...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/vagrant-up/5cbeee61-6b10-4fdd-ba08-1039ca622ac1%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Alvaro
>
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/4b80eaac-69ec-4c1e-b386-1061cbabb6cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] No response after "vagrant up" command in Git Bash

2017-12-06 Thread Alvaro Miranda Aguilera

hello

on a fresh install you should see a pop-up that ruby is asking for
permissions to add firewall access some networks (local/internet)

are you admin on the box?

can you cancel that, ensure there is not any unkown window open and try
again?

you should get the typical firewall windows pop up as long you are not in a
restricted setup where all is denied.

Alvaro.


On Wed, Dec 6, 2017 at 8:21 PM, Andy Carey  wrote:

> I am working in the Udacity course "Linux Command Line Basics". I have
> installed Git, and am running it fine. I have installed virtual box from
> here  for a windows host. And
> I have installed vagrant for a
> 64 bit OS. I got a VM configuration file (i have tried the one provided by
> the course, and the one downloaded from Vagrant). I navigatged to the
> directory i would be working in and typed in "vagrant up"... at that point
> my terminal stops producing anything. here is a screen shot of what i see -
> https://i.imgur.com/sMci4ik.png this has been like this since 9:00 AM CST
> today. Anybody have any suggestions?
>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> 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 vagrant-up+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/vagrant-up/170512c6-3a9a-40d6-9f81-4de67db52862%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Alvaro

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0ey%2BLVhSBO2F1rzG%2BQnGysWA1kSpcKT-8K-O2kU7DP%2Bixw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Trying to set up a virtual box with vagrant

2017-12-06 Thread Alvaro Miranda Aguilera

Hello

There is this error:


C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:333:in
`unlink': Permission denied @ unlink_internal - C:/Users/Carlos/Desktop/
Vagrant_base/.vagrant/machines/default/virtualbox/id (Errno::EACCES)

what user are you using?

are you in Windows over cmd.exe, powershell, wsl, some bash?

Alvaro

On Wed, Dec 6, 2017 at 12:40 PM, Carlos Morales <
carlosmoralesdi...@gmail.com> wrote:

> I have a virtualbox 5.1.30 and I have vagrant 2.0.1 and I have this error
> after doing a vagrant up --provider=virtualbox:
>
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:333:in
> `unlink': Permission denied @ unlink_internal - C:/Users/Carlos/Desktop/
> Vagrant_base/.vagrant/machines/default/virtualbox/id (Errno::EACCES)
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:333:in
> `delete'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:333:in
> `id='
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:146:in
> `initialize'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/vagrantfile.rb:79:in
> `new'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/vagrantfile.rb:79:in
> `machine'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:733:in
> `machine'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/plugin/v2/command.rb:180:in `block in with_target_vms'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/plugin/v2/command.rb:204:in `block in with_target_vms'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/plugin/v2/command.rb:186:in `each'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/
> vagrant/plugin/v2/command.rb:186:in `with_target_vms'
> from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/
> plugins/commands/up/command.rb:87:in `execute'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/cli.rb:42:in
> `execute'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:308:in
> `cli'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/bin/vagrant:138:in
> `'
>
>
> How can I solve it?. Thanks in advance
>
>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> 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 vagrant-up+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/vagrant-up/5cbeee61-6b10-4fdd-ba08-1039ca622ac1%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Alvaro

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0ezc0gCrwGiD45-OfH0ZJhvRN6LihCgeUX0isc3knNNRCw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Re: No response after "vagrant up" command in Git Bash

2017-12-06 Thread pixel fairy

Try running with debugging enabled

https://www.vagrantup.com/docs/other/debugging.html


On Wednesday, December 6, 2017 at 11:21:16 AM UTC-8, Andy Carey wrote:
>
> I am working in the Udacity course "Linux Command Line Basics". I have 
> installed Git, and am running it fine. I have installed virtual box from 
> here  for a windows host. And 
> I have installed vagrant for a 
> 64 bit OS. I got a VM configuration file (i have tried the one provided by 
> the course, and the one downloaded from Vagrant). I navigatged to the 
> directory i would be working in and typed in "vagrant up"... at that point 
> my terminal stops producing anything. here is a screen shot of what i see - 
> https://i.imgur.com/sMci4ik.png this has been like this since 9:00 AM CST 
> today. Anybody have any suggestions?
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/1ad44cb8-c6c9-45a2-a369-0de07f8d97d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] No response after "vagrant up" command in Git Bash

2017-12-06 Thread Andy Carey

I am working in the Udacity course "Linux Command Line Basics". I have 
installed Git, and am running it fine. I have installed virtual box from 
here  for a windows host. And I 
have installed vagrant for a 64 
bit OS. I got a VM configuration file (i have tried the one provided by the 
course, and the one downloaded from Vagrant). I navigatged to the directory 
i would be working in and typed in "vagrant up"... at that point my 
terminal stops producing anything. here is a screen shot of what i see 
- https://i.imgur.com/sMci4ik.png this has been like this since 9:00 AM CST 
today. Anybody have any suggestions?

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/170512c6-3a9a-40d6-9f81-4de67db52862%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Does not execute PHP files only shows the content

2017-12-06 Thread Giannino Di Tizio A.

Thanks Alvaro

El martes, 5 de diciembre de 2017, 19:34:18 (UTC-4), Alvaro Miranda 
Aguilera escribió:
>
> that means the webserver is not processing php.
>
> perhaps open an issue in puphpet?
>
> Alvaro
>
> On Tue, Dec 5, 2017 at 10:50 PM, Giannino Di Tizio A.  > wrote:
>
>> Hello,
>> I'm new to this vagrant.
>>
>> After having downloaded vagrant ver. 2.0.1 and having generated with 
>> puphpet a machine for VirtualBox with Ubuntu 16.04, Apache, PHP 5.6 and 
>> MySql 5.7.
>> Up to here everything ok, the localhost runs well.
>>
>> but when trying to execute scripts file in PHP, it does not run and only 
>> shows the content of the script on the screen.
>>
>> a file as basic as: infophp.php
>>
>> >phpinfo ();
>> ?>
>>
>> it does not run. and it only shows the content of the script.
>>
>> Any ideas of what is left to do?
>>
>>
>> -- 
>> This mailing list is governed under the HashiCorp Community Guidelines - 
>> https://www.hashicorp.com/community-guidelines.html. Behavior in 
>> violation of those guidelines may result in your removal from this mailing 
>> list.
>>  
>> GitHub Issues: https://github.com/mitchellh/vagrant/issues
>> IRC: #vagrant on Freenode
>> --- 
>> 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 vagrant-up+...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/vagrant-up/7b0e8a6a-d4de-4063-acb4-9f90b2bd6f4e%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Alvaro
>
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/cc76923f-d708-4451-845b-6a61528383fe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Unplanned host reboot causes vagrant to lose all virtualbox guest associations

2017-12-06 Thread Robert Lilly

Charlie, just for clarification, were the non-Vagrant Virtualbox VMs running at 
the time of the power down / reboot as well as the the Vagrant ones?

I have experienced this problem before on Windows 7 and 10, as well as OS X / 
MacOS. I didn't take the time to troubleshoot, I just made a habit of not 
leaving any VMs running when I was finished for the day. 

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/61e0e0c9-a551-4afc-9b42-5fb450e96881%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Trying to set up a virtual box with vagrant

2017-12-06 Thread Carlos Morales

I have a virtualbox 5.1.30 and I have vagrant 2.0.1 and I have this error 
after doing a vagrant up --provider=virtualbox:

C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:333:in
 
`unlink': Permission denied @ unlink_internal - 
C:/Users/Carlos/Desktop/Vagrant_base/.vagrant/machines/default/virtualbox/id 
(Errno::EACCES)
from 
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:333:in
 
`delete'
from 
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:333:in
 
`id='
from 
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/machine.rb:146:in
 
`initialize'
from 
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/vagrantfile.rb:79:in
 
`new'
from 
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/vagrantfile.rb:79:in
 
`machine'
from 
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:733:in
 
`machine'
from 
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/plugin/v2/command.rb:180:in
 
`block in with_target_vms'
from 
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/plugin/v2/command.rb:204:in
 
`block in with_target_vms'
from 
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/plugin/v2/command.rb:186:in
 
`each'
from 
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/plugin/v2/command.rb:186:in
 
`with_target_vms'
from 
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/plugins/commands/up/command.rb:87:in
 
`execute'
from 
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/cli.rb:42:in 
`execute'
from 
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/environment.rb:308:in
 
`cli'
from 
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/bin/vagrant:138:in 
`'


How can I solve it?. Thanks in advance


-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/5cbeee61-6b10-4fdd-ba08-1039ca622ac1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Trying to set up a virtual box with vagrant

Re: [vagrant-up] Trying to set up a virtual box with vagrant

Re: [vagrant-up] No response after "vagrant up" command in Git Bash

Re: [vagrant-up] Trying to set up a virtual box with vagrant

[vagrant-up] Re: No response after "vagrant up" command in Git Bash

[vagrant-up] No response after "vagrant up" command in Git Bash

Re: [vagrant-up] Does not execute PHP files only shows the content

Re: [vagrant-up] Unplanned host reboot causes vagrant to lose all virtualbox guest associations

[vagrant-up] Trying to set up a virtual box with vagrant

9 matches

Site Navigation

Mail list logo

Footer information