|vzctl on vanilla Linux 4.1.1 results in "Refusing to run" [message #52106]
||Wed, 01 July 2015 10:14
Registered: July 2013
Being using OpenVZ kernels ("2.6.32-openvz-042stab108.5-amd64" until yesterday) with vzctl 4.8, and no problems for years.|
However, now I need a newer kernel for a feature called "bcache" recently merged in linux.
When I boot from the new vanilla 4.1.1, the following happens:
$ su root
# vzctl start 105
> Directory /proc/vz not found, assuming non-OpenVZ kernel
> Starting container...
> Container private area is owned by 0:0, but configuration file says we should run with 100000:100000.
> Refusing to run.
All the containers have only basic configuration, nothing hardcore. Here's config for CT 105:
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
# This config is only valid for decent VSwap-enabled kernel
# (version 042stab042 or later).
# Disk quota parameters (in form of softlimit:hardlimit)
# CPU fair scheduler parameter
With a vanilla linux it would be enough for me to just be able to start/stop containers, assign IPs, set RAM caps and take offline backups. This should be possible with vanilla, so what's the problem?
[Updated on: Wed, 01 July 2015 10:18]
Report message to a moderator