Re: [vagrant-up] Vagrant keeping my disks awake

[Adrian Wallaschek]

It is not a matter of a VM. The magnetic disks are just in the host. They 
are not used by any VM nor VMware nor Vagrant. Right now, my MP3 collection 
is on them. The whole Vagrant and VM stuff ist on SSD.

But wenn I run "vagrant ssh" (e.g.) in the Powershell, then it first spins 
up the HDDs. They are not in the PATH, they do not contain Software, 
nothing.

I beliebe from some weird reason vagrant when starting enumerate the disks 
in the system and checks for - maybe - config files or so on each one of 
them.
I would think that somebody would know or recognize this behaviour and give 
me a hint on how to inhibit that. (config directive, whatever).

So to make it clear: even if no VM is running  this happens when 
running vagrant: it wakes up my HDDs (Y: and Z:, while VMware and Vagrant 
are on V: and system is on C: each on separate physical volumes).


To explain it in more detail:

C: is a mirror set of two NVMe SSDs (2x 1TB)
V: is a striped volume of two other NVMe SSDs (2x2TB)
some other SATA SSDs (4 pcs, unrelated) have own drive letters
Y: is a magnetic disk (8TB)
Z: is a magnetic disk (ditto)

If on V: I run vagrant whatever, the command spins up Y: and Z:, not only 
that ... it also waits for the spin up to complete, which is boring me.


Does that kind of explain the problem better?


Am Dienstag, 5. Mai 2020 11:06:37 UTC+2 schrieb Alvaro Miranda Aguilera:
>
> What about you mount in the guest some remote filesystem ??
>
> in that way will be accessed only when needed.
>
> without much information about how your pc looks like, boot disk, 
> filesystem layout, will be a lot of guessing.
>
> So i would take the simple route and use a filesystem to the VM.
>
> 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/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/95992818-0bd1-41b4-843c-4fdc0b1f0132%40googlegroups.com.

Re: [vagrant-up] Virtual Box bridged network and port forwarding VAGRANT

[Yayaoui Namoussi]

Well i think its cause i need a default route to the router 
0.0.0.0 10.0.2.20.0.0.0 UG0  00 eth0
10.0.2.00.0.0.0 255.255.255.0   U 0  00 eth0
192.168.1.0 0.0.0.0 255.255.255.0   U 0  00 eth1

when i add
0.0.0.0192.168.1.254 it start working,but i dont understund why 
its not add by 
   config.vm.provision "shell", run: "always", inline: "route add default 
gw 192.168.1.254"

Le dimanche 5 avril 2020 19:52:17 UTC+2, Alvaro Miranda Aguilera a écrit :
>
> it shoudl work without port forward
>
> whats the output from the vm of
>
> route -n
> ip addr
>
> as long default gw goes to the router it should work
>
>
>
> On Fri, Apr 3, 2020 at 10:08 PM Yayaoui Namoussi  > wrote:
>
>> 
>> This is my network : 
>>
>> Le vendredi 3 avril 2020 21:14:31 UTC+2, Alvaro Miranda Aguilera a écrit :
>>>
>>> if you comment out and try from the home network, does work?
>>>
>>> do you have how to test ?
>>>
>>> you dont need port forward if the VM is having a public IP on the network
>>>
>>> On Fri, Apr 3, 2020 at 5:22 PM Yayaoui Namoussi  
>>> wrote:
>>>
 Hey guys i'm having serious problme with to portforward my port 5060 
 i'm stuck on it since 1 week :(
 the probleme is i want to portforward the port 5060 on my bridge 
 network not in nat so naturaly i did this 
  

   config.vm.network "public_network", :bridge => "Realtek PCIe 
 2.5GbE Family Controller", :ip => "192.168.1.117" 


 ###DEFAULT ROUTER##
 config.vm.provision "shell",
 run: "always",
 inline: "route add default gw 192.168.1.254"
  
  config.vm.provision "shell",
 run: "always",
 inline: "eval `route -n | awk '{ if ($8 ==\"eth0\" && $2 != 
 \"0.0.0.0\") print \"route del default gw \" $2; }'`"
   config.vm.network "forwarded_port", :adapter=>2, guest: 5060,host: 
 5060, protocol: "udp"


 Then when i do vagrant reload i have this 

 default: VirtualBox adapter #2 not configured as "NAT". 
 Skipping port


 in my router i did port forwarding like this 192.168.1.117 / UDP / ALL 
 IP / 5060 / 5060 
 and still when i try to check open port through internet its says the 
 port is close

 -- 
 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/d647b519-e8f0-4d38-a738-3398e4eb9e96%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 vagra...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/vagrant-up/510b54bd-bf3f-487c-80bd-be9f9f42684e%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/0a61687e-49f2-4222-9d68-37c58a7ce38c%40googlegroups.com.

Re: [vagrant-up] NFS Sharing from host to Vagrant VM !!

[Alvaro Miranda Aguilera]

there is a nfs server on  192.168.121.1 ?

can you mount on the guest manually  192.168.121.1:/root/hlinux-
tools/netinst-iso
?


alvaro

On Tue, May 5, 2020 at 4:24 PM Ibrahim Vanak 
wrote:

> The issue is, while running “vagrant up” I am trying to do NFS mount from
> host to Vagrant VM. It’s failing to do so with the following error:
>
> ==> default: Mounting NFS shared folders...
>
> The following SSH command responded with a non-zero exit status.
>
> Vagrant assumes that this means the command failed!
>
>
>
> mount -o vers=4 192.168.121.1:/root/hlinux-tools/netinst-iso /vagrant
>
>
>
> Stdout from the command:
>
>
>
>
>
>
>
> Stderr from the command:
>
>
>
> mount.nfs: access denied by server while mounting 192.168.121.1:
> /root/hlinux-tools/netinst-iso
>
>
> My host VM is unbuntu 18.04 and vagrant VM would be debian Jessie.
>
>
> Snippet of NFS sharing code from Vagrant file:
>
>
> *  config.vm.synced_folder "./vagrantfolder", "/home/vagrant/output",*
>
> *nfs: true,*
>
> *linux__nfs_options: ['rw','no_subtree_check','all_squash','async']*
>
>
>
> *  config.vm.synced_folder "./vagrantfolder/repo",
> "/var/www/hLinuxArchive",*
>
> *nfs: true,*
>
> *linux__nfs_options: ['rw','no_subtree_check','all_squash','async']*
>
> --
> 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/1de9e302-83d1-4324-b1a8-373123fb3efe%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/CAHqq0ezdAyu%2Bt5YQU%3DYUAJkb6h3EB62CoBTTLfCFOF9tTuO4Zw%40mail.gmail.com.

Re: [vagrant-up] Unable to join HyperV node to swarm

[Alvaro Miranda Aguilera]

if you share the script we can have a look

Xwindows
https://en.wikipedia.org/wiki/X_Window_System



On Tue, May 5, 2020 at 11:29 AM kathir  wrote:

> yes that's correct
>
> I already did that individual commands are running in ssh, but not able
> run through vagrant external script provisioning
>
> i got the above error, is it related guest addition or what is that X ?
>
> Thanks & Regards,
> Kathirvel G
>
>
> On Tue, May 5, 2020 at 10:07 AM Alvaro Miranda Aguilera 
> wrote:
>
>> You don't seems to have an X running.
>>
>> This usually happens if you run a graphical application or an application
>> that need graphics
>>
>> just ssh to the machine, copy and run the script to see if you see the
>> same error.
>>
>> if you hit the same error, the error is coming from the scripts and the
>> way is being run and not vagrant.
>>
>> Thanks
>> Alvaro
>>
>> On Mon, Apr 27, 2020 at 11:52 AM kathir  wrote:
>>
>>> Hi
>>>
>>> When i tried to use vagrant file provisioning using external shell
>>> script, i ended up to look into log file as it says
>>>
>>>   Could not find the X.Org or XFree86 Window System, skipping
>>>
>>> Please suggest
>>> Thanks & Regards,
>>> Kathirvel G
>>>
>>>
>>> On Mon, Apr 27, 2020 at 10:00 AM Alvaro Miranda Aguilera <
>>> kiki...@gmail.com> wrote:
>>>
 so, make sure you can ping both IP from both host

 on machine1
 - ping local
 - ping remote

 on machine2
 - ping local
 - ping remote

 if one fails, then you should focus on that first.

 As you are using hyper-v, I can't help much, but basically you may want
 to see way to give to the VMs an IP from your network.

 Alvaro.

 On Fri, Apr 24, 2020 at 3:10 PM DC  wrote:

> I am using the latest vagrant version running on my windows 10
> professional x64. I configured my Network device to share the connection
> with my internal virtual switch (HyperV). Everything seams okay and I can
> bring up my VM without any issues. I am using the following box
> (generic/ubuntu1804).
>
> The problem that I have is that once that my host gets the assigned
> the admin role, after run "docker swarm init", I tried to add the
> Hypervisor as a Worker node and I seems like is docker can not see it :-/.
>
> *These are the steps that I followed:*
>
> # Bring up w1 (My vagrantfile will handle the provider,etc) IP =
> 192.163.135.199
> *vagrant up w1*
>
> # host machine
> *docker init swarm*
> *To add a worker to this swarm, run the following command:*
>
> *docker swarm join --token
> SWMTKN-1-36gi398mfzkq8q9f4qt6u5wll7xv88a4u0osv8rpofmmvknunn-91ogycjru6p29p44f7iam63il
>  *
> 192.163.135.197*:2377*
>
> *To add a manager to this swarm, run 'docker swarm join-token manager'
> and follow the instructions.*
>
> # Switch to Worker
> *$env:DOCKER_HOST="192.163.135.199"*
>
> # I verified that docker can see this node
>
> *docker info*
>
> # docker shows Name: w1 :-)
>
> # Join the current node as worker
> *docker swarm join --token
> SWMTKN-1-36gi398mfzkq8q9f4qt6u5wll7xv88a4u0osv8rpofmmvknunn-91ogycjru6p29p44f7iam63il
>  192.163.135.197:2377
> *
> *Error response from daemon: Timeout was reached before node joined.
> The attempt to join the swarm will continue in the background. Use the
> "docker info" command to see the current swarm status of your node.*
>
> *Troubleshooting:*
>
> I ping the VM and the host is able to see it, but if  *I try to ping
> the host from the VM, it failed* :-/. I am guessing that it has to do
> with the way that I configured the internal virtual switch :-/. Any
> recommendation?
>
>
> --
> 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/aa877eb8-2fd8-4e9c-b9ec-f3b586794631%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 

[vagrant-up] Re: NFS Sharing from host to Vagrant VM !!

[dragon788]

The issue is likely that NFS isn't installed inside the VM. You should read 
the documentation at vagrantup.com regarding the options for NFS or Rsync 
or "native" shared folders for Virtualbox or VMware (which require having 
some additional packages installed in the VM as well).

On Tuesday, May 5, 2020 at 9:24:07 AM UTC-5, Ibrahim Vanak wrote:
>
> The issue is, while running “vagrant up” I am trying to do NFS mount from 
> host to Vagrant VM. It’s failing to do so with the following error:
>
> ==> default: Mounting NFS shared folders...
>
> The following SSH command responded with a non-zero exit status.
>
> Vagrant assumes that this means the command failed!
>
>  
>
> mount -o vers=4 192.168.121.1:/root/hlinux-tools/netinst-iso /vagrant
>
>  
>
> Stdout from the command:
>
>  
>
>  
>
>  
>
> Stderr from the command:
>
>  
>
> mount.nfs: access denied by server while mounting 
> 192.168.121.1:/root/hlinux-tools/netinst-iso
>
>
> My host VM is unbuntu 18.04 and vagrant VM would be debian Jessie. 
>
>
> Snippet of NFS sharing code from Vagrant file:
>
>
> *  config.vm.synced_folder "./vagrantfolder", "/home/vagrant/output",*
>
> *nfs: true,*
>
> *linux__nfs_options: ['rw','no_subtree_check','all_squash','async']*
>
>  
>
> *  config.vm.synced_folder "./vagrantfolder/repo", 
> "/var/www/hLinuxArchive",*
>
> *nfs: true,*
>
> *linux__nfs_options: ['rw','no_subtree_check','all_squash','async']*
>

-- 
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/b51a181e-7610-466a-804f-5a95cc19a380%40googlegroups.com.