Article ID: 115244, created on Dec 3, 2012, last review on Apr 11, 2016

  • Applies to:
  • Operations Automation 6.0
  • Operations Automation 5.4
  • Virtuozzo containers for Windows 6.0
  • Virtuozzo containers for Windows 4.6

Symptoms

  1. Container cannot be migrated from one Parallels Virtuozzo Containers for Windows node to another.

  2. The similar output is observed in the command prompt window:

    C:\>vzmigrate -A myserver -U administrator -P password 100
    migrate 100->100
    migration started
      0%: Operation with the Container mycontainer is started
      0%: migrating "mycontainer" from "myserver" to "85560a38-6a21-6e1b-f9c7-9fdc28f49e2e"
      0%: Stopping source Container 100
    100%: Operation with the Container mycontainer is finished with errors: Internal error:
    SendPrivate completed with error 0x0 dwRes 0xffffffff
    Failed to send private file C:\vz\Private\100\root.efd
    Stage2 SendPrivates failed.
    
    migration error 0x1 Internal error: SendPrivate completed with error 0x0 dwRes 0xffffffff
    Failed to send private file file C:\vz\Private\100\root.efd
    Stage2 SendPrivates failed
    
  3. In Virtuozzo log file the similar errors are observed:

    {0000000000000000}; T=2012.07.22 09:57:00.955; A=vzaop; P=4192.2036; S=VZMIGSERVER; F=build\vt-win-i386\vzmig\MigExchange.cpp,CPrivateReceiver::Receive_Version1,267; L=INFO; R=ffff(65535); C=0(0); M=65535 [] RECEIVE: Stage1 private C:\vz\private\100\root.efd
    {0000000000000000}; T=2012.07.22 09:57:00.955; A=vzaop; P=4192.2036; S=VZMIGSERVER; F=build\vt-win-i386\vzmig\MigExchange.cpp,CPrivateReceiver::Receive_Version1,296; L=ERROR; R=ffff(65535); C=0(0); M=65535 [] Not enough disk space to create file C:\vz\private\100\root.efd of size 0x640000000 bytes
    {0000000000000000}; T=2012.07.22 09:57:00.955; A=vzaop; P=4192.2036; S=VZMIGSERVER; F=build\vt-win-i386\vzmig\MigExchange.cpp,ReceiverThread,655; L=ERROR; R=ffff(65535); C=0(0); M=65535 [] ReceiverThread failed to process tag 1 error 0x70
    

Cause

The container has the disk space limit which exceeds the amount of free disk space available on the destination node, even though it may not consume all allocated disk space.

Resolution

  1. Make sure the destination node has enough disk space to host the container.
  2. Decrease the container's disk space limit to fit amount of free space on the destination node.

    For example:

    A container has the disk space limit 200GB and the actual consumption is 25GB:

    C:\Users\Administrator>vzquota stat 1000        
         disk  resource   usage     hardlimit  path
         C:    1k-blocks  26214400  209715200  C:\vz\Private\1000\root.efd
    

    The destination node has 50GB free. It is reasonable to set disk space limit to 30GB in such case to be able to migrate the container:

    C:\Users\Administrator>vzctl set 1000 --save --diskspace 31457180
    Command 'set' is successfully finished
    
  3. Migrate the container.
  4. Set the former limit back.

NOTE: It is strongly not recommended to overcommit disk space, because it may lead to unpredictable containers' corruption and node's instability

Search Words

error

0xffffffff

ReceiverThread failed to process tag 1 error 0x70

SendPrivate completed with error

Stage2 SendPrivates failed

dwRes 0xffffffff

VzkrnlStartVps

Not enough disk space to create file

migration

blockedWrite failed

Failed to send private file

migration error

965b49118115a610e93635d21c5694a8 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f 5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 614fd0b754f34d5efe9627f2057b8642 6f8e3eda12803cf88a9587e9782c9ed6 6c20476fe6c3408461ce38cbcab6d03b ac82ce33439a9c1feec4ff4f2f638899 2554725ed606193dd9bbce21365bed4e 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF