-
New update candidates are available to fix the recently disclosed Xen security issues (see http://xenbits.xen.org/xsa/ and https://support.citrix.com/article/CTX246572).
Please test as soon as possible. Objective of the test: make sure that there is no obvious regression. Just tell us that you installed the update candidate, the version of XCP-ng, and whether it works as well as before or not after a reboot.
XCP-ng 7.6
xen-4.7.6-6.4.1.xcpngInstallation of the update candidate:
yum install --enablerepo='xcp-ng-updates_testing' xen-dom0-libs xen-hypervisor xen-tools xen-dom0-tools xen-libsReboot required after the installation.
XCP-ng 7.5
xen-4.7.5-5.8.1.xcpInstallation of the update candidate:
yum install --enablerepo='xcp-ng-updates_testing' xen-dom0-libs xen-hypervisor xen-tools xen-dom0-tools xen-libsReboot required after the installation.
-
Anyone? This update candidate should be as safe as could be and internal tests are OK, but I don't want to push it before I get feedback from a few testers.
-
Updated one host without issue and currently testing.
-
security fix installed. Does it require a reboot of the system?
-
nuts23 yes
-
stormi testhost updated, restored some part of our infrastructur (DC, Mail, ...) on local ZFS pool, connected the VMs to a test network. Runs. A bit slow (more vCPU used than the PCPU can delivier), but runs.
-
stormi said in Updates announcements and testing:
Anyone?
I updated one host in a pool and reboot. It is working as before. Seems no problem. I can't see any diffrence vcpu usage as borzel say.
-
So far so good .. I haven't noticed any visible change in performance like borzel but still monitoring.
-
Since there's an update for both XCP-ng 7.5 and 7.6, please all tell me which version you tested
-
AllooTikeeChaat there was no performance change, was the first use of that test host
stormi XCP-ng 7.6, just HVM, no PV
-
If all goes well I'll push the updates to everyone on monday. Meanwhile, please go on with the testing if you can.
-
stormi XCP-ng 7.6
-
Thanks to everyone who tested the update candidate. I've now pushed the security update for XCP-ng 7.6. I'm holding that of XCP-ng 7.5 until at least one person confirms that it's working for them.
-
Sorry been away this weekend .. stormi XCP-ng 7.6
-
I've installed the updates on a pool. Now every time I migrate a pfSense HVM VM within the pool the console is gone and memory usage is at 100%. I did do the following on the pool master:
yum update xenopsd xenopsd-xc xenopsd-xenlight --enablerepo='xcp-ng-updates_testing'. The package version also differs from other hosts (0.66.0-1.1.xcpngversus0.66.0-1.el7.centos). Would that be the cause? -
Ultra2D Could you downgrade to the previous version with
yum downgrade xenopsd xenopsd-xc xenopsd-xenlight, restart the toolstack and tell us if migration works better?Also make sure that you already have the latest updates for
xcp-emu-manager, which fixed many migration issues about two months ago. See https://github.com/xcp-ng/xcp/wiki/Updates-Howto#a-special-word-about-xcp-ng-75-76-and-live-migrations. -
Ultra2D In fact, you may be right, differing versions of those packages may cause an issue, because both hosts may behave differently regarding VMs that have no
platform:device-idset.So another test to do would be install the update candidate for those packages on all hosts and restart their toolstack, then test migration of that VM again.
-
stormi Thanks. Installing the update candidate on all hosts and restarting the toolstack works, but only after power cycling the VM once.
xcp-emu-manageris version0.0.9-1Is it advisable to stay on the testing repo until the next version? There are some more non-Windows HVM VM's.
-
Ultra2D so you mean that installing the updated packages would "break" the first migration of such a VM unless it's been rebooted once? If that is so, then I'd advise to revert to the previous version (or to make sure not to attempt a migration without power cycling the VMs once). Else, your choice. If the updated packages bring a benefit to you, you can keep them, else revert to the previous ones.
-
stormi I only tested with one VM. It crashed a couple of times when the pool master had updates from
xcp-ng-updates_testingand the slaves had the updates that were released yesterday. After updating the last remaining slave to updates fromxcp-ng-updates_testing, moving the VM resulted in a stuck VM. So I don't think you can draw any conclusions from this, except maybe that you should install the same version on master and slaves.
