Bug 1745449 - L2 guest hit kernel panic when do L1->L1 live migration on intel host
Summary: L2 guest hit kernel panic when do L1->L1 live migration on intel host
Keywords:
Status: CLOSED DUPLICATE of bug 1738741
Alias: None
Product: Red Hat Enterprise Linux Advanced Virtualization
Classification: Red Hat
Component: qemu-kvm
Version: 8.1
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: 8.0
Assignee: Paolo Bonzini
QA Contact: Li Xiaohui
URL:
Whiteboard:
Depends On: 1738741 1749495
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-26 07:29 UTC by Li Xiaohui
Modified: 2019-10-16 14:20 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1738741
Environment:
Last Closed: 2019-09-27 12:46:12 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
vmcore-dmesg.txt (51.77 KB, text/plain)
2019-08-26 07:33 UTC, Li Xiaohui 		no flags Details
View All

Comment 1 Li Xiaohui 2019-08-26 07:33:54 UTC 
Created attachment 1608019 [details]
vmcore-dmesg.txt
Comment 2 Li Xiaohui 2019-08-26 08:23:02 UTC 
Test on host(kernel-4.18.0-137.el8.x86_64&qemu-img-4.1.0-4.module+el8.1.0+4020+16089f93.x86_64), reproduce this issue.

vmcore log is some different from slow train bz : Bug 1738741, so attach vmcore again, please see link:
http://fileshare.englab.nay.redhat.com/pub/section2/images_backup/bz1745449/
Comment 5 Li Xiaohui 2019-08-27 05:03:49 UTC 
I test on two amd hosts(both are AMD EPYC 7251 8-Core Processor), migrate L1->L1 from src to dst host, migration finish successfully, L2&L1 all work well. So seems this bz didn't reproduce on two hosts

now have no twin intel hosts for test, will try it after hosts are available.
Comment 6 Li Xiaohui 2019-09-03 12:15:36 UTC 
Hi Karen, Paolo,
Update Comment5:
1.On amd host, do local migration or live migration(both are AMD EPYC 7251 8-Core Processor), migration finished successfully, and L1&L2 work well, too. 
2.On intel twins host, do live migration(both are Intel(R) Xeon(R) CPU E3-1225 v5), migration finished succuessfully, but L2 guest hit kernel panic and produce vmcore file

So seems get conclusion:
On amd host, won't hit this issue, but on intel host, whether local migration or live migration, all L2 guest will hit kernel panic.
Comment 7 Paolo Bonzini 2019-09-27 12:46:12 UTC 

*** This bug has been marked as a duplicate of bug 1738741 ***
Note You need to log in before you can comment on or make changes to this bug.