Github report is here: virtio issue 1453 - Read-retry errors on Windows Server 2025 with SQL Server (0.1.285+)
But please note that the network-related problems are still there (although I'm not sure if I'm affected), as it was out of my focus...
As I still wanna help you, this is the output of my quick GPT-5 Thinking session, regarding reports in this thread and the corresponding netkvm changes
Below is a focused delta review of NetKVM changes between those two points, what most...
OK, I'm quite confident that I've found and isolated the problem (and will drop it on github soon).
So let's start with the analysis. At first, be careful that virtio releases in time are not relevant to the commit dates.
I mean that if you see...
When you only have one fast network connection use that for the Ceph public network and do not configure a cluster network.
A cluster network is only useful when you have a separate physical network infrastructure that is at least twice as fast...
I did some new tests, this time with an unreleased, Pre-WHQL (i.e. non-certified) vioscsi driver 0.1.292, found here: attestation-virtio-win-prewhql-0.1-292.zip
And it was quite fast, the bug is present, still with the high incidence, so even...
Hi all, I'm the author of this ass-kicking post. After more than year, I'm back to service, as bug hunting never ends.
I'm sorry that I've missed many of the questions and messages, but let's move forward, we have another urgent problem(s).
In...
Hey everyone
Just a quick update from my side regarding the topic and my post above (#30).
I’ve been continuing to work on this idea and published it as PBS_Chunk_Checker.
The script has now been completely rewritten in Python, which gave it...
We're also testing the new Fabrics GUI and we see exactly the same behaviour with pings, even with a single fabric. Tested lots of different configurations, and the only one that makes it stable is setting node's /32 ip address to every interface...
I raised a ticket and am allowed to share the solution:
"The problem is that the ARP lookup failed because it takes the IP from the other fabric as source IP. That means with tcpdump you would have to see arp requests with whois 172.16.241.3...