Bug 1843970
Summary: | Crash on GCP nested instance when using qemu-kvm-2.12.0-99.module+el8.2.0+5827+8c39933c.x86_64 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Christophe Fergeau <cfergeau> |
Component: | qemu-kvm | Assignee: | Amnon Ilan <ailan> |
qemu-kvm sub component: | General | QA Contact: | Wei Shi <wshi> |
Status: | CLOSED WONTFIX | Docs Contact: | |
Severity: | unspecified | ||
Priority: | unspecified | CC: | ailan, coli, jinzhao, juzhang, prkumar, virt-maint, vkuznets, wshi, ymao |
Version: | --- | Keywords: | Regression, Reopened |
Target Milestone: | rc | ||
Target Release: | 8.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-12-30 12:38:23 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Christophe Fergeau
2020-06-04 14:09:57 UTC
Hi Christophe, Which kernel version is on your host ? Thanks, Qinghua Cheng It's 4.18.0-193.1.2.el8_2.x86_64 Hi Christophe, This crash happens on a Linux L1 guest or a windows L1 guest ? Thanks, Qinghua Cheng The kernel version I gave is for the L1 guest, so it's linux. L2 guest is also a linux guest running RHCOS. Assigned to Amnon for initial triage per bz process and age of bug created or assigned to virt-maint without triage. Could be miscategorized in General - perhaps more Machine/CPU related or maybe we need a new sub-component. I tried to reproduce this bug on our env: Host: # uname -r 4.18.0-193.el8.x86_64 qemu-kvm build: qemu-kvm-2.12.0-99.module+el8.2.0+5827+8c39933c.x86_64 L1 guest: # uname -r 4.18.0-193.1.2.el8_2.x86_64 qemu-kvm build: qemu-kvm-2.12.0-99.module+el8.2.0+5827+8c39933c.x86_64 I used the xml file in this bug to boot guest mv, both L1 guest vm and L2 guest vm are booted successfully, and work well. This bug is not reproduced in this environment. Vitaly, It seems this is the same bug as we fixed in RHEL-AV (RHBZ#1822682) Can NOT reproduce on qemu-kvm-2.12.0-88.module+el8.1.0+4233+bc44be3f.x86_64 qemu-kvm -cpu host ... Can reproduce on qemu-kvm-2.12.0-99.module+el8.2.0+5827+8c39933c.x86_64 qemu-kvm -cpu host ... (In reply to Wei Shi from comment #7) > Vitaly, > It seems this is the same bug as we fixed in RHEL-AV (RHBZ#1822682) > > Can NOT reproduce on > qemu-kvm-2.12.0-88.module+el8.1.0+4233+bc44be3f.x86_64 > qemu-kvm -cpu host ... > > Can reproduce on > qemu-kvm-2.12.0-99.module+el8.2.0+5827+8c39933c.x86_64 > qemu-kvm -cpu host ... Yes, most likely it's the same bug. You can check that it's not reproducible with qemu-kvm-4.2.0-19.module+el8.2.0+6296+6b821950 Verified nested VM can be launched successfully with qemu-kvm-4.2.0-19.module+el8.2.0+6296+6b821950.x86_64 on GCP *** This bug has been marked as a duplicate of bug 1822682 *** Aren't qemu-kvm-2.12.0-99.module+el8.2.0+5827+8c39933c.x86_64 and qemu-kvm-4.2.0-19.module+el8.2.0+6296+6b821950.x86_64 in different streams? Is there a bug tracking a backport to qemu-kvm-2.12.0 for the fix which was done in qemu-kvm-4.2.0? Reopening this as a 8.2.z backport would be very welcome. This is causing failures in OpenShift CI: - https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/code-ready_snc/204/pull-ci-code-ready-snc-master-e2e-snc/1298158234300846080 - https://storage.googleapis.com/origin-ci-test/pr-logs/pull/code-ready_snc/204/pull-ci-code-ready-snc-master-e2e-snc/1298158234300846080/artifacts/e2e-snc/gather-snc/crc-tmp-install-data/.openshift_install.log (not sure how long these links will persist) The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days |