half-configured container starts

vzctl 3.0.25 gives containers the amount of memory on the hostnode upon reboot, It also gives 'fake' swap which makes the OpenVZ VE appear to have the amount of swap on the main node.

A workaround for the time being is downgrading to 3.0.24.

Hi,

You had me worried for a minute... Looks like there a sefualt in either the kernel or vzctl.

[root@13 ~]# vzctl restart 1034
Removing stale lock file /vz/lock/1034.lck
Restarting container
Stopping container ...
Container was stopped
Container is unmounted
Starting container ...
Container is mounted
Adding IP address(es): 184.154.13.109
Setting CPU limit: 200
Setting CPU units: 1000
Setting CPUs: 2
Setting devices
Segmentation fault

2010-12-23T10:58:11-0500 vzeventd : Child 19264 failed with exit code 79
2010-12-23T11:03:25-0500 vzctl : CT 1034 : Removing stale lock file /vz/lock/1034.lck
2010-12-23T11:03:25-0500 vzctl : CT 1034 : Restarting container
2010-12-23T11:03:25-0500 vzctl : CT 1034 : Stopping container ...
2010-12-23T11:03:34-0500 vzctl : CT 1034 : Container was stopped
2010-12-23T11:03:34-0500 vzctl : CT 1034 : Container is unmounted
2010-12-23T11:03:34-0500 vzctl : CT 1034 : Starting container ...
2010-12-23T11:03:34-0500 vzctl : CT 1034 : Container is mounted
2010-12-23T11:03:35-0500 vzctl : CT 1034 : Adding IP address(es): 184.154.13.109
2010-12-23T11:03:35-0500 vzctl : CT 1034 : Setting CPU limit: 200
2010-12-23T11:03:35-0500 vzctl : CT 1034 : Setting CPU units: 1000
2010-12-23T11:03:35-0500 vzctl : CT 1034 : Setting CPUs: 2
2010-12-23T11:03:35-0500 vzctl : CT 1034 : Setting devices
2010-12-23T11:04:29-0500 vzeventd : Child 2261 failed with exit code 79


vzctl restart 1034
Removing stale lock file /vz/lock/1034.lck
Restarting container
Stopping container ...
Container was stopped
Container is unmounted
Starting container ...
Container is mounted
Adding IP address(es): *.*.*.*
Setting CPU limit: 200
Setting CPU units: 1000
Setting CPUs: 2
Setting devices
Segmentation fault