Reply to Message

View discussion in a popup

Replying to:
HDBR
Contributor
Contributor

Okay, I guess the heat has pretty much gone out of this one but I did get the VI web client to successfully "see" a disk created with vmkfstools.  It appears while that utility certainly creates the disk, it doesn't actually assign it to a VM (even though it seems to be embedded in the disk path spec):  until that happens, neither the VI client nor the earmarked VM can see it.  The trick was to use DCLI:

dcli com vmware vcenter vm hardware disk create --vm vm-idx --backing-type VMDK_FILE --backing-vmdk-file "[datastore] path/name.vmdk"

where idx is the "index" assigned to the VM, this can be obtained with another DCLI command:

dcli com vmware vcenter vm list

and the vmdk file path is the one previously created by vmkfstools.  When run successfully, this returns the disks integer ID and you should see it now reported against the VM's hardware with the Hard disk n label and the (I'm assuming Linux) VM will see it through the device file path /dev/sdx.

At least, that's how it's worked for me (vSphere/vCLI 6.5.0).

Reply
0 Kudos