Article ID: 117908, created on Oct 11, 2013, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo containers for Linux 4.7

Symptoms

A container based on the Ubuntu 12.04 OS template cannot start. The container goes to a "mounted" state immediately:

[root@test ~]# vzctl create 100500 --ostemplate ubuntu-12.04-x86_64
Creating Container private area (ubuntu-12.04-x86_64)
Container is mounted
Postcreate actions performed
Container is unmounted
Container private area was created
Container was successfully registered
[root@test ~]# vzctl start 100500
Starting the Container ...
Container is mounted
Setting permissions 20002 dev 0x7d00
Adding offline management to Container(1): 4643
Adding IP addresses:
Starting the Container ...
[root@test ~]# vzlist 100500
      CTID      NPROC STATUS       IP_ADDR         HOSTNAME
    100500          - mounted      -               -

Meanwhile, a container based on other templates (in this example - based on CentOS 6.x) starts correctly:

[root@test ~]# vzctl create 100501 --ostemplate centos-6-x86_64
Creating Container private area (centos-6-x86_64)
Container is mounted
Postcreate actions performed
Container is unmounted
Container private area was created
Container was successfully registered
[root@test ~]# vzctl start 100501
Starting the Container ...
Container is mounted
Setting permissions 20002 dev 0x7d00
Adding offline management to Container(1): 4643
Adding IP addresses:
Starting the Container ...
[root@test ~]# vzlist 100501
      CTID      NPROC STATUS       IP_ADDR         HOSTNAME
    100501         18 running      -               -                     

Cause

Containers based on Ubuntu 12.04 might not be able to start if the host is not up-to-date. Support for Ubuntu 12.04 was provided in TU-4.7.0-179. If this is not installed and the kernel is outdated, containers based on Ubuntu 12.04 will not be operable.

Resolution

To be able to host containers based on Ubuntu 12.04, ensure your node is up to date:

  1. Install all pending updates:

    [root@test ~]# vzup2date -m batch install
    
  2. Ensure that /etc/grub.conf has the newest kernel set up as the default one to boot in.
  3. Reboot the node.

Search Words

TU-4.7.0-179

unable to start

Starting VPS results in VPS being stuck in mounted state

ubuntu 12.04

unable to start container shows as mounted

ubuntu container cannot be started

d02f9caf3e11b191a38179103495106f 2897d76d56d2010f4e3a28f864d69223 e8e50b42231236b82df27684e7ec0beb 0c05f0c76fec3dd785e9feafce1099a9

Email subscription for changes to this article
Save as PDF