-
Notifications
You must be signed in to change notification settings - Fork 22
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
Propolis server panicked after hitting some ????????
rust_panic call stack
#755
Milestone
Comments
Also took a look at the crucible downstairs around that time and didn't see anything out of the ordinary.
|
Looking at the opcode(s), it would seem that the guest vCPU jumped off into space. This lends more credence to the necessity of #335. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@augustuswm found a VM that had a propolis server panic. Here are the propolis log lines at the time:
Both the core file and propolis log can be found in
/staff/rack3/BRM42220077/2024-08-29
(system-illumos-propolis-server:default.log.1723488297
andcore.oxz_propolis-server_cdcb2537-a5ee-4e9d-97d8-d8a86b57d2dd.propolis-server.23389.1723488093
.@leftwo got the stack from the core file:
The text was updated successfully, but these errors were encountered: