XCP-ng 7.6 RC1 available

WBA

I just upgraded from version 7.5 to 7.6 using yum upgrade, all seemed to go without error.
When I started to migrate our vm's from one of the 7.5 hosts to the new 7.6 host the vm's would be hung and unresponsive on the new host when the migration completed.
A forced stop and a fresh start of the VM brought the VMs back up.
After finding this post and seeing the notes about "xe-guest-utilities" I noticed that when I install the guest-tools the version remains the same, in fact the version remains at 7.4 looking at it in XCP-ng Center.
Optimized (version 7.4 installed)

This is what I see when I install guest-tools after migrating the VM to the 7.6 host.
root@# /mnt/Linux/install.sh
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:
- xe-guest-utilities_7.10.0-1_amd64.deb

Continue? [y/n] y

(Reading database ... 42324 files and directories currently installed.)
Preparing to unpack .../xe-guest-utilities_7.10.0-1_amd64.deb ...
Unpacking xe-guest-utilities (7.10.0-1) over (7.10.0-1) ...
Setting up xe-guest-utilities (7.10.0-1) ...
Processing triggers for systemd (232-25+deb9u4) ...

You should now reboot this Virtual Machine.
root@#

What is the correct version of guest-tools?
Are guest-tools not being updated because I have used yum to upgrade for the last 2 versions?
I should note these are 95% Linux VM's

Thanks, Will

stormi

WBA said in 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.
root@# /mnt/Linux/install.sh
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:

xe-guest-utilities_7.10.0-1_amd64.deb

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 xe in CLI to see if the wrong version number is reported by xapi directly or is coming from a bug in XCP-ng Center?

WBA

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

Thx Will

stormi

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.

wayne

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.

Adde

wayne
https://github.com/xcp-ng/xcp/wiki/Upgrade-Howto#from-command-line
'know you're doing it at your own risk and be prepared to fix any issues that would arise, especially unforeseen upgrade issues'

//Adde

stormi

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

Adde

stormi

Aha Ok then I understand
Sorry!!

wayne
Sorry for that

wayne

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.

stormi

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.

stormi

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.

conradical

FYI The newly released xcp-emu-manager-0.0.6-2.x86_64.rpm has resolved the migration issues that i could produce.

stormi

Thanks, this is good news!

conradical

stormi Yes it is!!

stormi

conradical Since you had issues in 7.5 also, would you mind testing xcp-emu-manager-0.0.3-1.2.x86_64.rpm which is still in the updates_testing repository too?

yum install xcp-emu-manager --enablerepo='xcp-ng-updates-testing'

conradical

stormi
I don't have that pool anymore because I just yum updated it. If I get time i'll deploy 7.5 again.

olivierlambert

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

conradical

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.

glipschitz

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.

Cheers
Greg

stormi

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-manager package. 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 xe-toolstack-restart.

Once all hosts have the update, migration should be smooth.