Steps to replicate the issue (include links if applicable):
- Restart the hypervisor where a Trove VM is running
What happens?:
At least one Trove VM did not resume correctly when all hypervisors were shut down and restarted during T329535 (as reported in T329853).
What should have happened instead?:
Trove VMs that were running before the restart should be restarted automatically,