Support for bridged networking

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

ping <the guest ip>

do not work.

It would be good if this supported bridged networking, which is more versatile, but is harder to configure.

I'm working to improve network in my development fork.

https://github.com/miurahr/vagrant-kvm in next branch.

This branch is for v0.2.0 development. Can you test it?

It works

1. Multiple vm definition in single Vagrant file
2. Multiple Vagrantfile in different project shares same subnet in default network and private network
3. No private network definition in Vagrantfile. It use 192.168.123.x as default network and select address automatically. This is as same behavior as VirtualBox driver does.

Known issues and limitations

1. Cannot detect and escape IP address collision in private network. This happens when user use same Vagrantfile with private network defition in multiple project
2. Not tested 1.5.x yet. tested on Vagrant 1.4.3.
3. Not tested bridged network.
4. Libvirt need to be fixed to support 9p file share. You may need to turn off selinux enforcement.

I'd like to listen your opinion how bridged network support working.

In ubuntu, there is OS default bridged network for libvirt/qemu. It is defined in /etc/libvirt/qemu/network/bridged.xml and autostart when system started. It is better to handle this default bridged network, 192.168.122.0/24. To realize it, vagrant-kvm should handle network update with libvirt (required libvirt 0.5.2.)

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. a9368ef7553a68b7d2a23dffba3c63f0b954ea15 It may be a chance to test now.

Here is experimental patch https://github.com/miurahr/vagrant-kvm/commit/c8f0673632325213d8368b00a7a5533e6ef9d3d2

Do we really want this? Isn't the default practice with vagrant to use port redirections for that?

It is for supporting public networks. http://docs.vagrantup.com/v2/networking/public_network.html

The document said that a key public_network will be changed bridged in future.

OK, I'll test it then

Is this still being worked on?

Sorry, chances are it won't happen, see #276