updating vzctl to 3.0.26.3-1 fixes the described issue. Thanks! Nikolay. Kirill Kolyshkin wrote on 10/05/11 19:33: > > The issue you are describing is believed to be fixed in vzctl 3.0.26.3 > which was released 2 days ago :) >