Network corruption inside guest OS

[eng3]

I've noticed that when I use Virtualbox on my W10 laptop (via WIFI connection) using NAT or bridged connection, I will get network corruption. Downloads of large (~ > 10MB) files will fail signature checks.

I've tested this with two different VMs. They are debian and Kali.
If I copy the images to my W10 desktop, I have no issues. Downloads in W10 on the laptop also have no issues. It is only when inside the linux guests.
This leads me to conclude that the issue may be only happening when on a WIFI connection (my laptop does not have wired capability).
I am using an Intel AC 8260 WIFI adapter

I am using the latest version of Virtualbox and latest driver version.
I've tried turning off windows defender and I have nothing else running that should interfere.

Has anyone else encountered this issue?
I've seen some sporadic mentions on the forum over the years with no solutions posted thinking that this is either very rare or there is an obvious solution I am not seeing.

[scottgus1]

Start the guest from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the guest from within the guest OS if possible. If not possible, close the Virtualbox window for the guest with the Power Off option set.

Right-click the guest in the main Virtualbox window's guest list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.

Also, right-click the guest in the main Virtualbox window's guest list, choose Show in Explorer. Zip the guest's .vbox file, and post the zip file, using the forum's Upload Attachment tab.

[eng3]

See attached

[eng3]

Note that there is no log activity during the period of the observed network corruption

[scottgus1]

Hyper-V is enabled. See HMR3Init: Attempting fall back to NEM (Hyper-V is active).

You're Bridging to Wi-fi. Bridged doesn't always work well with Wi-fi, see Virtualbox Networks: In Pictures.

The CPU core count of the guest is severely overprovisioned (hyperthreads don't count for Virtualbox):

00:00:03.257729 NumCPUs (in guest)<integer> = 0x0000000000000004 (4)
00:00:04.010500 CPUM: Physical host cores: 2

The network connection might not be an issue, but Hyper-V has been known to corrupt the hash checks. Disable Hyper-V as above, and set the guest processors to 2 max. Be aware that if the guest goes full throttle on both cores the host might go unstable. See if you still get network trouble.

[eng3]

Hyper-V was the issue. I am well aware of this compatibility issue with Virtualbox. However, I saw that it was not enabled in Add/Remove features window and though it was disabled. I wasn't aware of the command to run. After doing that, the issue went away.

I had the issue with NAT and bridging and the bridged wifi is working now so at least for me, it's working.

I'm aware of the recommendation to use the physical CPU count. I do check the performance of all my VMs where perform heavy processing and thus far in every case, I have had significantly better performance when I use the number of logical cores instead.

[scottgus1]

Glad you got Hyper-V turned off and are running well again!

Have to say that

significantly better performance when I use the number of logical cores instead.

is far different from usual forum advice. But, whatever floats the boat... If it works for you then I won't complain if you don't.