Community version doesn't have a release number, but a commit version on master. Please check you are on the latest commit and rebuild 🙂

That's correct. There's no more updates, that's why you MUST upgrade to 8.2 (see https://xcp-ng.org/docs/releases.html#all-releases )

@olivierlambert Done ✅

@wade_solarch Short answer: try to avoid that.

Back in the old XenServer days, you had to manually change the cpu feature flags so it would work at all.

https://xcp-ng.org/docs/requirements.html#pool-requirements
This confirms that you can't mix Intel & AMD in a pool

https://xcp-ng.org/docs/requirements.html#pool-requirements
This explains Heterogeneous pools a little

@stevewest15 Happy to help 😉

@Darkbeldin I did that and the job still failed.

{ "data": { "mode": "delta", "reportWhen": "failure" }, "id": "1646508682255", "jobId": "933a38ad-48d8-48ed-bbec-e037639c9d13", "jobName": "Sage", "message": "backup", "scheduleId": "c7da8664-c4a3-41f3-82a6-c065da75b3db", "start": 1646508682255, "status": "failure", "infos": [ { "data": { "vms": [ "13e70ae1-3223-7b94-dc59-c31f7416af82" ] }, "message": "vms" } ], "tasks": [ { "data": { "type": "VM", "id": "13e70ae1-3223-7b94-dc59-c31f7416af82" }, "id": "1646508683162", "message": "backup VM", "start": 1646508683162, "status": "failure", "tasks": [ { "id": "1646508683673", "message": "snapshot", "start": 1646508683673, "status": "success", "end": 1646508688331, "result": "fd17d98f-1f25-4671-7321-6416fb3de129" }, { "data": { "id": "35f70147-809e-4bec-9531-927d187fce7c", "isFull": true, "type": "remote" }, "id": "1646508688332", "message": "export", "start": 1646508688332, "status": "failure", "tasks": [ { "id": "1646508688372", "message": "transfer", "start": 1646508688372, "status": "failure", "end": 1646513475586, "result": { "canceled": false, "method": "GET", "url": "https://10.131.200.3/export_raw_vdi/?format=vhd&vdi=OpaqueRef%3Ac9d9f6be-fb17-4993-bc3a-c11405ba7f6e&session_id=OpaqueRef%3A5fb25acb-a5e3-4f3c-9dc1-49f55a527d74&task_id=OpaqueRef%3Af73a85cd-33ae-4b8e-bfad-c9139f035e06", "timeout": true, "message": "HTTP connection has timed out", "name": "Error", "stack": "Error: HTTP connection has timed out\n at IncomingMessage.emitAbortedError (/usr/local/lib/node_modules/xo-server/node_modules/http-request-plus/index.js:83:19)\n at Object.onceWrapper (node:events:509:28)\n at IncomingMessage.emit (node:events:390:28)\n at IncomingMessage.patchedEmit (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/configure.js:118:17)\n at IncomingMessage.emit (node:domain:475:12)\n at IncomingMessage._destroy (node:_http_incoming:179:10)\n at _destroy (node:internal/streams/destroy:102:25)\n at IncomingMessage.destroy (node:internal/streams/destroy:64:5)\n at TLSSocket.socketCloseListener (node:_http_client:407:11)\n at TLSSocket.emit (node:events:402:35)" } } ], "end": 1646513475586, "result": { "canceled": false, "method": "GET", "url": "https://10.131.200.3/export_raw_vdi/?format=vhd&vdi=OpaqueRef%3Ac9d9f6be-fb17-4993-bc3a-c11405ba7f6e&session_id=OpaqueRef%3A5fb25acb-a5e3-4f3c-9dc1-49f55a527d74&task_id=OpaqueRef%3Af73a85cd-33ae-4b8e-bfad-c9139f035e06", "timeout": true, "message": "HTTP connection has timed out", "name": "Error", "stack": "Error: HTTP connection has timed out\n at IncomingMessage.emitAbortedError (/usr/local/lib/node_modules/xo-server/node_modules/http-request-plus/index.js:83:19)\n at Object.onceWrapper (node:events:509:28)\n at IncomingMessage.emit (node:events:390:28)\n at IncomingMessage.patchedEmit (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/configure.js:118:17)\n at IncomingMessage.emit (node:domain:475:12)\n at IncomingMessage._destroy (node:_http_incoming:179:10)\n at _destroy (node:internal/streams/destroy:102:25)\n at IncomingMessage.destroy (node:internal/streams/destroy:64:5)\n at TLSSocket.socketCloseListener (node:_http_client:407:11)\n at TLSSocket.emit (node:events:402:35)" } } ], "end": 1646513527913, "result": { "canceled": false, "method": "GET", "url": "https://10.131.200.3/export_raw_vdi/?format=vhd&vdi=OpaqueRef%3Ac9d9f6be-fb17-4993-bc3a-c11405ba7f6e&session_id=OpaqueRef%3A5fb25acb-a5e3-4f3c-9dc1-49f55a527d74&task_id=OpaqueRef%3Af73a85cd-33ae-4b8e-bfad-c9139f035e06", "timeout": true, "message": "HTTP connection has timed out", "name": "Error", "stack": "Error: HTTP connection has timed out\n at IncomingMessage.emitAbortedError (/usr/local/lib/node_modules/xo-server/node_modules/http-request-plus/index.js:83:19)\n at Object.onceWrapper (node:events:509:28)\n at IncomingMessage.emit (node:events:390:28)\n at IncomingMessage.patchedEmit (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/configure.js:118:17)\n at IncomingMessage.emit (node:domain:475:12)\n at IncomingMessage._destroy (node:_http_incoming:179:10)\n at _destroy (node:internal/streams/destroy:102:25)\n at IncomingMessage.destroy (node:internal/streams/destroy:64:5)\n at TLSSocket.socketCloseListener (node:_http_client:407:11)\n at TLSSocket.emit (node:events:402:35)" } } ], "end": 1646513527914 }

Hi, thanks in advance.
I used the XCP-ng Center to connect to Host and restart the toolstack.
After that everything is going well.
Thank you very much.

VDI to coalesce number should decrease over time yes. If it's not, you might have a coalesce issue in your storage, check the /var/log/SMlog in the relevant host (master for shared storage, the host attached to its local storage otherwise). Rescan will scan for the LV/VHD files. But coalesce is automatically checked/started every 5 minutes. Coalesce can take time (depending on SR read/write and quantity to "merge"). Next releases will have a visible task for pending coalesce (next major XCP-ng release). Until then, you can do a ps axf | grep coalesce to see if there's something happening.

@nickdsl can you please share a terraform code example and the necessary commands to reproduce the problem? I'm not sure I understand what happened without seeing a concrete example of the problem.

@olivierlambert Done: https://github.com/vatesfr/xen-orchestra/commit/33b45d2eda2ce6d8071541da246bdcfd06b133b8

It's not perfect but that should help 🙂

Example:

vm.start { "id": "123e4f2b-498e-d0af-15ae-f835a1e9f59f", "bypassMacAddressesCheck": false, "force": false } { "errors": [ "R620-L3: VM_REQUIRES_SR(OpaqueRef:21fa00fc-62ce-4694-8b49-fcecd600a89e, OpaqueRef:4dd615a7-9a8c-4698-aceb-c10f782321c8)", "R620-L1: HOST_NOT_ENOUGH_FREE_MEMORY(216430280704, 18778341376)", "R620-L2: VM_REQUIRES_SR(OpaqueRef:21fa00fc-62ce-4694-8b49-fcecd600a89e, OpaqueRef:4dd615a7-9a8c-4698-aceb-c10f782321c8)" ], "message": "", "name": "Error", "stack": "Error: at Xapi._startVm (file:///home/julien/dev/vatesfr/xen-orchestra/packages/xo-server/src/xapi/index.mjs:1358:15) at Xapi.startVm (file:///home/julien/dev/vatesfr/xen-orchestra/packages/xo-server/src/xapi/index.mjs:1393:7) at Api.callApiMethod (file:///home/julien/dev/vatesfr/xen-orchestra/packages/xo-server/src/xo-mixins/api.mjs:307:20)" } 2 julien-f committed to vatesfr/xen-orchestra feat(xo-server): better info when failing to start a VM Fixes https://xcp-ng.org/forum/post/47329

@fohdeesha Thanks for the thorough explanation. Took me a while to get the network configuration working, but I think I've got it all working nicely now from a stock Ubuntu cloud image.

For those interested:

My cloud init:

#cloud-config hostname: {name} users: - default ssh_import_id: - gh:<username> package_update: true package_upgrade: true packages: - xe-guest-utilities byobu_by_default: system runcmd: - systemctl disable cloud-init power_state: delay: "+1" mode: reboot message: Rebooting system timeout: 5 condition: True

My network config:

version: 2 ethernets: eth0: addresses: [] dhcp-identifier: mac dhcp4: true nameservers: search: - my.nameserver.local

@Danp K great, thanks.

I came across this post in a google search.

"xe vm-param-cleaner" mentioned earlier doesnt seem to exist anymore. However the following command worked for me:

xe vm-param-clear uuid=<vm_uuid> param-name=blocked-operations

@fohdeesha Great, thank you!

@olivierlambert well, yes, there is definitely room for improvement on that part of the gui ;). although I was able to get any other plugin working 😛 no worries though, the quick fix is to remove the (optional) 😉

There's an open issue about this on Github, just check on the forum 🙂

Something is maybe interfering with websockets. Have you tried in private mode in case there's a problem with your cookies?

If you have pro support, that might be the right time to open a support ticket so we can assist you remotely 🙂

Good 🙂 If there's anything wrong in the doc, you can correct it!