-
Updated 3 hosts and so far no Problems. Transferred some machines etc no bad effects.
-
Hello everyone. I'm back from holidays with update candidates that need testing!
XCP-ng 7.6
xcp-ng-xapi-plugins
yum update xcp-ng-xapi-plugins --enablerepo=xcp-ng-updates_testing
This is the most important update. It fixes host memory consumption issues that could go as far as crashing several hosts at the same time (especially if EPEL repositories were active, which shouldn't be the case but often was prior to XCP-ng 8.0 where they are already present but disabled by default). Already fixed in XCP-ng 8.0.
Post-install:
xe-toolstack-restart
microcode_ctl
yum update microcode_ctl --enablerepo=xcp-ng-updates_testing
Microcode update for the SandyBridge family of CPUs regarding the MDS attacks.
Post-install: reboot if you want it to be taken into account.
xcp-ng-pv-tools
yum update xcp-ng-pv-tools --enablerepo=xcp-ng-updates_testing
Linux guest tools: support for SLES 15 SP1, updated README, support for recent CoreOS.
Post-install: nothing to do.
xen
yum update xen-dom0-libs xen-dom0-tools xen-hypervisor xen-libs xen-tools --enablerepo=xcp-ng-updates_testing
Avoids possible memory corruption when forcibly shutting down a VM with AMD MxGPU attached. Or when the guest crashes.
Post-install: reboot to apply the changes.
XCP-ng 8.0
xen + guest templates
yum update xen-dom0-libs xen-dom0-tools xen-hypervisor xen-libs xen-tools guest-templates-json guest-templates-json-data-windows guest-templates-json-data-xenapp guest-templates-json-data-linux guest-templates-json-data-other --enablerepo=xcp-ng-testing
Avoid doing that on several hosts of the same pool at the same time, because the guest-template-json* updates will need to update the XAPI database at the same time. The
/usr/bin/create-guest-templates
tool that is called post-update is not designed to run concurrently (thanks to Silmaril on IRC for finding out at the cost of a broken XAPI database).Changes:
- same fix as in XCP-ng 7.6 regarding VMs with AMD MxGPU attached
- fix a host crash that can occur when you force-shutdown a Windows VM that is in an unclean state
- Windows VMs could hang for more than a minute after live migration
- Windows VMs with the
viridian_reference_tsc
flag enabled could crash during live migration. This fix opens the door to possible performance improvements for your Windows VMs, because following that fix now Citrix advises to setviridian_reference_tsc
andviridian_stimer
flags totrue
for better performance. - Updated Windows VM templates with new default settings that set
viridian_*
to true.
Post-install:
- reboot the host to apply the
xen
changes - consider modifying your existing Windows VM settings for possible better performance. See "After installing this hotfix" in https://support.citrix.com/article/CTX258320
microcode_ctl
yum update microcode_ctl --enablerepo=xcp-ng-testing
Microcode update for the SandyBridge family of CPUs regarding the MDS attacks. XCP-ng 8.0 already contained updated microcodes from Intel when released, before Citrix released a hotfix, but their update contains one additional file so we synced with their package.
Post-install: reboot if you want it to be taken into account.
What we need
As usual, Vates tests the updates internally, but we also rely on the community to widen the test cases and hardware tested, so we need you to install the updates and give us feedback, either positive or negative, before we can consider pushing those updates to everyone!
-
@stormi said in Updates announcements and testing:
XCP-ng 7.6
[...]
microcode_ctl
yum update microcode_ctl --enablerepo=xcp-ng-updates_testing
Microcode update for the SandyBridge family of CPUs regarding the MDS attacks.
Post-install: reboot if you want it to be taken into account.
xcp-ng-pv-tools
yum update microcode_ctl --enablerepo=xcp-ng-updates_testing
I guess that above command for
xcp-ng-pv-tools
should not be the same as the one formicrocode_ctl
XCP-ng 8.0
[...]
microcode_ctl
yum update microcode_ctl --enablerepo=xcp-ng-updates_testing
This command returns error:
# yum update microcode_ctl --enablerepo=xcp-ng-updates_testing Loaded plugins: fastestmirror Error getting repository data for xcp-ng-updates_testing, repository not found
I guess it meant to be:
# yum update microcode_ctl --enablerepo=xcp-ng-testing
as this worked for me.
HTH
-
I installed all these updates for 8.0 and rebooted the host.
The reboot was extraordinary long. The time from shutting ssh session to getting ping packets back again was about 8 minutes. I don't know what it was doing during all this time as I rebooted remotely.
So I rebooted once more to see whether the boot time would be so long again.
This time it was only 1 minutes 46 seconds.The VMs seem to run OK so far, but it's just a test host with two VMs doing almost nothing, so I don't know for sure :-).
-
@MajorTom thanks, I've fixed the post
-
@stormi Installed the updates in our test pool. Until now everything is working. VM migration etc. Also set viridian flags as advised ( xoa vm has this set also? is this OK?)
RegardsChristian
-
I think Viridian will only have an effect on Windows VMs.
-
Thanks to those who tested. Still interested in feedback, including on XCP-ng 7.6.
-
I'll need at least one tester for the latest update candidates on XCP-ng 7.6, and one for 8.0.
-
OK. Installed it on our last 7.6 server. Reboot was OK. VMs run fine. As this is a test host I cannot test more. It runs on AMD so the microcode_ctl should do nothing on our server.
-
@cnaumer Thanks, this is good enough for me at this stage of the testing, so I can push the 7.6 updates now thanks to you!
-
@cnaumer said in Updates announcements and testing:
@stormi Installed the updates in our test pool. Until now everything is working. VM migration etc. Also set viridian flags as advised ( xoa vm has this set also? is this OK?)
RegardsChristian
This was an 8.0 pool here. Just to clarify this.
-
@stormi said in Updates announcements and testing:
I'll need at least one tester for the latest update candidates on XCP-ng 7.6, and one for 8.0.
At 8.0:
I didyum update
, but there are only new versions of guest-templates-json*, so can't quite see anything to check.Just in case I rebooted the host. The reboot took about 1 minute 40 seconds which i s OK for this host.
The test VMs started OK as well.
-
That's enough to check if everything is fine
-
So I have pushed the updates described in https://xcp-ng.org/forum/post/16360 to XCP-ng 7.6 and 8.0 repositories. Thanks for the tests.
-
Blog post about the latest updates: https://xcp-ng.org/blog/2019/09/13/software-updates-for-xcp-ng-7-6-and-8-0/
-
New update candidates for XCP-ng 8.0:
guest-templates*
andxcp-ng-pv-tools
XCP-ng 8.0
guest-templates*
The updated packages add templates for RHEL 8 and derivatives as well as a template for Debian 10.
Instructions there: https://github.com/xcp-ng/xcp/issues/274 (RHEL 8 and derivatives) and https://github.com/xcp-ng/xcp/issues/276 (debian 10).
xcp-ng-pv-tools
The updated package adds support for installing the tools on RHEL 8 and its derivatives (CentOS, Oracle Linux, etc.).
Update: a new revision of the package now also adds tentative support for:
- CloudLinux
- Alpine Linux
- FreePBX (Sangoma Linux)
Instructions there: https://github.com/xcp-ng/xcp/issues/293.
What we need
As usual, Vates tests the updates internally, but we also rely on the community to widen the test cases and hardware tested, so we need you to install the updates and give us feedback, either positive or negative, before we can consider pushing those updates to everyone!
Please use the github issues to provide feedback so this thread here remains clean.
-
installed and tried to use a centos8 template. It does not allow to use UEFI. Is this intended?
-
@cnaumer said in Updates announcements and testing:
installed and tried to use a centos8 template. It does not allow to use UEFI. Is this intended?
"Please use the github issues to provide feedback so this thread here remains clean."
-
Update: a new revision of the
xcp-ng-pv-tools
package now also adds tentative support for:- CloudLinux
- Alpine Linux
- FreePBX (Sangoma Linux)
I don't use those myself so I'm counting on community feedback