@olivierlambert Thank you. I thought maybe I was losing my mind/eye sight, especially after reading that google search indicating there was a start button in 6.

*** 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

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

Hi, It is indeed possible. See https://xcp-ng.org/forum/topic/8342/gpu-support-and-nvidia-grid-vgpu/33 for more info.

@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

That worked; thank you!!!

I just learned something new, thats awesome

Ping @team-xo-backend

Thank you guys! Problem temporarily fixed by Vates support,

not better with production upgraded to 6.0.1 (XOA and XO Proxies) we will open a support ticket ps : if we delog/relog from XOA with another user, we have better chance to get the file restore working... not 100% very unstable is there a link ?!

Ah indeed, labels are honored even in the case of a warm migration. We used it ourselves when we migrated from Intel to AMD CPUs, it was really the best compromise betweeen live and cold (especially when you change the CPU vendor). Glad to see it's helping many people and companies now

Excellent news

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

@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.

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

@Pilow error reporting is a feature in itself . Thanks

Yay! Santa came early this year!!