XCP-ng 8.2 updates announcements and testing

Andrew

@stormi Running both updates on everything. The 64 bit EFI console on the NUCs works for me with this kernel update.

If you (anyone) is using one of my NUC Test ISO install images then the EFI console will work with the update but the i225/r8125 network may not. To fix that issue, make sure you have installed the network PACKAGE and not just the ISO install. My test ISO installer may not have fully installed the needed package. Download and install the network driver BEFORE the kernel update. If it's too late then you can use a USB stick to just copy the RPM files and install them after the update.

It does not hurt to reinstall the r8125 or the IGC drivers anyway. login to XCP, download driver, install (remove very old driver if there is an error):

wget http://users.ntplx.net/~andrew/xcp/r8125-module-9.009.02-2.xcpng8.2.x86_64.rpm
yum install ./r8125-module-9.009.02-2.xcpng8.2.x86_64.rpm

wget http://users.ntplx.net/~andrew/xcp/igc-module-5.10.146-2.xcpng8.2.x86_64.rpm
yum remove intel-igc-5.10.108-1.xcpng8.2.x86_64
yum install ./igc-module-5.10.146-2.xcpng8.2.x86_64.rpm

Andrew

@stormi I do see this now at boot (related to netdata):

[   49.028835] xenstat.plugin[1818]: segfault at 80 ip 000000000040378a sp 00007ffc4f4278a0 error 4 in xenstat.plugin[400000+8000]
[   49.028842] Code: f4 ff ff 41 b8 68 5d 40 00 b9 d4 00 00 00 ba 30 5f 40 00 be d8 52 40 00 bf 8b 4f 40 00 31 c0 45 31 e4 e8 a9 04 00 00 4c 89 e3 <48> 8b 9b 80 00 00 00 48 85 db 0f 85 be f4 ff ff
e9 b7 f7 ff ff 8b

stormi

@Andrew It never happened before?

stormi

@Andrew said in Updates announcements and testing:

@stormi I do see this now at boot (related to netdata):

[   49.028835] xenstat.plugin[1818]: segfault at 80 ip 000000000040378a sp 00007ffc4f4278a0 error 4 in xenstat.plugin[400000+8000]
[   49.028842] Code: f4 ff ff 41 b8 68 5d 40 00 b9 d4 00 00 00 ba 30 5f 40 00 be d8 52 40 00 bf 8b 4f 40 00 31 c0 45 31 e4 e8 a9 04 00 00 4c 89 e3 <48> 8b 9b 80 00 00 00 48 85 db 0f 85 be f4 ff ff
e9 b7 f7 ff ff 8b

So, I reproduced, but also with the previous kernel, so it's not related to this kernel update.

Update: same regarding the Xen update candidate. Reverting it does not fix the segfault.

Andrew

@stormi I have just not seen that error before and it was not in the old logs. I guess it's just netdata getting old and cranky (grincheux). Otherwise things are good in normal operation.

stormi

Update published. Thanks for the tests!

https://xcp-ng.org/blog/2022/12/21/december-2022-security-update/

gduperrey

New Update Candidates (xen, xapi, templates)

Xen: Enable AVX-512 by default for EPYC Zen4 (Genoa)
Xapi: Redirect http requests on the host webpage to https by default.
Guest templates:
- Add the following templates: RHEL 9, AlmaLinux 9, Rocky Linux 9, CentOS Stream 8 & 9, Oracle Linux 9

Test on XCP-ng 8.2

From an up to date host:

For Xen, Xapi and Guest templates:

yum clean metadata --enablerepo=xcp-ng-testing
yum update xen-dom0-libs xen-dom0-tools xen-hypervisor xen-libs xen-tools xapi-core xapi-tests xapi-xe guest-templates-json guest-templates-json-data-linux guest-templates-json-data-other guest-templates-json-data-windows --enablerepo=xcp-ng-testing
reboot

Versions:

xen-*: 4.13.4-9.29.1.xcpng8.2
xapi-*: 1.249.26-2.2.xcpng8.2
guest-templates-json-*: 1.9.6-1.2.xcpng8.2

What to test

Normal use and anything else you want to test. The closer to your actual use of XCP-ng, the better.

Test window before official release of the updates

No precise ETA, but the sooner the feedback the better.

Andrew

@gduperrey Mirror error

failure: repodata/6b271e84b07dced2015bb0d835fb0ec1be1d308d92010993d44a1af0c130aa9f-primary.sqlite.bz2 from xcp-ng-testing: [Errno 256] No more mirrors to try.
http://mirrors.xcp-ng.org/8/8.2/testing/x86_64/repodata/6b271e84b07dced2015bb0d835fb0ec1be1d308d92010993d44a1af0c130aa9f-primary.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found

Name:   mirrors.xcp-ng.org
Address: 37.26.189.194

Andrew

@gduperrey The repository seems to work now....

stormi

Unrelated to the above: a security update for sudo was published. I don't think it's very likely to be an actual threat in the context of your use of XCP-ng, but it might be in specific contexts.

https://xcp-ng.org/blog/2023/01/31/january-2023-security-update/

brezlord

@stormi Applied the update through XO and now XO can not login to the host with the below error.

connect ECONNREFUSED 192.168.40.201:443

I rebooted the host and I can no longer login as root.

ssh: connect to host 192.168.40.201 port 22: Connection refused

Any ideas?

stormi

Was it the only update applied? Is the stunnel service running?

Oh, I also read that you can't connect as root.

brezlord

@stormi Yes only update.

stormi

Were you using sudo on the host before?

brezlord

@stormi No just default install

stormi

I hardly see a cause-effect link between the update and the issues (both SSH and XAPI not responding anymore?), but computers are full of surprises.

Did you change the firewall configuration? Could the IP address have changed or the same be attributed to another device?

brezlord

@stormi Done nothing but apply the update through XO web console. I have yanked the plug and making sure it actually reboots.

brezlord

That fixed it I can login via ssh with root and XO sees the host.

stormi

Maybe it was still rebooting, stuck on the shutdown phase, waiting for some kind of I/O or something. This would explain why it didn't respond.

olivierlambert

I concur. If the shutdown process is stuck somewhere (eg an NFS share), you can't connect at all (connection refused in SSH, no XAPI connection) and it can stays like this for a while.