@stormi Downgraded all hosts @home and @office. I have not done anything to running Windows Server VM's or touch anything regarding certs. So I guess I'm all good.

@gduperrey Updated 2 pools/2 servers @home, updated 3 pools/5 servers @ office with RPU.
All fine.

@dinhngtu

@dinhngtu Hopefully before the next updates to xcpng. Rolling pool update moves all VM's....

Does this bug clear itself after a VM reboot? Or has the tools to be reinstalled? Is it only cosmetic or does it affect the running VM?

Havne't tried this myself and as we have moved all VM's to these new tools I'd like to be aware of what I can expect.

@dinhngtu Is it impossible to report the correct Windows version? Seems to be the "correct" solution....

@dinhngtu Better to report it Windows11/Windows Server 202x

@dinhngtu One would suppose for it to report the correct Windows version.... Or at least a common "general one", e.g. "Windows 10 or newer". As it is it doesn't feel right.

@olivierlambert Moved all my homelab and business vm's to this, from Citrix-tools (latest version).
Apart from loosing all IP info in the network (as it's always a new network adapter) all went without any issues.
All Vates now

@olivierlambert Working again, using both build scripts.

As always

@olivierlambert Created issue on both githubs.

@olivierlambert In my case I have 2 VM's with XO.
One installed via https://github.com/ronivay/XenOrchestraInstallerUpdater
the other via https://github.com/Jarli01/xenorchestra_installer?tab=readme-ov-file

I can confirm this issue on both. And the last time I created a VM from scratch (debian) it was OK. I just tried this now to check this issue and I can confirm this on my end.

@itservices confirmed

@gduperrey Installed @home and @business. RPU had no issues this time.

@john.c Updated our 2 production pools, with RPU.

RPU emptied the master, rebooted BUT then nothing else.
It should have moved all VM's to the other host, patched/rebooted and then migrating the VM's where they were.
This did not happen. I had to manually empty the other hosts, patch, reboot and migrate the VM's.

@john.c Will apply to business EPYC servers right away

@gduperrey Installed at HomeLab. No issues.
Running via
yum clean metadata ; yum update

@Danp UEFI

@Thunder-Cloud

Working on ours for years without issues. 8.2 and since release 8.3

Might be some hardware issue...

@gduperrey said in XCP-ng 8.3 updates announcements and testing:

yum clean metadata ; yum update

OK, I'll try this next time.

P.S I've updated the 2 hosts via XO all teh time from 8.3 beta. Always showed patches available in XO. Started with the previous 8.3 updates that they didn't show and I had to run those commands.

said in XCP-ng 8.3 updates announcements and testing:

@gduperrey I wonder why now I have to run those commands on my hosts each time for the updates to show:

yum clean all
rm -rf /var/cache/yum

Not fun

@gduperrey Can you explain why this is happening and how to get updates showing automatically again?