[vagrant-up] Re: Vagrant keeping my disks awake
It is late and I am tired. Sorry for not putting this first: - Operating system is Windows 10 - I install vagrant 2.2.7 using Chocolatey (including the vmware utils) - VMware Workstation 15.5 latest (also via Chocolatey) - I use the paid provider for VMware vagrant_desktop Version 2.0.3 All of this works like a charme, minus the sleep-deprevation for my HDDs. What can I do about 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/258f17cf-8130-47dd-a0c9-a5a837eac4ae%40googlegroups.com.
[vagrant-up] Vagrant keeping my disks awake
I assembled a nice machine for use with Vagrant Threadripper 12c, 128GB RAM, 4 NVMe, some SATA SSD and ... two classic magnetic disks The idea is that the work happens on the NVMe SSDs, Storage is on SATA SSDs and Archive/Backup is on the magnetic disks. I believe this kind of makes sense ;-). In normal operation the archive disks (magnetic) are assume to power down and stay this way until the get explicitely accessed. So far for the theory. Vagrant shows a behaviour that strikes me, though: My archive disks go to sleep and power off after a while, that is they stop the spindles. Good! The moment I run the next vagrant command, e.g. a vagrant ssh on one of the disks, the vagrant command blocks, I hear the HDDs (both) starting the spindles and once they (acoustically) appear started, I see the vagrant command continuing its mission. This is ... confusing and annoying. It appears to me as if vagrant is checking the drives for some content or config before doing anything. Once the HDDs are active, there is no mentionable delay with vagrant anymore, but it insist on starting the drives before doing anything. Could anybody please tell me, what activity makes Vagrant talk to my HDDs and possibly how I could avoid this. Unless I can do something about it, my only way to get rid of this misbehaviour would be: 1. unmount the drives when not needed (not a bad idea, pretty much emotet-safe). 2. mount the drives to a directory rather than a drive-letter (untested) 3. configure the drives to not go to power-safe (by noise and ecology not my first choice) I really hope for a suggestions that looks better that this! Help? Thanks in advance! Adrian -- 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/b1cb9203-734e-4a95-b552-ca31f0401e94%40googlegroups.com.
[vagrant-up] Re: Specifying ansible start-at-task when running vagrant provision
Of course, soon after I post the question I find the solution: ansible.start_at_task = ENV['START_AT_TASK'] https://www.vagrantup.com/docs/provisioning/ansible_common.html On Sunday, May 3, 2020 at 10:13:04 AM UTC-4, Pavel Chernikov wrote: > > How can ansible --start-at-task be specified when running "vagrant > provision"? > > Is there a way to do this via an environment variable or vagrant > command-line switch? > -- 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/0d7ff12c-193c-4c24-ab0d-17fd0af83e90%40googlegroups.com.
[vagrant-up] Specifying ansible start-at-task when running vagrant provision
How can ansible --start-at-task be specified when running "vagrant provision"? Is there a way to do this via an environment variable or vagrant command-line switch? -- 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/71a07906-9b52-4081-a783-5718a647a468%40googlegroups.com.
