[vagrant-up] How to take backup of Vagrant box without reboot ?

[Adminbirds]

Hi

we have 33 vagrant box running on our physical machine. I need to take 
entire VM backup to our backup server.

I found this 

https://scotch.io/tutorials/how-to-create-a-vagrant-base-box-from-an-existing-one

Creating as package then copy it to remote location (vagrant package). But 
while doing vagrant package the box went down, is there is any option to 
take vagrant package with --no-reboot option.

For 100 GB box it took more than 2 hours to converting as package. we can't 
afford downtime :-)

One more question, I'm copying the current vmdk files & to remote folder, 
VM's is in running state, does it cause any data corruption for the box ? 
while syncing the data to remote location.

Simply my question is how we can take entire vm box backup without reboot 
box ? anybody knows the answer, please help ;-)

-- 
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/add0d9ca-0089-42b8-a426-0b4c04278c72%40googlegroups.com.

Re: [vagrant-up] how to create vm with existing vmdk file

[Adminbirds]

Yes I got the answer

vboxmanage internalcommands sethduuid "/data/VirtualBox
VMs/data_vm-tempOne_1570715511966_33620/centos-7-1-1.x86_64.vmdk"
"ab09cd7e-63df-4370-80e7-7ab0e8a19502"


vboxmanage internalcommands dumphdinfo "/data/VirtualBox
VMs/data_vm-tempOne_1570715511966_33620/centos-7-1-1.x86_64.vmdk"


solved the issues ;-)

On Tue, Nov 26, 2019 at 2:57 AM Alvaro Miranda Aguilera 
wrote:

> hello
>
> did you found a reply to your question?
>
>
> On Thu, Oct 10, 2019 at 4:11 PM Adminbirds  wrote:
>
>> Hi
>>
>> I need to create a vm with existing vmdk file, base machine is centos,
>> How to do in command line
>>
>> I tried box not up due to UUID mismatch, I have updated .vbox .xml file
>> after creating new UUID, no luck
>>
>> --
>> 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/fbd2ad48-06fc-4978-9d1e-e16c9fb980ee%40googlegroups.com
>> 
>> .
>>
>
>
> --
> Alvaro
>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Vagrant" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vagrant-up+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vagrant-up/CAHqq0ezfg6NeCa9UhLq0G4qeMfpEY4n8i0uDrWD4vBTN1rZLFQ%40mail.gmail.com
> 
> .
>

-- 
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/CACiVxAJwkGK0Qre8tpWKFu3%3DVaHm_P_7jpf93KU1s6dZ21uFdg%40mail.gmail.com.

Re: [vagrant-up] vagrant plugin install from a local file source without internet connection

[sahana Santhosh]

Hi Alvaro,

Thanks for the response I tried but faced the same issue

# vagrant plugin install ./vagrant-libvirt-0.0.45.gem

Installing the './vagrant-libvirt-0.0.45.gem' plugin. This can take a few 
minutes...
Vagrant failed to load a configured plugin source. This can be caused
by a variety of issues including: transient connectivity issues, proxy
filtering rejecting access to a configured plugin source, or a configured
plugin source not responding correctly. Please review the error message
below to help resolve the issue:

  no such name (https://gems.hashicorp.com/specs.4.8.gz)

Source: https://gems.hashicorp.com/


However I am able to install with command 
"vagrant plugin install --plugin-clean-sources vagrant-libvirt-0.0.45.gem"

but after the installation " vagrant box add test test.box"  failed with 
following error

 INFO manager: Loading plugin `ruby-libvirt` with slash require: 
`ruby/libvirt`
ERROR manager: Plugin loading error: LoadError - cannot load such file -- 
ruby/libvirt


I did install all the dependencies needed for  vagrant-libvirt like 
[formatador-0.2.5.gem, 
excon-0.68.0.gem,builder-3.2.3.gem,fog-core-1.43.0.gem,fog-json-1.2.0.gem 
,fog-libvirt-0.7.0.gem,fog-xml-0.1.3.gem , 
mini_portile-0.5.0.gem,multi_json-1.14.1.gem,nokogiri-1.6.0.gem,ruby-libvirt-0.7.1.gem]
 
.
I am not sure if the above way of installing the plugin is correct or not. 
Please guide.



On Tuesday, November 26, 2019 at 2:55:22 AM UTC+5:30, Alvaro Miranda 
Aguilera wrote:
>
> hello try
>
> vagrant plugin install ./vagrant-libvirt-0.0.45.gem
>
> On Wed, Nov 20, 2019 at 9:41 AM sahana Santhosh  > wrote:
>
>> Hi,
>>
>> I am trying to install vagrant plugin "vagrant-libvirt". I have 
>> downloaded all the necessary .gem file in my local machine which does not 
>> have access to internet. I am facing the following error...
>>
>> # vagrant plugin install vagrant-libvirt-0.0.45.gem
>>
>> Installing the 'vagrant-libvirt-0.0.45.gem' plugin. This can take a few 
>> minutes...
>>
>> Vagrant failed to load a configured plugin source. This can be caused
>> by a variety of issues including: transient connectivity issues, proxy
>> filtering rejecting access to a configured plugin source, or a configured
>> plugin source not responding correctly. Please review the error message
>> below to help resolve the issue:
>>
>>   no such name (https://gems.hashicorp.com/specs.4.8.gz)
>>
>> Source: https://gems.hashicorp.com/
>>
>>
>>
>> Why it is trying to access internet when we are pointing it to local gem 
>> file ?? Is it possible to install vagrant plugin offline ? This is bottle 
>> neck for us, please let us know if offline installation is possible or not.
>>
>> Thanks in advance
>>
>> -Sahana
>>
>> -- 
>> 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/4454c8d3-c52d-4ac1-8fb5-bdabf8b29428%40googlegroups.com
>>  
>> 
>> .
>>
>
>
> -- 
> Alvaro
>
>

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

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/be34b775-2ce7-429d-bb59-7c771f5fb752%40googlegroups.com.

Re: [vagrant-up] Re: Spinning up a few docker containers in Windows host + Vagrant + Virtualbox environment

[Alvaro Miranda Aguilera]

yes

and you can use private network to have connectivity between vms.

for vm to vm in docker to docker, it seems the best is create 2 nodes on
docker swarm.. just not sure whats the best for your setup

alvaro

On Sun, Oct 13, 2019 at 12:53 AM Sorcerer Stone 
wrote:

> Hmm, I googled. I think the instructions on this URL seems to be the
> solution I am looking for.
>
> https://www.vagrantup.com/docs/multi-machine/
>
> Am I correct?
>
>
> On Saturday, October 12, 2019 at 5:22:46 PM UTC-4, Sorcerer Stone wrote:
>>
>> In native Windows environment, I can use dos boxes to access docker
>> (docker toolbox + Virtualbox) so that I can run one docker container
>> against another related container.
>>
>> My OS is Win10 pro (with HyperV disabled), Running a Linux environment
>> using Vagrant & Virtualbox. So I am within a guest Ubuntu host and I want
>> to do something similar to the above aka run multiple docker containers
>> (i.e. I would like to run a docker container to interact with the existing
>> running container. How do I achieve in Vagrant environment?
>> In my host folder, I have a vagrantfile which tells the virtual host to
>> load Ubuntu using Vagrant Up and then I run a docker container. I can't
>> possibly pull up another dos box and try to access the same virtual
>> environment by running the same vagrantfile so that I can run another
>> docker container. Correct?
>> Can anyone please advise me how I can run multiple docker containers in
>> this mixed Vagrant, Virtualbox, environment? I need 2 docker containers
>> running side-by-side and interacting with each other.
>> Thanks in advance.
>>
>> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Vagrant" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vagrant-up+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vagrant-up/dea7cc4d-48b4-4bd2-a421-e1124200eba3%40googlegroups.com
> 
> .
>


-- 
Alvaro

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

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0ez%2BtAzSY_mF4-51AyKHTp-CeyJYcUtZ36mH1V9%2BnjYuQQ%40mail.gmail.com.

Re: [vagrant-up] [Vagrant 2.2.5] [Hyper-V] Guest-specific operations were attempted on a machine that is not ready for guest communication.

[Alvaro Miranda Aguilera]

hello

vagrant-vbguest is for virtualbox guest additions

i would suggest remove this and other plugins if not using virtualbox

the vm seems already was provisioned, so maybe did work at some point

you could try

vagrant destroy
vagrant up

if still fails, check hyper v console of this vm to check what may be
happening

alvaro

On Wed, Oct 16, 2019 at 8:30 PM Jacqueline Costa 
wrote:

> Well,
>
> I am using vagrant 2.2.5 and also provider is HyperV, I am using Stefan's
> Windows 10 box  
> But when one of my shell scripts start to working vagrant return:
>
> Bringing machine 'hyperv' up with 'hyperv' provider...
>
> ==> hyperv: Verifying Hyper-V is enabled...
>
> ==> hyperv: Verifying Hyper-V is accessible...
>
> ==> hyperv: Machine already provisioned.
>
> Run `vagrant provision` or use the `--provision`
>
> ==> hyperv: flag to force provisioning.
>
> Provisioners marked to run always will still run.
>
> ==> hyperv: Running provisioner: shell...
>
>
> Guest-specific operations were attempted on a machine that is not ready for 
> guest communication. This should not happen and a bug should be reported
>
>
> I tried install the plugin vagrant-vbguest and also without it, but the both 
> ways returns the message of Guest-specific.
>
> Any idea of what is happening?
>
> --
> 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/5318a3c5-df79-40b5-805a-0d7e791b794d%40googlegroups.com
> 
> .
>


-- 
Alvaro

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

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0eze545G6QUDK76oM5%3DDNU1iPjN%3D2nwkysBNco2Q9cdNPg%40mail.gmail.com.

Re: [vagrant-up] how to create vm with existing vmdk file

[Alvaro Miranda Aguilera]

hello

did you found a reply to your question?


On Thu, Oct 10, 2019 at 4:11 PM Adminbirds  wrote:

> Hi
>
> I need to create a vm with existing vmdk file, base machine is centos, How
> to do in command line
>
> I tried box not up due to UUID mismatch, I have updated .vbox .xml file
> after creating new UUID, no luck
>
> --
> 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/fbd2ad48-06fc-4978-9d1e-e16c9fb980ee%40googlegroups.com
> 
> .
>


-- 
Alvaro

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

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0ezfg6NeCa9UhLq0G4qeMfpEY4n8i0uDrWD4vBTN1rZLFQ%40mail.gmail.com.

Re: [vagrant-up] Run local exec after digitalocean droplet

[Alvaro Miranda Aguilera]

hello

sorry for the late reply

this is the vagrant mailing list

do you have a vagrant question?

On Tue, Oct 15, 2019 at 11:09 AM Julian Zielke 
wrote:

> Hi,
>
> I'm currently using Terragrunt in combination with Terraform to deploy
> digitalocean droplets.
>
> What I'm planning is to use local exec in order to run Ansbile on the
> deployed host(s) afterwards. So I need to access the list of hosts somehow
> but I always run into an error
> saying that the variable xyz is not (yet) declared.
>
> Here's an Example I've tried:
>
> resource "digitalocean_droplet" "instance" {
>  image = "${var.host_image}"
>  name  = "${var.host_name}"
>  region= "fra1"
>  size  = "${var.host_sizing}"
>  backups   = "${var.useBackups}"
>  tags  = "${split(",", replace(var.host_tags, " ", ""))}"
>  ssh_keys  = ["${digitalocean_ssh_key.default.fingerprint}"]
>  provisioner "remote-exec" {
>inline = ["echo"]
>
> connection {
>  host= "${data.digitalocean_droplet.instance.ipv4_address}"
>  type= "ssh"
>  user= "root"
>  private_key = "${file(var.public_key)}"
>}
>  }
> }
>
> Any chance to accomplish my goal?
>
> --
> 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/65cec1b4-203f-4f0d-bb96-5c9e8e5e137e%40googlegroups.com
> 
> .
>


-- 
Alvaro

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

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0ez8_GjdAdKts36%3Dupbq2PTXNVHik%3DFukV8jeEK9WfWaVg%40mail.gmail.com.

Re: [vagrant-up] vagrant plugin install from a local file source without internet connection

[Alvaro Miranda Aguilera]

hello try

vagrant plugin install ./vagrant-libvirt-0.0.45.gem

On Wed, Nov 20, 2019 at 9:41 AM sahana Santhosh 
wrote:

> Hi,
>
> I am trying to install vagrant plugin "vagrant-libvirt". I have downloaded
> all the necessary .gem file in my local machine which does not have access
> to internet. I am facing the following error...
>
> # vagrant plugin install vagrant-libvirt-0.0.45.gem
>
> Installing the 'vagrant-libvirt-0.0.45.gem' plugin. This can take a few
> minutes...
>
> Vagrant failed to load a configured plugin source. This can be caused
> by a variety of issues including: transient connectivity issues, proxy
> filtering rejecting access to a configured plugin source, or a configured
> plugin source not responding correctly. Please review the error message
> below to help resolve the issue:
>
>   no such name (https://gems.hashicorp.com/specs.4.8.gz)
>
> Source: https://gems.hashicorp.com/
>
>
>
> Why it is trying to access internet when we are pointing it to local gem
> file ?? Is it possible to install vagrant plugin offline ? This is bottle
> neck for us, please let us know if offline installation is possible or not.
>
> Thanks in advance
>
> -Sahana
>
> --
> 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/4454c8d3-c52d-4ac1-8fb5-bdabf8b29428%40googlegroups.com
> 
> .
>


-- 
Alvaro

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

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0ey0tupMRGPZXZWCwrHt7%2BWDgSao%2BAiERk%3DshPa14mZatA%40mail.gmail.com.

Re: [vagrant-up] feeding the host ssh port into the provisioner

[Alvaro Miranda Aguilera]

hello

2 things

1. you can set the port to something known

on one VM

config.vm.network :forwarded_port, guest: 22, host: 2291, id: "ssh"


on the second VM

config.vm.network :forwarded_port, guest: 22, host: 2292, id: "ssh"


and test


2. disable the insert ssh_key so you can connect with the insecure key



config.ssh.insert_key

=
false


then try to login with the insecure ssh key

https://github.com/hashicorp/vagrant/blob/master/keys/vagrant



Alvaro





On Fri, Oct 18, 2019 at 8:45 PM steve gibson  wrote:

> Hi,
>
> I'm am looking for a way to get the host port for the SSH port-forward and
> be able to write it in a file on the guest.
>
> My scenario is this:
> I have a multi-machine setup with 2 VMs (using vbox). Both machines need
> to be able to scp to each other. Since eth0 is on a private network, I
> cannot access one guest from the other. And because of the nature of my
> project, I cannot add a second network interface.
> So I am looking for a way to create a /root/.ssh/config file on each guest
> and define the peer guest with the port that is made available on the host.
> The IP would be the GW of the guest
>
> So how can I get VM1's ssh port when I am provisioning VM2 ?
>
> Thank you.
>
> --
> 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/077d5476-dff0-4db8-9d5e-029b9ef4a0d6%40googlegroups.com
> 
> .
>


-- 
Alvaro

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

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0ey91tXZP7DP755Otkx_aNM_%3DNJnbPCex7wd6KPEhYC2rQ%40mail.gmail.com.

Re: [vagrant-up] Change DNS for provionned box

[Alvaro Miranda Aguilera]

are those the dns of your host machine?

have you tried with a provisioning script set the new dns ?

alvaro

On Mon, Oct 28, 2019 at 9:48 AM Jean-Marc Messina 
wrote:

> Hi
>
> I need to spawn a bunch of boxes with vagrant that would use my DNS
> servers. Currently, they seem to use a static list that is :
>
>- 4.2.2.1
>- 4.2.2.2
>
> I'm quite new to terraform and have, so far, failed to find how to change
> these.
>
> Any clue ?
>
> --
> 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/82b49a4e-aa2b-4592-b646-25eb4eda54b1%40googlegroups.com
> 
> .
>


-- 
Alvaro

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

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0ewYnn_ma7R3hdFPRG5iCukQ3JbkUickEToc4w0A4YOc_Q%40mail.gmail.com.

Re: [vagrant-up] Vagrant ssh no longer working

[Alvaro Miranda Aguilera]

is this pure development?

if the VM gets into a inconsistent state, destroy/recreate is common
practice the VMs should be disponsable.

depening on the hypervisor you ae using, not sure if virtualbox or hyper-v
you should be able to login from the console

you may try to reload the vm, vagrant reload

however you should be able to login over the console and check the logs and
troubleshoot what is happening here

good luck

alvaro

On Fri, Oct 25, 2019 at 10:56 PM TB  wrote:

> Hello,
>
> I need help.  Recently, my chef server vagrant was working one day and the
> next it stopped working.  Everytime I run 'vagrant ssh' it said
> "ssh_exchange_identification: read: Connection reset by peer.' message.
> I've looked for this error message online, from other users suggesting to
> run vagrant halt, then vagrant up to bring it back, but it stills won't
> work.  Some suggested to check for enabling hyper-v and enabling vt-x, and
> it stills won't work.  I am thinking about to run vagrant destroy and bring
> back up again to its normal state with vagrant up, but afraid I might loose
> everything or how long it will take to get vagrant back to its normal
> working condition.
>
> Any suggestions/ideas to what caused this and how to resolve 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/c8820066-5da0-4a1d-a75e-a24652e137e1%40googlegroups.com
> 
> .
>


-- 
Alvaro

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

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0eyGwhO6dFGFg%2B%2Ba4Du%3DKMY-WWFvEB1OBSXyxATBdbJMeQ%40mail.gmail.com.

Re: [vagrant-up] Vagrant 2.2.6 on mac Os Catalina : Failed to start The Apache HTTP Server

[Alvaro Miranda Aguilera]

that is happening inside the VM.

so is not a vagrant issue at first sight

check the configuration file per error, seems line 7 is not good

Oct 28 03:43:18 homestead apachectl[3468]: AH00526: Syntax error on line 7
of /etc/apache2/sites-enabled/landingpage.local-ssl.conf:

alvaro

On Tue, Oct 29, 2019 at 1:21 AM Agus Mahendra B  wrote:

> macOS Catalina 10.15
> Vagrant 2.2.6 (installed via homestead)
>
>
> When I do "vagrant ssh" and "flip" ngix to appache, the process fails
> around this spot:
> nginx stopped
> Job for apache2.service failed because the control process exited with
> error code.
> See "systemctl status apache2.service" and "journalctl -xe" for details.
> apache started
>
>
> When I do "systemctl status apache2.service" showing like below:
>
> vagrant@homestead:~$ systemctl status apache2.service
> apache2.service - The Apache HTTP Server
> Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor
> preset: enabled)
> Drop-In: /lib/systemd/system/apache2.service.d
> └─apache2-systemd.conf
> Active: failed (Result: exit-code) since Mon 2019-10-28 03:43:18 UTC; 26s
> ago
> Process: 3468 ExecStart=/usr/sbin/apachectl start (code=exited,
> status=1/FAILURE)
>
> Oct 28 03:43:18 homestead systemd[1]: Starting The Apache HTTP Server...
> Oct 28 03:43:18 homestead apachectl[3468]: AH00526: Syntax error on line 7
> of /etc/apache2/sites-enabled/landingpage.local-ssl.conf:
> Oct 28 03:43:18 homestead apachectl[3468]: DocumentRoot takes one
> argument, Root directory of the document tree
> Oct 28 03:43:18 homestead apachectl[3468]: Action 'start' failed.
> Oct 28 03:43:18 homestead apachectl[3468]: The Apache error log may have
> more information.
> Oct 28 03:43:18 homestead systemd[1]: apache2.service: Control process
> exited, code=exited status=1
> Oct 28 03:43:18 homestead systemd[1]: apache2.service: Failed with result
> 'exit-code'.
> Oct 28 03:43:18 homestead systemd[1]: Failed to start The Apache HTTP
> Server.
>
>
> Has anyone experienced the same problem as 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/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/601e9b50-3409-4d6d-86f0-375ff7fcfdc8%40googlegroups.com
> 
> .
>


-- 
Alvaro

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

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0exEruskiiuTUNvQnPuOJ4DMLR7Fy9-heNfPPvbT37X09w%40mail.gmail.com.

Re: [vagrant-up] Vagrant error for adding a box, bsdtar: Error opening archive: Unrecognized archive format

[Alvaro Miranda Aguilera]

one option is download was incomplete.

other option is the file is damaged

try to delete the file and try a new download

alvaro

On Fri, Nov 1, 2019 at 12:43 PM sarah shakeri 
wrote:

> Hi,
>
>
>
> Vagrant version is: 2.2.6
> The host system is: Ubuntu 18.04.3 LTS
>
>
> I am going to add a box in vagrant by
>
> vagrant box add juniper/vqfx10k-pfe vqfx10k-pfe.box
>
> but I get below error:
>
> ==> box: Box file was not detected as metadata. Adding it directly...
> ==> box: Adding box 'juniper/vqfx10k-pfe' (v0) for provider:
> box: Unpacking necessary files from: 
> file:///home/sshakeri/ron19_sr/lab/vqfx10k-vagrant/vagrant_boxes/vqfx10k-pfe.box
> The box failed to unpackage properly. Please verify that the box
> file you're trying to add is not corrupted and that enough disk space
> is available and then try again.
> The output from attempting to unpackage (if any):
>
> bsdtar: Error opening archive: Unrecognized archive format
>
> Do you know what can be the possible problem?
>
> --
> 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/0c59721d-4b50-4dcd-b5b7-713ddb4a26a4%40googlegroups.com
> 
> .
>


-- 
Alvaro

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

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0ewkuE3HQWpHoJnsfBmP1W2pHUBmyo6CgnOM5SzUn%2BPn-A%40mail.gmail.com.

Re: [vagrant-up] Ping/Request OK in LAN, but KO via WAN

[Alvaro Miranda Aguilera]

you may be missing a router in this ip

whats the output of route print ?



On Fri, Nov 1, 2019 at 5:22 PM Namlu u  wrote:

> Hi !
>
> Summary:
> I have a virtual machine that hosts a website. The site is accessible
> anywhere in the local network, but neither to computers connected in VPN,
> nor in WAN interrogation with a correct port forwarding.
>
> Technically:
> - *Vagrant version*: 1.9.1
> - *Virtualbox version*: 5.2.34
> - *Host and virtual OS*: Debian 9
> - The website is the default installation of a nginx installed on the host
> (for diagnostics) and the virtual machine
>
> - Vagrantfile network configuration:
>
> config.vm.network "public_network", bridge: "enp0s25", ip: "192.168.1.201"
>
>
> - WAN forwarding port:
>
> 10080  >  192.168.1.100:80
> 20180  >  192.168.1.201:80
>
>
> Tests:
>
> *From raspberry in LAN (192.168.1.88)*
>
>
>- ping 192.168.1.100 *[host]*: *OK*
>   - ping 192.168.1.201*[vm] *   : *OK*
>   - curl 192.168.1.100 *[host]* : *OK*
>   - curl 192.168.1.201 *[vm] *   : *OK*
>   - curl mydomain:10080 *[host]* : *OK*
>   - curl mydomain:20180 *[vm]*   : *OK*
>
> *From my cellphone on VPN (192.168.1.52**)*
>
>- ping 192.168.1.100 *[host]*: *OK*
>- ping 192.168.1.201*[vm] *   : *KO*
>- curl 192.168.1.100 *[host]* : *OK*
>- curl 192.168.1.201 *[vm] *   : *KO*
>- curl mydomain:10080 *[host]* : *OK*
>- curl mydomain:20180 *[vm]*   : *KO*
>
> *From my cellphone off VPN (192.168.0.3**)*
>
>
>- curl mydomain:10080 *[host]* : *OK*
>   - curl mydomain:20180 *[vm]*   : *KO*
>
>
> Conclusion:
> I concluded it's my configuration of Vagrant and / or Virtualbox that is
> problematic. Do you have an idea of ​​what can happen?
> Thanks for your help !
>
> More data:
> - *Vagrant version* 1.9.1
> - *Virtualbox version* 5.2.34
> - *Host and virtual OS* Debian 9
> - *ifconfig on host*
>
> enp0s25: flags=4163  mtu 1500
> inet 192.168.1.100  netmask 255.255.255.0  broadcast 192.168.1.255
> ether 00:15:17:e6:94:bc  txqueuelen 1000  (Ethernet)
> RX packets 10351311  bytes 12044849276 (11.2 GiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 8569810  bytes 669605531 (638.5 MiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> device interrupt 20  memory 0xc2b0-c2b2
>
> lo: flags=73  mtu 65536
> inet 127.0.0.1  netmask 255.0.0.0
> inet6 ::1  prefixlen 128  scopeid 0x10
> loop  txqueuelen 1  (Boucle locale)
> RX packets 446809  bytes 51801204 (49.4 MiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 446809  bytes 51801204 (49.4 MiB)eth0:
> flags=4163  mtu 1500
> inet 10.0.2.15  netmask 255.255.255.0  broadcast 10.0.2.255
> inet6 fe80::a00:27ff:fe8d:c04d  prefixlen 64  scopeid 0x20
> ether 08:00:27:8d:c0:4d  txqueuelen 1000  (Ethernet)
> RX packets 11678  bytes 15457601 (14.7 MiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 5981  bytes 423088 (413.1 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
>
>
> - *ifconfig on virtual machine*
>
> eth0: flags=4163  mtu 1500
> inet 10.0.2.15  netmask 255.255.255.0  broadcast 10.0.2.255
> inet6 fe80::a00:27ff:fe8d:c04d  prefixlen 64  scopeid 0x20
> ether 08:00:27:8d:c0:4d  txqueuelen 1000  (Ethernet)
> RX packets 11678  bytes 15457601 (14.7 MiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 5981  bytes 423088 (413.1 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> eth1: flags=4163  mtu 1500
> inet 192.168.1.203  netmask 255.255.255.0  broadcast 192.168.1.255
> inet6 2a01:e35:2f4d:7aa0:a00:27ff:fe91:41e5  prefixlen 64  scopeid
> 0x0
> inet6 fe80::a00:27ff:fe91:41e5  prefixlen 64  scopeid 0x20
> ether 08:00:27:91:41:e5  txqueuelen 1000  (Ethernet)
> RX packets 110921  bytes 149988100 (143.0 MiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 83255  bytes 8211893 (7.8 MiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> lo: flags=73  mtu 65536
> inet 127.0.0.1  netmask 255.0.0.0
> inet6 ::1  prefixlen 128  scopeid 0x10
> loop  txqueuelen 1  (Local Loopback)
> RX packets 8  bytes 540 (540.0 B)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 8  bytes 540 (540.0 B)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> --
> 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
> ---
> 

Re: [vagrant-up] Create virtual interfaces for create isolated envs

[Alvaro Miranda Aguilera]

hello

on virtualbox the VM will have nat, and from there should be access any VM
that your host can access.

As each net VM will be on his own switch if the nics are different, but all
these switch are available to the host, every machine should be able to
reach any machine over the NAT interface.

is not clear from the diagram how you want to do it. can you elaborate a
bit more? maybe a diagram will help.

then, second question is why the projects need to be isolated?

are going to be using same ip segmentation?




On Sat, Nov 23, 2019 at 5:40 PM Fabio Pezzini  wrote:

> I'm trying to create isolated environments containing both Vm (virtualbox)
> and containers (docker). Then using virtualbox and docker.
> What I'm trying to achieve are closed networks where ONLY the machines in
> the given project can talk.
> The only way I could think of is by creating interfaces with a given
> gateway assigned to the virtual interface on the host machine and assigning
> this interface to all the guests I want to enclose in the subnet.
> I tried creating virtual namespaces but they can't talk (especially
> between container and vm). How can I do?
>
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in
> violation of those guidelines may result in your removal from this mailing
> list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Vagrant" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vagrant-up+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vagrant-up/dd4d7b76-6ebe-4730-a7e0-935fcd96990d%40googlegroups.com
> 
> .
>


-- 
Alvaro

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

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0eySrje%2Ba73VCoQj446MGC%2BuZpQ%3DK-zdxGA8Q3FUXKpYgQ%40mail.gmail.com.

[vagrant-up] Re: Is it possible to get the box version when you are inside the VM?

[D Morgan]

You have to pass the information in as part of the vagrant up/reload 
process. 

Through a combination of the shell provisioner or file provisioner you can 
accomplish what you need

# Env Variable
config.vm.provision "shell", inline: "EXPORT box_version = ..."

or 

# Text File
config.vm.provision "shell", inline: "echo box_version = ... > 
~/bversion.txt"

or 

#Hardcoded text file as part of some outside process
config.vm.provision "file", source: "~/bversion.txt", destination: 
"~/bversion.txt"




On Sunday, November 24, 2019 at 7:56:14 PM UTC-5, mike konovalov wrote:
>
> In one of the scripts that I run inside VM I need to figure out what is 
> the current box version.
> Is it possible to bake this information inside VM somehow? Maybe some env 
> vars or something?
> 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/5622092a-07ed-4a65-ada0-4db70ade24a5%40googlegroups.com.