VM migration failure

bberndt

I'll post the error below. Im using XO Xen Orchestra, commit 80e72
Master, commit 48603, from sources which I update form time to time.

Im trying to migrate sme VMs from XCP 7.6 to a different host that has 8.3 on it. Keep getting errors. I can migrate from a XCP 8.2 to the same destination I want, in the error. And from the 7.6 to 8.2.

is 7.6 and 8.3 too big a jump for XO? or am I a little far old and need an update? And XCP Center doesn't connect to XCP 8.3

xo_error.txt

olivierlambert

Hi,

XO isn't the culprit, it's likely the Xen version jump (so it's an XCP-ng thing). You could forever remove XO from the equation by simply trying to migrate with xe CLI, I'm sure the result will be similar.

What kind of OS are you migrating?

stormi

We do advise to jump to 8.2 from earlier releases, before jumping to 8.3.

bberndt

A couple Windows 2016, and 2019, and a couple Rocky Linux 8 is what Im moving.

I'll see if I have an 8.2 host suited (not too different CPU) to be a middle man.

thanks.

bberndt

found a similar machine that was testing some XCP-ng 8.3 stuff on it.
Re-installed 8.2
Now can't add to XO at all. All I can find for people with this error is adding a host thats already in a pool. In this case, there are no pools.

hrm.

server.enable
{
  "id": "a6cce2cd-f3c8-[redacted]-2bfce24a6d96"
}
{
  "poolId": "b5a4db02-f996-[redacted]-7ed3cad86788",
  "connectedServerId": "f1f0aa28-f820-[redacted]-7c15c1686461",
  "connectingServerId": "a6cce2cd-f3c8[redacted]-2bfce24a6d96",
  "message": "this pool is already connected",
  "name": "PoolAlreadyConnected",
  "stack": "PoolAlreadyConnected: this pool is already connected
    at XenServers.connectXenServer (file:///opt/xo/xo-builds/xen-orchestra-202505021422/packages/xo-server/src/xo-mixins/xen-servers.mjs:358:15)
    at Xo.enable (file:///opt/xo/xo-builds/xen-orchestra-202505021422/packages/xo-server/src/api/server.mjs:121:3)
    at Task.runInside (/opt/xo/xo-builds/xen-orchestra-202505021422/@vates/task/index.js:175:22)
    at Task.run (/opt/xo/xo-builds/xen-orchestra-202505021422/@vates/task/index.js:159:20)
    at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202505021422/packages/xo-server/src/xo-mixins/api.mjs:469:18)"
}

bberndt

removed the failed server connection.

Restarted xo-server service.

Added new host again. Seems fine now.

In hind sight, I could have very well recycled a DHCP ip here as well, if that is a known issue...