-
Notifications
You must be signed in to change notification settings - Fork 181
Cant boot VM (timeout) #246
Comments
Yeah, Vagrant times out because it tries to find out what's the container IP and since its network is not properly configured, it is not able to identify that the container is up. For 1.0, I'm planning to show a nice error message [GH-164] when the bridge can't be found, but as of now you'll need to manually create that bridge =/ Please have a look at the instructions for configuring the bridge on Debian hosts and LMK if that works out for you so we can update the wiki. Since there's nothing much we can do about this, I'm going to close the issue but I'm happy to continue the discussion and I'll still be notified ;-) |
I have created the lxcbr0 interface, but still dont work. Here is the interface defined in ifconfig:
my /etc/network/interfaces file
Do I need to configure anything in Vagrant file? |
Can u show us your |
I dont have any /etc/lxc/default.conf. I only have a /etc/lxc/lxc.conf. Here is the contents of lxc.conf:
|
Weird.... Maybe try to copy to that file to I'm planning to add some sort of networking sanity checks on the plugin with #164, so hopefully on the future people will start seeing a nice looking error message at least :P |
Hello.
I have installed vagrant-lxc plugin today and I am trying to start my first VM.
I am getting the following error:
Here is my Vagrantfile:
My system specs
Elementary OS Luna (based on ubuntu 12.04) with Kernel 3.2.60,
Vagrant 1.4.3
lxc version: 0.7.5
vagrant plugin version: 0.8.0
Not sure if its related to the problem but if I do ifconfig I dont have any lxcbr0 interface.
Any help?
The text was updated successfully, but these errors were encountered: