| Previous | Next |
| ERROR_HV_INVALID_PARTITION_ID | ERROR_HV_INVALID_PORT_ID |
ERROR_HV_INVALID_VP_INDEX
The failure is about the receiving virtual processor choice
Message and event ports ultimately target a virtual processor and a synthetic interrupt source. Hyper-V can report this status when the requested target VP no longer exists or when no available VP can accept the delivery. It can therefore appear even though the sender connection and destination port are otherwise valid.
Do not treat a VP index as a stable host CPU number. It is an identifier in the target partition's virtual-processor topology, and valid delivery also depends on the target being available to receive the chosen notification.
What to check
- Correlate the requested VP index with the current target-partition VP lifecycle, including hot removal or reset.
- For ports that can target any VP, distinguish an invalid explicit index from a situation where no enabled target is available.
- Check the target's SynIC and page configuration separately; those failures are reported as
ERROR_HV_INVALID_SYNIC_STATE. - Do not resend blindly if the consumer VM is stopping or being reconfigured; recreate or rebind the channel only after its target topology is stable.
Microsoft TLFS: virtual-processor delivery for posted messages · Microsoft TLFS: target VP and message queues
Looking for a different code? Search another status or error code.