Bridged Interface not showing up in CT

[JS2013]

Hello,

I have created a bridged interface for my CT (via the proxmox web UI), but that interface does not show up when I start my CT.
I have tried with CentOS 5,6 (x86 and x64), and also with Debian 7, but with no luck.

I see the following message:

Setting CPU units: 1000
Setting CPUs: 1
Configure veth devices: veth101.0
Adding interface veth101.0 to bridge vmbr0 on CT0 for CT101
Container start in progress...

But when I use "vzctl enter 101", and run "ifconfig", I do not see the eth0 interface inside the CT (whereas the veth101.0 interface is properly created on the host).

Here are the logs from /var/log/messages

Nov 24 08:01:30 sd-32691 kernel: CT: 101: started
Nov 24 08:01:31 sd-32691 kernel: device veth101.0 entered promiscuous mode
Nov 24 08:01:31 sd-32691 kernel: vmbr0: port 3(veth101.0) entering forwarding state

and output for pveversion -v

proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve)
pve-manager: 3.1-21 (running version: 3.1-21/93bf03d4)
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-8
qemu-server: 3.1-8
pve-firmware: 1.0-23
libpve-common-perl: 3.0-8
libpve-access-control: 3.0-7
libpve-storage-perl: 3.0-17
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-4
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.1-1

I have been banging my head with this for the whole day, so really any help would be greatly appreciated!

Thank you

 

[pirateghost]

When using a bridge with a container you need to go into the container and configure the network device. In Debian that would be in /etc/network/interfaces. Either create a eth0 as static or dhcp

Sent from my Nexus 5

 

[JS2013]

When using a bridge with a container you need to go into the container and configure the network device. In Debian that would be in /etc/network/interfaces. Either create a eth0 as static or dhcp

Thank you for the fast reply!!

I thought that OpenVZ would set up the interface automatically (like it does for venet). I guess I was wrong, and now I feel so stupid for thinking so

Are there any specific configurations that I need to write down, or is it just similar to adding any other network interface?

 

[mir]

It is done exactly the same way as you would handle it with a physical host.