Just a note to say thanks to all involved! Excellent job!
I yesterday upgraded our 8.3 release pool to 8.3 production. 2x Intel NUC11TNKi5. Running very nicely! The upgrade from release candidate with the ISO written to USB media went smoothly. Also the yum updates after the upgrade.
Now looking forward to see XO Lite be completed!
Keep up the great work!
I updated a test pool with 2 Intel NUC11TNHi5 hosts last week.
The updates went smooth. No issues after reboot.
Can't wait till 8.3 goes live!
Thanks @michael-manley for picking this up!
Looking forward to a new version that supports 8.3 (Beta) 
@Alexander-0 Thanks!
I'll compare this to my original notes (still from Xenserver 6 era, but used on 7 and 8 too)
Hi,
Interesting topic. Is there a best-practice for installing apcupsd on XCP-ng hosts? I would like to keep things as clean as possible.
@olivierlambert Thanks for the quick reply as always!
With respect, I did read that post, and it still leaves me with my questions above.
[TL;DR]
Is 8.3 alpha simply renamed to 8.3 beta, and there's nothing else to do than yum update untill there are no more updates?
or, should I upgrade?
If so, please read my question/remarks below:
[Full question]
I have years of experience of updating/upgrading from Xenserver 5.x all the way to XCP-ng 8.2. But I've never upgraded an alpha version before. I have 8.3-alpha, installed from the alpha2 iso on both hosts.
So, taking your advice, I again look at the section "Alpha testers: update from XCP-ng 8.3 alpha". I click on the "as usual" link, which directs me to updating (not upgrading). Beside the link is the remark (using Xen Orchestra or yum update).
So I go to Upgrade (https://xcp-ng.org/docs/upgrade.html#release-notes-known-issues).
I would have liked to try the yum update (from command line) method , but can't figure out if I have to define the target version, and if so what the name of the tarket version is (export VER=8.3 ?)
Or do you suggest I simply download the iso, dd it to USB stick, reboot boot the master with USB stick, install, reboot and then do the same for the other host server?
Or... is this all not required and am I overthinking this, because yum update was enough?
Congratulations!
I'm a bit confused about upgrading form 8.3 alpha to 8.3 beta.
If I type yum update on my two pool hosts, there is nothing to update.
Does that mean I'm now running 8.3 beta? Or are there extra steps to take if I want to use the command line upgrade from alfa to beta?
So far, my 2x NUC11TNKi5 testpool is running fine.
@olivierlambert Ooh, that's exciting!
I'm hoping you make the same jumps from beta to RC to production, in the same timescale you did with 8.2.
You then managed to go from Beta via RC to Release in only 6 weeks!
Keep up the great work!
@stormi
Do you mean that if I install i225 driver, next time I do “yum update” within 8.2, I loose the driver (leaving host without network connection), or do you mean the driver will not be added when I in the future do an upgrade to 8.3 (or for instance 8.2.x)? As these drives are in 8.3, that should not cause a problem, correct?
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.
Yes, it seems the patches fix it:
Host: Intel Nuc11TNK
CPU: i5-1135G7
RAM: 64GB G.SKILL Ripjaws F4-3200C22D-64GRS
SSD: Samsung 980 1TB
NIC: Intel i225 running at 2500 mbit
UEFI BIOS: TNTGL357.0064.2022.0217.1550
[16:51 xcpng33 xtf]# ./xtf-runner -aqq --host ; echo Result: $?
Combined test results:
test-pv64-xsa-167 SKIP
test-pv64-xsa-182 SKIP
[16:52 xcpng33 xtf]# ./xtf-runner selftest -q --host
Combined test results:
test-hvm32-selftest SUCCESS
test-hvm32pae-selftest SUCCESS
test-hvm32pse-selftest SUCCESS
test-hvm64-selftest SUCCESS
test-pv64-selftest SUCCESS
[16:52 xcpng33 xtf]# ./xtf-runner -aq --host
Combined test results:
test-hvm32-cpuid-faulting SUCCESS
test-hvm32pae-cpuid-faulting SUCCESS
test-hvm32pse-cpuid-faulting SUCCESS
test-hvm64-cpuid-faulting SUCCESS
test-pv64-cpuid-faulting SUCCESS
test-hvm64-fpu-exception-emulation SUCCESS
test-hvm32-invlpg~hap SUCCESS
test-hvm32-invlpg~shadow SUCCESS
test-hvm32pae-invlpg~hap SUCCESS
test-hvm32pae-invlpg~shadow SUCCESS
test-hvm64-invlpg~hap SUCCESS
test-hvm64-invlpg~shadow SUCCESS
test-hvm64-lbr-tsx-vmentry SUCCESS
test-hvm32-livepatch-priv-check SUCCESS
test-hvm64-livepatch-priv-check SUCCESS
test-pv64-livepatch-priv-check SUCCESS
test-hvm32pae-memop-seg SUCCESS
test-hvm64-memop-seg SUCCESS
test-pv64-memop-seg SUCCESS
test-hvm32pae-nmi-taskswitch-priv SUCCESS
test-pv64-pv-fsgsbase SUCCESS
test-pv64-pv-iopl~hypercall SUCCESS
test-pv64-pv-iopl~vmassist SUCCESS
test-hvm32-swint-emulation SUCCESS
test-hvm32pae-swint-emulation SUCCESS
test-hvm32pse-swint-emulation SUCCESS
test-hvm64-swint-emulation SUCCESS
test-hvm32-umip SUCCESS
test-hvm64-umip SUCCESS
test-hvm32-xsa-122 SUCCESS
test-hvm32pae-xsa-122 SUCCESS
test-hvm32pse-xsa-122 SUCCESS
test-hvm64-xsa-122 SUCCESS
test-pv64-xsa-122 SUCCESS
test-hvm32-xsa-123 SUCCESS
test-pv64-xsa-167 SKIP
test-hvm64-xsa-168 SUCCESS
test-hvm64-xsa-170 SUCCESS
test-hvm64-xsa-173 SUCCESS
test-pv64-xsa-182 SKIP
test-hvm32-xsa-186 SUCCESS
test-hvm64-xsa-186 SUCCESS
test-hvm32-xsa-188 SUCCESS
test-hvm32pae-xsa-188 SUCCESS
test-hvm32pse-xsa-188 SUCCESS
test-hvm64-xsa-188 SUCCESS
test-pv64-xsa-188 SUCCESS
test-hvm32-xsa-191 SUCCESS
test-hvm32-xsa-192 SUCCESS
test-pv64-xsa-193 SUCCESS
test-hvm64-xsa-195 SUCCESS
test-hvm64-xsa-196 SUCCESS
test-hvm32-xsa-200 SUCCESS
test-hvm32-xsa-203 SUCCESS
test-hvm64-xsa-204 SUCCESS
test-pv64-xsa-212 SUCCESS
test-pv64-xsa-213 SUCCESS
test-hvm64-xsa-221 SUCCESS
test-pv64-xsa-221 SUCCESS
test-pv64-xsa-224 SUCCESS
test-pv64-xsa-227 SUCCESS
test-hvm64-xsa-231 SUCCESS
test-pv64-xsa-231 SUCCESS
test-hvm64-xsa-232 SUCCESS
test-pv64-xsa-232 SUCCESS
test-pv64-xsa-234 SUCCESS
test-hvm32-xsa-239 SUCCESS
test-pv64-xsa-255 SUCCESS
test-pv64-xsa-259 SUCCESS
test-pv64-xsa-260 SUCCESS
test-hvm64-xsa-261 SUCCESS
test-pv64-xsa-265 SUCCESS
test-hvm64-xsa-269 SUCCESS
test-hvm64-xsa-277 SUCCESS
test-hvm64-xsa-278 SUCCESS
test-pv64-xsa-279 SUCCESS
test-pv64-xsa-286 SUCCESS
test-pv64-xsa-296 SUCCESS
test-pv64-xsa-298 SUCCESS
test-hvm64-xsa-304 SUCCESS
test-hvm64-xsa-308 SUCCESS
test-pv64-xsa-316 SUCCESS
test-hvm32-xsa-317 SUCCESS
test-hvm32pae-xsa-317 SUCCESS
test-hvm32pse-xsa-317 SUCCESS
test-hvm64-xsa-317 SUCCESS
test-pv64-xsa-317 SUCCESS
test-pv64-xsa-333 SUCCESS
test-pv64-xsa-339 SUCCESS
test-hvm32pae-xsa-consoleio-write SUCCESS
[16:53 xcpng33 xtf]# /usr/libexec/xen/bin/test-cpu-policy
CPU Policy unit tests
Testing CPU vendor identification:
Testing CPUID serialise success:
Testing CPUID deserialise failure:
Testing CPUID out-of-range clearing:
Testing MSR serialise success:
Testing MSR deserialise failure:
Testing policy compatibility success:
Testing policy compatibility failure:
Done: all ok
@stormi You're all welcome! Thanks so much for making this possible!
I will install the patch next week when I'm back in the office and send the updated results.
Here's the results on my new Intel NUC11 Pool (tested on one of the two identical NUCs)
Host: Intel Nuc11TNK
CPU: i5-1135G7
RAM: 64GB G.SKILL Ripjaws F4-3200C22D-64GRS
SSD: Samsung 980 1TB
NIC: Intel i225 running at 2500 mbit
UEFI BIOS: TNTGL357.0064.2022.0217.1550
[00:51 xcpng33 xtf]# ./xtf-runner -aqq --host ; echo Result: $?
Combined test results:
test-hvm64-lbr-tsx-vmentry CRASH
test-pv64-xsa-167 SKIP
test-pv64-xsa-182 SKIP
Result: 6
[00:53 xcpng33 xtf]# ./xtf-runner selftest -q --host
Combined test results:
test-hvm32-selftest SUCCESS
test-hvm32pae-selftest SUCCESS
test-hvm32pse-selftest SUCCESS
test-hvm64-selftest SUCCESS
test-pv64-selftest SUCCESS
[00:53 xcpng33 xtf]# ./xtf-runner -aq --host
Combined test results:
test-hvm32-cpuid-faulting SUCCESS
test-hvm32pae-cpuid-faulting SUCCESS
test-hvm32pse-cpuid-faulting SUCCESS
test-hvm64-cpuid-faulting SUCCESS
test-pv64-cpuid-faulting SUCCESS
test-hvm64-fpu-exception-emulation SUCCESS
test-hvm32-invlpg~hap SUCCESS
test-hvm32-invlpg~shadow SUCCESS
test-hvm32pae-invlpg~hap SUCCESS
test-hvm32pae-invlpg~shadow SUCCESS
test-hvm64-invlpg~hap SUCCESS
test-hvm64-invlpg~shadow SUCCESS
test-hvm64-lbr-tsx-vmentry CRASH
test-hvm32-livepatch-priv-check SUCCESS
test-hvm64-livepatch-priv-check SUCCESS
test-pv64-livepatch-priv-check SUCCESS
test-hvm32pae-memop-seg SUCCESS
test-hvm64-memop-seg SUCCESS
test-pv64-memop-seg SUCCESS
test-hvm32pae-nmi-taskswitch-priv SUCCESS
test-pv64-pv-fsgsbase SUCCESS
test-pv64-pv-iopl~hypercall SUCCESS
test-pv64-pv-iopl~vmassist SUCCESS
test-hvm32-swint-emulation SUCCESS
test-hvm32pae-swint-emulation SUCCESS
test-hvm32pse-swint-emulation SUCCESS
test-hvm64-swint-emulation SUCCESS
test-hvm32-umip SUCCESS
test-hvm64-umip SUCCESS
test-hvm32-xsa-122 SUCCESS
test-hvm32pae-xsa-122 SUCCESS
test-hvm32pse-xsa-122 SUCCESS
test-hvm64-xsa-122 SUCCESS
test-pv64-xsa-122 SUCCESS
test-hvm32-xsa-123 SUCCESS
test-pv64-xsa-167 SKIP
test-hvm64-xsa-168 SUCCESS
test-hvm64-xsa-170 SUCCESS
test-hvm64-xsa-173 SUCCESS
test-pv64-xsa-182 SKIP
test-hvm32-xsa-186 SUCCESS
test-hvm64-xsa-186 SUCCESS
test-hvm32-xsa-188 SUCCESS
test-hvm32pae-xsa-188 SUCCESS
test-hvm32pse-xsa-188 SUCCESS
test-hvm64-xsa-188 SUCCESS
test-pv64-xsa-188 SUCCESS
test-hvm32-xsa-191 SUCCESS
test-hvm32-xsa-192 SUCCESS
test-pv64-xsa-193 SUCCESS
test-hvm64-xsa-195 SUCCESS
test-hvm64-xsa-196 SUCCESS
test-hvm32-xsa-200 SUCCESS
test-hvm32-xsa-203 SUCCESS
test-hvm64-xsa-204 SUCCESS
test-pv64-xsa-212 SUCCESS
test-pv64-xsa-213 SUCCESS
test-hvm64-xsa-221 SUCCESS
test-pv64-xsa-221 SUCCESS
test-pv64-xsa-224 SUCCESS
test-pv64-xsa-227 SUCCESS
test-hvm64-xsa-231 SUCCESS
test-pv64-xsa-231 SUCCESS
test-hvm64-xsa-232 SUCCESS
test-pv64-xsa-232 SUCCESS
test-pv64-xsa-234 SUCCESS
test-hvm32-xsa-239 SUCCESS
test-pv64-xsa-255 SUCCESS
test-pv64-xsa-259 SUCCESS
test-pv64-xsa-260 SUCCESS
test-hvm64-xsa-261 SUCCESS
test-pv64-xsa-265 SUCCESS
test-hvm64-xsa-269 SUCCESS
test-hvm64-xsa-277 SUCCESS
test-hvm64-xsa-278 SUCCESS
test-pv64-xsa-279 SUCCESS
test-pv64-xsa-286 SUCCESS
test-pv64-xsa-296 SUCCESS
test-pv64-xsa-298 SUCCESS
test-hvm64-xsa-304 SUCCESS
test-hvm64-xsa-308 SUCCESS
test-pv64-xsa-316 SUCCESS
test-hvm32-xsa-317 SUCCESS
test-hvm32pae-xsa-317 SUCCESS
test-hvm32pse-xsa-317 SUCCESS
test-hvm64-xsa-317 SUCCESS
test-pv64-xsa-317 SUCCESS
test-pv64-xsa-333 SUCCESS
test-pv64-xsa-339 SUCCESS
test-hvm32pae-xsa-consoleio-write SUCCESS
[00:54 xcpng33 xtf]# /usr/libexec/xen/bin/test-cpu-policy
CPU Policy unit tests
Testing CPU vendor identification:
Testing CPUID serialise success:
Testing CPUID deserialise failure:
Testing CPUID out-of-range clearing:
Testing MSR serialise success:
Testing MSR deserialise failure:
Testing policy compatibility success:
Testing policy compatibility failure:
Done: all ok
Sorry for being very late to this show, but I would like to thank everybody involved in getting XCP-ng ready for using on modern 10th and 11th gen Intel NUCs! Great job!
So, to replace (in the near future) the old and large power guzzling lab servers in my office, I've just ordered 2x Intel NUC 11 with i5-1135G7 CPU and the intel 2.5 gbit I225 NIC.
Looking forward to testing them and getting ready for XCP-ng 8.3!
Haha, I lost belief in 'logical' many years ago. What I think is logical and what others think is logical, often is very different 
So, I still think it's great, cause it takes one command out of my CLI VM import pipe line
THANKS! That is a great addition!
When xe vm-export is run with compress=zstd, does the xe vm-import command need to be told that compression was used, or does the xe vm-import command see that zstd was used?
Excellent job, thanks!
I will enjoy reading this, to see if it will teach me anything new about XCP-ng.