-
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
Exception on virbr collision #16
Comments
You're right that we need more error checking (and testing to). Thanks for the bug reports, I'll clean that up. |
As an user, it may be better to re-use existing virbrN for creating new virtual network if it is in same subnet. |
I'm working for it now, as one of task to support multi-vm configuration. |
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. |
#47 may fix this. Hope test on your environment. (warn: need ruby-libvirt 0.5.0 that have not released yet) |
Yes, that's why we need ruby-libvirt 0.5.0 that support 'Update' of existing network that have same address range. |
Hello @miurahr! |
#111 is marked to merge in 0.1.6. |
Now fix is marged on master. |
Hi,
ran into this while trying out git master. I had a preexisting
network setup in virt-manager, and this was what I got.
Would be nice to have a better error message.
The text was updated successfully, but these errors were encountered: