Ad Widget

Collapse

vmware.vm.vfs.dev.discovery is not discovering NVME controller virtual disks

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • netscaper
    Junior Member
    • Aug 2022
    • 3

    #1

    vmware.vm.vfs.dev.discovery is not discovering NVME controller virtual disks

    Hello, please advise. We have Zabbix 5.0 and template "Virt VMware Guest" in that template is discovery of "Disk device discovery" and we have VMs that have not only IDE or SCSI disks but NVME disks.
    Item in prototype " vmware.vm.vfs.dev.read[{$URL},{HOST.HOST},{#DISKNAME},bps]" and where is #DISKNAME should be after discovery - vmware.vm.vfs.dev.read[{$URL},{HOST.HOST},scsi0:0,bps] as You see SCSI or IDE disk, but fo VM with NVME controller disk is not discovered.
    It is better in 6.0-6.2 version? I did not find any information about that in forum or documentation.
    Thanks
  • jtnfoley
    Member
    • Mar 2022
    • 76

    #2
    (waves wand) Threadus resurrectus!

    Not sure how we feel about necroposting here. I'm having the same issue - I have a very large data warehouse server that I migrated from HDD/NAS storage to SSD/SAN, and in order to eek the greatest performance out of the I/O stack I changed the HBAs to NVMe (from VMWare ParaVirtual SCSI.)
    Since changing HBAs, all my NVME filesystems now report "Performance counter instance was not found." in Zabbix.

    vmWare 7.0.3uSomething, Zabbix 7.2.6 upgraded from Zabbix 6.0.something (upgrade path may be noteworthy, since, as I understand it, the template for VMWare Guest will not have been upgraded during the 6.0.x->7.2.x migration??)

    Comment

    • Viktors Fomics
      Member
      • Oct 2025
      • 42

      #3
      Originally posted by jtnfoley
      Zabbix 7.2.6 upgraded from Zabbix 6.0.something (upgrade path may be noteworthy, since, as I understand it, the template for VMWare Guest will not have been upgraded during the 6.0.x->7.2.x migration??)
      Looks like the VMware template changed notably between 6.0 and 7.2, so might be a good idea to manually update the template to the corresponding version too and see if it helps.

      Comment

      Working...