XCP-ng 7.6 RC1 available
Thanks, this is good news!
@stormi Yes it is!!
@conradical Since you had issues in 7.5 also, would you mind testing
xcp-emu-manager-0.0.3-1.2.x86_64.rpmwhich is still in the
yum install xcp-emu-manager --enablerepo='xcp-ng-updates-testing'
I don't have that pool anymore because I just yum updated it. If I get time i'll deploy 7.5 again.
olivierlambert Vates 🪐 Co-Founder🦸 CEO 🧑💼
Yeah, the current patch is able to make it working if the load is not too huge. We are still working to get it fully functional
@olivierlambert said in XCP-ng 7.6 RC1 available:
e it working if the load is not
I had this happen on VMs even when they had no load, but now they work. I suspect it's ignoring other progress messages that were the problem in my case.
This issue still appears to be present in 7.6.
It it resolved in 7.6.3? I'm reluctant to pull hosts down without being able to move VM's safely without having to stop them.
There is no such thing as XCP-ng 7.6.3 (but there's XCP-ng Center 7.6.3). There's just XCP-ng 7.6 with latest updates applied.
The migration issues discussed above have been fixed in an update to the
xcp-emu-managerpackage. That specific update does not require a reboot of the hosts: only a toolstack restart.
You can either apply it from Xen Orchestra, or from command line with
yum update xcp-emu-manager. Then
Once all hosts have the update, migration should be smooth.
Then I recommend that you apply all the other updates, but you may want to wait for one day or two because there are security fixes on their way.
stormi Vates 🪐 XCP-ng Team 🚀
Actually, looks like I had already written something about it in the Updates Howto: https://github.com/xcp-ng/xcp/wiki/Updates-Howto#a-special-word-about-xcp-ng-75-76-and-live-migrations