Getting IP via DHCP fails on 82599-vf over ovmf UEFI

[ir1ka]

I want to passthrough 82599-vf to the virtual machine, and then do remote boot through iPXE. The following phenomena were found:

1. When I use ovmf UEFI firmware, I cannot get IP (default DHCP). The NIC ROM is bin-x86_64-efi/808610ed.efirom. Unable to ping the virtual machine from outside.
2. When using the ovmf UEFI firmware and bin-x86_64-efi/ipxe.usb, I have tried manually specifying the IP, but it doesn't seem to work because the virtual machine cannot be pinged from outside.
3. When I switch BIOS to seabios and bin/808610ed.rom, I can get IP (default DHCP). The virtual machine can be pinged from the outside.
4. When I turn off spoof checking of vf, use ovmf UEFI firmware and bin-x86_64-efi/808610ed.efirom, I can get IP (default DHCP). The virtual machine can be pinged from the outside.

[NiKiZe]

Exactly which binary? Which version? And what message? (Did you follow the guidence from the link in the message?)
What does ifstat show after the failure?
(Use Ctrl-B and run dhcp followed by ifstat)

[ir1ka]

Sorry for the late update, the main binary information has been updated, thanks.

[ir1ka]

My other virtual machines (spoof checking is on) that passthrough the vf NIC (spoof checking is on) of the can be used normally in the system.

My VMs include Windows 10, Ubuntu 20.04, RockyOS 8.5 and etc.

[NiKiZe]

In the scenario where it does not work and you boot full OS, does ping work? (Please rule out all factors except for iPXE)

[ir1ka]

In the scenario where it does not work and you boot full OS, does ping work? (Please rule out all factors except for iPXE)

Yes, it works on boot full OS. Like this:

My other virtual machines (spoof checking is on) that passthrough the vf NIC (spoof checking is on) of the can be used normally in the system.

My VMs include Windows 10, Ubuntu 20.04, RockyOS 8.5 and etc.

[ir1ka]

The following information may help resolve this issue.

On my DHCP server, I can see that 1. and 2. in the description have no lease information, and there is no relevant information in the log. while 3. and 4. can see lease information.

[stappersg]

FWIW Issue has been seen. Also seen passthrough 82599-vf to the virtual machine.

Not seen is why iPXE team should allocate further resources to this issue.

Advise for @Irikaq and all others who are bitten by the undesired behaviour, provide ways to reproduce this "feature". That in other words: Make your problem our challenge. (Yes, you are all invited to join the iPXE team.)

[NiKiZe]

Ok then, provide the information that was requested in my previous message.

[ir1ka]

Something unexpected happened when I tried to reproduce and I can't reproduce it for now, maybe I need to do more experiments to confirm it.

[NiKiZe]

Closing until the requested information is documented.