Bug 2108531
Summary: | Windows guest reboot after migration with wsl2 installed inside | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Li Xiaohui <xiaohli> | |
Component: | qemu-kvm | Assignee: | Vitaly Kuznetsov <vkuznets> | |
qemu-kvm sub component: | Live Migration | QA Contact: | Li Xiaohui <xiaohli> | |
Status: | CLOSED ERRATA | Docs Contact: | ||
Severity: | high | |||
Priority: | high | CC: | chayang, coli, jinzhao, juzhang, leobras, mdean, mrezanin, peterx, quintela, virt-maint, vkuznets, ymankad | |
Version: | 9.1 | Keywords: | Regression, Triaged, ZStream | |
Target Milestone: | rc | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | qemu-kvm-7.1.0-3.el9 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 2134896 (view as bug list) | Environment: | ||
Last Closed: | 2023-05-09 07:19:33 UTC | Type: | --- | |
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: | 2134896 |
Description
Li Xiaohui
2022-07-19 08:40:40 UTC
Note, 'hv_reenlightenment' feature *requires* 'tsc-frequency=' setting to make migration work. I don't see it on the QEMU command line above. Sadly, there was a bug discovered recently, see commit 99482726452bdf8be9325199022b17fa6d7d58fe Author: Vitaly Kuznetsov <vkuznets> Date: Tue Jul 12 15:50:09 2022 +0200 KVM: nVMX: Always enable TSC scaling for L2 when it was enabled for L1 I'm not exactly sure this fix is a must here (I've discovered the issue with Win11, not Win2022) but it might be. Hi Vitaly, I have tried on two different hosts to do postcopy migration with wsl2 installed according to your Comment 1, but win2022 guest still reboot after migration. src host: Intel(R) Xeon(R) Silver 4210 CPU @ 2.20GHz # virsh capabilities |grep counter <counter name='tsc' frequency='2194843000' scaling='yes'/> dst host: Intel(R) Xeon(R) CPU E5-2609 v3 @ 1.90GHz # virsh capabilities |grep counter <counter name='tsc' frequency='1899997000' scaling='no'/> Qemu command same as Description except cpu command: -cpu Haswell-noTSX-IBRS,vme=on,ss=on,vmx=on,pdcm=on,f16c=on,rdrand=on,hypervisor=on,arat=on,tsc-adjust=on,umip=on,md-clear=on,stibp=on,arch-capabilities=on,ssbd=on,xsaveopt=on,pdpe1gb=on,abm=on,ibpb=on,ibrs=on,amd-stibp=on,amd-ssbd=on,skip-l1dfl-vmentry=on,pschange-mc-no=on,hv_stimer,hv_synic,hv_vpindex,hv_relaxed,hv_spinlocks=0xfff,hv_crash,hv_vapic,hv_time,hv_frequencies,hv_runtime,hv_tlbflush,hv_reenlightenment,hv_stimer_direct,hv_ipi,hv_evmcs,tsc-frequency=1899997000 \ The fix I've mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=2108531#c1 was backported in kernel-5.14.0-145.el9 -- did you try this or a later version? I'm taking this BZ to my stash to look at. (In reply to Vitaly Kuznetsov from comment #3) > The fix I've mentioned in > https://bugzilla.redhat.com/show_bug.cgi?id=2108531#c1 > was backported in kernel-5.14.0-145.el9 -- did you try this or a later > version? Yes, the kernel version is 5.14.0-145.el9.x86_64 > > I'm taking this BZ to my stash to look at. I could reproduce this bug on qemu-kvm-7.1.0-1.el9, and retest on qemu-kvm-7.1.0-1.el9.vitty202209201648, the bug disappear. So the scratch build fixes this bug: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=47844255 (In reply to Li Xiaohui from comment #8) > I could reproduce this bug on qemu-kvm-7.1.0-1.el9, and retest on > qemu-kvm-7.1.0-1.el9.vitty202209201648, the bug disappear. > > So the scratch build fixes this bug: > https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=47844255 Thank you, now we're sure it's the same bug. QE bot(pre verify): Set 'Verified:Tested,SanityOnly' as gating/tier1 test pass. Verified this bug according to Description, and it passed. So mark this bug as verified 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 (Moderate: qemu-kvm 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:2162 |