Gerben Meijer
                                            Gerben Meijer
                                        
                                    There is code that updates the vm definition on a `vagrant up` but it does not cover everything. See https://github.com/vagrant-libvirt/vagrant-libvirt/blob/master/lib/vagrant-libvirt/action/start_domain.rb#L35 A PR with support for more will probably get merged...
I could not reproduce this issue on a clean install of Fedora 23. Please try upstream vagrant.
This isn't making much sense. ``` DEBUG create_networks: Searching for network with options {:iface_type=>:private_network, :netmask=>"255.255.255.0", :dhcp_enabled=>true, :forward_mode=>"nat", :type=>"dhcp", :protocol=>"tcp", :id=>"14d1feba-b035-461e-ab95-b6563b47490f", :network_name=>"vagrant-private-dhcp"} ... DEBUG create_network_interfaces: In config found network type private_network...
Here's what happens on my clean fedora 23 test box: ``` DEBUG create_networks: In config found network type private_network options {:type=>"dhcp", :protocol=>"tcp", :id=>"7c8cf156-ee65-430b-98a7-e3877f278cff"} DEBUG create_networks: Searching for network with options...
Can you also try with a different name for your private network? e.g. both name and range: ``` ruby ... v.vm.network :private_network, :type => "dhcp", :libvirt__network_name => 'foo-network', :ip =>...
So the issue must live somewhere in `action/create_networks.rb`: ``` ruby def handle_dhcp_private_network(env) net_address = '172.28.128.0' network = lookup_network_by_ip(net_address) #
OK, I think the real issue here is that it found a network matching your specification but it is then not using that networks name in `create_network_interfaces`. Definitely a bug...
So I'm trying to understand this question, because I'm not directly able to reproduce the issue. I don't think `owner` option that is mentioned here works as you expect it...
If nothing else, the bug here is that the 9p `owner` option should be renamed to `access` so that it accurately reflects what it does in the guest. @pronix not...
I'm flagging this as an enhancement only and by that I mean that the documentation should be updated to better inform the user. I do not see any bugs here...