Exception on virbr collision about vagrant-kvm HOT 10 CLOSED

You're right that we need more error checking (and testing to). Thanks for the bug reports, I'll clean that up.

from vagrant-kvm.

As an user, it may be better to re-use existing virbrN for creating new virtual network if it is in same subnet.

from vagrant-kvm.

I'm working for it now, as one of task to support multi-vm configuration.

from vagrant-kvm.

I need to test, but I think this happens when the plugin tries to re-create the "vagrant" network in the same address range as an existing libvirt network.

from vagrant-kvm.

#47 may fix this. Hope test on your environment. (warn: need ruby-libvirt 0.5.0 that have not released yet)

from vagrant-kvm.

 >I think this happens when the plugin tries to re-create the "vagrant" network in the same address range as an existing libvirt network.

Yes, that's why we need ruby-libvirt 0.5.0 that support 'Update' of existing network that have same address range.

from vagrant-kvm.

Hello @miurahr!
ruby-libvirt 0.5.2 is coming out. Need to update dependency in gemspec?

from vagrant-kvm.

#111 is marked to merge in 0.1.6.
We are working for 0.1.5 now.

from vagrant-kvm.

#111 is merged to master.
@eagleas @y-p could you test it?

There is #184 for multi-vm multi-network. Also you can test.

from vagrant-kvm.

Now fix is marged on master.

from vagrant-kvm.