Re: [vagrant-up] Post Collision on 2222 with Vagrant Up

Hi there, Is port in use by some other process? Are there any entries listed in the settings file? This is located at /opt/vagrant-vmware-desktop/settings/nat.json. If so, remove them (or just delete the file and let it be recreated) and restart the vagrant-vmware-utility with launchctl.

Re: [vagrant-up] how to disable automatic box update

Hi there, Are you setting a box_version in your Vagrantfile? If not, Vagrant will use the latest downloaded version of that box. For example, this will give you a CentOS 7.5 VM: Vagrant.configure("2") do |config| config.vm.box = "centos/7" config.vm.box_version = "1809.01" end If that

Re: [vagrant-up] Re: how to disable automatic box update

Hi Yusef, Thanks for the additional information. The update is coming from the vagrant-vbguest plugin, which runs a system update so that it can compile the kernel extension for the VirtualBox guest additions. That `yum update` will update the `centos-release` package from 7.5 to 7.8. If you

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

Hi Adrian, Thanks for the detailed report (nice system btw!). I'd recommend running Vagrant with the debug flag, like `vagrant ssh --debug`. That will show a detailed log of all the commands Vagrant is running. It could be that something like a PowerShell script or some other host introspection

Re: [vagrant-up] Isolated hostonly networks on the same host - Virtualbox provider

Hey Erik, Ah, I see, thanks for the additional details. I'm not super familiar with HAProxy, but here are a couple of ideas: 1.) Add port forwards for each service, and configure HAProxy point to the forwarded port. For example, you could add: vm2.vm.network "forwarded_port", guest: 8080,

Re: [vagrant-up] Isolated hostonly networks on the same host - Virtualbox provider

Hi there, If you're using VirtualBox, you can further isolate your VMs by using Internal Networking. For example: Vagrant.configure("2") do |config| config.vm.box = "hashicorp/bionic64" config.vm.define "vm1" do |vm1| vm1.vm.network "private_network", ip: "192.168.0.2",

Re: [vagrant-up] Vagrant complains about libvirt missing when I explicity ask it to use Virtualbox

Hi there, You can run `vagrant up --provider virtualbox` to tell Vagrant to use VirtualBox for the current environment. You can also set the environment variable `VAGRANT_DEFAULT_PROVIDER=virtualbox` if you want Vagrabt to use VirtualBox for all your VMs. Hope this helps! Cheers, Jeff On Sun,

Re: [vagrant-up] Vagrant user's pub ssh key location?

Hi there, Vagrant boxes are usually packaged with a default "insecure" keypair ( https://github.com/hashicorp/vagrant/tree/master/keys) so that Vagrant can SSH in on first boot. Vagrant will then generate a unique keypair and replace the public key in authorized_keys. Hope this helps! Jeff On

Re: [vagrant-up] Vagrant/VirtualBox no longer connects or halts machines

Hi there, Are the timeouts happening with all VMs, or just those based on the ubuntu/focal64 box? There's a reported issue in the cloud-images project that sounds similar to what you're experiencing: https://bugs.launchpad.net/cloud-images/+bug/1829625 As a workaround, you can add the following

Re: [vagrant-up] osx host cannot communicate with vagrant VMs

Hi there, Can you ssh into the VM using the host-only address (ssh vagrant@192.168.60.4)? Thanks, Jeff On Mon, Jul 20, 2020 at 8:14 AM Tony Wong wrote: > I setup 3 vms with vagrant. they are up and running on vbox and I can do > vagrant ssh to them > > but from my osx host, I am not able to

Re: [vagrant-up] Chaning VM ssh name

Hi there, Unfortunately it isn't possible to rename a running VM. I'd recommend destroying the machines with the old names, renaming the machines in your Vagrantfile, and then bringing up new machines with the new names. Cheers, Jeff On Thu, Jul 2, 2020 at 10:04 AM Makrand wrote: > Hi All, >