Search Engine: Elastic

Article ID: 118317, created on Oct 31, 2013, last review on Oct 3, 2015

  • Applies to:
  • Odin Business Automation Standard


When an old Virtuozzo node failed, the Virtual Machine (VM) was migrated to a new node with PS tools.

Under Top > Service Director > Virtuozzo Manager > Nodes > node_name > Containers tab after migration the VM is shown with the status "Not existent" in the old node and missing in the new node.


According to Odin Business Automation Standard (OBAS) limitations to VM management:

The current implementation of OBAS - Server Bare Metal (SBM) integration brings several limitations of Virtual Machine management:

    * A Virtual Machine can only be created from the online store upon a sales order.
    * Virtual Machines created at an SBM node before registration of this node in OBAS are not visible from OBAS and information about these Virtual Machines is not passed. The OBAS Conflict Resolver does not support Virtual Machine conflicts resolution.

This indicates that a VM cannot be registered in OBAS if they were created on this node (not through a store) - there is no Conflict Resolver for VM in the current OBAS implementation. Here is the feature request:

PBAS-27834 - Conflict resolver for VM


Avoid migrating a VM between Virtuozzo nodes registered in OBAS, follow OBAS limitations to VM management.

If the VM has been migrated because of the failure of the original node, please contact Odin Technical Support to fix the issue in the database.

400e18f6ede9f8be5575a475d2d6b0a6 caea8340e2d186a540518d08602aa065

Email subscription for changes to this article
Save as PDF