Exalogic Virtual: Incorrect Backup vm.cfg file Being Used During Guest vServer Startup When Backup vm.cfg File Exists Inside /OVS/Repositories Directory
Last updated on JULY 31, 2017
Applies to:Oracle Exalogic Elastic Cloud Software - Version 220.127.116.11.0 and later
Oracle Virtual Server x86-64
On Exalogic virtual racks when doing Guest vServer restarts, issue of Guest vServers starting up using incorrect backup vm.cfg file is seen. The vm.cfg file being used was the backup vm.cfg file inside /OVS/Repositories/*/backup/ directory instead of original vm.cfg file inside /OVS/Repositories/*/VirtualMachines/<Guest vServer UUID> directory.
The issue can be reproduced with following steps:
1. Create a vServer.
2. Backup the vm.cfg to /OVS/Repositories/*/backup/.
3. Make changes to Guest vServer from EMOC like updating HA flag or resizing memory which updates vm.cfg files. Or make changes to vm.cfg file manually like updating on_crash settings etc.
4. Restart the vServer.
5. After the vServer restart you will notice that the changes you made to the Guest vServer are not reflected and it is still picking the old settings.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms