-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documention on Forwarding Ports is invalid #58
Comments
I am running into problems with blocked ports and SMB. I am not sure how/why SMB is turned on by default. cat << EOF > Vagrantfile
Vagrant.configure("2") do |config|
config.vm.box = "ppggff/centos-7-aarch64-2009-4K"
config.vm.network "forwarded_port", guest: 80, host: 8080
end
EOF
vagrant up --provider=qemu I also get an issue that port 8080 is already used when I use --debug. But
|
This seems to work using an alternative image. The the other issues with issue #40 have to deal with private networks and/or multi-machine? I have then some confusion between where this won't work, especially given the message (https://github.com/ppggff/vagrant-qemu/blob/master/locales/en.yml#L18-L21) that is splashed on vagrant up.
|
If there are scenarios where this should not be expected to work, it would be great to document that. If these are always expected to work, then maybe remove or modify the warning, as the setting was not ignored:
|
The warning comes from vagrant, I will investigate how to remove it or change it. |
The current documentation (README.md) indicates that this functionality currently works, but with Macbook M1 (ARM64) with hvf, this is not working:
Please document exactly where this will work and where it does not. If it doesn't work for any solution, including q35 emulators, then maybe document that it doesn't work? Also, if there is a workaround through the qemu tool, then could this workaround be documented?
The text was updated successfully, but these errors were encountered: