Re: [vagrant-up] Re: Docker container runtime error,

[Chibuzor Michael Ekwonye]

I did not run the* apt install get vagrant* command since the vagrantfile
has been extracted and saved to a directory folder on the *C/ *path. I
stand to be corrected, I still cannot bring up the VM using the vagrantfile
the instructor shared for us to use.

Thank you as I await your informative response.

-- 
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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/CAAx9RsKa6JhEggZL7hDsJ2Zv2LhknPh9Kt4Ys9Dd9y5Dfd9fWw%40mail.gmail.com.

[vagrant-up] Docker container runtime error,

[Chibuzor Michael Ekwonye]

When i input the 'vagrant up' command to bring up my docker in the 
container's section, i usually get the;   bash: vagrant: no vagrant file 
found error prompt, please i am stuck here, i need advise[image: 
Capture.JPG]

-- 
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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/b7b14f96-1ab9-4aca-a872-f9ae4d181cb4n%40googlegroups.com.

Re: [vagrant-up] I get the error response that command not found, please assist me on this.

[Chibuzor Michael Ekwonye]

I cloned a vprofile-project using VS code, where the vagrant file is 
contained from my git repository.

Thanks
On Wednesday, 28 June 2023 at 12:43:12 UTC+1 Antony Stone wrote:

> On Wednesday 28 June 2023 at 13:38:57, Chibuzor Michael Ekwonye wrote:
>
> > I tried running the vagrant up command to bring up all VM's. And the 
> error
> > i got was,
> > 
> > * bash: vagrant: command not found*
>
> Okay, some basics:
>
> 1. How did you install vagrant on this machine?
>
> 2. What's the output of "which vagrant"?
>
> 3. What's the output of "echo $PATH"?
>
> 4. What's the output of "which vagrant" when run as root?
>
>
> Antony.
>
> -- 
> 3 logicians walk into a bar. The bartender asks "Do you all want a drink?"
> The first logician says "I don't know."
> The second logician says "I don't know."
> The third logician says "Yes!"
>
> Please reply to the list;
> please *don't* CC me.
>

-- 
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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/dd3a9955-16ac-4770-8e50-593fcacc1c8cn%40googlegroups.com.

Re: [vagrant-up] I get the error response that command not found, please assist me on this.

[Chibuzor Michael Ekwonye]

I tried running the vagrant up command to bring up all VM's. And the error 
i got was,

* bash: vagrant: command not found*


*Thanks.*
On Wednesday, 28 June 2023 at 12:33:43 UTC+1 Antony Stone wrote:

> On Wednesday 28 June 2023 at 13:26:15, Chibuzor Michael Ekwonye wrote:
>
> > I get the error response that command not found, please assist me on 
> this.
>
> At the very least please tell us which command you were trying to run.
>
> The quality of any response to a question is often directly related to the 
> quality of information provided in the question.
>
> Put yourself in our position - how are we supposed to know what you have 
> done 
> / what you are trying to do / what sort of machine you're trying to do it 
> on / 
> what you have installed on that machine / which user you are trying to run 
> a 
> command as / whether you've made a spelling mistake / etc.?
>
>
> Antony.
>
> -- 
> "Measuring average network latency is about as useful as measuring the 
> mean 
> temperature of patients in a hospital."
>
> - Stéphane Bortzmeyer
>
> Please reply to the list;
> please *don't* CC me.
>

-- 
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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/00fdd3e4-d8f3-47ba-ba54-98960afba957n%40googlegroups.com.

[vagrant-up] I get the error response that command not found, please assist me on this.

[Chibuzor Michael Ekwonye]

I get the error response that command not found, please assist me on this.

-- 
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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/aaff175e-5c30-4566-8480-725e3648f53cn%40googlegroups.com.

Re: [vagrant-up] Re: Cloning Git repository to my VS code

[Ekwonye Chibuzor Michael]

Thanks for the advice, I noticed after cloning the repository the vagrant
folder is appears missing.

Did you encounter such an anomaly at all ?

On Mon, Jun 26, 2023 at 9:16 PM dnmo...@gmail.com 
wrote:

> Have you tried
>
> Reading the Documentation? https://github.com/git-guides/git-clone
>
> OR
>
> git clone https://github.com/.git
>
> OR
>
> git clone  g...@github.com <https://groups.google.com/>:
> .git
>
> On Monday, June 26, 2023 at 4:04:04 PM UTC-4 Chibuzor Michael Ekwonye
> wrote:
>
>> Hello guys, How do i clone the GitHub repository, i need guidance on it.
>>
>> T for Thanks.
>>
> --
> 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/hashicorp/vagrant/issues
> Discuss: https://discuss.hashicorp.com/c/vagrant/24
> ---
> 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/1de4e16e-1f0e-424a-91d0-06549ecfd90bn%40googlegroups.com
> <https://groups.google.com/d/msgid/vagrant-up/1de4e16e-1f0e-424a-91d0-06549ecfd90bn%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/CAAnUvyveDcG5RMafHpBAjVADoJn6yejQaYAGbFkkJFirQGmoog%40mail.gmail.com.

[vagrant-up] Cloning Git repository to my VS code

[Chibuzor Michael Ekwonye]

Hello guys, How do i clone the GitHub repository, i need guidance on it.

T for Thanks.

-- 
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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/9b1e7e9a-f477-4eca-8338-1288b99afff3n%40googlegroups.com.

[vagrant-up] mkdir error

[Ekwonye Chibuzor Michael]

I tried creating directories and i got this error below

mkdir: cannot create directory ‘opt/devopsdir/’: No such file or directory

How do i correct this error fam.


Regards.

-- 
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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/4832384a-cfcd-4adf-b383-8acb0e09537dn%40googlegroups.com.

Re: [vagrant-up] bash: vagrant: command not found

[Ekwonye Chibuzor Michael]

Good day., I have fixed it, i noticed i had not installed the Vagrant.exe 
file on my windows PC.

Thank you so much for your advice, i appreciate.

Fixed and working now.

Regards.

On Sunday, May 14, 2023 at 10:16:55 AM UTC+1 Antony Stone wrote:

> On Sunday 14 May 2023 at 10:55:02, Ekwonye Chibuzor Michael wrote:
>
> > bash: vagrant: command not found
>
> Which operating system and version is this on, and how did you install 
> vagrant?
>
>
> Antony.
>
> -- 
> I still maintain the point that designing a monolithic kernel in 1991 is a 
> fundamental error. Be thankful you are not my student. You would not get a 
> high grade for such a design :-)
> - Andrew Tanenbaum to Linus Torvalds
>
> Please reply to the list;
> please *don't* CC me.
>

-- 
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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/9f3e706e-fd59-4796-9005-10d36eda851fn%40googlegroups.com.

[vagrant-up] bash: vagrant: command not found

[Ekwonye Chibuzor Michael]

bash: vagrant:  command not found



Please i need assistance
 
Regards.

-- 
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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/6018b37b-a383-42a6-9615-cbc74b3a041dn%40googlegroups.com.

[vagrant-up] Re: Why does Vagrant/Virtualbox assign the same MAC and IP address, and how to avoid

[Michael Ascenzi]

Hello again. I've posted a queston on the Vagrant Community forum as well. 
The post actually has more details and steps that I've taken to try to 
resolve the issue. 

Vagrant Multiple VM's with Unique IP address on public_network using DHCP - 
Vagrant - HashiCorp Discuss 
<https://discuss.hashicorp.com/t/vagrant-multiple-vms-with-unique-ip-address-on-public-network-using-dhcp/36374>

On Tuesday, March 1, 2022 at 7:48:09 AM UTC-5 Michael Ascenzi wrote:

> Hello, 
>
> I'm attempting to spin up multiple VM's utilizing Vagrant. However, no 
> matter the number of VM's they all share the same MAC address and IP 
> address. I need all VM's to be able to communicate with each other over 
> sockets, and thus need to have unique IP's. 
>
> I could assign them static addresses, which I'm doing temporarily as a 
> short-term fix, but I need the DHCP to assign addresses for the VM's.
>
> # -*- mode: ruby -*-
> # vi: set ft=ruby :
>
>
> $veh = 1
> $vehCount = 2
>
> $vehList ={}
>
>
> while $veh <= $vehCount do
>   $vehList["veh#{$veh}"] = "525400" + Array.new(6){[*"A".."F", 
> *"0".."9"].sample}.join
>   $veh+=1
> end
>
> Vagrant.configure("2") do |config|
>
>   $vehList.each do |vehName, macADDR|
>
> $name = vehName
> $mac = macADDR
>
> config.vm.define vehName do |vmConfig|
>
>   vmConfig.vm.box = "dcop"
>   # dcop.vm.base_mac = nil
>   
>   vmConfig.vm.network "public_network", bridge: "eno1", :mac => 
> macADDR 
> end
>   end
> end
>
> Through my reading, I've come across some saying its because its using the 
> same MAC address, so i updated the Vagrantfile to generate a random MAC, 
> and assigned it to the VM. But even with different MAC they are still 
> assigning the same IP for each VM. 
>

-- 
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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/2940d327-e943-4a66-b9d2-1a5b16aca8c8n%40googlegroups.com.

[vagrant-up] Why does Vagrant/Virtualbox assign the same MAC and IP address, and how to avoid

[Michael Ascenzi]

Hello, 

I'm attempting to spin up multiple VM's utilizing Vagrant. However, no 
matter the number of VM's they all share the same MAC address and IP 
address. I need all VM's to be able to communicate with each other over 
sockets, and thus need to have unique IP's. 

I could assign them static addresses, which I'm doing temporarily as a 
short-term fix, but I need the DHCP to assign addresses for the VM's.

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


$veh = 1
$vehCount = 2

$vehList ={}


while $veh <= $vehCount do
  $vehList["veh#{$veh}"] = "525400" + Array.new(6){[*"A".."F", 
*"0".."9"].sample}.join
  $veh+=1
end

Vagrant.configure("2") do |config|

  $vehList.each do |vehName, macADDR|

$name = vehName
$mac = macADDR

config.vm.define vehName do |vmConfig|

  vmConfig.vm.box = "dcop"
  # dcop.vm.base_mac = nil
  
  vmConfig.vm.network "public_network", bridge: "eno1", :mac => macADDR 
end
  end
end

Through my reading, I've come across some saying its because its using the 
same MAC address, so i updated the Vagrantfile to generate a random MAC, 
and assigned it to the VM. But even with different MAC they are still 
assigning the same IP for each VM. 

-- 
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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/03ee26e4-ff9f-47ea-8782-b9c477fb1d8fn%40googlegroups.com.

[vagrant-up] OpenGL in Cinder, clang-10, and a headless vm

[Michael]

Hello everyone,  

I am attempting to run an application compiled from C++ code that utilizes 
the Cinder library (https://www.libcinder.org/).  Specifically, Building 
and Running the BasicApp sample (
https://www.libcinder.org/docs/guides/linux-notes/ubuntu.html) included 
with Cinder.  

I am able to compile; however, when I attempt to run the application I 
receive the following error: 

(glfw:error): error=65544, desc=X11: RandR gamma ramp support seems broken
Rendering with OpenGL Core Profile 3.2
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
(glfw:error): error=65543, desc=GLX: An OpenGL profile requested but 
GLX_ARB_create_context_profile is unavailable
Segmentation fault (core dumped)

I am connected to the vm from the host (mac) using X windows forwarding.  I 
have no problem forwarding gedit to the host.  Here's my Vagrant 
configuration:

Vagrant.configure("2") do |config|
  config.vm.box = "hashicorp/bionic64"
  config.vm.box_version = "1.0.282"
  config.ssh.forward_x11 = true
  config.vm.provider "virtualbox" do |vb|
vb.memory = 1024
vb.cpus = 2
  end
end

The machine is provisioned with clang-10 and cinder dependencies (
https://www.libcinder.org/docs/guides/linux-notes/ubuntu.html).

I appreciate help that y'all can provide in resolving this issue.

Thanks again,

-- Michael 

-- 
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/hashicorp/vagrant/issues
Discuss: https://discuss.hashicorp.com/c/vagrant/24
--- 
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/5ad358d3-8b93-486c-93e1-8a98438ca6dcn%40googlegroups.com.

[vagrant-up] 403 Permission Denied issue with my vagrant box

[Michael Ference]

I'm working for a company and they use Vagrant for local dev with a Symfony 
system. I had a macbook air and it died the other day and I've tried to 
replicate the exact steps to get Vagrant up and running on my new machine. 
I've migrated to a ubuntu laptop. With the macbook there were a few steps I 
had to do to get things running. One is installing the vagrant-vbguest 
plugin in order for the build to work properly. After I got vagrant up and 
running there were some permission issues. At that point I was getting a 
stack trace with errors and the local site displayed the Symfony error bar 
or whatever it's officially called. To solve that issue I had to make some 
adjustments to the AppKernel.php file and adjusted the permissions and 
things worked fine. This time I'm getting a 403 permission denied with no 
stack trace from Symfony. One other thing when I run vagrant ssh-config and 
try to connect to that IP I'm getting an apache2 ubuntu default page, while 
my coworkers are getting a page from puphpet. I know that this description 
of my issue is kind of vague but if you have any clues as to what's going 
on I would greatly appreciate it. 

-- 
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/9c9813e8-c8ab-4bcb-a4ac-5a83a5274492%40googlegroups.com.

Re: [vagrant-up] Need help using someone elses box

[Michael Ference]

Hi Randall,

Here is what is currently in the Vagrantfile:

# -*- mode: ruby -*-

dir = File.dirname(File.expand_path(__FILE__))

require 'yaml'
require "#{dir}/puphpet/ruby/deep_merge.rb"
require "#{dir}/puphpet/ruby/to_bool.rb"

configValues = YAML.load_file("#{dir}/puphpet/config.yaml")

provider = ENV['VAGRANT_DEFAULT_PROVIDER'] ? ENV['VAGRANT_DEFAULT_PROVIDER'] 
: 'local'
if File.file?("#{dir}/puphpet/config-#{provider}.yaml")
custom = YAML.load_file("#{dir}/puphpet/config-#{provider}.yaml")
configValues.deep_merge!(custom)
end

if File.file?("#{dir}/puphpet/config-custom.yaml")
custom = YAML.load_file("#{dir}/puphpet/config-custom.yaml")
configValues.deep_merge!(custom)
end

data = configValues['vagrantfile']

Vagrant.require_version '>= 1.8.1'

Vagrant.configure('2') do |config|
eval File.read("#{dir}/puphpet/vagrant/Vagrantfile-#{data['target']}")
end


Do I need to edit this file or just remove it and try vagrant up from 
scratch?

Thanks,
Michael

On Thursday, July 11, 2019 at 1:42:05 PM UTC-6, Randall wrote:
>
> Hey Micheal,
>
> Well, there’s a chance he/she might have left the default configuration 
> behind. You can check your `vagrantfile` to be sure.
>
> Otherwise, depending on the configuration and what you’re running, 
> changing the provider could be be fairly easy. 
> https://www.vagrantup.com/docs/providers/configuration.html#provider-configuration
>
> -R
>
> On Jul 11, 2019, at 12:27 PM, Michael Ference  > wrote:
>
> Hi Randall,
> I had found Parallel's GitHub page and it appears it's only for Mac and 
> I'm currently working from a Windows environment.  Is that going to be an 
> issue?
>
> On Thursday, July 11, 2019 at 1:11:09 PM UTC-6, Randall wrote:
>>
>> Your developer was using Parallels (on MacOS) as his Vagrant provider, so 
>> you'll need to install the `vagrant-parallels` provider: 
>> https://github.com/Parallels/vagrant-parallels / 
>> https://parallels.github.io/vagrant-parallels. The basic installation 
>> step is listed in the repo’s README; and the other link is all the other 
>> documentation.
>>
>> If you’re trying to figure out the name of the VM, you find the 
>> documentation here: 
>> https://www.vagrantup.com/docs/virtualbox/configuration.html#virtual-machine-name
>> .
>>
>> Hope that helps. 
>>
>> On Jul 11, 2019, at 11:56 AM, Michael Ference  wrote:
>>
>> Hello, I received a box from a fellow developer and I'm trying to get it 
>> up and running.  He told me I just needed to extract the box files to a 
>> vagrant folder and use vagrant up command, but I'm getting this error: 
>>
>> The provider 'parallels' could not be found, but was requested to
>> back the machine '...'. Please use a provider that exists.
>>
>> Vagrant knows about the following providers: docker, hyperv, virtualbox
>>
>> where ... is the name of the machine.
>>
>> Any help would be greatly appreciated.  
>> Thanks!
>>
>>
>> -- 
>> 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 vagra...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/vagrant-up/f102bb79-a4d4-4ae0-a322-08634aa0acd0%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/vagrant-up/f102bb79-a4d4-4ae0-a322-08634aa0acd0%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
> -- 
> 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 vagra...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/vagrant-

Re: [vagrant-up] Need help using someone elses box

[Michael Ference]

Hi Randall,
I had found Parallel's GitHub page and it appears it's only for Mac and I'm 
currently working from a Windows environment.  Is that going to be an issue?

On Thursday, July 11, 2019 at 1:11:09 PM UTC-6, Randall wrote:
>
> Your developer was using Parallels (on MacOS) as his Vagrant provider, so 
> you'll need to install the `vagrant-parallels` provider: 
> https://github.com/Parallels/vagrant-parallels / 
> https://parallels.github.io/vagrant-parallels. The basic installation 
> step is listed in the repo’s README; and the other link is all the other 
> documentation.
>
> If you’re trying to figure out the name of the VM, you find the 
> documentation here: 
> https://www.vagrantup.com/docs/virtualbox/configuration.html#virtual-machine-name
> .
>
> Hope that helps. 
>
> On Jul 11, 2019, at 11:56 AM, Michael Ference  > wrote:
>
> Hello, I received a box from a fellow developer and I'm trying to get it 
> up and running.  He told me I just needed to extract the box files to a 
> vagrant folder and use vagrant up command, but I'm getting this error: 
>
> The provider 'parallels' could not be found, but was requested to
> back the machine '...'. Please use a provider that exists.
>
> Vagrant knows about the following providers: docker, hyperv, virtualbox
>
> where ... is the name of the machine.
>
> Any help would be greatly appreciated.  
> Thanks!
>
>
> -- 
> 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 vagra...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/vagrant-up/f102bb79-a4d4-4ae0-a322-08634aa0acd0%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/vagrant-up/f102bb79-a4d4-4ae0-a322-08634aa0acd0%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
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/286e4106-abc3-46bf-a6db-74290056%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Need help using someone elses box

[Michael Ference]

Hello, I received a box from a fellow developer and I'm trying to get it up 
and running.  He told me I just needed to extract the box files to a 
vagrant folder and use vagrant up command, but I'm getting this error: 

The provider 'parallels' could not be found, but was requested to
back the machine '...'. Please use a provider that exists.

Vagrant knows about the following providers: docker, hyperv, virtualbox

where ... is the name of the machine.

Any help would be greatly appreciated.  
Thanks!

-- 
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/f102bb79-a4d4-4ae0-a322-08634aa0acd0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Enabling/Disabling plugins

[Michael]

Hi all,

I'm looking at creating a Vagrant VM using a CI server with no internet 
connection. Or rather, the CI only has a connection to the internet via 
Artifactory, which is acting as a proxy for Yum packages and Vagrant boxes, 
including caching those files for reproducibility.

I'm trying to build a VM with centos/7 (v1801.02, Virtualbox) as a base 
image. I would also like to install VirtualBox Guest Additions, using the 
Vagrant plugin vagrant-vbguest. 

I will include a sanitised Vagrantfile and build script as attachments for 
this process.


What I am trying to do is the following:
 - Disable vagrant-vbguest
 - Provision the VM
 - Enable vagrant-vbguest
 - Vagrant up again (to install Guest Additions)
 - Export the VM

However, it seems that after provisioning the machine with the plugin 
disabled, re-enabling the plugin has no effect. How can I cause the above 
set of steps to occur?

Michael

-- 
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/06daea1a-c111-48e0-87ab-205cf0f28bbe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Vagrantfile
Description: Binary data
#!/bin/bash
set -e

# Ensure that the box is added from Artifactory
vagrant box add "https://my/artifactor/url/centos7;

# Disable the guest additions plugin
export VAGRANT_NO_PLUGINS=1

# First build of VM
vagrant up

# Enable guest additions plugin to install Guest Additions
unset VAGRANT_NO_PLUGINS

# For some reason, running the script a few times is needed for the guest additions
vagrant halt && vagrant up
vagrant halt && vagrant up
vagrant halt

# Package the output into a box file
vagrant package --output my-centos7.box

# Upload the box file to Artifactory - command not included here

Re: [vagrant-up] Broken routes with changed default router on macOS

[michael]

On Monday, November 20, 2017 at 10:44:56 AM UTC+1, Alvaro Miranda Aguilera 
wrote:
>
>
> are you doing a macOS guest and you want to override the default gw there?
>

The guest is a Linux VM. The relevant part of my provision script is:

route add default gw 192.168.222.1
eval "$(route -n | awk '{ if ($8 =="enp0s3" && $2 != "0.0.0.0") print "route 
del default gw " $2; }')"

192.168.222.1 is the host IP address. The guest uses a private network; 
from the Vagrant file:

c.vm.network "private_network", ip: "192.168.222.10"

This all works on a Linux host. On a macOS host the guest is not able to 
connect to the internet after the default gw was changed.

 

-- 
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/e31e7b26-0713-4b69-b749-d27c82d50b08%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Powershell remote on Mac/Linux

[Michael Smith]

With Powershell open-sourced and running on Mac and Linux, it seems that 
'vagrant powershell' could be extended to support Powershell remoting from 
those host platforms.

Has anyone looked into this? I've done a little hacking but so far didn't get 
anything working.

-- 
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/4f3a2c02-ec42-4801-bca0-54044f65%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Which type should be used to force /vagrant to use VMware for the default synced folder?

[Michael Vermaes]

Well, VMware Tools in this case :) But yes, that's the plan.

I'm including insert_key = false in our Vagrantfiles currently, but
I'd like to remove that again once 1.8.6 is available with
https://github.com/mitchellh/vagrant/pull/7611. These boxes are only
used privately, so we prefer to have the key replaced.

Thanks again for your advice.

On Tue, Sep 20, 2016 at 3:59 PM, Alvaro Miranda Aguilera
<kiki...@gmail.com> wrote:
> Hello
>
> Just make sure you install Virtualbox Guest additions before.
>
> Also, in the intermediate box, is good to add config.ssh.insert_key = false
> so Vagrant doesn't replace the insecure one.
>
> Alvaro
>
> On Tue, Sep 20, 2016 at 5:07 AM, Michael Vermaes <mverm...@gmail.com> wrote:
>>
>> Ah great, that looks like the file I was looking for. I will try
>> repackaging the box with a Vagrantfile that doesn't specify rsync and see
>> how I go. Thanks for pointing me in the right direction.
>>
>> On Tue, Sep 20, 2016 at 12:56 AM, Alvaro Miranda Aguilera
>> <kiki...@gmail.com> wrote:
>>>
>>> hello
>>>
>>> for some vm in atlas some vendor/people choose not to install guest
>>> additions and use rsync
>>>
>>> check a vagrant file ~/,vagrant.d/boxes/centos-VAGRANTSLASH-7
>>>
>>> you will see the code that disable the folder and enable rsync
>>>
>>> i will suggest other vm first to ensure all is right
>>>
>>>
>>>
>>> On Mon, Sep 19, 2016 at 7:27 AM, Michael Vermaes <mverm...@gmail.com>
>>> wrote:
>>>>
>>>> When setting up the CentOS 7 box from
>>>> https://atlas.hashicorp.com/centos/boxes/7 with the VMware Fusion provider,
>>>> /vagrant is always shared using the rsync method. Is there a way to 
>>>> override
>>>> this using the Vagrantfile? I've tried the following:
>>>>
>>>> - Setting different values for the 'type' of the synced_folder, such as
>>>> vmware/vmware_fusion/vmware_desktop, but this generates an error on reload:
>>>> ...
>>>> ==> default: Verifying vmnet devices are healthy...
>>>>
>>>> .../.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.11/lib/vagrant-vmware-fusion/synced_folder.rb:10:in
>>>> `usable?': wrong number of arguments (2 for 1) (ArgumentError)
>>>> ...
>>>>
>>>> - Setting the folder with id: "vagrant-root" to disabled, and then
>>>> redefining it on a new line. This is ignored, and rsync is still used.
>>>>
>>>> - Defining a second synced_folder with a different guest path
>>>> (/vagrant2). This works.
>>>>
>>>> Given the last point, I believe VMware Tools are set up correctly. The
>>>> Tools were configured by installing open-vm-tools from CentOS 
>>>> repositorities
>>>> and then adding the tools from the Fusion iso to get shared folder support.
>>>>
>>>> Other version details:
>>>> - OS X 10.11.6
>>>> - VMware Fusion 8.5 (same behaviour with 8.1.1)
>>>> - Vagrant 1.8.5
>>>> - vagrant-vmware-fusion 4.0.11
>>>>
>>>> Thanks for any suggestions anyone can provide.
>>>>
>>>> --
>>>> 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/bc85b54b-8845-4303-b210-199fadc5e246%40googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>>
>>>
>>> --
>>> Alvaro
>>> (+31)103400555
>>>
>>> --
>>> 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.

Re: [vagrant-up] Which type should be used to force /vagrant to use VMware for the default synced folder?

[Michael Vermaes]

Ah great, that looks like the file I was looking for. I will try
repackaging the box with a Vagrantfile that doesn't specify rsync and see
how I go. Thanks for pointing me in the right direction.

On Tue, Sep 20, 2016 at 12:56 AM, Alvaro Miranda Aguilera <kiki...@gmail.com
> wrote:

> hello
>
> for some vm in atlas some vendor/people choose not to install guest
> additions and use rsync
>
> check a vagrant file ~/,vagrant.d/boxes/centos-VAGRANTSLASH-7
>
> you will see the code that disable the folder and enable rsync
>
> i will suggest other vm first to ensure all is right
>
>
>
> On Mon, Sep 19, 2016 at 7:27 AM, Michael Vermaes <mverm...@gmail.com>
> wrote:
>
>> When setting up the CentOS 7 box from https://atlas.hashicorp.com/ce
>> ntos/boxes/7 with the VMware Fusion provider, /vagrant is always shared
>> using the rsync method. Is there a way to override this using the
>> Vagrantfile? I've tried the following:
>>
>> - Setting different values for the 'type' of the synced_folder, such as
>> vmware/vmware_fusion/vmware_desktop, but this generates an error on
>> reload:
>> ...
>> ==> default: Verifying vmnet devices are healthy...
>> .../.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.11/lib/
>> vagrant-vmware-fusion/synced_folder.rb:10:in `usable?': wrong number of
>> arguments (2 for 1) (ArgumentError)
>> ...
>>
>> - Setting the folder with id: "vagrant-root" to disabled, and then
>> redefining it on a new line. This is ignored, and rsync is still used.
>>
>> - Defining a second synced_folder with a different guest path
>> (/vagrant2). This works.
>>
>> Given the last point, I believe VMware Tools are set up correctly. The
>> Tools were configured by installing open-vm-tools from CentOS
>> repositorities and then adding the tools from the Fusion iso to get shared
>> folder support.
>>
>> Other version details:
>> - OS X 10.11.6
>> - VMware Fusion 8.5 (same behaviour with 8.1.1)
>> - Vagrant 1.8.5
>> - vagrant-vmware-fusion 4.0.11
>>
>> Thanks for any suggestions anyone can provide.
>>
>> --
>> 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/ms
>> gid/vagrant-up/bc85b54b-8845-4303-b210-199fadc5e246%40googlegroups.com
>> <https://groups.google.com/d/msgid/vagrant-up/bc85b54b-8845-4303-b210-199fadc5e246%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Alvaro
> (+31)103400555
>
> --
> 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 a topic in the
> Google Groups "Vagrant" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/vagrant-up/cRCqsKmgMAs/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CAHqq0exa0FgzYSm9kZhWuUDZcWQJo
> 51UiToocdyskVBAkCW2iA%40mail.gmail.com
> <https://groups.google.com/d/msgid/vagrant-up/CAHqq0exa0FgzYSm9kZhWuUDZcWQJo51UiToocdyskVBAkCW2iA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAAQZgJw9gUtEOfN07TH8F%2BpN4fz%2BibiWztzuRX2%2B0G-%3DU%2BdnsA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Re: Which type should be used to force /vagrant to use VMware for the default synced folder?

[Michael Vermaes]

Actually, using type: "vmware_desktop" or "vmware_fusion" results in:

/opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builtin/mixin_synced_folders.rb:137:in
 
`block in synced_folders': Internal error. Report this as a bug. Invalid: 
vmware_desktop (RuntimeError)

which is the same message as when specifying random text for the type, so I 
believe vmware is the correct value. I'm not sure why it doesn't work 
though. Here is my Vagrantfile:

Vagrant.configure("2") do |config|
  config.vm.box = "centos/7"

  # Disable the default rsync sync method:
  config.vm.synced_folder "./", "/vagrant", id: "vagrant-root", disabled: 
true
  # This just enables the folder using rsync again:
  config.vm.synced_folder "./", "/vagrant"
  
  # This (exporting a different location in the guest) syncs the folder 
using VMware:
  config.vm.synced_folder "./", "/vagrant2"
  
  config.ssh.insert_key = false
end





On Monday, September 19, 2016 at 1:27:51 PM UTC+8, Michael Vermaes wrote:
>
> When setting up the CentOS 7 box from 
> https://atlas.hashicorp.com/centos/boxes/7 with the VMware Fusion 
> provider, /vagrant is always shared using the rsync method. Is there a way 
> to override this using the Vagrantfile? I've tried the following:
>
> - Setting different values for the 'type' of the synced_folder, such as 
> vmware/vmware_fusion/vmware_desktop, but this generates an error on reload:
> ...
> ==> default: Verifying vmnet devices are healthy...
> .../.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.11/lib/vagrant-vmware-fusion/synced_folder.rb:10:in
>  
> `usable?': wrong number of arguments (2 for 1) (ArgumentError)
> ...
>
> - Setting the folder with id: "vagrant-root" to disabled, and then 
> redefining it on a new line. This is ignored, and rsync is still used.
>
> - Defining a second synced_folder with a different guest path (/vagrant2). 
> This works.
>
> Given the last point, I believe VMware Tools are set up correctly. The 
> Tools were configured by installing open-vm-tools from CentOS 
> repositorities and then adding the tools from the Fusion iso to get shared 
> folder support.
>
> Other version details:
> - OS X 10.11.6
> - VMware Fusion 8.5 (same behaviour with 8.1.1)
> - Vagrant 1.8.5
> - vagrant-vmware-fusion 4.0.11
>
> Thanks for any suggestions anyone can provide.
>

-- 
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/15f08708-cbc0-49b5-be8c-1276e4f66025%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Bundler Error on vmware_fusion Install

[Michael W. Fleming]

On 5/12/16 4:43 PM, Alvaro Miranda Aguilera wrote:
> vagrant plugin install *vagrant-vmware-fusion*

That was it. Thanks.

-- 
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/a82a7729-5564-2e71-ca65-ca617ae7de1f%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Bundler Error on vmware_fusion Install

[Michael Fleming]

El Capitan, clean vagrant 1.8.1 install

$ vagrant plugin install vmware_fusion

Installing the 'vmware_fusion' plugin. This can take a few minutes...

Bundler, the underlying system Vagrant uses to install plugins,

reported an error. The error is shown below. These errors are usually

caused by misconfigured plugin installations or transient network

issues. The error from Bundler is:


Could not find gem 'vmware_fusion (>= 0) ruby' in any of the gem sources 
listed in your Gemfile or available on this machine.


Warning: this Gemfile contains multiple primary sources. Using `source` 
more than once without a block is a security risk, and may result in 
installing unexpected gems. To resolve this warning, use a block to 
indicate which gems should come from the secondary source. To upgrade this 
warning to an error, run `bundle config disable_multisource true`.



-- 
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/ce753346-dbb6-40f4-b8ca-229fe3fb6cb8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] My solution for better output from vagrant shell provisioning scripts

[Michael Ward]

I got tired of seeing red messages in my provisioning script out, so I set 
out looking for a solution.

The problem, red lines from non errors makes it difficult to spot some 
genuine errors.

The requirements for a solution, accept any command and show green output 
for all commands that succeed.

The solution: a shell function that accepts a description and command, 
returns success messages for commands with a zero exit code, returns the 
output of a command for non zero exit codes.

I have decided to share the function with the vagrant community in the hope 
some of you find it useful. You can find the project on Github:

https://github.com/michaelward82/vagrant-provisioning-shell-function-helper

Example usage:

exe "Update apt indexes" \
sudo apt-get update

Provisioning output:

==> Execute: Update apt indexes
==> ...  
==> ...  
==> ...  
==> ✔ Success

Example of the default vagrant output from a fully functioning provisioning 
script that calls openssl and php composer command:



Example of the same script using my exe function:



And output should there be a genuine error in your script:



This script function has only been used by myself and isn't widely battle 
tested. I'd love feedback and fixes for edge cases through Github. Hope 
this makes a few lives a little easier :)

-- 
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/de91808d-6670-498e-ae09-a8c3123fd073%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] libruby errors when running kitchen create

[Michael Wyatt]

Hi Alvaro,

I sent the email to the address below this evening.  I've had a busy few 
weeks and finally just had some time to do the debug.

Thanks for the help.
Michael

On Friday, February 5, 2016 at 4:47:15 AM UTC-5, Alvaro Miranda Aguilera 
wrote:
>
> Hello,
>
> Can you send an email to support at hashicorp.com ?
>
> For the Vagrant part
>
> Attach a verbose output.
>
> VAGRANT_LOG=debug vagrant up 2>&1 | tee vagrant_up.log
>
> VAGRANT_LOG=debug vagrant destroy -f 2>&1 | tee vagrant_destroy.log
>
> The ssh not working, may be (or may be not) something in the box. Can you 
> check if /etc/udev/rules.d/70-persistent-net.rule (or similar) doesn't 
> exist before you create the box image?
>
> Thanks
> Alvaro.
>
> On Fri, Feb 5, 2016 at 1:16 PM, Michael Wyatt <mike...@gmail.com 
> > wrote:
>
>> Hello Alvaro,
>>
>> Thanks for the reply.  I've tried doing vagrant init and vagrant up and 
>> vagrant init and it failed with a timeout message.  The ruby error is 
>> intermittent, it seems.  The timeouts seem to be happening much more often.
>>
>> However, this time, after running vagrant init and vagrant up, I got the 
>> error on the vagrant destroy:
>>
>> [wyatt@oc4642434687 ibm-cds-appserver]$ vagrant box list
>> IBM.EI.RHEL.6(vmware_desktop, 0)
>> IBM.EI.RHEL.6(virtualbox, 6.7.20151128)
>> opscode-ubuntu-14.04 (vmware_desktop, 0)
>>
>>  
>>
>> [wyatt@oc4642434687 ibm-cds-appserver]$ vagrant init IBM.EI.RHEL.6
>> 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.
>>
>>  
>>
>> [wyatt@oc4642434687 ibm-cds-appserver]$ vagrant up 
>> Bringing machine 'default' up with 'vmware_workstation' provider...
>> ==> default: Cloning VMware VM: 'IBM.EI.RHEL.6'. This can take some 
>> time...
>> ==> default: Checking if box 'IBM.EI.RHEL.6' is up to date...
>> ==> default: Skipping vmnet device verification, verify_vmnet is set to 
>> false.
>> ==> default: Preparing network adapters...
>> ==> default: Fixed port collision for 22 => . Now on port 2201.
>> ==> default: Starting the VMware VM...
>> ==> default: Waiting for machine to boot. This may take a few minutes...
>> default: SSH address: 192.168.211.147:22
>> 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.
>>
>>
>> [wyatt@oc4642434687 ibm-cds-appserver]$ vagrant destroy 5e9ff42
>> default: Are you sure you want to destroy the 'default' VM? [y/N] y
>> ==> default: Stopping the VMware VM...
>> ==> default: Deleting the VM...
>> ruby: error while loading shared libraries: libruby.so.2.2: cannot open 
>> shared object file: No such file or directory
>>
>>  
>>
>>
>> Not sure what is really going on, but things don't seem to be very stable 
>> right now.
>>
>> Thanks,
>> Michael
>>
>> -- 
>> 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 

Re: [vagrant-up] libruby errors when running kitchen create

[Michael Wyatt]

Hello Alvaro,

Thanks for the reply.  I've tried doing vagrant init and vagrant up and 
vagrant init and it failed with a timeout message.  The ruby error is 
intermittent, it seems.  The timeouts seem to be happening much more often.

However, this time, after running vagrant init and vagrant up, I got the 
error on the vagrant destroy:

[wyatt@oc4642434687 ibm-cds-appserver]$ vagrant box list
IBM.EI.RHEL.6(vmware_desktop, 0)
IBM.EI.RHEL.6(virtualbox, 6.7.20151128)
opscode-ubuntu-14.04 (vmware_desktop, 0)

 

[wyatt@oc4642434687 ibm-cds-appserver]$ vagrant init IBM.EI.RHEL.6
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.

 

[wyatt@oc4642434687 ibm-cds-appserver]$ vagrant up 
Bringing machine 'default' up with 'vmware_workstation' provider...
==> default: Cloning VMware VM: 'IBM.EI.RHEL.6'. This can take some time...
==> default: Checking if box 'IBM.EI.RHEL.6' is up to date...
==> default: Skipping vmnet device verification, verify_vmnet is set to 
false.
==> default: Preparing network adapters...
==> default: Fixed port collision for 22 => . Now on port 2201.
==> default: Starting the VMware VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 192.168.211.147:22
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.


[wyatt@oc4642434687 ibm-cds-appserver]$ vagrant destroy 5e9ff42
default: Are you sure you want to destroy the 'default' VM? [y/N] y
==> default: Stopping the VMware VM...
==> default: Deleting the VM...
ruby: error while loading shared libraries: libruby.so.2.2: cannot open 
shared object file: No such file or directory

 


Not sure what is really going on, but things don't seem to be very stable 
right now.

Thanks,
Michael

-- 
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/dac9f131-554f-4d24-8174-b56a2c31e526%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Need to see real source IPs from behind port forwarding, can I disable SNAT?

[Michael Taylor]

Got it. I added the customize line to the vagrantfile:

config.vm.provider "virtualbox" do |v|
v.memory = 4096
v.customize ["modifyvm", :id, "--nataliasmode1", "proxyonly"]
end

Pay attention to the number one at the end of "--nataliasmode", that's not 
the letter L and it refers to the interface number in the VM.


On Monday, November 30, 2015 at 7:41:15 PM UTC-5, Alvaro Miranda Aguilera 
wrote:
>
> Once you get the commands that work, you should be able to put them in 
> the vagrant file. 
>
>

-- 
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/dbdb1600-56ef-4c79-aeb1-f36dc595a4ec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [vagrant-up] Need to see real source IPs from behind port forwarding, can I disable SNAT?

[Michael Taylor]

Yes, but I was hoping for a way to do it within the vagrantfile.

On Saturday, November 28, 2015 at 1:00:18 AM UTC-5, Alvaro Miranda Aguilera 
wrote:
>
> Hello,
>
> If you comment those out, and then use the gui I think the result will be 
> the same.
>
> I think if you can came up with the VBoxManage  that can do 
> what you are afterm then you may use a virtualbox block to run that, and 
> not use the out of the box forward port.
>
> make sense?
>
>

-- 
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/dc22f215-83ff-4929-b461-78a49cea38d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Need to see real source IPs from behind port forwarding, can I disable SNAT?

[Michael Taylor]

I'm trying to use graylog with Vagrant in a port forwarded Virtualbox 
appliance and I'm noticing that every message has 10.0.2.2 as its source IP.

Vagrantfile:
Vagrant.configure(2)  do |config|
  config.vm.box = "ubuntu/trusty64"
  config.vm.hostname = "graylog"

  config.vm.network :forwarded_port, guest: 1514, host: 1514, protocol: 
'udp'
  config.vm.network :forwarded_port, guest: 9000, host: 9000
  config.vm.network :forwarded_port, guest: 12900, host: 12900
  config.vm.network :forwarded_port, guest: 12201, host: 12201, protocol: 
'udp'
  config.vm.network :forwarded_port, guest: 12201, host: 12201, protocol: 
'tcp'

Example from tcpdump:

15:34:33.986334 IP 10.0.2.2.58556 > graylog.12201: Flags [P.], seq 
76983:77640, ack 1, win 65535, length 657

This tells me that Vagrant set up the VM with SNAT and every forwarded 
packet gets the firewall IP as its source. Is there a way to disable this 
(use DNAT only) so the source IP of forwarded packets is correct? I don't 
dare make a bridged network for security reasons: graylog requires a 
version of Elasticsearch with no support for authentication and the Java 
version in the official appliance image is quite old.



-- 
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/5dafbfe8-c7cf-4735-90d1-21e1b0a5cee5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Re: Windows 10 Could not be detected by Vagrant

[Michael Legleux]

While this does somewhat put a band-aid on the cannot detect operating 
system error,
the networking configuration doesn't complete.

== win10: Configuring and enabling network interfaces...
The following WinRM command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

netsh interface ip set address Ethernet 2 dhcp
if ($?) { exit 0 } else { if($LASTEXITCODE) { exit $LASTEXITCODE } else { 
exit 1 } }

Stdout from the command:

Stderr from the command:



On Thursday, August 6, 2015 at 4:51:38 PM UTC-7, Michael Legleux wrote:

 But it obviously can, as in the debug output I see windows 10 all over the 
 place.

 This was with Virtualbox 4 and 5.

 This seems to be a relevant part of the debug output:

 DEBUG guest: Trying: windows
 DEBUG winrmshell: powershell executing:
 $p = $Env:SystemRoot
 if ((Test-Path $p) -and (get-item $p).PSIsContainer) {
   exit 0
 }
 exit 1

 if ($?) { exit 0 } else { if($LASTEXITCODE) { exit $LASTEXITCODE } else { 
 exit 1 } }
 DEBUG winrmshell: Output: {:data=[{:stderr=# CLIXML\r\n}, 
 {:stderr=Objs Version=\1.1.0.1\ xmlns=\
 http://schemas.microsoft.com/powershell/2004/04\;Obj S=\progress\ 
 RefId=\0\TN 
 RefId=\0\TSystem.Management.Automation.PSCustomObject/TTSystem.Object/T/TNMSI64
  
 N=\SourceId\1/I64PR N=\Record\AVPreparing m}, {:stderr=odules 
 for first use./AVAI0/AINil 
 /PI-1/PIPC-1/PCTCompleted/TSR-1/SRSD 
 /SD/PR/MS/Obj/Objs}], :exitcode=0}
 ERROR warden: Error occurred: The guest operating system of the machine 
 could not be detected!
 Vagrant requires this knowledge to perform specific tasks such
 as mounting shared folders and configuring networks. Please add
 the ability to detect this guest operating system to Vagrant
 by creating a plugin or reporting a bug.
  INFO warden: Beginning recovery process...
  INFO warden: Calling recover: 
 #Vagrant::Action::Builtin::HandleForwardedPortCollisions:0x39dfb78
  INFO warden: Recovery complete.

 How can no one else be experiencing this?


-- 
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/b25c1d65-585e-4171-b8c0-ed5a313fdf45%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Windows 10 Could not be detected by Vagrant

[Michael Legleux]

But it obviously can, as in the debug output I see windows 10 all over the 
place.

This was with Virtualbox 4 and 5.

This seems to be a relevant part of the debug output:

DEBUG guest: Trying: windows
DEBUG winrmshell: powershell executing:
$p = $Env:SystemRoot
if ((Test-Path $p) -and (get-item $p).PSIsContainer) {
  exit 0
}
exit 1

if ($?) { exit 0 } else { if($LASTEXITCODE) { exit $LASTEXITCODE } else { 
exit 1 } }
DEBUG winrmshell: Output: {:data=[{:stderr=# CLIXML\r\n}, 
{:stderr=Objs Version=\1.1.0.1\ 
xmlns=\http://schemas.microsoft.com/powershell/2004/04\;Obj 
S=\progress\ RefId=\0\TN 
RefId=\0\TSystem.Management.Automation.PSCustomObject/TTSystem.Object/T/TNMSI64
 
N=\SourceId\1/I64PR N=\Record\AVPreparing m}, {:stderr=odules 
for first use./AVAI0/AINil 
/PI-1/PIPC-1/PCTCompleted/TSR-1/SRSD 
/SD/PR/MS/Obj/Objs}], :exitcode=0}
ERROR warden: Error occurred: The guest operating system of the machine 
could not be detected!
Vagrant requires this knowledge to perform specific tasks such
as mounting shared folders and configuring networks. Please add
the ability to detect this guest operating system to Vagrant
by creating a plugin or reporting a bug.
 INFO warden: Beginning recovery process...
 INFO warden: Calling recover: 
#Vagrant::Action::Builtin::HandleForwardedPortCollisions:0x39dfb78
 INFO warden: Recovery complete.

How can no one else be experiencing this?

-- 
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/a555c9d6-b8b4-4464-922f-0e2bf2a160b8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] The box could not be found, anywhere

[Michael Muratet]

Greetings

I am trying to use vagrant v1.4.3 with virtualbox 4.3.10_Ubuntu_r93012 and 
my version of curl is 7.35.0

I am unable to get past:

vagrant init chef/centos-7.0; vagrant up --provider virtualbox

I have attached the debug output. I don't see any cause, but a more 
experienced eye might.

I went reviewed the manual regarding boxes, and tried:

vagrant --debug add chef/centos-7.0

This is a valid entry in the Atlas catalog, so I am puzzled why it doesn't 
work. That debug output is also attached.

I took the error message at face value and tried the command with URL. It 
looks like it tried to fetch the file but didn't get anything that would 
unpack. That log is attached.

I've run out of things to try. Does anyone have any ideas?

Cheers

Mike

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


vagrant_init.log
Description: Binary data


vagrant_add.log
Description: Binary data


vagrant_url.log
Description: Binary data

[vagrant-up] Re: Vagrant package creates vmdk files using virtualbox

[Michael Legleux]

   
   - 
   
   Box File - This is a compressed (tar, tar.gz, zip) file that is specific 
   to a single provider and can contain anything. Vagrant core doesn't ever 
   use the contents of this file. Instead, they are passed to the provider. 
   Therefore, a VirtualBox box file has different contents from a VMware box 
   file and so on.
   

On Friday, June 12, 2015 at 11:37:31 AM UTC-7, dragon788 wrote:

 This is a cross compatible format (not restricted to just VMware, it works 
 with Virtualbox as well), though might require some conversion to do so 
 with an output file. I believe the logic is that you can reuse a VMDK with 
 a couple types of builders/providers.

 On Wednesday, June 10, 2015 at 4:09:54 PM UTC-5, Michael Legleux wrote:

 If the original disk is a .vdi, the disk in the box file ends up being a 
 .vmdk file.

 Is this intentional? 



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

[vagrant-up] Vagrant package creates vmdk files using virtualbox

[Michael Legleux]

If the original disk is a .vdi, the disk in the box file ends up being a 
.vmdk file.

Is this intentional? 

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

[vagrant-up] Mult-Machine Grouping

[Michael O'Connor]

Hi, I've been trying to figure out if there is a way to define a group of 
vms within a Vagrantfile in such a way that I could call vagrant up group 
name and bring up the specified group of vms

For example I tried something similar to the following:
config.vm.define 'foobar-group' do |foobar|
  foobar.vm.define 'foo' do |foo|
foo.vm.hostname = 'foo'
...
  end
  foobar.vm.define 'bar' do |bar|
bar.vm.hostname = 'bar'
...
  end
end

config.vm.define 'stuff-group' do |stuff|
  stuff.vm.define 'some-stuff' do |something|
something.vm.hostname = 'something'
...
  end
  ...
end

Basically I was hoping I'd be able to call vagrant up foobar-group and get 
only the vms in that group to come up, however this does not work at all.

Is there a way to do this other than using some sort of naming convention 
and a pattern with vagrant up?

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

[vagrant-up] Re: changing default vagrant user

[Michael Legleux]

Yeah I am packaging the box from scratch as I have done several times 
before with success, but I want vagrant to be able to log in as a different 
user WITHOUT additional modification in a vagrantfile.
I want the box to be already packaged and ready to use a different 
username/password.
This must be possible?

On Thursday, May 28, 2015 at 6:38:32 PM UTC-7, Michael Legleux wrote:

 I'm creating a base box of windows and would like to NOT have user/pass 
 vagrant/vagrant.

 The wording in the documentation is not very clear on how to accomplish 
 something like this.

 Furthermore, http://docs.vagrantup.com/v2/virtualbox/boxes.html says that:

- 

The MAC address of the first network interface (the NAT adapter) 
should be noted, since you'll need to put it in a Vagrantfile later as the 
value for config.vm.base_mac. To get this value, use the VirtualBox 
GUI.

 But then at the bottom of the page it's stated that:
 If you're not using vagrant package --base above, you'll have to set the
 config.vm.base_mac setting in this Vagrantfile to the MAC address of the 
 NAT device without colons.
 I have always used  vagrant package --base alone and seemingly have never 
 had a problem (with communication at least.)
 So what i want is to set config.ssh.username to be NOT vagrant by default.
 From what I gather i should vagrant package --base the_vb_name 
 --vagrantfile somevagrantfile where vagrantfile has the username/password 
 configuration in it. ALSO if I do that, I will have to manually set the MAC 
 address in there?
 Thanks, hope that was intelligible! 



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

[vagrant-up] Re: vagrant adding box problem

[Michael Legleux]

While your first statement seems logical, the second statement you suggest 
is exactly what I've been doing. 
The problem is, when I bring it to the new system from windows 8(which in 
this case was ubuntu AND windows 8), vagrant's bsdtar has the error I 
posted.

On Thursday, May 21, 2015 at 12:32:35 PM UTC-7, Michael Legleux wrote:

 I packaged a windows 7 box using vagrant 1.6.5 on windows 8.1 and have 
 been using it successfully for awhile on the same machine.

 I just moved the .box to a few other machines (windows 8.1 and 
 ubuntu12.04) and when adding the box I get the error:

 The box failed to unpackage properly. Please verify that the box
 file you're trying to add is not corrupted and try again. The
 output from attempting to unpackage (if any):

 x ./box-disk1.vmdk: truncated gzip input
 bsdtar.EXE: Error exit delayed from previous errors.





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

[vagrant-up] Re: changing default vagrant user

[Michael Legleux]

So once again, I assumed the command:
vagrant package --base thevbox --vagrantfile 
vagrantfile_in_this_directory would put that vagrantfile into the 
package.box after it was done.
I just ran that command, decompressed the box file and lo and behold the 
vagrantfile in the package.box does NOT contain anything that was in the 
vagrantfile included via --vagrantfile thevagrantfile, only the 
config.vm_base_mac line.

What gives!?! 


On Thursday, May 28, 2015 at 6:38:32 PM UTC-7, Michael Legleux wrote:

 I'm creating a base box of windows and would like to NOT have user/pass 
 vagrant/vagrant.

 The wording in the documentation is not very clear on how to accomplish 
 something like this.

 Furthermore, http://docs.vagrantup.com/v2/virtualbox/boxes.html says that:

- 

The MAC address of the first network interface (the NAT adapter) 
should be noted, since you'll need to put it in a Vagrantfile later as the 
value for config.vm.base_mac. To get this value, use the VirtualBox 
GUI.

 But then at the bottom of the page it's stated that:
 If you're not using vagrant package --base above, you'll have to set the
 config.vm.base_mac setting in this Vagrantfile to the MAC address of the 
 NAT device without colons.
 I have always used  vagrant package --base alone and seemingly have never 
 had a problem (with communication at least.)
 So what i want is to set config.ssh.username to be NOT vagrant by default.
 From what I gather i should vagrant package --base the_vb_name 
 --vagrantfile somevagrantfile where vagrantfile has the username/password 
 configuration in it. ALSO if I do that, I will have to manually set the MAC 
 address in there?
 Thanks, hope that was intelligible! 



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

[vagrant-up] changing default vagrant user

[Michael Legleux]

I'm creating a base box of windows and would like to NOT have user/pass 
vagrant/vagrant.

The wording in the documentation is not very clear on how to accomplish 
something like this.

Furthermore, http://docs.vagrantup.com/v2/virtualbox/boxes.html says that:

   - 
   
   The MAC address of the first network interface (the NAT adapter) should 
   be noted, since you'll need to put it in a Vagrantfile later as the value 
   for config.vm.base_mac. To get this value, use the VirtualBox GUI.
   
But then at the bottom of the page it's stated that:
If you're not using vagrant package --base above, you'll have to set the
config.vm.base_mac setting in this Vagrantfile to the MAC address of the 
NAT device without colons.
I have always used  vagrant package --base alone and seemingly have never 
had a problem (with communication at least.)
So what i want is to set config.ssh.username to be NOT vagrant by default.
From what I gather i should vagrant package --base the_vb_name 
--vagrantfile somevagrantfile where vagrantfile has the username/password 
configuration in it. ALSO if I do that, I will have to manually set the MAC 
address in there?
Thanks, hope that was intelligible! 

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

[vagrant-up] Re: vagrant adding box problem

[Michael Legleux]

Could this be possibly related to the commands vagrant is using being 32bit 
while the file i'm trying to package is greater than 4GB?

On Thursday, May 21, 2015 at 12:32:35 PM UTC-7, Michael Legleux wrote:

 I packaged a windows 7 box using vagrant 1.6.5 on windows 8.1 and have 
 been using it successfully for awhile on the same machine.

 I just moved the .box to a few other machines (windows 8.1 and 
 ubuntu12.04) and when adding the box I get the error:

 The box failed to unpackage properly. Please verify that the box
 file you're trying to add is not corrupted and try again. The
 output from attempting to unpackage (if any):

 x ./box-disk1.vmdk: truncated gzip input
 bsdtar.EXE: Error exit delayed from previous errors.





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

[vagrant-up] Re: vagrant adding box problem

[Michael Legleux]

Unfortunately I got the exact same error using Vagrant 1.7.2.


On Thursday, May 21, 2015 at 4:33:51 PM UTC-7, Michael Legleux wrote:

 Thanks a lot Alvaro, I am in the process of installing 1.7.2 for windows.

 I did see that it was using bsdtar during packaging.
 Does 1.7 use a different compression utility or just a different version.

 The strange thing is that the process works fine on the one windows 8 
 machine but any other machine with different vagrant versions, it doesn't 
 like it.

 Will report back if the same thing occurs in 1.7.2. after the long 
 packaging process.



 On Thursday, May 21, 2015 at 12:32:35 PM UTC-7, Michael Legleux wrote:

 I packaged a windows 7 box using vagrant 1.6.5 on windows 8.1 and have 
 been using it successfully for awhile on the same machine.

 I just moved the .box to a few other machines (windows 8.1 and 
 ubuntu12.04) and when adding the box I get the error:

 The box failed to unpackage properly. Please verify that the box
 file you're trying to add is not corrupted and try again. The
 output from attempting to unpackage (if any):

 x ./box-disk1.vmdk: truncated gzip input
 bsdtar.EXE: Error exit delayed from previous errors.





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

[vagrant-up] Re: vagrant adding box problem

[Michael Legleux]

Thanks a lot Alvaro, I am in the process of installing 1.7.2 for windows.

I did see that it was using bsdtar during packaging.
Does 1.7 use a different compression utility or just a different version.

The strange thing is that the process works fine on the one windows 8 
machine but any other machine with different vagrant versions, it doesn't 
like it.

Will report back if the same thing occurs in 1.7.2. after the long 
packaging process.



On Thursday, May 21, 2015 at 12:32:35 PM UTC-7, Michael Legleux wrote:

 I packaged a windows 7 box using vagrant 1.6.5 on windows 8.1 and have 
 been using it successfully for awhile on the same machine.

 I just moved the .box to a few other machines (windows 8.1 and 
 ubuntu12.04) and when adding the box I get the error:

 The box failed to unpackage properly. Please verify that the box
 file you're trying to add is not corrupted and try again. The
 output from attempting to unpackage (if any):

 x ./box-disk1.vmdk: truncated gzip input
 bsdtar.EXE: Error exit delayed from previous errors.





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

[vagrant-up] Re: Vagrant 1.6.x with windows guest and virtualbox

[Michael Zhou]

Understanding this topic is a couple of months old, but I hope this can 
benefit anyone who is searching for the answer. I fixed the same issue in 
my case by having these two lines added to my Vagrantfile.

  config.winrm.username = Administrator
  config.winrm.password = supply your administrator password here

That should allow Vagrant to WinRM into the Windows guest using the 
supplied credentials. You can use other users created on the base box, but 
make sure that user is added to administrators group and it has the 
privilege to remotely execute programs.

Here is my environment:

Vagrant: 1.6.5
Host OS: Windows 7
Guest OS: Windows 2008 R2


On Tuesday, June 10, 2014 at 3:46:18 PM UTC-4, Nick Anderson wrote:

 I am trying to build a Windows Server 2012 vm that I can use with Vagrant 
 and Virtualbox.

 It's not clear to me what I need to do. Here are the things I have done on 
 the Windows vm that I am preparing as a basebox.

 Disable password complexity requirements
 Set minimum password age to 0
 Set Administrator password to 'vagrant'
 Create vagrant user
 Set vagrant users password to 'vagrant'
 Enable remote desktop
 Add the vagrant user to the allowed list of remote desktop users
 Allow all connections from computers running any version of RDP (or my 
 linux client cant rdp successfully)
 Install ruby 1.9.3 from rubyinstall.org
 Install winrm with geminstall -rwinrm
 Configure winrm with winrm quickconfig
 Disable UAC
 Disable Server Manager on login
 Disable Shutdown Tracker
 Ensure that network is set to Private
 Install Virtualbox guest tools

 I export the vm as a box, import it to vagrant 
 I think generate a vagrant config using vagrant init name of windows box
 And then I added config.cm.communicator = winrm
 Finally I vagrant up my env.

 The VM comes up without issue, but Vagrant just sits waiting for the 
 machine to boot until it times out.
 vagrant rdp does nothing

 I am able to manually log in with rdesktop if I specifically forward a port
 config.vm.network forwarded_port, guest: 3389, host: 53389

 Then rdesktop localhost:53389 will give me the windows login screen.

 I have tried with and without the vagrant-windows plugin.

 I am running vagrant 1.6.3 on Ubuntu.

 It seems like I am missing some basic thing. Have I missed some 
 documentation somewhere?


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

[vagrant-up] Vagrant packaging issue

[Michael Legleux]

I'm trying to package a new box from a virtualbox machine on ubuntu 14.10.

In 1.6.5, vagrant package --base some_vm works.
Now in 1.7.2.dev, I am getting an error at:

../vagrant/plugins/commands/package/command.rb:83: in `package_vm': wrong 
argument type String (expected Symbol) (TypeError)

At first I thought it seemed like the error in 1.7 that was failing at that 
exact line with wrong number of arguments when trying to package the box, 
but now I am running 1.7.2.dev which fixed that error but is still not 
working for me.


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

[vagrant-up] multi-machine overriding provsioner settings

[Michael Lindsay]

Hey Group, 

I'm new to ruby but on the strength of work I've done so far with vagrant 
and chef I'm trying to do a multi-machine configuration, but I'm having 
some trouble with the syntax for allowing each vm to share configuration 
with the outer configuration.  

For example, I'd like the auth machine definition (and any other machine 
definitions I create) to use the provisioning settings from the outer 
block. I've tried many variations of the code below, and if I don't produce 
a syntax error, the chef server url does not get into the auth block.  I 
think I don't understand what is meant by To override settings, you must 
assign a name to your provisioner. in the documentation 
here: https://docs.vagrantup.com/v2/provisioning/basic_usage.html.

Vagrant.configure(2) do |config|

  config.vm.provision chef_client do |chef|
 chef.chef_server_url = https://foo.bar.com;
  end

  config.vm.define auth do |auth|
auth.vm.provision chef_client  do |chef|
  chef.run_list = [
recipe[auth::developer]
  ]
end
  end
end

TIA, Michael


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

[vagrant-up] Re: multi-machine overriding provsioner settings

[Michael Lindsay]

When I try sticking to the syntax in the example provided by the 
documentation:

Vagrant.configure(2) do |config|
  config.vm.provision base_chef,
type: chef_client,
chef_server_url: https://foo.bar.com;

  config.vm.define auth do |auth|
auth.vm.network private_network, ip: 192.168.15.101
auth.vm.provision base_chef,
  type: chef_client,
  run_list: recipe[base::users],recipe[auth::developer]
  end
end

I get the error * The 'base_chef' provisioner could not be found

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

[vagrant-up] Re: multi-machine overriding provsioner settings

[Michael Lindsay]

after looking at the 1.7.0 I noticed: Named provisioners.  I was on 1.6.3, 
I have now upgraded (1.7.1), but I'm getting this now:  

* The '' provisioner could not be found.

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

[vagrant-up] Exporting Pillar Data

[MICHAEL KAPLAN]

Hi,

I've been unable to define pillar data in my Vagrantfile and have it 
accessible after provisioning. When I do a salt '*' pillar.items, i do not 
see the additional items I added during my call to salt.pillar in the 
Vagrantfile. I am simply trying to recreate the one example in the Vagrant 
documentation. Has anyone else had trouble with this? I am using Vagrant 
1.6.3

Thanks.

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

Re: [vagrant-up] Use box versioning without Vagrant Cloud?

[Michael Baydoun]

ditto




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

Re: [vagrant-up] Multiple VMS from one box - storage

[Michael Quinn]

Apologies Alvaro
 
Seems like this is a known bug on windows hosts (another reason to hate 
windows, not that I need many ;-)
 
https://github.com/mitchellh/vagrant/issues/3584
 
I should have searched sorry

 

   


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

Re: [vagrant-up] Multiple VMS from one box - storage

[Michael Quinn]

Alvaro
  did not make any difference, looking at vagrant debug output, it seems 
the target path is what sets the storage
  
  looks like Vagrant does a simple VirtualBox import and its virtualbox 
setting the target path.  Would be nice to be able
  to explicitly set the storage location, and while the VBox api can let u 
do it, I cant from Vagrant ??

  9: Hard disk image: source image=box-disk2.vmdk, target 
path=E:\VirtualBoxHome\vms\TestEnv1_default_1403862581501_72384\box-disk2_2.vmdk,
 
controller=8;channel=0
(change target path with --vsys 0 --unit 9 --disk path;
disable with --vsys 0 --unit 9 --ignore)
10: Hard disk image: source image=box-disk3.vmdk, target 
path=E:\VirtualBoxHome\vms\TestEnv1_default_1403862581501_72384\box-disk3_6.vmdk,
 
controller=8;channel=1
(change target path with --vsys 0 --unit 10 --disk path;
disable with --vsys 0 --unit 10 --ignore)



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

Re: [vagrant-up] Multiple VMS from one box - storage

[Michael Quinn]

Alvaro
   thanks for the help, and I'll attach the Vagrantfile below

   Irrespective of what I name the VM as, the storage will always end up in 
   E:\VirtualBoxHome\vms (my setting in prefs on VirtualBox) under the 
   TestEnv1_default_1403862581501_72384 directory, which is defined
   in the box.ovf file of the OEL6.4_64_UEK_xWin_puppet_60Gb base box i 
created
  The rest of the VM is in the test1.example.com directory
  as expected



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

# Vagrantfile API/syntax version. Don't touch unless you know what you're 
doing!
VAGRANTFILE_API_VERSION = 2

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
  config.vm.box = OEL6.4_64_UEK_xWin_puppet_60Gb
  config.vm.network :private_network, ip: 10.10.10.70
  config.vm.provider :virtualbox do |vb|
  vb.customize [modifyvm, :id, --memory, 4096]
  vb.customize [modifyvm, :id, --name  , test1.example.com]
  vb.customize [modifyvm, :id, --vram  , 32]
  vb.gui = true
end
end




On Sunday, 29 June 2014 19:25:55 UTC+10, Alvaro Miranda Aguilera wrote:

 Hello, please share you vagrantfile

 you can have 3 different names that will do different things.

 one is for hostname inside the guest, other is the gui name in virtualbox 
 and other is the name of the VM, that is the one used in the folder.

 I can check and review.

 Alvaro.


 On Sun, Jun 29, 2014 at 4:31 PM, Michael Quinn micha...@gmail.com 
 javascript: wrote:

 All 
 Host : Windows 7 64bit - 16Gb RAM
 Vagrant version  : 1.6.3
 Virtual Box version : 4.3.12 r93733

 Question
  1 - can you specify the storage location during a vagrant up
   

   *Details below*

 I am creating multiple VMS(VirtualBox) from a single box - quite 
 normal i would expect and these are named VMS
 When ever I create a new VM from the box, the storage(vmdk) always 
 goes into the 
 same directory , based on the ovf:id in the box.ovf file - in my 
 case TestEnv1_default_1403862581501_72384
 irrespective of the named VM directory

 And the storage never gets moved into the directory of the vm name 
 (in my case oer.example.com)
 and in the oer.example.com directory is the oer.example.com.vbox.
   
 heres the relevant snippet from debug log

  INFO subprocess: Starting process: [D:\\VirtualBox\\VBoxManage.exe, 
  import, 
 E:\\Vagrant\\home\\boxes\\OEL6.4_64_UEK_xWin_puppet_60Gb\\0\\virtualbox\\box.ovf,
  
  --vsys, 0, --vmname, 
 TestEnv1_default_1403862581501_72384_1404013328373_24331,
  --vsys, 0, --unit, 9, 
  --disk, 
 E:\\VirtualBoxHome\\vms\\TestEnv1_default_1403862581501_72384\\box-disk2.vmdk,
  --vsys, 0, --unit, 10, --disk, 
 E:\\VirtualBoxHome\\vms\\TestEnv1_default_1403862581501_72384\\box-disk3_4.vmdk]

 
 
 

 -- 
 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 javascript:.
 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 vagrant-up+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Multiple VMS from one box - storage

[Michael Quinn]

All 
Host : Windows 7 64bit - 16Gb RAM
Vagrant version  : 1.6.3
Virtual Box version : 4.3.12 r93733

Question
 1 - can you specify the storage location during a vagrant up
  

  *Details below*

I am creating multiple VMS(VirtualBox) from a single box - quite normal 
i would expect and these are named VMS
When ever I create a new VM from the box, the storage(vmdk) always goes 
into the 
same directory , based on the ovf:id in the box.ovf file - in my 
case TestEnv1_default_1403862581501_72384
irrespective of the named VM directory

And the storage never gets moved into the directory of the vm name (in 
my case oer.example.com)
and in the oer.example.com directory is the oer.example.com.vbox.
  
heres the relevant snippet from debug log

 INFO subprocess: Starting process: [D:\\VirtualBox\\VBoxManage.exe, 
 import, 
E:\\Vagrant\\home\\boxes\\OEL6.4_64_UEK_xWin_puppet_60Gb\\0\\virtualbox\\box.ovf,
 
 --vsys, 0, --vmname, 
TestEnv1_default_1403862581501_72384_1404013328373_24331,
 --vsys, 0, --unit, 9, 
 --disk, 
E:\\VirtualBoxHome\\vms\\TestEnv1_default_1403862581501_72384\\box-disk2.vmdk,
 --vsys, 0, --unit, 10, --disk, 
E:\\VirtualBoxHome\\vms\\TestEnv1_default_1403862581501_72384\\box-disk3_4.vmdk]





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

Re: [vagrant-up] Vagrant plugin install offline/sandbox

[Michael Sumulong]

Ah. I didn't see this article. I'll check it out.

On Wednesday, June 18, 2014 10:05:29 PM UTC-4, Alvaro Miranda Aguilera 
wrote:

 does this still works?

 http://3ofcoins.net/2013/06/10/installing-vagrant-plugins-from-local-file/




 On Wed, Jun 18, 2014 at 7:52 AM, Michael Sumulong msum...@gmail.com 
 javascript: wrote:

 Is there a way to install a vagrant plugin on a machine that is not 
 connected to the internet?
  
 -- 
 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 javascript:.
 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 vagrant-up+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Vagrant plugin install offline/sandbox

[Michael Sumulong]

Is there a way to install a vagrant plugin on a machine that is not 
connected to the internet?

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

[vagrant-up] vagrant rdp windows_box username needs domain name also

[Michael Legleux]

The username being supplied to rdp via vagrant is vagrant. 
This gets rejected by the box as the remote desktop connection is looking 
for the username to be: domain/username.

How do I tell vagrant to not just user vagrant, but to use 
domain/vagrant?

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

Re: [vagrant-up] windows communicator settings

[Michael Legleux]

Changing the ports as vagrant suggests (from host 3389 ) boots just fine 
but vagrant cannot communicate with windows for some reason and times out 
while waiting for the machine to boot.

On Saturday, May 17, 2014 1:19:00 AM UTC-7, Alvaro Miranda Aguilera wrote:

 does vagrant if rdp port is on a different port than 3389 ?

 or, does winrm fails as not all the vms have por 5985 forwarded?



 On Sat, May 17, 2014 at 11:19 AM, Michael Legleux 
 leg...@gmail.comjavascript:
  wrote:

 I created a base box of windows 7 and 8 using virtualbox.
 I configured the winrm according to the vagrant-windows port-forwarding 
 for rdp and winrm.
 also this post helped since:
 https://github.com/mitchellh/vagrant/issues/3685

   config.vm.network :forwarded_port, guest: 5985, host: 5985, id: winrm, 
 auto_correct: true

   config.vm.network :forwarded_port, guest: 3389, host: 3389, id: rdp, 
 auto_correct: true

 Using linux, my custom box imported and boots fine. The basebox winrm 
 configuring seems to work as vagrant doesn't hang and give up while 
 waiting for machine to boot.

 However... when trying on a windows machine, vagrant complains that it 
 can't forward the specified ports on this vm because it is already in use 
 on the host machine.
 The port being 3389, which is windows remote desktop port.

 When I changed the forwarded ports for the guest (as it suggests) vagrant 
 is unable to communicate with the windows box.
 Now I am unsure how to proceed.

 -- 
 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 javascript:.
 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 vagrant-up+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Openstack provider - broken?

[Michael Sverdlik]

Hey,
I'm trying to make openstack-provider-plugin work, and it seems broken 
(with Vagrant 1.6.2.).

Is anyone here works with openstack provider and can tell me if it is 
broken or I'm doing something wrong?

Thanks

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

[vagrant-up] windows communicator settings

[Michael Legleux]

I created a base box of windows 7 and 8 using virtualbox.
I configured the winrm according to the vagrant-windows port-forwarding for 
rdp and winrm.
also this post helped since:
https://github.com/mitchellh/vagrant/issues/3685

  config.vm.network :forwarded_port, guest: 5985, host: 5985, id: winrm, 
auto_correct: true

  config.vm.network :forwarded_port, guest: 3389, host: 3389, id: rdp, 
auto_correct: true

Using linux, my custom box imported and boots fine. The basebox winrm 
configuring seems to work as vagrant doesn't hang and give up while 
waiting for machine to boot.

However... when trying on a windows machine, vagrant complains that it 
can't forward the specified ports on this vm because it is already in use 
on the host machine.
The port being 3389, which is windows remote desktop port.

When I changed the forwarded ports for the guest (as it suggests) vagrant 
is unable to communicate with the windows box.
Now I am unsure how to proceed.

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

[vagrant-up] Re: vagrant up gives timeout

[Michael Sverdlik]

Vagrant file is running fine on my machine (Vagrant 1.6.2 on OS X).
I'm not sure why first vagrant up command gave you error, seems like you 
already had some previous machine running from before?


On Wednesday, May 14, 2014 1:27:59 PM UTC+3, Chamila Wijayarathna wrote:

 Hello All,
 I'm trying to create vagrant image at 
 https://github.com/apache/thrift/blob/master/contrib/Vagrantfile; for 
 building Apache Thrift.I installed virtualbox and then vagrant. When I 
 execute ' vagrant up', it gives me message at [1]. Am I doing anything 
 wrong here? How can I fix this?

 1. 
 https://gist.github.com/cdwijayarathna/759cfa38a40c3484f4d3https://www.google.com/url?q=https%3A%2F%2Fgist.github.com%2Fcdwijayarathna%2F759cfa38a40c3484f4d3sa=Dsntz=1usg=AFQjCNFXeLe0Wobm_MxATZO_RwhkYCMN2w

 Thank You!


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

[vagrant-up] Re: Vagrant Docker hangs on syncing folder to host VM

[Michael Sverdlik]

Try to manually specify rsync sync 
folderhttp://docs.vagrantup.com/v2/synced-folders/rsync.html as 
a workaround, see if that helps. You need to use rsync since boot2docker 
image doesn't support VirtualBox Guest Additions.

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

[vagrant-up] Re: Windows and Vagrant not playing nice.

[Michael Sverdlik]

I think you forgot to change the communicator definition, see 
herehttp://www.vagrantup.com/blog/feature-preview-vagrant-1-6-windows.html
.

On Friday, May 9, 2014 9:50:26 PM UTC+3, akshtray wrote:

 In a nutshell, 'vagrant up' is running into an issue where I keep getting:

 *default: SSH address: 127.0.0.1: http://127.0.0.1:*
 *default: SSH username: vagrant*
 *default: SSH auth method: password*
 *default: Warning: Connection timeout. Retrying...*
 *default: Warning: Remote connection disconnect. Retrying...*
 *default: Warning: Remote connection disconnect. Retrying...*
 *default: Warning: Remote connection disconnect. Retrying...*
 *default: Warning: Remote connection disconnect. Retrying...*

 till it eventually times out and says:

 *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.*

 However, the box does come up just fine and is usable. To give some 
 details and background (lots of information down there):

 I have Vagrant 1.6.1 and VirtualBox 4.3.10r93012 running on my work laptop 
 which is running Windows 7 Professional (64 bit). I have a Base Box for 
 Windows 2008 Server (64 bit) created and in place. I made sure to do the 
 following on the Windows VM (in Virtualbox) before packaging/creating the 
 Base Box using 'vagrant package':

 Created a OS user called vagrant with password vagrant. Made it 
 'Administrator'
 Turned off UAC (Msconfig)
 Disabled complex passwords.
 Disabled Shutdown Tracker.
 Disabled Server Manager Starting at login.
 Enabled and configured WinRM.

 My Vagrant file is fairly simple:
 *
 Vagrant.configure(2) do |config|

   # Max time to wait for the guest to shutdown
   config.windows.halt_timeout = 60
   config.windows.set_work_network = true
   
   # Admin user name and password
   config.winrm.username = Administrator
   config.winrm.password = password

   # Configure base box parameters
   config.vm.box = BaseBox
   config.vm.box_url = ./BaseBox.box
   config.vm.guest = :windows
   config.vm.provider virtualbox do |v|
 v.gui = true
   end

   # Port forward WinRM and RDP (changed values to NOT conflict with host)
   config.vm.network :forwarded_port, guest: 3389, host: 3391
   config.vm.network :forwarded_port, guest: 5985, host: 5987
 end
 *

 Things I have tried unsuccesfully:

 1. 'vagrant reload' 
 2. 'vagrant destory' - modify vagrantfile - 'vagrant up'. Some of the 
 things I tried:

 - config.windows.set_work_network = true
 - config.vm.network private_network, type: dhcp
 - config.ssh.password = vagrant -- tried forcing it to use password 
 instead of keys for authentication.

 3. Tried using 'NAT' and 'Bridged' both for the Network adapters on the VM 
 before packaging them.

 To test, I tried to create a brand new VM using:

 vagrant init hashicorp/precise64
 vagrant up

 This worked great and I ran into no issues. I am really out of ideas at 
 this point of time regarding what else I can try.

 Help will be greatly appreciated.

 Thanks.


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

[vagrant-up] Centos 6.5 Network Manager breaks vagrant ssh

[Michael Quinn]

I had an issue where i used a base vagrant box 
- https://dl.dropboxusercontent.com/s/np39xdpw05wfmv4/centos-6.5-x86_64.box
which is an excellent one with puppet installed etc... - thanks to Edwin 
Beimond - he's a genius for sure.

I wanted to add a decent desktop and chose gnome, via yum -y groupinstall 
fonts X11 basic-desktop

After this was applied (the yum, that is), vagrant up, hung fatally,

After debugging etc, I came to the conclusion that the gnome NetworkManager 
package was causing the problem, and after
removing it, the vagrant ssh and the Vagrantfile commands that rely on the 
ssh (hostnames, networks etc...)
started working no problems.

Does vagrant make some assumptions about the network config that are broken 
by NetworkManager 

Anyway, if anyone has some clues as to why, it would be good to know, as I 
arrived at this conclusion with a degree of trial and error

thanks

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

[vagrant-up] Re: After adding Desktop to Centos 6.5 - vagrant ssh fails

[Michael Quinn]

Alvaro, 
   worked it out myself   ;-)
  
  I should have looked for your reply

thanks

On Friday, 18 April 2014 12:36:18 UTC+10, Michael Quinn wrote:

 All
after adding Desktop (yum -y groupinstalll Desktop) 
and then restarting the VirtualBox image (vagrant up)
I get the following

   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.  etc...

if I put vb.gui = true I can see the machine has started no probs ?

 help 


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