View Single Post
  #3  
Old 21st May 2012, 14:37
theWeird theWeird is offline
Member
 
Join Date: Nov 2009
Posts: 70
Thanks: 10
Thanked 6 Times in 5 Posts
Default

I had the same problem on my ISP-installations inside an OpenVZ container.

It is a bug in an older openvz-kernel on the host node which has been fixed some month ago. But because openvz is developed on a redhat kernel the patches need really long time to be ported into the official debian kernel.

But the people of the Proxmox project work much faster on that point than the debian devs.
I switched the kernel used on the host node to Proxmox (which is based on debian) and now all problems I had with openVZ disappeared.

Just follow the steps
'Adapt your sources.list' and 'Install Proxmox VE Kernel'
on this wiki page to make it work like a charm.
http://pve.proxmox.com/wiki/Install_...Debian_Squeeze

BUT:
If you already had VEs configurated:
Proxmox moves the directory /etc/vz/conf to /etc/vz/conf.org and creates a symlink from /etc/vz/conf to /etc/pve/openvz.
So after installing Proxmox VE it seems that all your VEs are gone.
Just copy the config files from conf.org back to conf and restart openvz
# /etc/init.d/vz restart
Afterwards everything is fine.

My original post in the german forum:
http://www.howtoforge.de/forum/29686-post23.html
Reply With Quote