@acebmxer Hello, the XO team is currently working on a solution. We will keep you inform as soon as it is on release.

@acebmxer said in Windows Server not listening to radius port after vmware migration: After migrating our windows server that host our Duo Proxy manager having an issue. [info] Testing section 'radius_client' with configuration: [info] {'host': '192.168.20.16', 'pass_through_all': 'true', 'secret': '*****'} [error] Host 192.168.20.16 is not listening for RADIUS traffic on port 1812 [debug] Exception: [WinError 10054] An existing connection was forcibly closed by the remote host After the migration I did have to reset the IP address and I did install the Xen tools via windows update. Any suggestions? I am thinking I may have the same issue if i spin up the old vm as the vmware tools were removed which i think effected that nic as well.... On your VM that runs the Duo Auth Proxy service, check if the service is actually listening on the external IP or if its just listening on 127.0.0.1 If its just listening on 127.0.0.1 you can try to repair the Duo Auth Proxy service, take a snapshot before doing so. Also, if you're using encrypted passwords in your Duo Auth Proxy configuration you probably need to re-encrypt them, just a heads up, since I just had to do so after migrating one of ours. Edit: Do you have the "interface" option specified in your Duo Auth Proxy configuration?

@acebmxer I did install the certs, and everything went fine with that. But I never went back to try and install any uefi VMs through XO-Lite. Something I may or may not get back to, should really wipe the system and start fresh again to see how things have advanced. Things may be changing, and my lab may not have a physical place in my world. Which troubles me because I'll need to model things if this path turns into reality. Lots of unknowns right now.

I will create a new thread from your message

@olivierlambert Thank you for bringing this to the attention of other folks

@stormi Unless new Dom0 is Kernel 6.15 or newer (with updates), this will be an ongoing problem to support the newest hardware as they seem to keep updating the chips (you can't stop progress). The current r8125 driver in 8.2/8.3 supports the 8125 and some 8126 chips, but not 8127. Other than supporting the new hardware versions of the chips, I have not seen any real complaints posted about the current r8125 driver (may be there are some Vates tickets?) While the risk on the new driver is low, it is different (not just an update). I agree that it would be best to have r8125-module-alt for the new code and then r8126-module and r8127-module. Note, that the new r8126-module driver should not be installed without the r8125-module-alt as the existing r8125-module would conflict with the new r8126-module driver. The work is already done (compiled and running)... I'm just waiting for Realtek to fix some issues with the new code before it's worth fully testing the drivers (issues already acknowledged by Realtek).

Can confirm that OME 4.5 works, installation plugins and tools works.

We have some sites with a single-host XCP-ng pool backed by a small UPS. We install nut directly in dom-0. I'm aware of the policy for adding anything to dom-0 but we believe this usecase fits in the recommendations (simple enough, no vast dependencies, marginal resources usage, no interference ...). With proper testing works pretty well. nut inside a dedicated RPi definitely makes sense for a site with multiple hosts backed by the same UPS.

Unikraft would a a good fit for ram-constained devices. Being able to have useful VMs with 32-64 MB each.

Thank you very much for your feedback! I will make sure to pass the kind words to the entire team

@Danp said in The emulator required to run this VM failed to start..?: Restart the toolstack on each server. This worked for me too.

@AtaxyaNetwork It is Debian 12. I found the problem and will post again if there's more issue. The VM stopped using its static IP, not sure how that happened, but I re-added it to /etc/network/interfaces and it's working again.

Good luck and keep us posted!

Hi, thank you for the example! We will take a look. It could be a good idea to have a dedicated documentation/web page with usage examples of 'DevOps' tools

@bufanda I'm sure all my backup since this bug was appear in my system is Full backup, I don't know if the two issues are related but they appeared at the same time.

Hello, @DustinB The https://vates.tech/xostor/ says: The maximum size of any single Virtual Disk Image (VDI) will always be limited by the smallest disk in your cluster. But in this case, maybe it can be stored in the "2TB disks" ? Maybe others can answer, i didn't test it.

Hi @Andrew. This PR should fix your issue https://github.com/vatesfr/xen-orchestra/pull/8854 MathieuRA opened this pull request in vatesfr/xen-orchestra closed fix(xo-server): fix incorrect state when remove server #8854

@arovella74 said in Definition backup full & incremental.: Our S3 bucket fills up with objects. Set up retention and deletion rules on your bucket so your bucket is cleaning this out. @arovella74 said in Definition backup full & incremental.: We want a full backup to be performed every two incremental runs, so we can keep the S3 bucket in check. Without more details I'm not sure how you could do that, besides alternating schedules, specifically run an incremental bi-weekly (for simplicity) and then run a full every 3 Saturday.

@AtaxyaNetwork I'll check it out! Im currently on chrome. So ill see if they have something close to it. Thank you!