On a newly deployed Windows Server 2008 (non-R2) node all new containers cannot start:
C:\> vzctl start 101 Starting container ... ctid=101 LogonUI timeout (300 secs) Container 101 is not started
Wrong permissions on OS template registry hive prevent containers to start. The issue is recognized as a product bug with internal ID PCWIN-22504.
The permanent fix is planned to be included in one of the next product updates. In order to fix current installation, the following workaround should be performed:
Mount one of the containers.
C:\> vzctl mount 101 Container is mounted
Open registry editor
regeditand modify permissions for the
HKEY_LOCAL_MACHINE\vz0_windows_2008_ent_sp1-6.0.6001-20090319\MACHINE\COMPONENTShive. Set the same permissions as for
HKEY_LOCAL_MACHINE\COMPONENTShive (there should be 4 users, if there are only two — add the rest).
- If the containers created previously need to be started, mount them and change permissions for
HKEY_LOCAL_MACHINE\vzCTID\MACHINE\COMPONENTSin the same way.