OID_SRIOV_VF_SERIAL_NUMBER
An overlying driver issues an object identifier (OID) query request of OID_SRIOV_VF_SERIAL_NUMBER to determine the serial number of the PCI Express (PCIe) Virtual Function (VF) network adapter. This virtual network adapter is exposed in the guest operating system of a Hyper-V child partition to which the VF is attached.
The InformationBuffer member of the NDIS_OID_REQUEST structure contains a pointer to an NDIS_SRIOV_VF_SERIAL_NUMBER_INFO structure.
Remarks
The overlying driver uses the serial number to map the VF network adapter to an instance of a VF on the physical network adapter. The serial number is generated by the virtualization stack before resources for the VF are allocated through an OID set request of OID_NIC_SWITCH_ALLOCATE_VF.
Return Status Codes
NDIS handles the OID query request of the OID_SRIOV_VF_SERIAL_NUMBER request for miniport drivers. The drivers will not be issued this OID request.
When NDIS handles the OID_SRIOV_VF_SERIAL_NUMBER request, it returns one of the following status codes.
| Status Code | Description |
|---|---|
NDIS_STATUS_SUCCESS |
The OID request completed successfully. |
NDIS_STATUS_NOT_SUPPORTED |
The miniport driver either does not support the single root I/O virtualization (SR-IOV) interface or is not enabled to use the interface. |
NDIS_STATUS_INVALID_LENGTH |
The information buffer was too short. NDIS sets the DATA.QUERY_INFORMATION.BytesNeeded member in the NDIS_OID_REQUEST structure to the minimum buffer size that is required. |
NDIS_STATUS_FAILURE |
The request failed for other reasons. |
Requirements
Version |
Supported in NDIS 6.30 and later. |
Header |
Ntddndis.h (include Ndis.h) |
See also
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for