-
Notifications
You must be signed in to change notification settings - Fork 519
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
acrn hypervisor not handle the handle_reset_reg_read properly #8688
Labels
status: new
The issue status: new for creation
Comments
[External_System_ID] ACRN-10751 |
yonghuah
added a commit
to yonghuah/acrn-hypervisor
that referenced
this issue
Aug 9, 2024
Guest VM, such as Linux, may read RST_CNT register before writing to, in this case, ACRN should not always return dummy value. Tracked-On: projectacrn#8688 Signed-off-by: Yonghua Huang <[email protected]> Reviewed-by: Junjie Mao <[email protected]>
yonghuah
added a commit
to yonghuah/acrn-hypervisor
that referenced
this issue
Aug 9, 2024
Guest VM, such as Linux, may read platform RESET_CNT(0xCF9) register before writing to, in this case, ACRN should not always return dummy value. Tracked-On: projectacrn#8688 Signed-off-by: Yonghua Huang <[email protected]> Reviewed-by: Junjie Mao <[email protected]>
yonghuah
added a commit
to yonghuah/acrn-hypervisor
that referenced
this issue
Aug 9, 2024
Guest VM, such as Linux, may read RESET_CONTROL(0xCF9) register before writing to, in this case, ACRN should not always return dummy value. Tracked-On: projectacrn#8688 Signed-off-by: Yonghua Huang <[email protected]> Reviewed-by: Junjie Mao <[email protected]>
acrnsi-robot
pushed a commit
that referenced
this issue
Aug 12, 2024
Guest VM, such as Linux, may read RESET_CONTROL(0xCF9) register before writing to, in this case, ACRN should not always return dummy value. Tracked-On: #8688 Signed-off-by: Yonghua Huang <[email protected]> Reviewed-by: Junjie Mao <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
we find when we add the reboot=p,c,panic_w to enable the cold reset in normal reboot and warm reset when kernel panic happen, we can see only cold reboot available, while the default reboot is always warm reset.
We need the warm reset to do memory dump to help debug, as hypervisor will only return the ~0x0,
The text was updated successfully, but these errors were encountered: