problem proxmox:S

M

mcxxxx

New Member
Mar 4, 2010
7
0
1
/usr/sbin/vzctl start 101
Starting container ...
Container is mounted
Adding IP address(es):
Setting CPU units: 1000
Setting CPUs: 16
Configure meminfo: 2097152
Set hostname: server.sahhosting.com
File resolv.conf was modified
Setting quota ugidlimit: 0
Configure veth devices: veth101.0
Adding interface veth101.0 to bridge vmbr0 on CT0 for CT101
/usr/sbin/vznetaddbr: line 34: /proc/sys/net/ipv4/conf/veth101.0/proxy_arp: No such file or directory
/usr/sbin/vznetaddbr: line 35: /proc/sys/net/ipv4/conf/veth101.0/forwarding: No such file or directory
Container start in progress...
VM 101 started

How can I fix this error :(
/usr/sbin/vznetaddbr: line 34: /proc/sys/net/ipv4/conf/veth101.0/proxy_arp: No such file or directory
/usr/sbin/vznetaddbr: line 35: /proc/sys/net/ipv4/conf/veth101.0/forwarding: No such file or directory
 
Hello, I have the same error. It started when I changed the network config to this [I changed to this type of network in order to use 2 networks in the container].

NETIF="ifname=eth0,bridge=vmbr0,mac=00:00:00:01:01:00,host_ifname=veth101.0,host_mac=00:01:00:01:01:00;ifname=eth1,bridge=vmbr1,mac=00:00:00:01:01:01,host_ifname=veth101.1,host_mac=00:01:00:01:01:01"

pveversion -v
pve-manager: 1.5-8 (pve-manager/1.5/4674)
running kernel: 2.6.18-2-pve
proxmox-ve-2.6.18: 1.5-5
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-10
vncterm: 0.9-2
vzctl: 3.0.23-1pve8
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-5

The container seems to work fine

here is the output at start:
root@proxmox1: ~ # vzctl start 101
Starting container ...
Container is mounted
Adding IP address(es):
Setting CPU units: 1000
Setting CPUs: 1
Configure meminfo: 262144
Set hostname: localhost.fantinibakery.com
File resolv.conf was modified
Setting quota ugidlimit: 0
Configure veth devices: veth101.0 veth101.1
Adding interface veth101.0 to bridge vmbr0 on CT0 for CT101
/usr/sbin/vznetaddbr: line 34: /proc/sys/net/ipv4/conf/veth101.0/proxy_arp: No such file or directory
/usr/sbin/vznetaddbr: line 35: /proc/sys/net/ipv4/conf/veth101.0/forwarding: No such file or directory
Adding interface veth101.1 to bridge vmbr1 on CT0 for CT101
/usr/sbin/vznetaddbr: line 34: /proc/sys/net/ipv4/conf/veth101.1/proxy_arp: No such file or directory
/usr/sbin/vznetaddbr: line 35: /proc/sys/net/ipv4/conf/veth101.1/forwarding: No such file or directory
Container start in progress...


if there is anything I can do to help test a fix , or you need more info, just let me know.
 
Last edited:
Hello,

i have the same problem and would know if someone has fixed this?

It seems that the interface is not correctly created for ipv4 but for ipv6 it is correct.
Code: 
vm02:~# cat /proc/sys/net/ipv6/conf/
all/       default/   eth0/      lo/        veth103.0/ vmbr0/

Code: 
vm02:~# cat /proc/sys/net/ipv4/conf/
all/     default/ eth0/    lo/      venet0/  vmbr0/
 
Last edited:
The container ist running ok, but i have sporadically problems with the network (veth).

From an nagios monitoring System i´m pinging the Container every 1 minute. Sporadically the pings are lost 100% for 5-10 minutes and this happens only on the one Container with veth Interface. All other Container with venet Interface works ok.

Perhaps these Problems are coming from the missing proxy_arp and forwarding parameter for that Interface. So i ask if these has somenone fixed.
 
Hello:

I had proxmox 1.5 installed from the iso available on the web page.
I tried to upgrade using proxmox-ve-2.6.32 but then nothing worked. The CT wouldn't start at all.
I finally upgraded to proxmox-ve-2.6.24 and now everything seems to work fine.
Thank you
 
I am using open-vz containers. I haven't tried kvm containers. In fact, maybe my cpu does not support kvm as I get a message saying "This CPU does not support KVM virtual machines"
 
I have the same problem when I downgraded to 2.6.18 kernel from 2.6.32 kernel
On 2.6.18 VETH is not created for IPV4 but IPV6 is created but on 2.6.32 no problem at all, VETH is created on both IPV4 and IPV6.

I'm running OpenVZ before so I look at my documentation.
On my reference on adding the VETH interface I use, "ifconfig $host_ifname 0"
So I tried to comment the "ip link set dev "$host_ifname" up" and add the "ifconfig $host_ifname 0".
Then I restarted the VE and the error is gone and the VETH is created on both IPV4 and IPV6.

I'm not sure if this is a fixed but the VE is running without any problems as of now.

Here is my PVE.

proxmox:~# pveversion -v
pve-manager: 1.8-15 (pve-manager/1.8/5754)
running kernel: 2.6.18-5-pve
proxmox-ve-2.6.18: 1.8-14
pve-kernel-2.6.32-4-pve: 2.6.32-32
pve-kernel-2.6.18-5-pve: 2.6.18-14
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-16
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-11
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-14
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back