Alex Drahon

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

OK, I'll test it then

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

Would be great to have a pull request for this.

We have an open issue for this #181 I just pushed some changes to the networking code, I'm going to start working on bridge network next.

It would be cool if you tried implementing support for that. You could look at the implementation of another option in the domain definition like https://github.com/adrahon/vagrant-kvm/commit/5b8de4f359330587539fd648cd0a770c42cab820#diff-a592055369fbc5b7f1427ad7ffa622ab

Wow, that was fast, thanks! I'll have a look asap.

I was thinking the same, but part of the problem is we have both driver.rb and things in util/ like vm_definition.rb. I'm not sure what's the right way to factor...

There were regressions with the changes we introduced to the networking code recently. Prior to https://github.com/adrahon/vagrant-kvm/commit/fea85417f11260728f465fb46def1b164b35119a the dhcp entries weren't cleaned up on `vagrant destroy`. Best would be to build...

There's no consideration for non-x86 vms at the moment, but it shouldn't be too hard to implement as an option. Do you have a working VM we could use to...