@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.

@abudef @olivierlambert @thomas-dkmt I agree. I read block the same way... how about disable or prevent. (French? empêcher)

@julien-f @olivierlambert

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

@stormi I did a standalone host ISO install, all works as expected. I also did a pool ISO upgrade (8.2.1 to 8.3), master first, others second, migrated live VMs from old to new, all works as expected.

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

It would be nice to have an "unregister" button, or better, a "use free license" button.

@stormi Got it... I missed that one for coretemp. Vates ticket opened for the XOA stats problem after 8.3 upgrade.

@stormi Upgrade problem... I upgraded a good working busy 8.2.1 server to 8.3 (using the new ISO). The upgrade went well without error. No guest VMs were changed.

Same issue in XO (Master 7be70) and XOA (5.107.2), so it must be an XCP issue. There are three new problems (all was working before);

1. XCP coretemp no longer loads/works. Error: coretemp coretemp.0: Adding Core 0 failed
2. XO Host CPU stats and Load are now reported as zero (It's a busy machine, they are not zero)
3. XO All guest VMs report zero CPU usage. Some just report No stats. for CPU. They do have current recognized guest tools (Linux and Windows). They do report other stats (memory, network, disk).

Other older XCP 8.3 hosts/guests are working.

@stormi I did a standalone host ISO install, all works as expected. I also did a pool ISO upgrade (8.2.1 to 8.3), master first, others second, migrated live VMs from old to new, all works as expected.

@dinhngtu @olivierlambert @stormi I think the Windows VM's with old tools should show up in the Dashboard Heath report under "Guest Tools status"...

@flakpyro From my experience, VM with UEFI boots faster than BIOS. For some OS versions UEFI runs faster IF there are no Xen drivers. But for most installs it does not matter much, except for Debian... which has given me problems with pool/migration/reboot with the UEFI installs on XCP (there's a workaround).

So, I would vote for UEFI as the default for all OS/VMs that support it correctly since most are moving to that anyway (including XCP hosts).

@olivierlambert Any backups that run cause RPU to fail and not continue/restart. My example of this is hourly continuous replication breaks RPU.

@olivierlambert @flakpyro Commit 2fd5759 seems to solve the issue for me.

@xcplak With a LVM guest, you can restore the whole VM now. The backup data is actually saved correctly and it is possible to manually restore a single file. So they can fix XO and the old backup data is still good.

@flakpyro Nice catch! I see the same problem.

@olivierlambert @florent Running XO source (master 6ed35). I see the Windows VMs in the CR backup job report, but they no longer appear on the destination host as a VM. Some have updated tools, others do not. It worked before... Non-windows VMs seems to be fine. These are all old VMs, so it's a new problem on existing systems.