Skip to content
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.

Sign up for GitHub

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

Jump to bottom

ACRN hypervisor crash when Post-launched resume from S3 #8577

Open
yonghuah opened this issue Apr 15, 2024 · 1 comment
Open

ACRN hypervisor crash when Post-launched resume from S3 #8577

yonghuah opened this issue Apr 15, 2024 · 1 comment
Labels
status: new The issue status: new for creation

Comments

@yonghuah
Copy link
Contributor

Steps:

  1. suspend post-launched VM
  2. suspend ACRN service VM
  3. wakeup Service VM
  4. wakeup Post-launched VM "acrnd -t"

Note: this issue does not impact VM that LAPIC PT is not configured.*
ACRN hypervisor crash in this case, refer to below crash log for details:

[771764773us][cpu=2][vm1:vcpu0][sev=2][seq=15]:
delta = (actual_load_address - CONFIG_HV_RAM_START) = 0x0
L
i[771776360us][cpu=2][vm1:vcpu0][sev=2][seq=16]:
Host Stack: CPU_ID = 2
s
t[771784294us][cpu=2][vm1:vcpu0][sev=2][seq=17]:addr(0x9acf08) 0x00000000009b41b8 0x0000000000000000 0x00000000009ab000 0x00000000009b41b8
e
n[771798943us][cpu=2][vm1:vcpu0][sev=2][seq=18]:addr(0x9acf28) 0x0000000000000000 0x00000000009acf80 0x0000000000426dcf 0x00000000009acf80
i
n[771813597us][cpu=2][vm1:vcpu0][sev=2][seq=19]:addr(0x9acf48) 0xacf473dc477e35cb 0x00000000009acfb0 0x000000000045b300 0x00000000009ab000
g
[771828260us][cpu=2][vm1:vcpu0][sev=2][seq=20]:addr(0x9acf68) 0x000000000000001e 0x00000000009b4228 0x0000000000447fbb 0x00000000009acfb0
0
.[771842912us][cpu=2][vm1:vcpu0][sev=2][seq=21]:addr(0x9acf88) 0x00000000004218a1 0x00000000009b4018 0x00000000009ab000 0x00000000009b4018
.
.[771857573us][cpu=2][vm1:vcpu0][sev=2][seq=22]:addr(0x9acfa8) 0x0000000000447f98 0x00000000009acff0 0x000000000041fa73 0x0000000000000000

[771872242us][cpu=2][vm1:vcpu0][sev=2][seq=23]:addr(0x9acfc8) 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000
V
M[771887005us][cpu=2][vm1:vcpu0][sev=2][seq=24]:addr(0x9acfe8) 0x0000000000000000 0x0000000000000000 0x00000000696e746c 0x0000000000000000

a[771901660us][cpu=2][vm1:vcpu0][sev=2][seq=25]:addr(0x9ad008) 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000
u
t[771916318us][cpu=2][vm1:vcpu0][sev=2][seq=26]:addr(0x9ad028) 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000
o
-[771930975us][cpu=2][vm1:vcpu0][sev=2][seq=27]:addr(0x9ad048) 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000
s
t[771945628us][cpu=2][vm1:vcpu0][sev=2][seq=28]:addr(0x9ad068) 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000
a
r[771960282us][cpu=2][vm1:vcpu0][sev=2][seq=29]:addr(0x9ad088) 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000
t
[771974943us][cpu=2][vm1:vcpu0][sev=2][seq=30]:addr(0x9ad0a8) 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000
i
n[771989601us][cpu=2][vm1:vcpu0][sev=2][seq=31]:addr(0x9ad0c8) 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000

0[772004262us][cpu=2][vm1:vcpu0][sev=2][seq=32]:addr(0x9ad0e8) 0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000
s
.[772018921us][cpu=2][vm1:vcpu0][sev=2][seq=33]:

"[772024364us][cpu=2][vm1:vcpu0][sev=2][seq=34]:Host Call Trace:
s
y[772031396us][cpu=2][vm1:vcpu0][sev=2][seq=35]:----> 0x0000000000426dcf
s
t[772039218us][cpu=2][vm1:vcpu0][sev=2][seq=36]:----> 0x00000000004218a1
e
m[772047038us][cpu=2][vm1:vcpu0][sev=2][seq=37]:----> 0x000000000041fa73
c
t[772054860us][cpu=2][vm1:vcpu0][sev=2][seq=38]:
l
[772060316us][cpu=2][vm1:vcpu0][sev=2][seq=39]:

================================================s
t[772070616us][cpu=2][vm1:vcpu0][sev=2][seq=40]:================================
@yonghuah yonghuah added the status: new The issue status: new for creation label Apr 15, 2024
@yonghuah
Copy link
Contributor Author

[External_System_ID] ACRN-10309

yonghuah added a commit to yonghuah/acrn-hypervisor that referenced this issue Apr 15, 2024
@yonghuah
hv: restore stack protector canary if it was configured
d5a0636 
 Restores canary values of stack protector on all APs
 if it was configured, instead of generating a new canary
 value.

Tracked-On: projectacrn#8577
Signed-off-by: Yonghua Huang <yonghua.huang@intel.com>
Reviewed-by: Junjie Mao <junjie.mao@intel.com>
Reviewed-by: Fei Li <fei1.li@intel.com>
@yonghuah yonghuah mentioned this issue Apr 15, 2024
Merged
yonghuah added a commit to yonghuah/acrn-hypervisor that referenced this issue Apr 16, 2024
@yonghuah
hv: restore stack protector canary if it was configured
1d03547 
 Restores canary value of stack protector on pCPU
 if it was configured, instead of generating a new one.

Tracked-On: projectacrn#8577
Signed-off-by: Yonghua Huang <yonghua.huang@intel.com>
Reviewed-by: Junjie Mao <junjie.mao@intel.com>
Reviewed-by: Fei Li <fei1.li@intel.com>
yonghuah added a commit to yonghuah/acrn-hypervisor that referenced this issue Apr 23, 2024
@yonghuah
hv: refine set_fs_base() function
e6b4804 
 Leave canary of stack protector untouched on pCPU
 if it has been initialized, instead of generating a new one.

Tracked-On: projectacrn#8577
Signed-off-by: Yonghua Huang <yonghua.huang@intel.com>
Reviewed-by: Junjie Mao <junjie.mao@intel.com>
Reviewed-by: Fei Li <fei1.li@intel.com>
yonghuah added a commit to yonghuah/acrn-hypervisor that referenced this issue Apr 23, 2024
@yonghuah
hv: refine set_fs_base() function
3de6bf1 
 Leave canary of stack protector untouched on pCPU
 if it has been initialized, instead of generating a new one.

Tracked-On: projectacrn#8577
Signed-off-by: Yonghua Huang <yonghua.huang@intel.com>
Reviewed-by: Junjie Mao <junjie.mao@intel.com>
Reviewed-by: Fei Li <fei1.li@intel.com>
acrnsi-robot pushed a commit that referenced this issue Apr 23, 2024
@yonghuah @acrnsi-robot
hv: refine set_fs_base() function
7bcd9d7 
 Leave canary of stack protector untouched on pCPU
 if it has been initialized, instead of generating a new one.

Tracked-On: #8577
Signed-off-by: Yonghua Huang <yonghua.huang@intel.com>
Reviewed-by: Junjie Mao <junjie.mao@intel.com>
Reviewed-by: Fei Li <fei1.li@intel.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status: new The issue status: new for creation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@yonghuah