Also here the task progression can't be followed (stays at 0% until completed):

instead of

As shown above the evacuation tasks are not shown.
The last steps migrating thre VM's to the original place are shown:

Just did my RPU and checked on the new v6 interface.
The old one has task details that are missing on the new one (or I didn't find them:

I like to see the evacuation tasks happening (in the past I could identify hangs etc)

Here instead of the ID of the VM host the real names should be shown:

@McHenry This should not happen. If thr VM runs on the slave and the master is rebooted or shut down it still should continue to run. Done this many times. The only thing happening is that XO can't access the VM's any longer as it needs the master.

That being said: running the firewall/router on a VM opens you to a lot of future pain (as you just have experienced). Don't do that unless you absolutely must and can work around down-times caused by VM/host issues.

Install it on a dedicated machine!

@dinhngtu Updated from previous version running on 8 Windows Server 2022 VM's across HomeLab & Office.

No issues.

@acebmxer Fixed. Worked here now. Had the same error before

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