vmware.log, you see entries similar to:[YYYY-MM-DDTHH:MM:SS] In(05) vmx - Module 'DevicePowerOn' power on failed
/var/run/log/vmkernel.log, you see entries similar to:[YYYY-MM-DDTHH:MM:SS] In(182) vmkernel: cpu5:2104019)PCIPassthru: 4636: pcipDevInfo(0x431f80001610) allocated for xxxx:xx:xx.x[YYYY-MM-DDTHH:MM:SS] In(182) vmkernel: cpu5:2104019)PCI: 1363: Skipping device reset on xxxx:xx:xx.x; no reset method found[YYYY-MM-DDTHH:MM:SS] In(182) vmkernel: cpu5:2104019)PCIPassthru: 5333: xxxx:xx:xx.x :Reset for device failed with Not supported[YYYY-MM-DDTHH:MM:SS] In(182) vmkernel: cpu5:2104019)PCIPassthru: 1039: pcipdevInfo: 0x431f80001610 (xxxx:xx:xx.x), state 0, destroyed[YYYY-MM-DDTHH:MM:SS] In(182) vmkernel: cpu5:2104019)PCIPassthru: 4636: pcipDevInfo(0x431f80001610) allocated for xxxx:xx:xx.x[YYYY-MM-DDTHH:MM:SS] In(182) vmkernel: cpu5:2104019)PCI: 1363: Skipping device reset on xxxx:xx:xx.x; no reset method found[YYYY-MM-DDTHH:MM:SS] In(182) vmkernel: cpu5:2104019)PCIPassthru: 5333: xxxx:xx:xx.x :Reset for device failed with Not supported[YYYY-MM-DDTHH:MM:SS] In(182) vmkernel: cpu5:2104019)PCIPassthru: 1039: pcipdevInfo: 0x431f80001610 (xxxx:xx:xx.x), state 0, destroyed[YYYY-MM-DDTHH:MM:SS] In(182) vmkernel: cpu5:2104019)PCIPassthru: 4636: pcipDevInfo(0x431f80001610) allocated for xxxx:xx:xx.x[YYYY-MM-DDTHH:MM:SS] In(182) vmkernel: cpu5:2104019)PCI: 1363: Skipping device reset on xxxx:xx:xx.x; no reset method found[YYYY-MM-DDTHH:MM:SS] In(182) vmkernel: cpu5:2104019)PCIPassthru: 5333: xxxx:xx:xx.x :Reset for device failed with Not supported[YYYY-MM-DDTHH:MM:SS] In(182) vmkernel: cpu5:2104019)PCIPassthru: 1039: pcipdevInfo: 0x431f80001610 (xxxx:xx:xx.x), state 0, destroyed[YYYY-MM-DDTHH:MM:SS] In(182) vmkernel: cpu5:2104019)PCIPassthru: 4636: pcipDevInfo(0x431f80001610) allocated for xxxx:xx:xx.x[YYYY-MM-DDTHH:MM:SS] In(182) vmkernel: cpu5:2104019)PCI: 1363: Skipping device reset on xxxx:xx:xx.x; no reset method found
This is a known issue. Currently there is no resolution.
To workaround this issue follow the below steps,
NOTE: Setting enablePCIEHotplug=FALSE prevents ESXi from enabling hot-plug during server boot, even if the hardware supports it.
Disable PCIe Hot-Plug by running the following command on the ESXi host:esxcli system settings kernel set -s "enablePCIEHotplug" -v "FALSE"
Modify the passthrough configuration
cp /etc/vmware/passthru.map /etc/vmware/passthru.map.bak vi/etc/vmware/passthru.map.Verify that PCIe device hot-plug is disabled by entering the command:
esxcli system settings kernel list -o enablePCIEHotplug
The entry, "FALSE," should be displayed under the Configured column:Name Type Configured Runtime Default Description ------------ ---- --------- ------ ------- -----------enablePCIEHotplug Bool FALSE FALSE TRUE Enable PCI-E Native Hotplug support