vz.conf bug?

SCR512

New Member
Jan 19, 2009
7
0
1
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.
 
Last edited:
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.

On a standard installation of Proxmox VE, VE_ROUTE_SRC_DEV is not set in etc/vz/vz.conf. so how do you installed?
 
This installation was installed with the 1.0 CD installer.

Only changes made were just running "apt-get update" and "apt-get upgrade" in order to get the installation up to date.
 
Whats the output of

# pveversion -v

and please can you post the contents of file "/etc/network/interfaces"
 
pveversion -v
Code:
pve-manager: 1.1-1 (pve-manager/1.1/3664)
qemu-server: 1.0-7
pve-kernel: 2.6.24-4
pve-kvm: 83-1
pve-firmware: 1
vncterm: 0.9-1
vzctl: 3.0.23-1pve1
vzdump: 1.1-1
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1dso1
/etc/network/interfaces
Code:
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
        address 10.1.3.96
        netmask 255.255.0.0
        gateway 10.1.1.1
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0
 
A proxmox ve standard install has VE_ROUTE_SRC_DEV disabled:

Code:
#VE_ROUTE_SRC_DEV="eth0"

what does your vz.conf contain now?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!