Article ID: 125282, created on Apr 25, 2015, last review on Apr 25, 2015

  • Applies to:
  • Virtuozzo 6.0

Symptoms

After successful online migration container stays in the invalid state on the source node:

[root@destination ~]# prlctl list 101
UUID                                    STATUS       IP_ADDR         T  NAME
{77745c85-c7f6-41f0-b9f2-9271461bb6fc}  running      192.0.2.1      CT  101

[root@source ~]# prlctl list 101
UUID                                    STATUS       IP_ADDR         T  NAME
{77745c85-c7f6-41f0-b9f2-9271461bb6fc}  invalid      192.0.2.2      CT  101

Container was migrated over a shared storage (e.g. Virtuozzo storage) using vzmigrate --online command or through Virtual Automation web-interface.

Cause

This issue was recognized as a product bug with internal ID #PSBM-32870.

Resolution

The issue will be permanently fixed in one of the future updates.

To avoid leaving the containers in invalid state on the source node, prlctl migrate should be used instead of vzmigrate:

[root@source ~]# prlctl migrate 101 203.0.113.2

To get rid of invalid instance of migrated container on the source node, parallels-server service should be restarted:

[root@source ~]# service parallels-server restart

NOTE: parallels-server restart will cause all running virtual environments on the node to restart.

Search Words

online migration

invalid

c62e8726973f80975db0531f1ed5c6a2 2897d76d56d2010f4e3a28f864d69223 0dd5b9380c7d4884d77587f3eb0fa8ef

Email subscription for changes to this article
Save as PDF