[VMC on AWS] VMs become unmanageable and are unable to shut down, reset, or vMotion, saying "Syscall kill returned error (-1)"
search cancel

[VMC on AWS] VMs become unmanageable and are unable to shut down, reset, or vMotion, saying "Syscall kill returned error (-1)"

book

Article ID: 334968

calendar_today

Updated On:

Products

VMware Cloud on AWS VMware Cloud on Dell EMC

Issue/Introduction

To explain the troubleshooting steps and resolution.

Symptoms:

Customer VMs crash and become unmanageable. They cannot be moved to another host, shut down, reset, or anything else.

You will see constant vSphere HA reset attempts in the VM tasks.

There should be an error that states "Syscall kill returned error (-1) during vm termination attempt: with cartel id: <cartel ID> and error message: No such process" in LINT for that VM.


Cause

A race condition in NVME ring processing logic.

Resolution

Please create a VMC Support Request (Creating and managing Broadcom support cases) with a screenshot of the error and a reference to this KB.

Additional Information

Impact/Risks:
Customer will be unable to use the affected VMs.