@stormi Microcode updated on affected Gen11 i7. Running normally.

@gduperrey I jumped in all the way by mistake... I updated a wrong host, so I just did them all. Older AMD, Intel E3/E5, NUC11, etc. So far, so good. Add/migrate/backup/etc VMs are working as usual. Good for guest tools too, but mine are mostly Debian 7-11. Stuff is as usual so far.

I agree and I'll say it again, Thanks! It's not just Linux/Xen stuff. It is XCP-ng and XO that make everything work as a cohesive vertical open-source solution (some nice buzz words). Thanks to the Vates team and community that have built and support it. I look forward to ongoing continuous improvement and innovation!

@bleader Installed and running.

@bleader Updates running on several old and new intel machines (including microcode update). Working fine so far. Rolling Pool Reboot is a helpful feature.

@bleader I installed it on a bunch of busy hosts. All are fine, but none used PCI passthrough. The Rolling Pool Reboot in XO was very helpful.

@julien-f @olivierlambert

Thanks for the ability to delete XO task logs feature! (XO commit f6e6e)

@gduperrey I have several hosts updated and running. I'm happy to see 8.3 updates on parity with 8.2.

@stormi Installed on several test and pre-production machines.

@bleader I installed it on many 8.2 machines. On one I did get a warning:

  Cleanup    : xen-libs-4.13.5-9.40.3.xcpng8.2.x86_64                     14/14
warning: %posttrans(microcode_ctl-2:2.1-26.xs29.5.xcpng8.2.x86_64) scriptlet failed, exit status 1
Non-fatal POSTTRANS scriptlet failure in rpm package 2:microcode_ctl-2.1-26.xs29.5.xcpng8.2.x86_64
  Verifying  : xcp-ng-release-8.2.1-13.x86_64                              1/14

But it did not seem to have any effect. Nothing extra in the yum.log

@jasonnix Update to nodejs 22.x. It should be good for a while. Nodejs 24 will be out soon but not required yet.

@tjkreidl Interesting that ASRock is also using the NUC name. ASUS also has the new NUC15.

This new ASRock box uses the Ultra 7 255H which has 6P/8E/2LPE cores (no HT).

@TeddyAstie I ran iperf3 tests between two VMs on Xeon E5-2680v2 and average results were within 2% of each other with the patch being slower. Peak speed was 14.5 vs. 13.7 Gbits/sec.

@2planks Make sure your BIOS settings are correct. Make sure all the virtualization (VTx) and IOMMU (VT-d) features are enabled.

@escape222 Yes, using XO.

You can do a quick deploy of XOA as a bootstrap to build your own XO VM.

@escape222 I have no problem UEFI booting the same debian-12.10.0-amd64-netinst.iso image on XCP 8.3. I just created a new VM using the Debian 12 template and it worked correctly.

Can you try setting the DVD-drive first in the boot order for the VM (on the Advanced tab). You can disable the network boot too (and also maybe the hard drive as a test).

@archw Yes.

@cairoti I have had this happen to me.... With HA enabled, when the master fails, a new pool member becomes the new master. With HA enabled and shared storage, designated HA VMs should be restarted on the pool.

If you have stand-alone (per server) storage then VMs on the dead server can't be restarted because their storage is gone.

If you don't have HA enabled then you need to manually force a new master and restart failed VMs.

To force a new master on a pool member use the command xe pool-emergency-transition-to-master from a XCP console. You can't do much to the pool without a master. If your old master just needs to reboot quickly then just do that without changing the pool. If you master is going to be down for a while (more than a few minutes) then pick a new master beforehand, or after as a forced change.

It may take a while to force another pool member to become the new master as the members have to timeout contacting the old dead master.

With a failed master or pool member you have two choices:

1. Kick out the dead host from the pool forever (from the new master). After you fix/replace the dead host you need to REFORMAT and START OVER with a NEW install of XCP (there may be a reset command, not sure). You can then add the NEW host to the existing pool. You CAN NOT re-add a host that has been kicked out from the pool. IF you reformat the dead host and start over with a clean install, you need to kick the old host from the pool as the new server has a new UUID and you can't replace a pool member (just kick old and add new).
2. Don't kick out the dead host and fix the hardware (as long as the drives boot the same XCP data as before). Just turn on the host and it should join the pool and know that it was the master, but there is a new master now and it should just become a normal pool host.

If you fix the old master (and did NOT kick it from the pool) then boot it with the same disks, it should just connect to the pool and know there is a newer master. You can re-designate it as the new master if you wish or just let it be a pool member.

Yes, I have done this (again, just now as a test) with XCP 8.2.1

@ItsAlwaysDNS I still have some old Debian systems running just fine. XCP 8.2.1, HVM, Debian 7, upgraded kernel 3.16 (32 bit). They were cloned from hardware systems and just added the XCP agent. I have run even older systems (same age as CentOS 6) and they work correctly.

You can look at this old CentOS 6 post.

@bradmbreer You only need to connect to the pool master. XO will find the other hosts in the pool. If you connect to a non-master, XO will be redirected to the master. If you connect to other hosts in the pool (after the master) it will just give an error. Just ignore the error connecting to other hosts in the same pool.