VMware vSphere

 View Only
  • 1.  vCenter - VCSA machine NMI watchdog: BUG: soft lockup -CPU#

    Posted Nov 30, 2023 08:58 PM
      |   view attached

    Hello,

    I've been having issues with our VCSA machine with regards to backups (using Veeam). 

     

    This is the warning message from Veeam 

    Removing VM snapshot... (0% done)
    Removing VM snapshot Details: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

     

    From the above I noticed the archive disk was 95% full so I removed any files older than 40 days. Ran the back up again and received the same Veeam error. 

     

    Currently the VCSA monitor has a lot of 'NMI watchdog: BUG: soft lockup -CPU#...  (image attached).

     

    I am trying to figure out of this is an issue that Veeam is causing, or an issue with the VCSA machine, which is causing the backup issues. 

     

     

    vCenter information:

    VMware® vSphere®
    vSphere Client version 6.7.0.54000

     

    VCSA Machine Info

     
     
    VMware Tools:
    • Running Status:Running
    • Version11365 (11.3.5)
    • Version Status:Guest Managed
      The VMware Tools status is unknown. A VMware Tools

     

    Thank you, Ryan



  • 2.  RE: vCenter - VCSA machine NMI watchdog: BUG: soft lockup -CPU#

    Posted Dec 01, 2023 01:36 AM

    NMI watchdog BUG soft lockup CPU this message can be ignore

    The most common cause for this could be due to the system is stunned or suffering very high latency

    https://kb.vmware.com/s/article/6

     

    remove vcsa vm from veeam , then reboot vcsa and trigger new back up

    During the backup check disk latency , and vcsa backup should be in off business' hour other backup should not running along with vcsa



  • 3.  RE: vCenter - VCSA machine NMI watchdog: BUG: soft lockup -CPU#

    Posted Dec 01, 2023 03:28 PM

    Thanks Rajeev,

    I will try those steps and then reply back here.