said in Unable to enable High Availability - INTERNAL_ERROR(Not_found): said in Unable to enable High Availability - INTERNAL_ERROR(Not_found): @psafont Would designating a new pool master do the same thing? I ran the above command and its had no effect Well, I tried changing the pool master and when VMHost11 was the master I was able to enable HA. Switching back to VMHost13 as the master now so will see how that goes Everything is working as expected/hoped. So for anyone reading through this and wants a TL;DR Issue was related to the pool master setting, changing the pool master to a different host and then back to the original fixed the incorrect settings allowing HA to be enabled

[{"name": "CPU Temp", "value": "39 degrees C", "event": "ok"}, {"name": "System Temp", "value": "31 degrees C", "event": "ok"}, {"name": "Peripheral Temp", "value": "46 degrees C", "event": "ok"}, {"name": "NIC Temp", "value": "59 degrees C", "event": "ok"}, {"name": "CPU_VRM0 Temp", "value": "43 degrees C", "event": "ok"}, {"name": "CPU_VRM1 Temp", "value": "34 degrees C", "event": "ok"}, {"name": "SOC_VRM Temp", "value": "44 degrees C", "event": "ok"}, {"name": "VDDIO_VRM Temp", "value": "48 degrees C", "event": "ok"}, {"name": "DIMMA~C Temp", "value": "45 degrees C", "event": "ok"}, {"name": "DIMME~G Temp", "value": "44 degrees C", "event": "ok"}, {"name": "MB 12V", "value": "12.08 Volts", "event": "ok"}, {"name": "MB 5VCC", "value": "5.10 Volts", "event": "ok"}, {"name": "MB 3.3VCC", "value": "3.35 Volts", "event": "ok"}, {"name": "VBAT", "value": "0x04", "event": "ok"}, {"name": "MB 5VSB", "value": "5.06 Volts", "event": "ok"}, {"name": "MB 3.3VSB", "value": "3.39 Volts", "event": "ok"}, {"name": "MB 1.8VSB", "value": "1.84 Volts", "event": "ok"}, {"name": "BMC 2.5V", "value": "2.47 Volts", "event": "ok"}, {"name": "BMC 1.8V", "value": "1.77 Volts", "event": "ok"}, {"name": "BMC 1.2V", "value": "1.19 Volts", "event": "ok"}, {"name": "BMC 1.0V", "value": "0.99 Volts", "event": "ok"}, {"name": "BMC 3.3VSB", "value": "3.28 Volts", "event": "ok"}, {"name": "CPU_SOC", "value": "1.22 Volts", "event": "ok"}, {"name": "CPU_VDDIO", "value": "1.12 Volts", "event": "ok"}, {"name": "FAN1", "value": "2100 RPM", "event": "ok"}, {"name": "FAN2", "value": "1960 RPM", "event": "ok"}, {"name": "FAN3", "value": "2100 RPM", "event": "ok"}, {"name": "FAN4", "value": "no reading", "event": "ns"}, {"name": "FANA", "value": "no reading", "event": "ns"}, {"name": "FANB", "value": "no reading", "event": "ns"}, {"name": "FANC", "value": "no reading", "event": "ns"}, {"name": "M2_SSD1 Temp", "value": "no reading", "event": "ns"}, {"name": "M2_SSD2 Temp", "value": "no reading", "event": "ns"}, {"name": "Chassis Intru", "value": "0x00", "event": "ok"}, {"name": "NVMe_SSD1 Temp", "value": "no reading", "event": "ns"}, {"name": "NVMe_SSD2 Temp", "value": "no reading", "event": "ns"}, {"name": "GPU4 Temp", "value": "49 degrees C", "event": "ok"}, {"name": "GPU6 Temp", "value": "34 degrees C", "event": "ok"}]

@Davidj-0 i'll ping back here whenever the app is ready to be tested will be MS O365 auth to access

@archw and forgot to type "Not compatible with the "Manage Citrix PV drivers via Windows Update" option. You must disable this option before installing."

@Forza We plan to make it configurable during the upcoming months.

Helped if i read the error message.... raise RuntimeError(f"{vm_type} {vm_uuid} is {power_state}, expected Halted; refusing to fix") Shut down vm ran the fix again, and fix applied. Edit - I did have to disable secure boot on windows vms for them to boot afterwards.

@dinhngtu No, I haven't tried those. The host reboot appeared to fix the original issue and I had forgotten about them when I was troubleshooting the restart yesterday. I'll do a bit more playing around with this in a few days and report back.

@pierrebrunet Are you aware if there is an official guide on how to use this with AzureAD ?

@olivierlambert Host started and issue resolved.

I'm going to build an updated installer with an updated bnxt_en driver, as more and more servers require it.

Happy to hear that there's a potential lead, im also happy I found this thread so I can kick back and wait for Vates to fix it

@dinhngtu Hi For my i made on offline Install to solve my issue, installed failed when downloading the kernel from servers, so offline install worked fine for me.

See https://docs.xen-orchestra.com/load_balancing

@olivierlambert The only thing I can think of from newer kernels is NFS options like nconnect=xx for hopefully more speed in the day to day range of duties. As of the pre-LTS, this still wasn't in 8.3. I haven't checked after LTS.

@Andrew many thanks. As do I. See my OP. A failed build doesn't break XO. It leaves the previous successful build in place. My post wasn't to ask how to fix my problem, but to point out the issue to others who might care to know (see my last post). Cheers.

i found that whole pool is not alive enough. Can't reboot or mirgate anything. Have issue only with this 1 pool. Is it safe to reboot hosts? https://paste.vates.tech/?7e565d3abe23fd11#7JcQbjRguFpNfw281asxdmb2Zrd7GKXpuE17iDtwt3KG

@rk9268vc said in Having issues installing StartOS as a VM. Cant detect a disk for it to install to.: @TeddyAstie so can i just not run this OS on xcp-ng? is there no workaround? Would this run on proxmox? you can try adding to Linux command-line (in grub) xen_emul_unplug=never to disable PV drivers, thus making udev see ATA/NVMe drivers, maybe that's enough as long it's only the installer

Happy to get your logs to get on the bottom of this. Sadly, we don't have a CM7 around so we cannot reproduce. Thank you very much for the feedback!

I have this error too installing the new PV driver, after uninstalling Citrix driver, reboot, execute XenClean, reboot again, it said that an unsupported device is still present. I must uninstall the device by showing hidden device in Device manager and the Windows PV driver now install. So adding this step in XenClean would be appreciated.