Actually.... It just decided to move to a different. My
generic/oraclelinux7 vm is now doing the exact same thing as the centos7 vm
did.
Any idea what port I can use with localhost? `vagrant port` doesn't work.
The libvirt provider does not support listing forwarded ports. This is
most likely a limitation of the provider and not a bug in Vagrant. If you
believe this is a bug in Vagrant, please search existing issues before
opening a new one.
Scrolling up to the provisioning output doesn't offer any clues to the
localhost port. Just a second 192.168.n.n ip.
==> oraclelinux7: Configuring and enabling network interfaces...
oraclelinux7: SSH address: 192.168.121.82:22
oraclelinux7: SSH username: vagrant
Thanks.
- David
On Tuesday, August 6, 2019 at 11:40:26 AM UTC-7, David Reagan wrote:
>
> Thanks for the response.
>
> Annoyingly, the issue has cleared up since yesterday. I guess a reboot of
> the host did the trick. Sheesh.
>
> - David
>
> On Tuesday, August 6, 2019 at 12:02:13 AM UTC-7, Dennis Chang wrote:
>>
>> The VM is accessible via a specific port on address 127.0.0.1
>> (localhost). Try adding the port and use localhost instead and see if that
>> works.
>>
>> Dennis
>>
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/c8120ead-4db2-4699-ab6d-58684ce2ae78%40googlegroups.com.
