Steps performed:
1) NVMe controller is passed through to a Windows 10 VM
2) Perform any PCI reset - Hot reset/ Warm reset/ Sub system reset:
- Device is resetting
- NVMe controller is configured successfully and ready
- but, here onwards commands are timing out because MSIX values are no longer valid
- It works after a manual rescan is performed
Further observations:
* PCI trace shows Config Read/ Write 1 which is for a switch device.
* Devices are visible in both host and VM, with different BAR values
* We are getting new address for MSIX after POR, which is seen only after manual rescan
* In PCI config space only RW fields are resetting to 0xffff, other values are still there. Normally entire config space should be reset
Please suggest if any additional step/ configuration required.
1) NVMe controller is passed through to a Windows 10 VM
2) Perform any PCI reset - Hot reset/ Warm reset/ Sub system reset:
- Device is resetting
- NVMe controller is configured successfully and ready
- but, here onwards commands are timing out because MSIX values are no longer valid
- It works after a manual rescan is performed
Further observations:
* PCI trace shows Config Read/ Write 1 which is for a switch device.
* Devices are visible in both host and VM, with different BAR values
* We are getting new address for MSIX after POR, which is seen only after manual rescan
* In PCI config space only RW fields are resetting to 0xffff, other values are still there. Normally entire config space should be reset
Please suggest if any additional step/ configuration required.
Last edited: