Article ID: 128962, created on Jun 17, 2016, last review on Jun 17, 2016

  • Applies to:
  • Operations Automation 6.0


All VEs provisioning and recreate operations are failing on particular Virtuozzo node. The following error message could be found in PACI-im.log right after VE creation:

ERROR GenericVePcsTask [Shared executor thread #2 @4] - No storage id for PCS drive

On Vm2vf side, the following notable structure is displayed at the end of creation process:

Invoked callback [done_with_capacity_and_id(0, 37435960672256, 1466097127270, null, 3e5cdcd0-f7ef-4845-9b29-f4a9012710c7)]

Note 'null' value in the line above. There should be location of CT or VM private space. When this callback is received, VE considered as corrupted and gets immediately deleted.


VM home directory is configured to the non-default location:

[root@pcs ~]# prlsrvctl info | grep 'VM home'
VM home: /pcs


According to OA documentation, when Virtuozzo node operates in cluster environment, default directory should be used for VM home.

You can correct this setting the following way:

# prlsrvctl user set --def-vm-home /var/parallels/
# prlsrvctl user list

NAME MNG_SETTINGS DEF_VM_HOME root@. deny /var/parallels/

Then edit file /etc/vz/vz.conf and change value for VE_PRIVATE from:




Perform these operations on all nodes where you find incorrect values for VM home. Please note that OACI IM restart might be needed as described in KB article.

Search Words

cannot create VE

No storage id for PCS drive

cannot create VE on particular node

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF