pm30
Posted: Wed May 22, 2013 6:39 am
pm30 locked up and needed a reset to come back.
It looks like the patched ovz kernel (against the 2.6.37+ backported vulnerability) is much more unstable than before, the lockups more than doubled, maybe tripled since the patch, as well as it introduced the 127.0.0.1 loopback connection problem for some OSes and architectures.
I remind everyone that cannot connect to the loopback interface to change in their hosts file the ip for localhost to 127.0.0.2 as a workaround until the next patch round.
As soon as we hear there is a version that fixes at least the loopback problem, we will schedule a maintenance round.
In the meantime, for stable production systems, I recommend Xen/KVM.
It looks like the patched ovz kernel (against the 2.6.37+ backported vulnerability) is much more unstable than before, the lockups more than doubled, maybe tripled since the patch, as well as it introduced the 127.0.0.1 loopback connection problem for some OSes and architectures.
I remind everyone that cannot connect to the loopback interface to change in their hosts file the ip for localhost to 127.0.0.2 as a workaround until the next patch round.
As soon as we hear there is a version that fixes at least the loopback problem, we will schedule a maintenance round.
In the meantime, for stable production systems, I recommend Xen/KVM.