-
Notifications
You must be signed in to change notification settings - Fork 60
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
Support for bridged networking #181
Comments
I'm working to improve network in my development fork. https://github.com/miurahr/vagrant-kvm This branch is for v0.2.0 development. It works
Known issues and limitations
I'd like to listen your opinion how bridged network support working. In ubuntu, there is OS default bridged network for libvirt/qemu. IMHO, next branch is good start point to support bridged network. |
I'll definitely test your branch as soon as I get a chance. Looking at the source code, it does look like this won't support booting multiple VMs from different Vagrantfile. This is how I currently use vagrant-kvm, so this support for this would need to be added before I can fully use it. On my side, I'll play around with using the default bridge on ubuntu. Expect a PR soon :) |
Now multiple VM are supported on current master. a9368ef |
Here is experimental patch |
Do we really want this? Isn't the default practice with vagrant to use port redirections for that? |
It is for supporting public networks. The document said that a key |
OK, I'll test it then |
Is this still being worked on? |
Sorry, chances are it won't happen, see #276 |
As far as I can tell, currently this only supports NAT networking. The main issue with it, is that there's no way to connect to the guest from the host.
Simple things like
do not work.
It would be good if this supported bridged networking, which is more versatile, but is harder to configure.
The text was updated successfully, but these errors were encountered: