XenServer-8 to XCP-NG

rfx77

@ricardowz Are you able do attach the vhds (vdi) to a new vm after reinstalling with xcpng. so no import but using the old files.

if this works you could export the vdi to a vhd or raw and reimport it.

We didnt update to the latest xenserver version so according to your test we may be safe, but what i dont want is to reinstall with xcpng an than the vms are dead.

we have an old server so i may install xcpng there and migrate over from xenserver. than migrate back afterwards. but this is all very time-consuming in that situation.

ricardowz

@rfx77 said in XenServer-8 to XCP-NG:

@ricardowz Are you able do attach the vhds (vdi) to a new vm after reinstalling with xcpng. so no import but using the old files.

if this works you could export the vdi to a vhd or raw and reimport it.

We didnt update to the latest xenserver version so according to your test we may be safe, but what i dont want is to reinstall with xcpng an than the vms are dead.

we have an old server so i may install xcpng there and migrate over from xenserver. than migrate back afterwards. but this is all very time-consuming in that situation.

Is your XenCenter displaying the countdown message?

The current Trial Edition license expires in ... days. You will not be able to start VMs after expiry.

If it's, I think the in place migration is not gonna work for you to. For me, it looks like it does not matter if it's not on the latest version, but if you installed some upgrade after initial installation of XenServer.

rfx77

@ricardowz
No Warning. Updates are from 2. April. I attached the Screenshot.

Can someone confirm that we could just "upgrade" to XCP-NG 8.3 and the VMs will run?

Greetings

reiichi001

I've got a similar situation to this thread.

Currently, we have a mix of Citrix Hypervisor 8 (8.2 CU1 LTS), which is going end of support later this year. We use a mix of standard license and xenserver express licenses.

I've been testing out migrations to both XenServer 8 through Citrix and XCP-Ng, but most of the staff I work with primarily use XenCenter for managing VMs, and XCP-Center hasn't quite had the ability to keep up with recent changes. We do have XOA as well, but as we make use of importing/exporting VM images quite often, XOA doesn't quite work work well here, which would mean having to have XenCenter for our licensed VMs and XCP-Center for our unlicensed ones if we go with XCP. But that's a tangent for context.

What I've noticed is that I can upgrade from CHU8 to XS8 or XCP 8.2.1 fine, but there doesn't appear to be any way to "upgrade" or migrate from XS8 to XCP8.

And exported XVA files from XS8 cannot be imported to XCP 8.2.1 or 8.3, which is a blocker if we want to fully migrate to XCP to keep our environment uniform.

If I put in a XCP-Ng ISO (either 8.2.1 or 8.3), it does not offer the ability to upgrade from a XS8 install. XOA is also unable to copy a XS8 VM over to XCP 8.3.

olivierlambert

Hi,

You can use warm migration to solve this. Also, we provide pro support and services to help you to migrate, it's probably a lot of time saved with our expertise

reiichi001

@olivierlambert said in XenServer-8 to XCP-NG:

You can use warm migration to solve this. Also, we provide pro support and services to help you to migrate, it's probably a lot of time saved with our expertise

Reply

I have tried this over XOA, but it does not work with even a cold migration where the VM is shut down.

This is the XOA error I receive when trying to go from XS8 (DBV 2024.0229) to XCP-ng 8.3 (build date Oct 11, 2024 4:26:51 AM / DBV 0.0.1 reported).

We use XOA Enterprise 5.103.0 in this environment but would be planning to use XCP-Ng 8.2.1 community for these VMs in particular.

If the recommendation would be to open a support ticket from my XOA account to help ease this process, I can do so. ...we were hoping XS8 would keep an indefinite trial, but that has been shown to not be in Citrix's interests.

vm.migrate
{
  "vm": "b62f3bf3-72b9-ad40-885f-77c69d5f0f1a",
  "mapVifsNetworks": {},
  "migrationNetwork": "eeb0d173-74b2-8f00-d5be-906339714f42

",
  "sr": "e20f5eac-f34d-7151-b1f6-5d6cb960843d",
  "targetHost": "523f39b6-d4e8-4347-94e2-5c6c9c9705ba"
}
{
  "code": "IMPORT_INCOMPATIBLE_VERSION",
  "params": [],
  "task": {
    "uuid": "816c7f21-8825-4ad8-1080-13c87edda67b

",
    "name_label": "Async.VM.assert_can_migrate",
    "name_description": "",
    "allowed_operations": [],
    "current_operations": {},
    "created": "20250204T00:32:55Z",
    "finished": "20250204T00:32:57Z",
    "status": "failure",
    "resident_on": "OpaqueRef:33c97776-8b37-455a-ab62-13139da98726",
    "progress": 1,
    "type": "<none/>",
    "result": "",
    "error_info": [
      "IMPORT_INCOMPATIBLE_VERSION"
    ],
    "other_config": {},
    "subtask_of": "OpaqueRef:NULL",
    "subtasks": [],
    "backtrace": "(((process xapi)(filename ocaml/xapi/importexport.ml)(line 373))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 39))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 39))((process xapi)(filename ocaml/xapi/xapi_vm_migrate.ml)(line 1866))((process xapi)(filename ocaml/xapi/message_forwarding.ml)(line 2544))((process xapi)(filename ocaml/xapi/rbac.ml)(line 188))((process xapi)(filename ocaml/xapi/rbac.ml)(line 197))((process xapi)(filename ocaml/xapi/server_helpers.ml)(line 77)))"
  },
  "message": "IMPORT_INCOMPATIBLE_VERSION()",
  "name": "XapiError",
  "stack": "XapiError: IMPORT_INCOMPATIBLE_VERSION()
    at Function.wrap (file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/_XapiError.mjs:16:12)
    at default (file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/_getTaskResult.mjs:13:29)
    at Xapi._addRecordToCache (file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/index.mjs:1068:24)
    at file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/index.mjs:1102:14
    at Array.forEach (<anonymous>)
    at Xapi._processEvents (file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/index.mjs:1092:12)
    at Xapi._watchEvents (file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/index.mjs:1265:14)"
}```

olivierlambert

Warm migrate doesn't use migration. It's better than cold migration.

Are you sure you have used specifically that feature?

rfx77

@olivierlambert
So when i read the posts from @reiichi001 it is NOT possible to do an implace-upgrade from XenServer-8 to XCP-NG (8.2.1 or 8.3)

Are there any options now? Do you know of someone who has done this sucessfully without backup/restore or such thing?

Greetings, Franz

olivierlambert

Question for @stormi or @yann

stormi

XenServer 8 is actually XenServer 8.3 (or 8.4 let's not complicate things, for our matter here 8.3 is good enouhg).

So you can migrate it to XCP-ng 8.3 but not to XCP-ng 8.2.1.