Skip to content

.NET 9 container SIGILL for rdvl (a normal SVE instruction) on Apple M4 #133030

Closed

Description

@OPS-NeoRetro

Description

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.

Reproduction Steps

Refer to orbstack/orbstack#2670.

Expected behavior

Refer to orbstack/orbstack#2670.

Actual behavior

Refer to orbstack/orbstack#2670.

Regression?

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.

Activity

  1. dotnet-policy-service commented on Sep 1, 2026

    @dotnet-policy-service
    Contributor

    Tagging subscribers to this area: @dotnet/area-meta
    See info in area-owners.md if you want to be subscribed.

  2. OPS-NeoRetro commented on Sep 1, 2026

    @OPS-NeoRetro
    Author
  3. added
    area-CodeGen-coreclrCLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI
    arm-sveWork related to arm64 SVE/SVE2 support
    and removed on Sep 1, 2026
  4. dotnet-policy-service commented on Sep 1, 2026

    @dotnet-policy-service
    Contributor

    Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
    See info in area-owners.md if you want to be subscribed.

  5. EgorBo commented on Sep 1, 2026

    @EgorBo
    Member

    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

  6. AndyAyersMS commented on Sep 1, 2026

    @AndyAyersMS
    Member

    .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.

  7. OPS-NeoRetro commented on Sep 2, 2026

    @OPS-NeoRetro
    Author

    .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.

  8. AndyAyersMS commented on Sep 2, 2026

    @AndyAyersMS
    Member

    @agocke do you think we'd take a fix for this for .NET 9?

  9. agocke commented on Sep 2, 2026

    @agocke
    Member

    Is this also in 8.0 or is this 9.0-specific?

  10. AndyAyersMS commented on Sep 2, 2026

    @AndyAyersMS
    Member

    Looks like only 9.0 and up (already fixed in 10+).

  11. added and removed
    area-CodeGen-coreclrCLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI
    on Sep 2, 2026
  12. removed
    untriagedNew issue has not been triaged by the area owner
    on Sep 2, 2026
  13. dotnet-policy-service commented on Sep 2, 2026

    @dotnet-policy-service
    Contributor

    Tagging subscribers to this area: @agocke
    See info in area-owners.md if you want to be subscribed.

  14. OPS-NeoRetro commented on Sep 4, 2026

    @OPS-NeoRetro
    Author

    @agocke, @VSadov, will the fix actually land? If not, then I'll have to do it myself.

  15. OPS-NeoRetro commented on Oct 12, 2026

    @OPS-NeoRetro
    Author

    orbstack/orbstack#2670 has been closed, so I'm now closing this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    • Status
      No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions