Ladar Levison

@murphye if I were to guess, that error is telling you that libvirt is looking for the network interface you specificed, aka `virbr1` but it can't be found, or created....

P.S. If you do have a default network, aka `virbr0` interface already, perhaps specifying it explicitly in your Vagrantfile will side step this issue.

@murphye that error implies it had trouble connecting to the libvirt system daemon, and it's suggesting you use a local libvirt session. Not sure how, or why a network config...

@electrofelix this is an old thread, so I won't dive deep. Just let me know if there are any changes (hopefully trivial) that need to be made to the robox...

@electrofelix you'll find there are a lot small, but critical differences with MacOS. It's based off BSD, so many of the tools, commands, and APIs are very different from what...

@electrofelix like I said, if you're interested in getting it vagrant+libvirt working on Macs, I don't mind setting up access to the MacBook Air I mentioned. I can set you...

@electrofelix regarding the network/storage volume setup for user session virtual machines... I think outputting a warning is probably what's important. Arguably, you could ask for permission with a y/n prompt...

It looks like an issue with the zlib build function. Can you upload the log output from: ```res/scripts/build.dimedeps.sh zlib-log``` That same script has functions for building each dependency and those...

Let me know if I can help with this.

I got tired of waiting for the developers to fix this bug. And having to figure out the solution everytime I install atom on a RHEL/CentOS 7 system. So I...