• OS: Fedora
• vagrant version: 2.2.6
• vagrant-libvirt (0.0.45, system)

Actual results

The content of the output indicates that the tool is not aware of the input command, as illustrated:

• it suggests to run that last, vagrant global-status --prune.
• statement "_The above shows information about all known Vagrant environments on this machine.. This data is cached and may not be com

Sometimes when provisioning, apt fails to retrieve packages due to network issues. This seems to have happened in #1991 but if there had been a backup to fall back to this might have been avoided.

For MariaDB at least we can add mirrors, and there are quite a few to choose from listed here:

https://downloads.mariadb.org/mariadb/repositories/#mirror=digitalocean-ams

We might be able to m

Hello,

with yum info audit I can confirm that the package audit is installed.
with rpm -ql audit I can see a list of files, including /usr/share/doc/audit-2.3.7/*
But those files are missing
ls: cannot access /usr/share/doc/audit-2.3.7: No such file or directory

CentOS 6.7
Can you help with that?
Thanks.

I'm using vagrant 2.2.6 in a WSL (Windows Services for Linux) Ubuntu environment installed on Windows 10.

Please update the book example of the Vagrantfile on page 241 of the pdf to reflect github:

4 Vagrant.configure(2) do |config|
5 config.vm.box = "geerlingguy/ubuntu1804"
6 config.ssh.insert_key = false

and append a line which is common to your other Vagrantfiles to the Vagrant.

• I've read the guidelines for Contributing to Roots Projects
• This request isn't a duplicate of an existing request
• This is not a personal support request that should be posted on the Roots Discourse community

Feature request

When re-provisioning a server with a users tag `trelli

Hi All,

I like to use Ansible AWX for my Automation project instead of Ansible Tower
I have working on to install AWX Vagrant VM using this geerlingguy AWX example.
When I run vagrant up, I am getting below error,

task path: /home/user/dhanasekar/Automation/awx/roles/geerlingguy.awx/tasks/awx-install-playbook.yml:2
fatal: [awx]: FAILED! => {"changed": true, "cmd": ["ansible-pla

Tutorial assumes Europe. (https://github.com/Artemmkin/infrastructure-as-code-tutorial/blob/master/docs/01-prerequisites.md)

Set a default compute region:
$ gcloud config set compute/region europe-west1
Set a default compute zone:
$ gcloud config set compute/zone europe-west1-b

Recommend pointing student to https://cloud.google.com/compute/docs/regions-zones

Is anyone following "Development" instructions getting anything other than lots of failed tests?

My result: 25 examples, 23 failures — and time waste, of course.

If the tests are actually broken why Docs don't say a thing to reflect this?

Also it's not documented whether all the "[Installation](https://github.com/vagr

环境：

• Mac
• vagrant 2.1.2
• virtualBox: 5.2.16
• Kubernetes 1.11.0

遇到了几个问题：

1. 在系统自动挂起之后vm 的时间会不对，没有自动同步，导致 Prometheus 监控数据显示不出来，应该同步时间就可以，不过我没有，而是使用的 vagrant halt ，就导致了另一个问题。
2. 执行 vagrant halt 按照【重启】 的操作后，之前配置的 Istio 相关所有东西都不见了，包括 istio-system namespace 。
3. 按照[文档](

Issue Type

• Feature Idea

Summary

I would like to use GoAccess as a dev tool instead of PimpMyLog. How can I go about setting it up automatically when I create a new VM?

Of the learning environments that leverage Ansible, very few are using roles. This can make porting Ansible playbooks across learning environments more difficult. To fix this, Ansible-using learning environments need to be refactored (where possible) to use an Ansible role.

When using the box built with osx-vm-templates, there is always some setting to tune in upper Vagrantfile.

Can we built those common settings into box with vagrantfile_template

There is a good [reference here](https://github.com/blueimp/boot2docker/blob/b33c71d07f2cfdc94e6f9150793bbb47a78f6b70/packer.jso

following the instructions at http://vccw.cc/#h2-2, i get the following message at the "vagrant box add" step:

$ vagrant box add vccw-team/xenial64 --name=vccw-team/xenial64

The box 'vccw-team/xenial64' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Atlas, please verify you're logged in via
`vagrant login`. Also, please doub

Some old programs versions can be found here if someone needs them to test old exploits for instance.

The documentation should mentioned and explain the use of the various backing files in the Vagrant data directory.

On Windows, you can hit some really obscure issues when starting (h/t @missjwo), e.g. failed to create symbolic link

These are due to symlinks requiring admin on Windows. The solution is to open your console as an admin in the first place: hashicorp/vagrant#6024 (comment)

Alternatively, you can create local security policies: https://github.com/hashic

In addition to CPU and memory, it would be useful to be able to specify the amount of VRAM, since the default value (at least for Parallels) is quite low.

It should be fairly straightforward to implement, again, for Parallels it would be:

prl.customize ["set", :id, "--videosize", "256"]

This would set VRAM to 256 MB.