I noticed that in http://bugzilla.openvz.org/show_bug.cgi?id=2133 someone did have an issue with ping -R no longer working (but yes, at least no oops any more) is there anything to be done to get a kernel that allows ping -R?
New 2.6.32 Kernel for 1.9
- Thread starter martin
- Start date
With the pve 7 Kernel the Bug with ping -R is fixed but i´ve got another issue with Network Delays up to 30 seconds and a lot of messages in dmesg
"vmbr0: port 2(tap102i0d0) entering disabled state"
Please delete. Problem was same mac adresses
"vmbr0: port 2(tap102i0d0) entering disabled state"
Please delete. Problem was same mac adresses
Last edited:
L
lastguru
Guest
Yes, but you can not configure it from the web interface. Given that for the new kernels (use this ONLY if you have 2.6.32-55 kernel, maybe -54 also works, but I am not sure; however there are VERY important stability fixes released as -55, so please upgrade!!!) it is sufficient to specify only RAM and vSwap amounts (read http://openvz.livejournal.com/39644.html, http://openvz.livejournal.com/39765.html and http://openvz.livejournal.com/35628.html), you can try the following command:
This will set 8GB of RAM and 8GB of SWAP limits to the container 101 and save the settings (note: this is one single line)
WARNING: it is possible that this will break the web interface and probably make it buggy or even impossible to modify some other parameters. I am not sure about the consequences, as I have not done any testing AT ALL. Use on your own risk. I do have a container working correctly with these settings, but I do not use the web interface frequently (right now, the most important parts of the Proxmox project for me are its kernel and installer; but when 2.0 will be finalized I will start using the interface too, however this is still a long way to go).
Code:
vzctl set 101 --save --physpages 0:8G --swappages 0:8G --kmemsize unlimited --lockedpages unlimited --privvmpages unlimited --shmpages unlimited --numproc unlimited --vmguarpages unlimited --oomguarpages unlimited --numtcpsock unlimited --numflock unlimited --numpty unlimited --numsiginfo unlimited --tcpsndbuf unlimited --tcprcvbuf unlimited --othersockbuf unlimited --dgramrcvbuf unlimited --numothersock unlimited --dcachesize unlimited --numfile unlimited --numiptent unlimitedThis will set 8GB of RAM and 8GB of SWAP limits to the container 101 and save the settings (note: this is one single line)
WARNING: it is possible that this will break the web interface and probably make it buggy or even impossible to modify some other parameters. I am not sure about the consequences, as I have not done any testing AT ALL. Use on your own risk. I do have a container working correctly with these settings, but I do not use the web interface frequently (right now, the most important parts of the Proxmox project for me are its kernel and installer; but when 2.0 will be finalized I will start using the interface too, however this is still a long way to go).
Last edited by a moderator:
Hello Martin,
Could you tell me if it's going to be fixed with a new release or reverted?
Regards,
Stas
