Article ID: 123066, created on Oct 4, 2014, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo 6.0

Symptoms

  1. The virtual machine cannot be created with "Failed to register the VM" error message in Parallels Cloud Storage environment:

    # prlctl create MY_VM_test.com
    Creating the virtual machine...
    Generate the VM configuration for win-2008.
    Failed to register the VM: Failed to perform the operation. An error occurred when managing the cluster resource. Contact your system administrator for assistance.
    Failed to create the virtual machine.
    
  2. Already existing VM cannot be registered with the same error:

    # prlctl register /var/parallels/MY_VM_test.com.pvm/config.pvs --preserve-uuid
    Register the VM...
    Failed to register the VM: Failed to perform the operation. An error occurred when managing the cluster resource. Contact your system administrator for assistance.
    
  3. Related /var/log/parallels.log part contains "Shaman" service (High Availability feature) records as in the example:

04-15 21:46:27.842 F /disp:20207:546749/ Failed to wait for finished /usr/sbin/shaman : Unknown error
            04-15 21:46:27.842 F /disp:20207:546749/ cluster resource 'MY_VM_test.com' registration error
            04-15 21:46:27.854 F /disp:20207:546749/ Error occurred while registering configuration with code [0x80046900][PRL_ERR_CLUSTER_RESOURCE_ERROR]
            04-15 21:46:27.859 F /disp:20207:546749/ Task '12Task_CloneVm' with uuid = {e83e2571-f4f7-4098-953b-b3cbdb0ab0ee} was finished with result
    PRL_ERR_CLUSTER_RESOURCE_ERROR (0x80046900) )
            04-15 21:46:28.151 F /disp:20207:1022593/ Processing command 'DspCmdDirGetVmList' 2029 (PJOC_SRV_GET_VM_LIST)

Cause

The issue may take place if you already had a VM with this name and it was not deleted properly or the previous attempt to create a VM with this particular name did not finish gracefully (e.g. because of sudden connection lost between the cluster nodes).

Shaman service may still keep the VM name among existing resources and that would prevent the creation of a new VM with exactly the same name.

Resolution

  1. Find the VM name among Shaman resources (can be executed from any Parallels Cloud Storage cluster member):

    # find $CLUSTER_MOUNT_POINT/.shaman/md.*/resources/ -name *VM_NAME*
    

    (Replace CLUSTER_MOUNT_POINT with appropriate path, and VM_NAME with the real name of VM)

    Cluster mount point can be checked with:

    # mount |grep fuse
    pstorage://pcs on /pstorage/pcs type fuse.pstorage (rw)
    

    Real-life example:

    # find /pstorage/pcs/.shaman/md.*/resources/ -name *MY_VM_test*
    /pstorage/pcs/.shaman/md.00d841b886064558/resources/vm-MY_VM_test.com
    
  2. Remove Shaman resource manually:

    # rm -rf /pstorage/pcs/.shaman/md.00d841b886064558/resources/vm-MY_VM_test.com
    
  3. Create/register the VM:

    # prlctl create MY_VM_test.com --ostemplate template-centOS6.x-x86_64
    Creating the VM on the basis of the template-centOS6.x-x86_64 template...
    Successfully cloned.
    
    # prlctl list MY_VM_test.com
    UUID                                    STATUS       IP_ADDR         T  NAME
    {6e48e199-1673-437e-80bf-08c4ade8a91f}  stopped      -               VM MY_VM_test.com
    

    OR

    # prlctl register /var/parallels/MY_VM_test.pvm/config.pvs --preserve-uuid 
    Register the VM...
    The VM has been successfully registered.
    

Additional information

119938 VM created from a template does not start: The virtual machine is registered on another server

Search Words

cluster resource

0x80046900

fail to create

An error occurred when managing the cluster resource

PRL_ERR_CLUSTER_RESOURCE_ERROR

Failed to register the VM

c62e8726973f80975db0531f1ed5c6a2 2897d76d56d2010f4e3a28f864d69223 0dd5b9380c7d4884d77587f3eb0fa8ef

Email subscription for changes to this article
Save as PDF