We have installed OS using in-box AHCI driver (StorAhci). After OS installation we installed OSR sample VirtualMinport driver. In DriverEntry of VMinport we have added FeatureSupport , STOR_FEATURE_DUMP_POINTERS and STOR_FEATURE_DUMP_RESUME_CAPABLE. We also added support for SRB_FUNCTION_DUMP_POINTERS in StartIo of VMiniport.
As per MSDN
(https://msdn.microsoft.com/en-us/library/windows/hardware/ff552471(v=vs.85).aspx)
we were expecting, during crashdump VMiniport DriverEntry,FindAdapter should get invoked. But we saw DriverEntry, FindAdapter of StorAhci got invoked.
Is this expected behavior??
What else we need to do to ensure VMiniport gets invoked in crashdump path?
It sounds like you’re saying you boot from the AHCI controller and the system then uses the AHCI controller to write a crash dump, even though your driver is also loaded and reports being crash dump write capable?
If you want the OS to use your controller for crash dumps you need to boot from it. This generally implies you also need some sort of boot option ROM on your device that exposes the correct BIOS/UEFI interface for the OS loader.
Jan
On 9/4/15, 7:34 AM, “xxxxx@lists.osr.com on behalf of xxxxx@gmail.com” wrote:
>we were expecting, during crashdump VMiniport DriverEntry,FindAdapter should get invoked. But we saw DriverEntry, FindAdapter of StorAhci got invoked.
>Is this expected behavior??
>
>What else we need to do to ensure VMiniport gets invoked in crashdump path?
>