XCP-ng 8.3 public alpha 🚀
-
A new batch of updates for XCP-ng 8.3 alpha arrived.
It's been a while: one specific update I wanted to push together with everything that was ready gave us more trouble than expected, but now it's solved and so I pushed all the updates at once.
Main changes
xcp-ng-release*: updated repository definitions in/etc/yum.repos.d/xcpng.repo, to add more testing repositories (disabled by default. More about this here - look for "About the new testing repositories"). Warning: If you have any local changes to this file, it won't be overwritten. In this case, look for/etc/yum.repos.d/xcpng.repo.rpmnewafter applying the update, and move it overxcpng.repo. This won't change much for you as testers of XCP-ng 8.3, because we're still pushing the updates directly toxcp-ng-basewhen they are ready for your testing, but there might be the occasional experimental package in some other location - and the updated .repo file with make it easier to pull from there if needed.- AMD and Intel microcode updates (not the very latest yet, though)
sm(Storage Manager) ported to python 3 by XenServer, and we rebased our additional storage drivers on it- XAPI and related components
- HTTP to HTTPS redirection on the host's web page.
- lots of changes from upstream. Full changelog.
- IPv6 support added to
xhaandxsconsole. You'll need to wait for an updated installer in order to test this and the rest of IPv6 support for the management interface. memtest86+updated to 6.20 to support EFI hosts and more hardware. Will be available in the installer.xen: better hardware support (Ryzen...), security fixes, bug fixes...- Other updates synced from the preview release of XenServer 8.3.
zstd1.5.4 (1.5.5 soon)- removed corosync and dlm from installed systems. They were unneeded dependencies for XenServer's clustering support, which is proprietary and thus unsupported on XCP-ng. Let's trim dom0 down slightly.
We also continued our work on the installer and on automating the build of installer ISO images. We'll have new builds for you shortly.
How to update
From an installed XCP-ng 8.3 alpha, just run
yum update, and reboot. The usual update rules apply: master host first, etc. Check https://xcp-ng.org/docs/updates.html. I haven't tested it on this update, but XOA's Rolling Pool Update should work on this update.What to test
Depending on the time available, it goes from "just update and check things still work as expected" to "test everything you can think of", with an intermediate step of "test specific features which are important to you".
-
@stormi Thank you!
Are there any planned work related to hot backups of VM's, where a USB device are attached? It's currently not possible.
In the weekend I ended up moving a single container to a alpine image, so I could continue backing up my primary docker VM. But I was hoping to have rolling backup of the alpine VM, too
-
Update done on an Intel NUC11ATKC4 and a NUC8i5BEH, both are working fine
-
@exetico The topic of snapshots (and subsequently, backups) for VMs with USB passthrough is an identified one but there's no ETA at the moment.
-
@stormi Fair. Are there any public issue to follow? Maybe I didn't do my search that well? Thank you for the answer.
-
@exetico There are https://github.com/xcp-ng/xcp/issues/164 at XCP-ng level and https://github.com/xapi-project/xen-api/issues/4573 at upstream XAPI level.
-
@stormi Update done on the 8.3 server in my test lab and all goes well so far. HP Microserver N36L
-
@stormi Thanks. I'll cross my fingers for a fix, at some time.
I also updated yesterday, on my ODROID H3+. Everything worked as expected.
I noticed that
/etc/xensource/usb-policy.confwas send back to stock configuration, so I readded my modification to it. I'm not sure, if that's the expected behavior, after the host update + restart.Thank you for the latest update
. -
@stormi I have updated 8.3 machines, but they are only test machines. I also did a fresh 8.3 install and update. Working as usual.
-
@stormi No problem with a rolling pool update of my two playlab host. Pool reports up-to-date and healthy (XO from source). Basic VM and VDI tasks work as expected. Looking good
-
@stormi No issues so far on Ryzen 1700x, Xeon e5-2640v3, and 2 Epyc 7313P systems
-
Updated my HP DL360 G7 home lab with no problem at all.. Everything seems to work OK.. 8-)
-
@exetico said in XCP-ng 8.3 public alpha
:@stormi Thanks. I'll cross my fingers for a fix, at some time.
I noticed that
/etc/xensource/usb-policy.confwas send back to stock configuration, so I readded my modification to it. I'm not sure, if that's the expected behavior, after the host update + restart.Yes, it is. I opened this upstream issue about it, but no common decision was reached yet: https://github.com/xapi-project/xen-api/issues/4935
-
No problems here updating a testpool with 2x NUC11TNHi5 (i5-1135G7 and I225-LM 2.5GB NIC)
Updated both from shell, rebooted master first, then the other NUC. -
anyone tried to install on asus pn52?
struggling with the network not working. is bad speed without guest tolls not installed and with installed Xcp-ng tools 8.2.2.200 the network hangs and does not exist same with xen guest tools
-
I pushed a few updates to the
xcp-ng-baserepository. Update withyum updateor Xen Orchestra.Changes:
xcp-ng-release*mostly changes for the imminent new release of installer imagesopenvswitch: fix DoS security issue, CVE-2023-1668xcp-ng-xapi-plugins: enable installing new packages from Xen Orchestra, and also applying updates from the xcp-ng-linstor repository. This is preliminary work for XOSTOR support in XCP-ng 8.3.zstdupdated to 1.5.5, which is a bugfix release.
-
@stormi ok, installing the patch didn't help the network speed.
Are probably the drivers for the RTK8125B with which there are some bugs. I get full speed when I install Windows 10 on the Asus PN52.
-
@steff22 Are the guest tools that have support for Xcp-ng 8.3 ?
-
@olivierlambert Any plans to support this for manual snapshots as well ? If required we could add [NOSNAP] as well to have an option.
-
@CptHyper I'm not sure to understand what are you talking about. Can you be more specific?
