Because doing an update without rebooting doesn't reload the updated main programs, like XAPI. A host in only updated after a full reboot.

*** Warning *** This process and the attached file is only appropriate for restoring towards XAPI 25.27.0. Use this procedure at your own risk. We recently put together a solution for a customer that had this exact issue. Below are the basic instructions to update freshly installed 8.3 hosts to the set of updates that were available on October 24th, including XAPI 25.27.0 -- Install XCP-ng 8.3.0 LTS scp the attached package_list_for_update.txt to the hosts /root. This file contains package versions from our update repository on October 24th. then, on the hosts, from /root: cat package_list_for_update.txt | xargs yum update-to -y This will output a lot of messages saying that this or that package is not found. That's expected. Then it will proceed to install the updates. In my tests, 73 of them. Once the update completes, reboot the host. Restore the XAPI metadata Restart XAPI Verify that XAPI is running. Install the remaining updates with yum update -y. Reboot package_list_for_update.txt

Thank you guys! Problem temporarily fixed by Vates support,

@MathieuRA I disabled Traefik and reverted to my old XO config (port 443, ssl encryption, http to https redirection), rebuild the docker container using your branch and tested: it is working fine on my end now Thank you very much! I did not expect this to get fixed so fast!

@Pilow error reporting is a feature in itself . Thanks

Yes!! Congrats for everyone (including you for the feedback @dcskinner !)

I just learned something new, thats awesome

@McHenry Turning off the Manage via Windows update first + tools uninstall + reinstall should take care of it.

Use "warm migration" then. VM/advanced view/warm migration button.

That worked; thank you!!!

Excellent news

@MathieuRA Thank you, perfect Br,

@Danp said in VDI not showing in XO 5 from Source.: xe vdi-param-list uuid= Hi Dan, [18:52 mycsskvdcxcp03 ~]# xe vdi-param-list uuid=5f899e22-f3a7-4f0b-8de6-2b8058c0f575 uuid ( RO) : 5f899e22-f3a7-4f0b-8de6-2b8058c0f575 name-label ( RW): ADSIM-UAT_DISK01 name-description ( RW): is-a-snapshot ( RO): false snapshot-of ( RO): d31f2db0-be21-4794-b858-1bea357869c8 snapshots ( RO): snapshot-time ( RO): 19700101T00:00:00Z allowed-operations (SRO): clone; snapshot current-operations (SRO): sr-uuid ( RO): 5d22cba7-fbf6-a03b-bb73-9ffba3a3ee75 sr-name-label ( RO): SR-HDD-DEV-2 vbd-uuids (SRO): c6f4c7fa-4f6f-7999-d13c-3a29d887d828 crashdump-uuids (SRO): virtual-size ( RO): 171798691840 physical-utilisation ( RO): 50272698880 location ( RO): 5f899e22-f3a7-4f0b-8de6-2b8058c0f575 type ( RO): User sharable ( RO): false read-only ( RO): false storage-lock ( RO): false managed ( RO): true parent ( RO) [DEPRECATED]: <not in database> missing ( RO): false is-tools-iso ( RO): false other-config (MRW): xenstore-data (MRO): sm-config (MRO): host_OpaqueRef:c3426081-ce96-507b-a219-8d2cb124c3ad: RW; read-caching-enabled-on-e1594701-28e9-4127-858e-74d4663669f8: true on-boot ( RW): persist allow-caching ( RW): false metadata-latest ( RO): false metadata-of-pool ( RO): <not in database> tags (SRW): cbt-enabled ( RO): false [18:54 mycsskvdcxcp03 ~]# Best regards, Azren

@dinhngtu I believe it was changing the guest TSC Mode that seems to have done the trick.

No idea if anyone have "fixed" anything No, the XO commit 5fcb6 hang for ~3 min at reboot today. edit: I disabled the sceduled reboot yesterday.

Yay! Santa came early this year!!

@olivierlambert said in Xen Orchestra Node 24 compatibility: Can you reproduce the issue on XOA? Or it's only on the sources + your current OS? We do not have a XOA license (yet) which is why I am currently solely using XO from sources. Therefore currently not able to reproduce on XOA. OS is Debian 13.

Hi, It's coming next month. You can even upvote as a priority: https://feedback.vates.tech/posts/1/vm-complete-lifecycle-management