@nick-lloyd I think the answer would depend on the state of your XAPI database given the fact that each host thinks that it in the pool master. To convert one or more of the hosts to a slave, you would need to --

edit the file so that it contains slave:<IP address of master> instead of master run mv /var/xapi/state.db /var/xapi/state.db-old to get rid of the old xapi database reboot the host

Once rebooted, the xapi database will be regenerated by syncing with the pool master.

Hi,

I think that's a XAPI behavior, I'm not sure it's propagated when the VM is migrated. You might ask upstream XAPI project about this 🙂

There's no stupid questions, only bad UX/UI 🙂

No, it really depends on many factors. There's no universal tuning.

@JacobyBarr said in Windows 2022 server not rebooting:

It was quite frustrating, to say the least! I found that sometimes it's down to updates or even some funky settings in the BIOS. Have you checked those yet?

I think, its not an option, to stay on a patchlevel prior to 02/2023...
Did you try to disable secure-boot?

@Kajetan321 You should consider the effects of NUMA/vNUMA in terms of performance. Crossing over to other physical CPUs or memory banks will create slowdowns.
If possible, unless you absolutely need all those VCPUs on any or both VMs, you may be best off splitting the 36 VCPUs and assigning 18 on each VM, checking to see if all the memory stays with the bank(s) of those specific VCPUs. See my articles on the CUCG site about NUMA and in particular, graphics performance (and of course, calculations will also be affected). Best would be to
run benchmarks with both configurations. Shrinking the number of VCPUs on a running VM can lead to issues (as indicated in the video posted just before my response).
See the Tale of Two Servers articles here for details: https://community.citrix.com/profile/46909-tobias-kreidl/#=

If it's only the XAPI that was damaged, you can restore metadata from your XO/Pool metadata backup. Alternatively, if you forgot to make metadata backup, you can introduce SR to find back all your previous disks (but you will lose the medata data with it).

@olivierlambert It was DR. I was testing DR a while ago and after running it once I disabled the backup job so these backups have just been sitting on the server. I don't think I've rebooted that server since running that backup.

@Andrew
Thank you so much, I was not sure if there was a weird quirk between the generations that would cause them to be ejected from the current pool. That simplifies the rest of my upgrade then, first will be the CPU's, and then I will do memory next, just have to wait slightly due to my budget, but looking forward to the uplift for multi threaded. The single core uplift will just be a bonus on top, but I am trying to stretch out this platform for as long as I can get away with. Again thank you for the response much apprciated

@andyhhp Well, then I'm glad I spent $35 each on the 2683s while the company spent $125 each on the 2697s. Saved me $180 and it has all the same functionality but just a bit less speed.

@KPS I also patched Windows 2016 und 2022 to latest version. With xen guest tools. Both worked fine as well. We dont have a 2019 machine to test with.

@AtaxyaNetwork YOU ROCK! I am working hard to rise to your level!!! LOVE IT! Great Job!

@jjanvier check your disk empty space....

@Danp i did not have this notifcation is that limited to the pro version?

Hello everyone,

XCP-NG 8.2.1 here. Recently, I encountered issues with SR network connectivity (10Gb iSCSI), which caused a few virtual machines (VMs) to stop and subsequently fail to start, displaying the well-known error message: FAILED_TO_START_EMULATOR. While restarting the toolstack or the host are proven solutions, I would like to suggest two additional approaches:

If you have at least two hosts in the same pool, attempt to start the VM on another host. Create a snapshot of the VM and immediately revert to it. Then try to start the VM again. This should resolve the issue.

@andSmv

Thanks 🙂
Let me know and i will be happy to continue testing 👍

Thanks a lot for your feedback!