This was the same issue I hit a few weeks ago. I ended up having to reinstall the OVMM manager with the -uuid flag and discover all my VMs again to workaround the issue. Hopefully someone from Oracle can come up with a better solution than that. Seems like it is a bad idea to try and stop the servers from the web interface at this point. Sorry I can't be of more help.
Thanks for responding moongloom. Since there were no helpful responses to your post or any replies to my post, I too decided to reinstall. I am in the process reinstalling VM Manager and it is almost complete. Perhaps Oracle can try and recreate the issue and try and resolve it. FYI my OVM and OVS are both 3.2.2
I just ran into the same issue, except with OVM 3.2.3. After a week or so without a resolution from support, I noticed 3.2.4 was available and upgraded my OVM Manager.
Within a few minutes of finishing the upgrade, the OVM server that had been rebooting continually for the past several days joined, auto discovered and is now online and healthy.
I don't see anything in the release notes to suggest 3.2.4 fixed anything, but I suspect the upgrade process cleared whatever hidden job was in the queue initiating the reboot.
Since your server was continually rebooting, do you remember if you issued a shutdown or reboot from OVM web interface? Mine was just shutting down. Have you tried to use the Oracle Virtual Manage Web Interface to either reboot or shutdown the server after your upgrade to 3.2.4? FYI I do not have support. This is my sandbox.
After a week or so without a resolution from support, I noticed ....
Are you saying that even paying for Oracle Support, they did not resolve this issue?
LOL, I have noticed as well that none of the issues we experience with Oracle VM make it to the release notes ;-)
The release notes do not seam in-line with the patches/fixes.
Its just my humble oppinion, save your self some time and headach and move to 220.127.116.115, the 3.2 releases are very bugy.
I believe I had issued a shutdown from OVM Manager on that server, because I had a rogue VM that marked HA but failing to PXE boot and was failing to start over and over again on that server.
The only reboot I've issued against that server since upgrading OVMM to 3.2.4 has been when I upgraded the server to OVS 3.2.4.
Support suspected there was a stuck shutdown job, but I couldn't find it via the CLI or GUI and I just tried the upgrade as a last ditch effort.