Would be nice to share our homelabs, might interest new users:

I'll begin:

1 pool with 2x Protectli VP6670 (64GB and 96GB RAM) (2x 10G bonded for VM network, 1x 2,5G for management network).
Both with Internal 1TB SSD as local ext4 SR, 1TB nvme for OS and SR.
NFS-SR on QNAP TBS-h574TX (10G connection) and QNAP TVS-h1288X for backups (10G connection, NFS).

2 switches:
Mikrotik CRS312-4C+8XG for 10G network
Mikrotik CRS328-24P-4S for 1G and POE

Netgate 8200 pfsense for firewall
ODROID-N2+ for HomeAssistant, Uptime Kuma moitoring

@gduperrey 1 HomeLab-Pool (via cli: yum update and reboot), 3 Business-Pools (via RPU), total 7 servers updated without issues.

@olivierlambert Master, commit fcefa: fixed!

@florent Updated.

Did a backup job: OK
Did the mirror job: OK

Great!

@Prilly Man you need to calm down. Your post(s) with shit here shit there has bad "tone".

I don't think this will get a lot of help/attention from Vates.

And they are more than helpful, even without payed support.

@olivierlambert The units are top notch!

I still have 1 FW6C 2 FW6E's (had them running proxmox before, xcp-ng after that but switched to the VP6670 because of 10G network).

NEVER ever had one single issue with them. Also bios updates are easy.

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

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

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

@bleader All pools updated via RPU without issues.

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