XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Migrating VM fails with (VDI_COPY_FAILED, [ End_of_file } Failure from sparse_dd:

    Scheduled Pinned Locked Moved
    Xen Orchestra
    3
    9
    1.2k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      alisson luz1068
      last edited by Danp

      I'm having error when migrating only 2 vms between different servers.
      Over 40 vms were migrated without errors.
      I don't think it's a problem with corrupted vdi, as the vms are up and running, it's also possible to restart them without any problems.
      Even turning off vms and trying to migrate, it also generates the error.
      The architecture of the source and destination servers are the same
      Both the source and destination server have spare resources.
      I detach the vdis and reattach it, however the difficulty with the migration remained.

      Note, it only occurs on 2 vms, any other vm I move between hosts works.

      VM Powerstate also returns no errors.

      Using vhd-util repair -n and check I don't get errors either.

      XenTools installed correctly on them

      Migration fails after 4%...5%

      Copying, exporting, creating on another host via snapshot also generates an error. Below is the live migration log

      I don't think it's a network problem either, as I can migrate any other vm without any difficulties between hosts.

      Nov 23 10:43:11 vmhost923 xapi: [debug||4892 |VM.assert_can_migrate D:e1f906ea31a8|stunnel] check_reusable: caught exception Unix.Unix_error(Unix.EPIPE, "single_write", ""); assuming not reusable
Nov 23 10:45:38 vmhost923 xapi: [error||5208 ||sparse_dd_wrapper] Failure from sparse_dd: Using protocol: nbd#012really_read offset = 15254683648 len = 2097152: Unix.Unix_error(Unix.EIO, "read", "")#012Fatal error: exception Unix.Unix_error(Unix.EIO, "read", "")#012 raising End_of_file
Nov 23 10:45:40 vmhost923 xapi: [error||4985 |Async.VM.migrate_send R:5b42496446dc|storage_migrate] Caught Server_error(VDI_COPY_FAILED, [ End_of_file ]): performing cleanup actions
Nov 23 10:45:40 vmhost923 xapi: [error||4985 |Async.VM.migrate_send R:5b42496446dc|storage_migrate] Caught Server_error(VDI_COPY_FAILED, [ End_of_file ]): performing cleanup actions
Nov 23 10:45:43 vmhost923 xapi: [error||5694 ||backtrace] VDI.destroy D:d783458677a5 failed with exception Storage_access.No_VDI
Nov 23 10:45:43 vmhost923 xapi: [error||5694 ||backtrace] Raised Storage_access.No_VDI
Nov 23 10:45:43 vmhost923 xapi: [error||5694 ||backtrace] 1/1 xapi Raised at file (Thread 5694 has no backtrace table. Was with_backtraces called?, line 0
Nov 23 10:45:43 vmhost923 xapi: [error||5694 ||backtrace]
Nov 23 10:45:43 vmhost923 xapi: [error||5694 ||storage_interface] Storage_error ([S(Vdi_does_not_exist);S(59165d4f-f024-4991-8770-e4f9575a7fb6)]) (File "storage/storage_interface.ml", line 420, characters 51-58)
Nov 23 10:45:43 vmhost923 xapi: [error||5691 INET :::80|Querying services D:94312a117a95|storage_interface] Storage_error ([S(Vdi_does_not_exist);S(59165d4f-f024-4991-8770-e4f9575a7fb6)]) (File "storage/storage_interface.ml", line 415, characters 50-57)
Nov 23 10:45:43 vmhost923 xapi: [error||5691 INET :::80|Querying services D:94312a117a95|storage_interface] Storage_error ([S(Vdi_does_not_exist);S(59165d4f-f024-4991-8770-e4f9575a7fb6)]) (File "storage/storage_interface.ml", line 420, characters 51-58)
Nov 23 10:45:43 vmhost923 xapi: [error||4985 |Async.VM.migrate_send R:5b42496446dc|storage_interface] Storage_error ([S(Vdi_does_not_exist);S(59165d4f-f024-4991-8770-e4f9575a7fb6)]) (File "storage/storage_interface.ml", line 415, characters 50-57)
Nov 23 10:45:43 vmhost923 xapi: [error||4985 |Async.VM.migrate_send R:5b42496446dc|storage_migrate] Caught Storage_error ([S(Vdi_does_not_exist);S(59165d4f-f024-4991-8770-e4f9575a7fb6)]) while performing cleanup actions
Nov 23 10:45:43 vmhost923 xapi: [error||4985 |Async.VM.migrate_send R:5b42496446dc|task_server] Task 3 failed; Storage_error ([S(Backend_error);[S(VDI_COPY_FAILED);[S(End_of_file)]]])
Nov 23 10:45:43 vmhost923 xapi: [debug||4985 |Async.VM.migrate_send R:5b42496446dc|storage] TASK.signal 3 = ["Failed",["Backend_error",["VDI_COPY_FAILED",["End_of_file"]]]]
Nov 23 10:45:43 vmhost923 xapi: [error||4892 ||xapi] Caught Storage_error ([S(Backend_error);[S(VDI_COPY_FAILED);[S(End_of_file)]]]): cleaning up
Nov 23 10:45:43 vmhost923 xenopsd-xc: [error||264 ||backtrace] Async.VM.migrate_send R:5b42496446dc failed with exception Xenops_interface.Xenopsd_error([S(Does_not_exist);[S(VM);S(30ab6397-557a-0ffb-337a-31c90b1241af/config)]])
Nov 23 10:45:43 vmhost923 xenopsd-xc: [error||264 ||backtrace] Raised Xenops_interface.Xenopsd_error([S(Does_not_exist);[S(VM);S(30ab6397-557a-0ffb-337a-31c90b1241af/config)]])
Nov 23 10:45:43 vmhost923 xenopsd-xc: [error||264 ||backtrace] 1/1 xenopsd-xc Raised at file (Thread 264 has no backtrace table. Was with_backtraces called?, line 0
Nov 23 10:45:43 vmhost923 xenopsd-xc: [error||264 ||backtrace]
Nov 23 10:45:43 vmhost923 xenopsd-xc: [error||264 ||xenops_interface] Xenops_interface.Xenopsd_error([S(Does_not_exist);[S(VM);S(30ab6397-557a-0ffb-337a-31c90b1241af/config)]]) (File "xen/xenops_interface.ml", line 158, characters 53-60)
Nov 23 10:45:43 vmhost923 xapi: [error||4892 ||xenops_interface] Xenops_interface.Xenopsd_error([S(Does_not_exist);[S(VM);S(30ab6397-557a-0ffb-

      Any hints of what it might be?

      DanpD 1 Reply Last reply Reply Quote 0
      • DanpD
        Danp Vates 🪐 Pro Support Team
        last edited by

        Please tell us more about your hosts. Are you running CH or XCP-ng? What version? Fully patched? Etc.

        1 Reply Last reply Reply Quote 0
        • A
          alisson luz1068
          last edited by

          @danp said in Migrating VM fails with (VDI_COPY_FAILED, [ End_of_file } Failure from sparse_dd::

          Please tell us more about your hosts. Are you running CH or XCP-ng? What version? Fully patched? Etc.

          I'm using the fully patched xcp-ng version 8.1

          1 Reply Last reply Reply Quote 0
          • DanpD
            Danp Vates 🪐 Pro Support Team @alisson luz1068
            last edited by

            @alisson-luz1068 said in Migrating VM fails with (VDI_COPY_FAILED, [ End_of_file } Failure from sparse_dd::

            Copying, exporting, creating on another host via snapshot also generates an error. Below is the live migration log
            I don't think it's a network problem either, as I can migrate any other vm without any difficulties between hosts.

            Sounds more like a problem with the VHD or the underlying storage. Have you checked the smlog file for any related errors?

            A 1 Reply Last reply Reply Quote 0
            • A
              alisson luz1068 @Danp
              last edited by

              @danp said in Migrating VM fails with (VDI_COPY_FAILED, [ End_of_file } Failure from sparse_dd::

              Sounds more like a problem with the VHD or the underlying storage. Have you checked the smlog file for any related errors?

              @danp said in Migrating VM fails with (VDI_COPY_FAILED, [ End_of_file } Failure from sparse_dd::

              Sounds more like a problem with the VHD or the underlying storage. Have you checked the smlog file for any related errors?

              Yes, check the smlog file and I found no errors.
              I also followed the live execution of the migration tasks and it just returns a fatal error with some exceptions

              1 Reply Last reply Reply Quote 0
              • olivierlambertO
                olivierlambert Vates 🪐 Co-Founder CEO
                last edited by

                8.1 isn't supported anymore. That would be interesting to check if you experience the same thing on a 8.2 host.

                1 Reply Last reply Reply Quote 0
                • A
                  alisson luz1068
                  last edited by Danp

                  @olivierlambert said in Migrating VM fails with (VDI_COPY_FAILED, [ End_of_file } Failure from sparse_dd::

                  8.1 isn't supported anymore. That would be interesting to check if you experience the same thing on a 8.2 host.

                  Thanks, I will do this experiment.

                  In a last test I verified that the following message checking the vdis:

                  [10:06 vmhost923 6dee0c53-26a7-56b2-6b05-7b67060f40eb]# vhd-util check -n /var/run/sr-mount/6dee0c53-26a7-56b2-6b05-7b67060f40eb/19ac4698-2a28-45df-a12029-ac06 .vhd
primary footer invalid: invalid cookie
/var/run/sr-mount/6dee0c53-26a7-56b2-6b05-7b67060f40eb/19ac4698-2a28-45df-a029-c046812e35a6.vhd appears invalid; dumping metadata

                  After repairing (vhd-util repair) the vdis with errors and doing a new check, the error is corrected, so I ran the SR rescan, and tried to migrate again and the VDIS returned to show an error message

                  Any tips on what can be done in this situation?

                  A 1 Reply Last reply Reply Quote 0
                  • A
                    alisson luz1068 @alisson luz1068
                    last edited by

                    @alisson-luz1068 said in Migrating VM fails with (VDI_COPY_FAILED, [ End_of_file } Failure from sparse_dd::

                    primary footer invalid: invalid cookie

                    Hi, it's the exact same error recorded in the ticket below. Was there any solution in this case?
                    https://bugs.xenserver.org/browse/XSO-842?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel

                    1 Reply Last reply Reply Quote 0
                    • olivierlambertO
                      olivierlambert Vates 🪐 Co-Founder CEO
                      last edited by

                      I opened that ticket myself. But it's an old bug that should have been solved or not reproduced since. You should at least upgrade to a supported version to see if it's still happening.

                      1 Reply Last reply Reply Quote 0
                      • First post
                        Last post