I was experiencing some difficulty with OpenVZ containers starting properly using venet configuration. After creating a new container using a template and assigning an IP through the web interface I would attempt to start the container and received the following error:
vps-net_add ERROR: Unable to get source ip
After some digging the problem became quite obvious. I ran ifconfig to list the network devices on the host machine. I noted that "vmbr0" was named instead of "eth0" to my ethernet device. I then looked at the OpenVZ config /etc/vz/vz.conf and changed VE_ROUTE_SRC_DEV from "eth0" to "vmbr0". This resolved my issue with the OpenVZ containers not starting properly.
I'm going to assume that this issue might be specific to my machine due to the lack of posts on this specific issue.
I'm currently testing ProxmoxVE 1.1 on a Dell Optiplex 740. I figured I would go ahead and post my fix just in case anyone else experienced difficulties setting up OpenVZ containers.
vps-net_add ERROR: Unable to get source ip
After some digging the problem became quite obvious. I ran ifconfig to list the network devices on the host machine. I noted that "vmbr0" was named instead of "eth0" to my ethernet device. I then looked at the OpenVZ config /etc/vz/vz.conf and changed VE_ROUTE_SRC_DEV from "eth0" to "vmbr0". This resolved my issue with the OpenVZ containers not starting properly.
I'm going to assume that this issue might be specific to my machine due to the lack of posts on this specific issue.
I'm currently testing ProxmoxVE 1.1 on a Dell Optiplex 740. I figured I would go ahead and post my fix just in case anyone else experienced difficulties setting up OpenVZ containers.
Last edited: