Bug 2174605
| Summary: | [EDK2] disable dynamic mmio window | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Nitesh Narayan Lal <nilal> | |
| Component: | edk2 | Assignee: | Gerd Hoffmann <kraxel> | |
| Status: | CLOSED ERRATA | QA Contact: | Xueqiang Wei <xuwei> | |
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 9.2 | CC: | berrange, coli, germano, jinzhao, juzhang, kraxel, mrezanin, pbonzini, pvlasin, vgoyal, virt-maint, xiaohli, xuwei, yalzhang, ymankad, zhguo | |
| Target Milestone: | rc | Keywords: | Triaged | |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
|
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | edk2-20221207gitfff6d81270b5-8.el9_2 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 2174749 2176920 (view as bug list) | Environment: | ||
| Last Closed: | 2023-05-09 07:25:12 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 2176920 | |||
|
Description
Nitesh Narayan Lal
2023-03-02 00:03:55 UTC
Problem: recent OVMF start using the full physical address space which is available. See https://bugzilla.redhat.com//show_bug.cgi?id=2084533 and https://issues.redhat.com/browse/RHEL-60 libvirt host capabilities (for live migration compatibility) do not include the physical address space size though, so this causes problems in heterogeneous clusters. PLAN: disable for 9.2, enable again for 9.3 (and eventually 9.2.z), after libvirt has been fixed. Hi Yalan, can you help try again with the scratch build in Comment 5? Hi Xueqiang, Reproduce below bug on qemu-kvm-7.2.0-10.el9.x86_64 and edk2-ovmf-20221207gitfff6d81270b5-7.el9.noarch when migrate VM from Xeon(R) Silver 4110 to Xeon(R) CPU E3-1240 v5, dst qemu core dump when migration finishes: (qemu) 2023-03-06T03:21:58.968405Z qemu-kvm: warning: TSC frequency mismatch between VM (2095072 kHz) and host (3503988 kHz), and TSC scaling unavailable 2023-03-06T03:21:58.968512Z qemu-kvm: error: failed to set MSR 0x202 to 0xe000000000 qemu-kvm: ../target/i386/kvm/kvm.c:3177: int kvm_buf_set_msrs(X86CPU *): Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed. Bug 2171860 - migration: larger->E3: vm failed with "failed to set MSR 0x202 to 0x380000000000" Only upgrade edk2 to edk2-ovmf-20221207gitfff6d81270b5-7.el9.bz2174605.20230302.1201.noarch, other environment and qemu cmds keep the same with above, then migration succeeds Notes: CPU commands -> -cpu Skylake-Client-v4 So the scratch build should fix Bug 2171860 (In reply to Li Xiaohui from comment #7) > Hi Xueqiang, > > Reproduce below bug on qemu-kvm-7.2.0-10.el9.x86_64 and > edk2-ovmf-20221207gitfff6d81270b5-7.el9.noarch when migrate VM from Xeon(R) > Silver 4110 to Xeon(R) CPU E3-1240 v5, dst qemu core dump when migration > finishes: > (qemu) 2023-03-06T03:21:58.968405Z qemu-kvm: warning: TSC frequency mismatch > between VM (2095072 kHz) and host (3503988 kHz), and TSC scaling unavailable > 2023-03-06T03:21:58.968512Z qemu-kvm: error: failed to set MSR 0x202 to > 0xe000000000 > qemu-kvm: ../target/i386/kvm/kvm.c:3177: int kvm_buf_set_msrs(X86CPU *): > Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed. > > Bug 2171860 - migration: larger->E3: vm failed with "failed to set MSR 0x202 > to 0x380000000000" > > > Only upgrade edk2 to > edk2-ovmf-20221207gitfff6d81270b5-7.el9.bz2174605.20230302.1201.noarch, > other environment and qemu cmds keep the same with above, then migration > succeeds > > Notes: CPU commands -> -cpu Skylake-Client-v4 > > > > So the scratch build should fix Bug 2171860 Thank you Xiaohui. Could you please double check with the final build edk2-20221207gitfff6d81270b5-8.el9_2? I will do the regression test. Many thanks. Retest this bug according to Comment 7 on edk2-20221207gitfff6d81270b5-8.el9_2, it has the fix: migration succeeds, qemu on the src and dst host work well. Only get some tsc unstable dmesg info in guest after migration: [ 75.412616] clocksource: timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the skew is too large: [ 75.413853] clocksource: 'kvm-clock' wd_nsec: 504016065 wd_now: 15f0d2b67c wd_last: 15d2c809bb mask: ffffffffffffffff [ 75.415213] clocksource: 'tsc' cs_nsec: 842961982 cs_now: 2e8f76fb7e cs_last: 2e2632f39c mask: ffffffffffffffff [ 75.416490] clocksource: 'kvm-clock' (not 'tsc') is current clocksource. [ 75.417405] tsc: Marking TSC unstable due to clocksource watchdog QE bot(pre verify): Set 'Verified:Tested,SanityOnly' as gating/tier1 test pass. The migration succeed with edk2-ovmf-20221207gitfff6d81270b5-8.el9_2.noarch. The issue is fixed. Did regression test, no new bug was found. Versions: kernel-5.14.0-284.el9.x86_64 qemu-kvm-7.2.0-11.el9_2 edk2-ovmf-20221207gitfff6d81270b5-8.el9_2.noarch 1. Tested qemu gating test, the results were passed. Job link: http://virtqetools.lab.eng.pek2.redhat.com/kvm_autotest_job_log/?jobid=7613910 2. Tested edk2 test loop, the results were passed. Job link: http://virtqetools.lab.eng.pek2.redhat.com/kvm_autotest_job_log/?jobid=7615585 Thank you Xiaohui and Yalan, many thanks. According to Comment 13, Comment 17 and Comment 18, set status to VERIFIED. Thanks all. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: edk2 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2023:2165 |