-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hermit in uhyve can't read processor frequency #30
Comments
When do you get the panic? If get_tsc_info doesn't return |
The panic occurs here (inside the rust-cpuid module) : https://github.com/gz/rust-cpuid/blob/b64cef2bbfd577b2d3e1c65b8ca76456730efa65/src/lib.rs#L3769 |
Can you specify your processor? Maybe the output of |
Sure. As you can see below, A virtual ubuntu has no problems reading the basic CPU information from kvm, so uhyve should have access to this information too. I also want to note that lscpu native Ubuntu
lscpu virtualized Ubuntu (kvm hypervisor)
|
I think that we solved this issue. Can we close it? |
Yes, the two issues I described here are now solved. |
On my system using uhyve hermit fails to read the cpu-frequency with
detect_from_cpuid
anddetect_from_cpid_tsc_info
.The first issue is that
detect_from_cpuid
can return a frequency of 0, which is Some, but not a valid value. This is fixed by #29.The second issue I encountered is that
detect_from_cpid_tsc_info
fails with a panic, due to a division by zero here: https://github.com/gz/rust-cpuid/blob/b64cef2bbfd577b2d3e1c65b8ca76456730efa65/src/lib.rs#L3769Is this something that should be fixed upstream or should we catch the panic on our side (I'm new to rust but I assume that's possible)?
The next method
detect_from_hypervisor
works fine for me.The text was updated successfully, but these errors were encountered: