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

    ESXi 7.0.1 → XCP-ng 8.3 import fails immediately at disk stage with “stream has ended without data, was looking for 134 bytes” (via vCenter)

    Scheduled Pinned Locked Moved Migrate to XCP-ng
    2 Posts 2 Posters 49 Views 2 Watching
    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.
    • I Offline
      ItzJay
      last edited by

      Environment:

      • Xen Orchestra Appliance 6.1.0-43 (6.2.0)
      • XCP-ng 8.3
      • XOA running on same XCP-ng host
      • Default Local LVM SR (1.44 TB free)

      Source:
      • ESXi 7.0.1-16850804-standard
      • Managed by vCenter 7.0.3.00500
      • Connected to XO via vCenter endpoint
      • Source datastore VMFS6
      • Thin provisioned disks

      Network:
      • XO and XCP-ng host have interfaces on ESXi VLAN
      • Bonded network
      • MTU 1500
      • No firewall/IDS in path

      Behavior:
      Import steps succeed until disk phase:
      Connects to vCenter
      Retrieves metadata
      Creates VM on XCP side
      Builds disk chain
      Immediately fails when disk import begins

      Error:
      Error: stream has ended without data, was looking for 134 bytes
      at readChunkStrict (@vates/read-chunk)

      Additional Observations:
      • Reproducible 100%
      • Occurs on all VMs tested
      • Happens at same stage
      • Changing concurrency (2 → 1) has no effect
      • Restarting xo-server does not change behavior
      • No snapshots
      • VMs boot normally on ESXi
      • sslVerify disabled

      florentF 1 Reply Last reply Reply Quote 0
      • florentF Offline
        florent Vates 🪐 XO Team @ItzJay
        last edited by

        @ItzJay in your journalctl -i xo-server log you should have something like nbdkit logs of ${diskPath} are in ${tmpDir} where tmpDir is something like /tmp/xo-serverXXXX/stderr

        can you post the file ?

        alternatively, you can open a support ticket

        1 Reply Last reply Reply Quote 0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        • First post
          Last post