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
    1 Posts 1 Posters 28 Views 1 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

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