Hang on a moment - this thread is getting very muddled. Where did we get the idea that benchmarks hadn't run from? And whose account, which host, were we talking about at the time?

It seems to have started with AndreyOR's message 71185 - but that wasn't replying to a specific prior post, and the reference to 'you' is ambiguous.

I'm assuming that the reference was to Dark Angel, who is showing two computers on his account:

Linux host 1534740
Windows host 1548438 - further assumed to be running in a VM on the Linux machine, per message 71172

As I type now, both hosts are showing a normal 'measured speed' - Linux 3.14GHz, Windows 5.73GHz (*)

Where exactly did the 'no benchmark' idea come from?

* the difference in speed between the two instances is itself interesting, but for another thread.

For some reason it's not letting me have any.
I upped the number of CPU cores and RAM in my VM last night to do more, extended my work cache settings, and freed up disk space, but it's still not giving me any more than the three I currently have.

What's your client log say about the reason it's not requesting new work? There's usually some obvious-ish reason listed.

So is there any word on when further new work will drop?

Server status currently showing 704 tasks ready to send, though doubtless that has dropped a bit since the last server update. I am guessing it may not be till next week that we get another of the batches that was mis configured sent out. The person who normally sends batches out is away and I don't know how much time Glenn has free to do this. If he doesn't have time it will have to wait till the person who normally does it is back.

Edit, 704 was from the newest batch. there were also a few retreads from 1001.

Which network adapter are you using with VirtualBox out of interest? eno1 or wlp6s0? I checked my Win10 VM and I have wlp6s0 enabled (aka wireless), which strictly speaking I shouldn't have for bridging but I was lazy and selected the first option. Curious to know if the problem only affects the ethernet adapter, eno1.

I was also reading this article about problems with the default VirtualBox ethernet network adapter being the root cause:
https://petri.com/how-to-improve-network-performance-in-windows-virtualbox-guests/
It suggests installing the virtio-net adapter type for better performance. I was trying to check the driver was not junk when I saw your fix. I might still try this though.

Ok, I did a thing. It appears to have worked. In a sense I was right about not having this problem if they were linux tasks but only because if they were I wouldn't be using a VM to run them. The problem is a bug in the Virtualbox Bridged Network adaptor.
The change I made wasn't NAT, it was to the Windows network device driver settings.
Specifically I disabled “Large Send Offload (IPv4)” in the adaptor settings.
BOOM! Next upload file runs at 2000KBps instead of 3.2

I found the solution here in the last post: https://forums.virtualbox.org/viewtopic.php?t=110486

I changed my VM networking from Bridged to NAT to see if it makes any difference but I'll have to wait until the server unlocks the files again.

I doubt that'll make any difference as that just affects how the VM appears on the local network. The outside world only sees your router IP address, not the local IPs.