Unable to import vmdk

SERGIO_372

I'm trying to import an VMDK disk of 10Gb, but every time I get the following error.

vm.stats
{
  "id": "31599c8f-a0aa-755a-41f2-ce57d9712a6f"
}
{
  "errno": -110,
  "code": "ETIMEDOUT",
  "syscall": "connect",
  "address": "10.10.10.2",
  "port": 443,
  "url": "https://10.10.10.2/rrd_updates?cf=AVERAGE&host=true&interval=5&json=true&start=1673122561&session_id=OpaqueRef%3Abd3db29e-0a70-455a-b9a0-22296ad92a02&task_id=OpaqueRef%3Aa3a1b0d7-659d-4a67-8b5c-874eabc44898",
  "message": "connect ETIMEDOUT 10.10.10.2:443",
  "name": "Error",
  "stack": "Error: connect ETIMEDOUT 10.10.10.2:443
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)
    at TCPConnectWrap.callbackTrampoline (internal/async_hooks.js:134:14)"
}

The transfer seems to be going well but all sudden it stops. My XCP-ng is up-to-date and my XOA too. Can someone help me? Thx!

SERGIO_372

@SERGIO_372 "interval=5" on the URL is the time that I have to transfer the file? It seems that error occur about this 5 mim after the transfer stats.

Danp

This sounds like the same issue discussed here. If you are using XOA (the prebuilt appliance), then you should either contact support for the fix or wait until the next release (tomorrow?) and then retest using the latest release channel.

olivierlambert

Yes, we are doing a release in less than in the next 24h

edit: that might be also a good reason to alternatively try the new VMware import tool (also landing in latest tomorrow!)

SERGIO_372

Ok, I have changed from stable to latest, updated and restarted the Xen Orchestra. After trying again, I received the same error, BUT it worked. What I have noticed.

It took approximately 5m24s for the error to appear.
The speed really improved (import). I was only able to reach 45% of progress before it stops, this time I went up to 75%
After I get the error, the progress freezes, and then a few seconds later the task disappears.

I thought at first that it was just another fail, but the disk was actually imported when I went to check. Have booted on it and all. Weird.

olivierlambert

Please retry on today's release on latest (in few hours). It should work even better

SERGIO_372

@olivierlambert Hi there! I just updated to the 5.79.0 version and the error persists. Now I receive the error message in less than a minute and the importation freezes until reaches five minutes (approximately). The task despairs and the disk wasn't imported.

olivierlambert

That would be fine to open a ticket and give us an access to that VMDK so we can take a look on it (maybe it's another case where's there's something weird inside).

In the mean time, if you have an ESXi running with that VM, I encourage you to try our migration script

SERGIO_372

@olivierlambert I uploaded the disk.
https://mega.nz/folder/53YTGRCI#4qP16Kfj-XtKcwkWduGEOg