runtime: Failed to create CoreCLR, HRESULT: 0x8007001F on MacOSX
From @nbkolchin on Sunday, March 15, 2020 5:05:59 PM
related: #10737
MacOSX: 10.15.3, dotnet installed via brew cask.
Any dotnet cli command in MacOSX fails after starting Windows inside Parallels Desktop. After stopping Parallels, dotnet commands run normally.
bash-3.2$ dotnet --info
Failed to create CoreCLR, HRESULT: 0x8007001F
Host (useful for support):
Version: 3.1.2
Commit: 916b5cba26
.NET Core SDKs installed:
3.1.102 [/usr/local/share/dotnet/sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.App 3.1.2 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 3.1.2 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download
bash-3.2$ dotnet fsi
Failed to create CoreCLR, HRESULT: 0x8007001F
bash-3.2$ dotnet run
Failed to create CoreCLR, HRESULT: 0x8007001F
Gist with COREHOST_TRACE: https://gist.github.com/nbkolchin/667e96211531eb277bdb320fcc23fc90
Copied from original issue: dotnet/sdk#10870
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 22 (22 by maintainers)
From @am11 on Monday, March 16, 2020 1:03:35 AM
Decoding this error:
reveals that it is
ERROR_GEN_FAILURE
, and it might be related to CoreCLR not being about to allocate enough memory, when Parallels is running on the system. Here is a similar discussion about FreeBSD getting the same error when VirtualBox is running on the host: https://github.com/dotnet/runtime/issues/6353#issuecomment-234250926.cc @janvorli