My Oracle Support Banner

Oracle VM 3.4.x : OVM Manager Misinterprets on_crash parameter in vm.cfg upon Refreshing Repository (Doc ID 2214836.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle VM - Version 3.4.1 to 3.4.2 [Release OVM34]
Linux x86-64

Symptoms

While vm.cfg contains on_crash = 'coredump-restart', refreshing repository causes OVM Manager to mis-interpret VM's 'Restart Action On Crash:' as "Stop After Dump", while actual vm.cfg remains 'coredump-restart'.  Likewise, if on_crash has its value 'destroy', then refreshing repository causes OVM Manager to show VM's 'Restart Action On Crash:' to "Stop after Dump" as well.  If on_crash is set to 'restart' or 'coredump-destroy', showing VM's 'Restart Action On Crash:' as  'stop after dump' which is ok.

Such issue could be observed if a VM is recently imported from the template, or if Oracle VM is upgraded from 3.3 or earlier versions.

 

Cause

To view full details, 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 a vibrant support community of peers and Oracle experts.