Posted 02 September 2017 - 06:07 AM
I would think with host-cpu-info you should be able to compare settings and tell which one is different.
Yeah I thought so too.... but every node reported the same flags.
In the end I was disassembling the pool and found the bad node - I'd managed to live-migrate 7production VMs into the pool using --force from the CLI on another pool - they were all running 64 bit but probably would have failed to reboot!
By right-clicked a running VM to migrate it, live-migrate menu showed all 12 hosts in the pool and that node9 claimed
"the host does not have some of the CPU features that the VM is currently using"
As soon as I kicked node9 from the pool, then all was well and 64 bit VMs worked fine.
Curiously, 64 bit VMs worked perfectly on the node once it was out of the pool too. So something got confused and carried through.
I did a fresh xenserver 7.2 install on node9 and it worked fine as well, and is now member of a pool again like it should be.