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
Indicate any of these common scenarios that apply:
a program hangs under hermit
hermit panics internally
hermit runs the program but divergence (nondeterminism) occurs
To Reproduce
Minimal input to reproduce the behavior.
cargo test
Expected behavior
A clear and concise description of what you expected to happen.
all tests passed
Environment
Linux kernel version (uname -a): Linux 5.14.0-rc5 #2 SMP Sat Jun 24 11:10:07 CEST 2023 x86_64 x86_64 x86_64 GNU/Linux
CPU version (/proce/cpuinfo): Intel(R) Xeon(R) Gold 6348 CPU @ 2.60GHz
Linux distro flavor (/etc/issue, /etc/redhat-release): Ubuntu 20.04.4 LTS
Additional context
Attach the logs to this issue as a text file generated by hermit --log=trace --log-file=FOO run.
Add any other context about the problem here.
I saw other people having a similar issue but he was running hermit inside a VM. That issue was because hermit cannot intercept CPUID instruction on VMs. Here I am running on a bare metal so I wonder what might be the reason here. Is it because of some CPU features? If that's the case, is there a list of supported CPUs by hermit.
If this is a bug, I would also like to help fix it.
The text was updated successfully, but these errors were encountered:
Describe the bug
A clear and concise description of what the bug is.
I cloned hermit on the server and ran the
cargo test
. There are two failed tests.Indicate any of these common scenarios that apply:
To Reproduce
Minimal input to reproduce the behavior.
cargo test
Expected behavior
A clear and concise description of what you expected to happen.
all tests passed
Environment
uname -a
):Linux 5.14.0-rc5 #2 SMP Sat Jun 24 11:10:07 CEST 2023 x86_64 x86_64 x86_64 GNU/Linux
/proce/cpuinfo
):Intel(R) Xeon(R) Gold 6348 CPU @ 2.60GHz
/etc/issue
,/etc/redhat-release
):Ubuntu 20.04.4 LTS
Additional context
Attach the logs to this issue as a text file generated by
hermit --log=trace --log-file=FOO run
.Add any other context about the problem here.
I saw other people having a similar issue but he was running hermit inside a VM. That issue was because hermit cannot intercept CPUID instruction on VMs. Here I am running on a bare metal so I wonder what might be the reason here. Is it because of some CPU features? If that's the case, is there a list of supported CPUs by hermit.
If this is a bug, I would also like to help fix it.
The text was updated successfully, but these errors were encountered: