You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
.NET 9 container SIGILL for rdvl (a normal SVE instruction) on Apple M4 #133030
This is a proxy issue for orbstack/orbstack#2670. Once this issue is closed, the OrbStack issue should be closed in a short amount of time following the closure of this issue. Refer to title.
This is a similar regression to users of .NET Core 10 in Linux containers and VMs on Apple M4 and M5-series systems.
Known Workarounds
Users have worked around by downgrading their OrbStack version from 2.2.3 or higher to 2.2.2. This masked away SME support from CPUID and feature ID MSRs in OrbStack containers, causing the problem to disappear.
Configuration
.NET 9.0
MacOS Tahoe host
ARM64
Very specific to Apple M4 and M5 systems running ARM64 .NET Core in Linux containers and VMs
Other information
ARM-software/ComputeLibrary#1306 is a closely related issue. I wrote a comment there about why Apple's ARM SME is different from the real ARM SME.
.NET 9 is going out of service very soon (Nov 10, 2026). Since there is a workaround and .NET 10 contains a fix I'm not sure if we'd port this even further back.
.NET 9 is going out of service very soon (Nov 10, 2026). Since there is a workaround and .NET 10 contains a fix I'm not sure if we'd port this even further back.
Wait, I think this must be fixed, because this involves applications with any vector processing, and there is a new M5 Ultra chip coming next year with 4 M5 Max dies fused together. I don't know if the M6 will have SVE all around, but it is safe to just backport the fix to .NET 9 ASAP. The fix was made 5 months ago, and there is only 2 months left until .NET 9 officially goes out of official support.
Activity
dotnet-policy-service commentedon Sep 1, 2026
Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.
OPS-NeoRetro commentedon Sep 1, 2026
@agocke @VSadov @kotlarmilos
dotnet-policy-service commentedon Sep 1, 2026
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.
EgorBo commentedon Sep 1, 2026
I presume it was fixed in .NET 11.0 via #127398 and backported to 10.0, but not to 9.0 (it is approaching EOL btw)
cc @AndyAyersMS
AndyAyersMS commentedon Sep 1, 2026
.NET 9 is going out of service very soon (Nov 10, 2026). Since there is a workaround and .NET 10 contains a fix I'm not sure if we'd port this even further back.
OPS-NeoRetro commentedon Sep 2, 2026
Wait, I think this must be fixed, because this involves applications with any vector processing, and there is a new M5 Ultra chip coming next year with 4 M5 Max dies fused together. I don't know if the M6 will have SVE all around, but it is safe to just backport the fix to .NET 9 ASAP. The fix was made 5 months ago, and there is only 2 months left until .NET 9 officially goes out of official support.
AndyAyersMS commentedon Sep 2, 2026
@agocke do you think we'd take a fix for this for .NET 9?
agocke commentedon Sep 2, 2026
Is this also in 8.0 or is this 9.0-specific?
AndyAyersMS commentedon Sep 2, 2026
Looks like only 9.0 and up (already fixed in 10+).
dotnet-policy-service commentedon Sep 2, 2026
Tagging subscribers to this area: @agocke
See info in area-owners.md if you want to be subscribed.
OPS-NeoRetro commentedon Sep 4, 2026
@agocke, @VSadov, will the fix actually land? If not, then I'll have to do it myself.
build: lockstep versions, shared pack checks and safer test matrix
OPS-NeoRetro commentedon Oct 12, 2026
orbstack/orbstack#2670 has been closed, so I'm now closing this