XenServer-8 to XCP-NG
-
When we released XCP-ng 8.3, migration from XenServer 8 did work. However, XS8 has kept on evolving, rolling-release style, so it's possible that the current installation ISOs for XCP-ng 8.3 are not recent enough to migrate a current day XenServer 8.
However, the problems I would expect are not the ones you describe. I would expect the upgrade process to go smoothtly, and then the XAPI service fail to start because our version of XAPI sees a database that is too recent.
If no choices are displayed to upgrade an existing XenServer 8 with the 8.3 ISO, the reason will be provided in the logs in
/tmp/install-log(ALT+RIGHT thenview /tmp/install-log, IIRC). It can be several things: a first boot process not complete on XS side, booting in BIOS mode when the system is currently UEFI, ... But there's also the possibility that the platform number we use to detect an upgradeable product has changed. -
@stormi said in XenServer-8 to XCP-NG:
But there's also the possibility that the platform number we use to detect an upgradeable product has changed.
This is probably the case. When I tried in-place upgrades, XCP would sometimes see it, but not always. I expected that to be the case when trying out XCP 8.2.1, but this would still happen occasionally on XCP 8.3 as well. (Given that XenServer 8 is reporting itself as 8.4, Citrix probably did this on purpose.)
I'm assuming this is also why XVA export/import also doesn't work and live migrations don't work?
I did eventually just spin up Xen Orchestrator Community Edition in my environment so I could use Warm Migrations, as XO Enterprise does not offer those. (Knowing that if something went wrong, I wouldn't be able to get support for that, but it beats out having to rebuild around 200 customized-for-clients VMs and migrating their data using software tools)
-
@stormi said in XenServer-8 to XCP-NG:
When we released XCP-ng 8.3, migration from XenServer 8 did work. However, XS8 has kept on evolving, rolling-release style, so it's possible that the current installation ISOs for XCP-ng 8.3 are not recent enough to migrate a current day XenServer 8.
However, the problems I would expect are not the ones you describe. I would expect the upgrade process to go smoothtly, and then the XAPI service fail to start because our version of XAPI sees a database that is too recent.
If no choices are displayed to upgrade an existing XenServer 8 with the 8.3 ISO, the reason will be provided in the logs in /tmp/install-log (ALT+RIGHT then view /tmp/install-log, IIRC). It can be several things: a first boot process not complete on XS side, booting in BIOS mode when the system is currently UEFI, ... But there's also the possibility that the platform number we use to detect an upgradeable product has changed.
I'll try to collect the logs, thank your for the
What if the XAPI service fail to start ? Is it recoverable ? Should I study @ricardowz because it'll be safer ?
@reiichi001 thanks for your comment I didn't know about this option. Did it work properly on your side for all the VMs ?
-
@psylo We are working on updating XAPI in XCP-ng 8.3. When that's done, a simple
yum updateshould be enough to recover. But for now @ricardowz's or @reiichi001's way is safer. -
@stormi Thank you for your reply.
