Issues with live vm migration on 2 ryzen hosts xcp-ng

I realise to do live migrations you should use 2 similar, ideally identical, cpu’s on the hosts.

My hosts have the following cpu

Host 1

AMD Ryzen 5 2600 Six-Core Processor

Host 2

AMD Ryzen 3 3200G with Radeon Vega Graphics

I get ‘operation failed’ if I try to live migrate, with the following log below.

I am learning xcp-ng just for fun so not vital that this feature works - just trying to understand why it doesn’t.


“vm”: “c0ac518b-44c8-f799-68b6-44c7781b68d7”,
“mapVifsNetworks”: {
“d09799e7-556f-ace3-9576-0964fa9cabd7”: “76839e14-8714-b9fb-2cf2-4298fbb5ff36”
“migrationNetwork”: “76839e14-8714-b9fb-2cf2-4298fbb5ff36”,
“sr”: “e1176db5-f5f5-278f-7a7c-586cdfcb55a9”,
“targetHost”: “e6f5f2de-719f-491f-b86b-daeee71b8662”
“code”: 21,
“data”: {
“objectId”: “c0ac518b-44c8-f799-68b6-44c7781b68d7”,
“message”: “operation failed”,
“name”: “XoError”,
“stack”: “XoError: operation failed
at factory (/opt/xo/xo-builds/xen-orchestra-202023041900/packages/xo-common/src/api-errors.js:21:32)
at /opt/xo/xo-builds/xen-orchestra-202023041900/packages/xo-server/src/api/vm.js:508:15
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at runNextTicks (internal/process/task_queues.js:66:3)
at processImmediate (internal/timers.js:429:9)
at Object.migrate (/opt/xo/xo-builds/xen-orchestra-202023041900/packages/xo-server/src/api/vm.js:497:3)
at Api.callApiMethod (/opt/xo/xo-builds/xen-orchestra-202023041900/packages/xo-server/src/xo-mixins/api.js:293:20)”

I’ve never use XCP-NG nor Xen in general, but it appears this is the actual error:

I googled that and found this:

If you already have Xen Tools installed in the guest, then I don’t know anything further to help.

if there are feature differences in the CPU then it will often have issues with live migrations.

I think you are right…installing the Xen Tools may help :roll_eyes:…thanks