Questionable on Hyper-V on customer editions (Windows 10 and 11)

[anhvlttfs]

Since DDA only works on Windows Server, and if the assignment is made on a virtual machine on client Windows host, it will never be able to boot.

Question:

1. The only possible resolution for this is applying the flag of ProductType with value either 2 or 3 of class Win32_OperatingSystem or installing license of Windows Server onto Windows Client. However, this should not be a solution, as the Hyper-V DPD only helps on the Hyper-V (including manipulation of data on the namespace of virtualization\v2)
2. How on the earth can the Hypervisor detects and blocks a virtual machine if it has a PCIe device passthrough it on the client Windows host
3. If the detection is running within the namespace of virtualization\v2, how to, specifically, make the virtual machine boot with a PCIe device?

I also have looked for the errors of "A hypervisor feature is not available to the user" on Error Lookup Tool. Hope those may help.

# for hex 0xc035001e / decimal -1070268386
  STATUS_HV_FEATURE_UNAVAILABLE                                  ntstatus.h
# A hypervisor feature is not available to the user.
  ERROR_HV_FEATURE_UNAVAILABLE                                   winerror.h
# A hypervisor feature is not available to the user.
# as an HRESULT: Severity: FAILURE (1), FACILITY_USERMODE_HYPERVISOR (0x35), Code 0x1e
# for hex 0x1e / decimal 30
  ERROR_READ_FAULT                                               winerror.h
# The system cannot read from the specified device.
# 3 matches found for "0xC035001E"

[shiroinekotfs]

In the respond, I will not claim that there is impossible for the Windows 10/11 to implement PCIe passthrough. Instead, I will just the link of a blog

https://ourwindowsman.wordpress.com/2020/12/11/the-magic-flag-mystery/

Hope with those hypercalls, you can investigate further.

[anhvlttfs]

In the respond, I will not claim that there is impossible for the Windows 10/11 to implement PCIe passthrough. Instead, I will just the link of a blog

https://ourwindowsman.wordpress.com/2020/12/11/the-magic-flag-mystery/

Hope with those hypercalls, you can investigate further.

Well, thanks. I just look up for the debugging snapshot of that blog.

Also, I found out some good old BCD configurations, that may help further investigate of the Hyper-V itself.

https://geoffchappellmirror.github.io/notes/windows/boot/bcd/elements.htm

[anhvlttfs]

@shiroinekotfs

If possible, can you investigate further for whatever the valid value of BcdOSLoaderString_HypervisorProductSkuType on the BCD?

The unofficial documentation is above.

[shiroinekotfs]

@shiroinekotfs

If possible, can you investigate further for whatever the valid value of BcdOSLoaderString_HypervisorProductSkuType on the BCD?

The unofficial documentation is above.

Instead of status of investigating, I will just nya~