Docs: VirtIO-Win driver compatibility with MS SQL Server workloads#455
Open
jasnoyaeger wants to merge 1 commit into
Open
Docs: VirtIO-Win driver compatibility with MS SQL Server workloads#455jasnoyaeger wants to merge 1 commit into
jasnoyaeger wants to merge 1 commit into
Conversation
Documents the vioscsi/viostor SRB ID race condition in virtio-win v0.1.285 and v0.1.292 (upstream issue #1453) that produces SQL Server read-retry errors on heavily loaded Windows VMs, especially on Windows Server 2025. Includes driver version verification, the recommended v0.1.271 downgrade path, and the clean uninstall procedure. Refs #454 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/knowledge-base/posts/virtio-win-mssql-compatibility.mdvioscsi/viostorSRB ID race condition in virtio-win v0.1.285 and v0.1.292 (commit1bbc422) that surfaces as SQL Server read-retry log entries on heavily loaded Windows VMs, most acutely on Windows Server 20250x80070643rollback workaround)loading-virtio-drivers-in-windows-recovery-console,database-best-practices) using slug-style absolute URLs so they survive file renamesRefines the original issue framing: upstream confirms these are read-retry messages with matching expected/actual values, not on-disk corruption —
DBCC CHECKDBtypically comes back clean. The article reflects this so customers aren't sent chasing a corruption hunt.Closes #454
Test plan
mkdocs serve— confirm the article renders, admonitions display correctly, and there are no broken-link warnings/knowledge-base/loading-virtio-drivers-in-windows-recovery-consoleand/knowledge-base/database-best-practices) resolve in the served site.28500→ 0.1.285,.27100→ 0.1.271) holds in observed customer environments🤖 Generated with Claude Code