You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please note that the Vagrant issue tracker is reserved for bug reports and
enhancements. For general usage questions, please use the Vagrant mailing list: https://groups.google.com/forum/#!forum/vagrant-up. Thank you!
Vagrant version
Vagrant 1.9.1
Host operating system
macOS 10.12.3
virtual box version
Version 5.1.14 r112924 (Qt5.6.2)
Guest operating system
RHEL
uname -a
Linux nettest.test.local 3.10.0-514.2.2.el7.x86_64 #1 SMP Wed Nov 16 13:15:13 EST 2016 x86_64 x86_64 x86_64 GNU/Linux
Vagrantfile
# -*- mode: ruby -*-# vi: set ft=ruby :# All Vagrant configuration is done below. The "2" in Vagrant.configure# configures the configuration version (we support older styles for# backwards compatibility). Please don't change it unless you know what# you're doing.Vagrant.configure("2")do |config|
# The most common configuration options are documented and commented below.# For a complete reference, please see the online documentation at# https://docs.vagrantup.com.# Every Vagrant development environment requires a box. You can search for# boxes at https://atlas.hashicorp.com/search.config.vm.box="bigfix/redhat72x64-db2"config.vbguest.auto_update=falseconfig.vm.hostname="nettest.test.local"# Create a forwarded port mapping which allows access to a specific port# within the machine from a port on the host machine. In the example below,# accessing "localhost:8080" will access port 80 on the guest machine.config.vm.network:forwarded_port,guest: 80,host: 8080config.vm.network:forwarded_port,guest: 443,host: 9443config.vm.network:forwarded_port,guest: 8083,host: 8083config.vm.network"private_network",ip: "10.10.1.12",auto_correct: trueconfig.vm.provider"virtualbox"do |vb|
vb.gui="false"vb.memory=4096vb.cpus=2vb.customize["modifyvm",:id,"--natdnshostresolver1","on"]endend
Debug output
Provide a link to a GitHub Gist containing the complete debug output: https://www.vagrantup.com/docs/other/debugging.html. The debug output should
be very long. Do NOT paste the debug output in the issue, just paste the
link to the Gist.
As @d-lorenzo pointed out, this issue is fixed in 1.9.2 so I'm going to close this issue. If you are still experiencing problems after upgrading, please either reopen this issue, or create a new one. Thanks for the report!
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 2, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Please note that the Vagrant issue tracker is reserved for bug reports and
enhancements. For general usage questions, please use the Vagrant mailing list:
https://groups.google.com/forum/#!forum/vagrant-up. Thank you!
Vagrant version
Vagrant 1.9.1
Host operating system
macOS 10.12.3
virtual box version
Version 5.1.14 r112924 (Qt5.6.2)
Guest operating system
RHEL
Vagrantfile
Debug output
Provide a link to a GitHub Gist containing the complete debug output:
https://www.vagrantup.com/docs/other/debugging.html. The debug output should
be very long. Do NOT paste the debug output in the issue, just paste the
link to the Gist.
Expected behavior
vm should have ip of 10.10.1.12
Actual behavior
vm doesn't have this ip.
Steps to reproduce
The text was updated successfully, but these errors were encountered: