Last Modified: Apr 10, 2019
Opened: Jan 06, 2016
On a cross-blade vCMP guest, if the guest is disabled from the hypervisor, a tmm core file may be resulted on the secondary blade.
Since the guest is in the process of being disabled, there will be no impact on traffic. The core file may take up disk spaces on the secondary blade guest.
A cross-blade vCMP guest is disabled.
To mitigate the guest disk space problem, the user has to manually delete the core file from the secondary blade guest.
The change to disable core dump on the guest is not desirable, as there may be useful information in the case the guest actually encounters a HSB failure. A fix to avoid host actions on the DMA engine allocated to the guest being disabled by the host may be a more appropriate solution.