Unable to import 3.4TB disk from VMware.

[tjshuff]

Are you using XOA or XO from the sources?

XO from the sources

Which release channel?

latest

Provide your commit number

6dc18

Describe the bug

Premature close on attempt to import a 3.4TB VM disk from vmware.

I have attempted to import to a local SR and an ISCSI SR, both receiving the same error message.

Error message

vm.importMultipleFromEsxi
{
  "concurrency": 2,
  "host": "**********",
  "network": "f65c8a3b-4ac7-40ce-76de-e45ab43e56dc",
  "password": "* obfuscated *",
  "sr": "fd63ac45-b411-fcfb-e7f7-1d4215ce1ddf",
  "sslVerify": false,
  "stopOnError": true,
  "stopSource": false,
  "user": "root",
  "vms": [
    "1"
  ]
}
{
  "code": "ERR_STREAM_PREMATURE_CLOSE",
  "succeeded": {},
  "message": "Premature close",
  "name": "Error",
  "stack": "Error: Premature close
    at new NodeError (node:internal/errors:405:5)
    at ClientRequest.<anonymous> (node:internal/streams/pipeline:417:14)
    at ClientRequest.emit (node:events:529:35)
    at ClientRequest.patchedEmit [as emit] (/opt/xo/xo-builds/xen-orchestra-202404250924/@xen-orchestra/log/configure.js:52:17)
    at TLSSocket.socketCloseListener (node:_http_client:464:9)
    at TLSSocket.emit (node:events:529:35)
    at TLSSocket.patchedEmit [as emit] (/opt/xo/xo-builds/xen-orchestra-202404250924/@xen-orchestra/log/configure.js:52:17)
    at node:net:350:12
    at TCP.done (node:_tls_wrap:657:7)
    at TCP.callbackTrampoline (node:internal/async_hooks:128:17)"
}

To reproduce

1. Go to Import -> From VMWare
2. Enter information -> Connect
3. Select VM & SR
4. Error

Expected behavior

No response

Screenshots

No response

Node

18.20.2

Hypervisor

XCP-ng 8.2.1

Additional context

No response

[olivierlambert]

Hi,

On a regular SR (storage repository), the maximum virtual disk size is 2TiB. This is not a limitation of the XO V2V tool, but on the storage layer.

Some workarounds exists (with some tradeoff), but it's not directly usable with the V2V tool. Feel free to contact us for a direct investigation and possible solutions for your use case, or alternatively, open a thread on our community forum.