XCP-ng 7.6 RC1 available
This is what I see when I install guest-tools after migrating the VM to the 7.6 host.
Detected `Debian GNU/Linux 9.5 (stretch)' (debian version 9).
The following changes will be made to this Virtual Machine:
- packages to be installed/upgraded:
This is the correct version of the tools in XCP-ng 7.6 and is the same as in XCP-ng 7.5. It was 7.9.0 in 7.4.
Using yum to upgrade does give you the right version of the guest tools ISO.
So we need to find out why XCP-ng Center reports version 7.4.
Does anyone know how to check using
xein CLI to see if the wrong version number is reported by
xapidirectly or is coming from a bug in XCP-ng Center?
- packages to be installed/upgraded:
This is what I see, not sure how that correlates to the correct tools build for 7.6
xe vm-param-get param-name=PV-drivers-version uuid=3a8a717f-c998-f05f-d096-f486a4990d1
major: 7; minor: 4; micro: 50; build: 1
I think the tools were built by XS before 7.5 was released and still carry the 7.4 version number, but they are the latest.
@olivierlambert honestly, my problem is that i was using 7.4 and i upgraded to 7.6, which made a perfectly stable pool pretty unstable.
It would have been really helpful to read a warning beforehand about this nasty bug which still exists in 7.6 as you were aware at that point.
'know you're doing it at your own risk and be prepared to fix any issues that would arise, especially unforeseen upgrade issues'
@Adde Wayne's issues are not related to the update via
yum, they're related to a bug in our replacement of the proprietary
emu-manager(for which we'll release update candidates today).
@stormi my problem isn't the bug, there always be bugs.
My problem is that there is no proper communication about it still. I think it is a serious issue about which you know before the 7.6 release as it was tested in rc phase apparently.
It should have been mentioned when 7.6 was released, so anybody be aware what they're risking with upgrading.
Anyhow, I'm glad that the fix is coming.
@wayne while it was found during the testing phase for 7.6, it was already present in 7.5 and hadn't been detected until late, so it let us assume that only few users were affected and that is was not worse to release 7.6 with it (and fix it fast) than it had been releasing 7.5 with it. We did not foresee that people still in 7.4 would skip 7.5 and discover the bug with 7.6.
That last comment is not intended as criticism of users who'd skip a release. It's just an explanation of why we thought it would not harm to release the 7.6 release as it was.
FYI The newly released xcp-emu-manager-0.0.6-2.x86_64.rpm has resolved the migration issues that i could produce.
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.
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
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.