Not until we can have our own piece of code doing it. Right now, it's a binary that's not Open Source made by Citrix, we cannot legally re-distribute it.
Vates
People working at Vates
Posts
-
RE: GPU Virtualization
-
RE: restore metadata for pool -> incompatible version
*** 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.txtto 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
-
RE: Migrate windows VM from Xenserver 8.4 to XCP-ng 8.3.0 (GPLv2)
Use "warm migration" then. VM/advanced view/warm migration button.
-
RE: Staring up a shutdown VM in XO 6
Hi,
It's coming next month. You can even upvote as a priority: https://feedback.vates.tech/posts/1/vm-complete-lifecycle-management
-
RE: Migrate windows VM from Xenserver 8.4 to XCP-ng 8.3.0 (GPLv2)
Hi,
It's possible your XenServer 8.4 has slightly more recent packages so it won't work. You can use continuous replication or warm migration to achieve the goal of migrating to XCP-ng.
-
RE: GPU Virtualization
Hi,
It is indeed possible. See https://xcp-ng.org/forum/topic/8342/gpu-support-and-nvidia-grid-vgpu/33 for more info.
-
RE: XCP-ng 8.3 updates announcements and testing
@stormi Yes, I'm also affected in here, due to an USB device that's disabled by default.
