Article ID: 1315, created on Oct 6, 2008, last review on May 10, 2014

  • Applies to:
  • Virtuozzo containers for Windows

Symptoms

  1. A container (CT #1829 in this case) may fail to start with the following error messages:

    ERROR: Failed to open registry key vz1829\MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters, code 0x57
    ERROR: Unexpected error 0xc000000d ZwOpenKey(\registry\machine\vz1829\MACHINE) failed
    ERROR: Unexpected error 0xc000000d RemoveLinksFromMachine(\registry\machine\vz1829\MACHINE) failed
    WARNING: Virtuozzo API function call 'RemoveIncorrectLinks' failed CTID = 1829 Error = 0xC000000D
    WARNING: Virtuozzo API function call 'VzhiveUMount' failed CTID = 1829
    WARNING: Windows API function call 'delete_VPSmp' failed, code 0xe CTID 1829
    WARNING: Windows API function call 'vzfs_umount' failed, code 0x2000 CTID 1829
    WARNING: Windows API function call 'GetDiskFreeSpace' failed, code 0x5
    WARNING: Virtuozzo API function call 'dq_umount' failed
    

    or

  2. A container is stuck in Starting state and the error messages mentioned above can be found in the log file C:/vzlog/YYYY.MM.DD-vzlog.

Cause

The reason for the failed start is that the registry of the specific container could not be unmounted correctly. When the container was stopped, there may still have been some opened handles within some of the registry keys, even though the processes finished correctly. Since the system cannot mount the container's registry, the containers may fail to start properly.

Resolution

To resolve this situation, the Parallels Virtuozzo Containers Hardware Node should be rebooted.

Search Words

0xc000000d

RemoveLinksFromMachine

RemoveIncorrectLinks

VzhiveUMount

code 0x57

dq_umount

Failed to open registry key

Unexpected error 0xc000000d

965b49118115a610e93635d21c5694a8 d02f9caf3e11b191a38179103495106f 2897d76d56d2010f4e3a28f864d69223

Email subscription for changes to this article
Save as PDF