Fails to bring up new machine after updating to 0.1.9 about vagrant-kvm HOT 2 OPEN

There were regressions with the changes we introduced to the networking code recently. Prior to fea8541 the dhcp entries weren't cleaned up on vagrant destroy. Best would be to build the rubygem from source, but I am going to publish 0.2.0 as soon as I implement bridge network support.

One way to clean up you networks in the meantime is to do a virsh net-destroy vagrant && virsh net-undefine vagrant (also for any vagrant-xxx network, you can list them with virsh net-list), you need to be root to do that.

from vagrant-kvm.

I tried net-destroy and net-undefine yesterday as well on all vagrant related networks but no success. I'll wait until 0.2.0 is released but untill then I'll keep my systems on 0.1.8. Thanks for the quick response, I appreciate it.

On 12 Oct 2014, at 12:08, Alexandre Drahon [email protected] wrote:

There were regressions with the changes we introduced to the networking code recently. Prior to fea8541 the dhcp entries weren't cleaned up on vagrant destroy. Best would be to build the rubygem from source, but I am going to publish 0.2.0 as soon as I implement bridge network support.

One way to clean up you networks in the meantime is to do a virsh net-destroy vagrant && virsh net-undefine vagrant (also for any vagrant-xxx network, you can list them with virsh net-list), you need to be root to do that.

—
Reply to this email directly or view it on GitHub.

from vagrant-kvm.