@pierrebrunet fixed now, thanks.

@olivierlambert yes.

@olivierlambert 8.3

After commit 36d1e883e2ef02375ec7cd0cf6170cde167a5974 everything looks like

Every disk created by XO not supported by XO? What a criteria of "unsupported"?

I found that mac address and disks are not syncing. Is it possible to add them?

@psafont
nvm something weird happens. I removed cert and everything fixed. Thank you.
Need to specify extention xe pool-uninstall-ca-certificate name=sdn-controller-ca.pem --force

But this cert shouldn't exist at backup because i never use sdn, plugin is disabled. Other hosts has no this cert. Looks like bug?

@psafont
is it safe to remove it on production pool?

whenever the SDN controller is turned on.

so, i can do something on new host, before joining into pool to generate this cert?

i tried https://docs.xenserver.com/en-us/xenserver/8/dr/backup.html#back-up-single-host-installations but, "command not found".

At this time, the meta restore works perfectly. I got all my VMs back, but

• since I don't believe in success, I didn't shut down the unavailable slave host, where the VMs was still running.
• After restoring on a new master, all the VMs were also running.
• except for IP conflicts, in that case I had double VDI usage!
• The old server was shut down ASAP, but some VDIs were still corrupted anyway.

This wasn't a critical issue, but after EMERGENCY restoration, I expected that the host would be in emergency mode and the VMs would be halted.

And next problem. How to restore info about VMs?
2nd affected pool https://xcp-ng.org/forum/post/95369 lost master, all VMs now running on slave which i can't connect.
If setup new host and reconnect it to SR, i only can get a VDI, not VM itself.

My pool died so i decied to restore it from backup.

• fresh xen install, retore metadata, everything looks fine, but i can't join any new hosts into this pool.
  https://paste.vates.tech/?ca81f43fd2d10456#Ay6yKRNTS8LDDSHTkin7eLppP33eAMS5grLrevuqf5rL

• ok, 3 hosts fresh install, joined into pool, restore metadata - i got pool with 1 host and others 2 removed from XO.
  2nd host unavailable, as i see it got same IP as 1st.
  3rd host - nothing happens.
  https://paste.vates.tech/?112eb74c063a36d9#cgQi8jsG4htscEtEtAUS9vqRWnGQvD6REXd3XAzCxK2

• i add 2nd host with his "old" ip to XO. But can't connect and can't remove. Probably, IP change happens at this time.
  https://paste.vates.tech/?2c81fd68ed70cff2#7jXMPfj8wGePEC6KDTpTX9GVDmc2kuLG9Kd7ueb6MfSv
  https://paste.vates.tech/?07a7b2f07f699815#5w3qM7R7eVAauQ7rGGN3Wwx5DgQF2QejbJZcQh949Uqu

Only way i found to remove it - disable, change ip to not existed, tried to connect, remove works after error.

That looks like bloody mess. No host mapping, random results, pool is blocked from any new hosts in future.

@olivierlambert damn it at very bottom of page) i checked the doc first.

@florent wow, easter egg. thanks.

How about to create public api resource like swagger? or maybe bundled with XO.

@DustinB I advise you not to decide for others what they should do. I'm tired.

@DustinB yes, you can do it.

@DustinB the problem is that wrong drivers could be installed on wrong OS without warning. nothing else.

@DustinB meh. This VMs cost me nothing, i spend zero time since it can't stop working. Not a my decision, not my job, not my problem.

@DustinB Some things can't be migrated to anything else.

new tools has no 2012 server support. https://xcp-ng.org/forum/topic/10888/xsa-468-multiple-windows-pv-driver-vulnerabilities-update-now/40?_=1748855490094

it looks we need v9.2.3 for 2012. https://docs.xenserver.com/en-us/xenserver/8/vms/windows/vm-tools.html#923

i have old citrix tools 9.3.1, XO detect them.