Try to add RDM disk to VM got error "Incompatible device backing specified for device '0'". about vsphere-automation-sdk-python HOT 15 CLOSED

@14kosta Apologies for the late response.

Can you try to comment out "type=Disk.HostBusAdapterType.SCSI," when creating the Disk.CreateSpec?

If it's still not working. Could you please post the stacktrace from /var/log/vmware/vpxd/vpxd.log so we get more info?

from vsphere-automation-sdk-python.

Hi tianhao64,
Commenting out "type=Disk.HostBusAdapterType.SCSI," doesn't help - I get the same error.
Attaching vpxd.log
vpxd.zip

Thank you

from vsphere-automation-sdk-python.

@14kosta Hmm. the log doesn't have related error message. Will ask the storage expert to take a look. Meanwhile, can you check this post? https://cormachogan.com/2013/04/08/microsoft-clustering-on-vsphere-incompatible-device-errors/

from vsphere-automation-sdk-python.

Hi tianhao64,
I looked at the sent by you link. My configuration is the following: I have SCSI device /vmfs/devices/disks/eui.57df0280647efa2de9751c5d0000000 that is seen on three ESXi hosts. Then I attaching it to VM that is on one of ESXi hosts and the command fails thru SDK, but succeeded thru PowerCli and Web client. Situation described in the sent link looks for me a little bit different.
Thank you

from vsphere-automation-sdk-python.

I filed a SR against the storage team. Will keep you posted. Can you check hostd.log see if you see related error message?

from vsphere-automation-sdk-python.

Command "find / -name hostd" doesn't return any hostd.log on vCenter or ESXi. Where to search for it?
BTW, in debugger I see that the error comes from requests module i.e. really comes from a server side.

from vsphere-automation-sdk-python.

Modern versions of ESXi keep the hostd.log in /var/run/log. Generally when you pull down a vm-support, the files will be gzip'ed

from vsphere-automation-sdk-python.

when I run RDM mapping in the file /var/log/hostd.log (which is the link to /var/run/log/hostd.log) appears the following error:
2019-01-13T10:02:19.576Z info hostd[2099318] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/5bdb7b78-27334b79-c9e6-2c600c66a3ff/RHEL70_thick13/RHEL70_thick13.vmx opID=2aebc039-01-e6-9f95 user=vpxuser:AUTO01.LOCAL\Administrator] Send config update invoked
2019-01-13T10:02:19.611Z info hostd[2099318] [Originator@6876 sub=Libs opID=2aebc039-01-e6-9f95 user=vpxuser:AUTO01.LOCAL\Administrator] DictionaryLoad: Cannot open file "/usr/lib/vmware/config": No such file or directory.
2019-01-13T10:02:19.611Z info hostd[2099318] [Originator@6876 sub=Libs opID=2aebc039-01-e6-9f95 user=vpxuser:AUTO01.LOCAL\Administrator] Could not expand environment variable HOME.
2019-01-13T10:02:19.611Z info hostd[2099318] [Originator@6876 sub=Libs opID=2aebc039-01-e6-9f95 user=vpxuser:AUTO01.LOCAL\Administrator] DictionaryLoad: Cannot open file "~/.vmware/config": No such file or directory.
2019-01-13T10:02:19.614Z info hostd[2099318] [Originator@6876 sub=Vimsvc.TaskManager opID=2aebc039-01-e6-9f95 user=vpxuser:AUTO01.LOCAL\Administrator] Task Completed : haTask-5-vim.VirtualMachine.reconfigure-1122499 Status error
2019-01-13T10:02:19.614Z warning hostd[2099318] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/5bdb7b78-27334b79-c9e6-2c600c66a3ff/RHEL70_thick13/RHEL70_thick13.vmx opID=2aebc039-01-e6-9f95 user=vpxuser:AUTO01.LOCAL\Administrator] Reconfigure failed

from vsphere-automation-sdk-python.

Hi tianhao64,
I run RDM mapping and simultaneously took vpxd.log (attached to this message) and hostd.log
(see the previous message).
In the current vpxd.log appears "Incompatible device backing specified for device '0'.":
vim.fault.InvalidDeviceBacking:
--> Result:
--> (vim.fault.InvalidDeviceBacking) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = ,
--> property = ,
--> deviceIndex = 0
--> msg = "Incompatible device backing specified for device '0'."
--> }
vpxd.zip

from vsphere-automation-sdk-python.

Hi tianhao64,
Any news about this issue?

from vsphere-automation-sdk-python.

No update from the feature team yet. Will ping them again.

from vsphere-automation-sdk-python.

@tianhao64 , thank you!

from vsphere-automation-sdk-python.

@tianhao64
Was there any progress from the feature team?

@14kosta
Do you know if this issue still exists with the latest SDK?

from vsphere-automation-sdk-python.

from vsphere-automation-sdk-python.

@14kosta
I am very sorry to hear that. The teams are distributed and features sometimes don't make it to the priority list and are kept hanging. We will try to fix this gap in the future.
Glad you were able to resolve with powercli.

from vsphere-automation-sdk-python.