Determine when the VM first writes to the VMDK.

Products

• VMware vSphere ESXi

Issue/Introduction

In some cases, after adding a VMDK to a VM, and need to determine if the Guest OS is able to issue an IO to the VMDK. 

Environment

vSphere 7.x

vSphere 8.x

 

Resolution

Add a VMDK to a VM 

[vmware.log]
In(05) vmx mbq15ar9-2074670-auto-18gtr-h5:70469473-4d-01-32-4ad5 DISK: OPEN scsi0:1 '/vmfs/volumes/######-######-######-######/<VM_NAME>/<VM_NAME>.vmdk' persistent R[]
In(05) vmx mbq15ar9-2074670-auto-18gtr-h5:70469473-4d-01-32-4ad5 DISK: Disk '/vmfs/volumes/######-######-######-######/<VM_NAME>/<VM_NAME>.vmdk' has UUID '60 00 c2 9f 1d 33 99 88-51 10 87 26 0c 32 b4 84'
In(05) vmx mbq15ar9-2074670-auto-18gtr-h5:70469473-4d-01-32-4ad5 DISK: OPEN '/vmfs/volumes/######-######-######-######/<VM_NAME>/<VM_NAME>.vmdk' Geo (401024/255/63) BIOS Geo (0/0/0)
No(00) vmx mbq15ar9-2074670-auto-18gtr-h5:70469473-4d-01-32-4ad5 ConfigDB: Setting scsi0:1.fileName = "<VM_NAME>.vmdk"

[vmkernel.log]
In(182) vmkernel: cpu43:6330273 opID=8dd99cfc)World: 12745: VC opID mbq15ar9-2074670-auto-18gtr-h5:70469473-4d-01-32-4ad5 maps to vmkernel opID 8dd99cfc
In(182) vmkernel: cpu43:6330273 opID=8dd99cfc)VSCSI: 5394: handle 0(GID:0)(vscsi0:1):handle->blockSize : 512, handle->numBlocks : 6442450944, handle->length = 3298534883328, BE-blockSize : 512
In(182) vmkernel: cpu43:6330273 opID=8dd99cfc)VSCSI: 5473: handle 27188328398856238(GID:8238)(vscsi0:1):Creating Virtual Device for world 6330276 (FSS handle 447747448) numBlocks=6442450944 (bs=512)
In(182) vmkernel: cpu43:6330273 opID=8dd99cfc)VSCSI: 272: handle 27188328398856238(GID:8238)(vscsi0:1):Input values: res=0 limit=-2 bw=-1 Shares=1000

 

The first time GOS writes to the VMDK 

[vmware.log]
In(05) vcpu-0 - HBACommon: First write on scsi0:1.fileName='/vmfs/volumes/######-######-######-######/<VM_NAME>/<VM_NAME>.vmdk'
[vmkernel.log]
In(182) vmkernel: cpu5:6330286)VSCSI: 8329: Handle: 27188328398856238 CID update old=0xfcdb849e new=0x7376df2a