yep I had no snapshots my side either and same error

My backups are getting stuck! They run to a S3 bucket and I just haven't got it running smoothly, yet!

In the meantime I'm running to an NFS share which has been working but now I'm seeing this issue...

EIO: i/o error, open '/run/xo-server/mounts/b5xxx29-a0cc-440b-b8b7-b1cxxxx59/.keeper_w8xxxxxzk'

I'm not quite sure what this actually means and Dr. Google hasn't helped. Is anyone able to point me in the right direction? I feel like its something to do with the .keeper thing?

• NFS share is on and has been working
• Network interface (for the storage share) is on and working
• I've restarted the toolstack (but not the host yet)

Many thanks in advance.

@olivierlambert Oh roger that, I didn't realise the distinction!

@olivierlambert woohooo! Thank you team - have just tested on XOA built from sources and its working!

If I give my XOA more CPU and/or RAM will it speed up the import? Is it bound to the resources of XOA? I'm getting 7.5MiB and have got 20MiB before but no more. My hardware (both sides) does support reads and writes at over 500MiB across my 10Gb link.

yep I had no snapshots my side either and same error

@olivierlambert

I'm running ESXi 6.7 update 3, trying to transfer a Windows 2019 Server, running or halted I get the same error, I have tried several other vms with the same result. Tried different storage and network options too, all same result.

Import
Property description must be an object: undefined

Running XOA on latest with trial enabled fully up to date, two hosts in pool fully up to date.

vm.importMultipleFromEsxi
{
  "concurrency": 2,
  "host": "192.168.150.39",
  "network": "d41468b9-53d8-63af-b474-d3062625ce10",
  "password": "* obfuscated *",
  "sr": "1477ad1f-0d29-ec1f-fa8e-7b8d3bb04ae4",
  "sslVerify": false,
  "stopOnError": true,
  "stopSource": false,
  "thin": false,
  "user": "root",
  "vms": [
    "21",
    "20"
  ]
}
{
  "succeeded": {},
  "message": "Property description must be an object: undefined",
  "name": "TypeError",
  "stack": "TypeError: Property description must be an object: undefined
    at Function.defineProperty (<anonymous>)
    at Task.onProgress (/usr/local/lib/node_modules/xo-server/node_modules/@vates/task/combineEvents.js:51:16)
    at Task.#emit (/usr/local/lib/node_modules/xo-server/node_modules/@vates/task/index.js:130:21)
    at Task.#emit (/usr/local/lib/node_modules/xo-server/node_modules/@vates/task/index.js:124:17)
    at Function.set (/usr/local/lib/node_modules/xo-server/node_modules/@vates/task/index.js:47:17)
    at file:///usr/local/lib/node_modules/xo-server/src/api/vm.mjs:1388:20
    at Task.runInside (/usr/local/lib/node_modules/xo-server/node_modules/@vates/task/index.js:149:22)
    at Task.run (/usr/local/lib/node_modules/xo-server/node_modules/@vates/task/index.js:134:20)
    at asyncEach.concurrency.concurrency (file:///usr/local/lib/node_modules/xo-server/src/api/vm.mjs:1372:11)"
}

Even selecting just 1 vm at a time produces the same error

I'm getting the same error from sources and from a fresh XOA fully updated on Latest channel even started a trial of premium. Any ideas?

I'm transferring a large vm about 2TB from VMware 6.7 on a dual socket Xeon intel host with 128GB RAM with local SSD storage to an up to date XCP-ng host with one intel Silver socket and 64GB RAM to shared NFS storage on a truenas core up-to-date host.

All connected via 10gbe DAC to a large switch.

Performance to local storage was equivalent.

I know there is a crazy amount of variables but I wanted to ask what speeds people are seeing on imports from VMware with the new tool.

I'm getting 7MB/s import very very consistently which I was a bit disappointed at to be honest, over 10 gig networks too.

So, just for a bit of fun, what performance are you seeing?

I've recently added the Github Auth plugin to allow staff within my Github organisation to access XOA with 2FA. Seems like a sensible idea as we use Github anyway.

When I set the plugin up and tested it all seems great and working. I then tested with a user outside of my GitHub org and that let them in too! (Although with no permissions). I need to reduce the scope of the access to only users in my GitHub org.

I can't see anywhere on the OAuth App settings which specifies scope. Does anyone have any experience of this?