Bug 1879163
Summary: | [virtio-win][balloon]balloon value change is very slow inside win2016-64 guest | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | FuXiangChun <xfu> |
Component: | qemu-kvm-rhev | Assignee: | Yvugenfi <yvugenfi> |
Status: | CLOSED WONTFIX | QA Contact: | xiagao |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.5 | CC: | ailan, chayang, jinzhao, juzhang, lijin, qzhang, virt-maint, xiagao, yfu, yuhuang, yvugenfi |
Target Milestone: | rc | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Windows | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-06-08 07:31:04 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
FuXiangChun
2020-09-15 14:57:04 UTC
Didn't hit this issue on RHEL8.3.0 with the same virtio-win driver, so it seems not the balloon driver's issue. pkgs: qemu-kvm-5.1.0-2.module+el8.3.0+7652+b30e6901.x86_64 seabios-1.14.0-1.module+el8.3.0+7638+07cf13d2.x86_64 kernel-4.18.0-229.el8.x86_64 virtio-win-1.9.12-4.el7.iso/virtio-win-1.9.12-2.el8.iso(balloon driver version: 177) But it can be reproduced on the qemu of comment0. @yuhuang could you have a check if it's qemu's bug? Hi Xiaoling, I tried win2012 guest with the same packages in comment 0, and it works well. I guess it's win2016 OS or driver problem. Is this even a valid scenrario? VM was given 30720MB of memory and we are trying to inflate Balloon to 32G. At somepoint, all OS free memory will be consumed and it will be heavily using swap (thus the slowness). (In reply to Yan Vugenfirer from comment #4) > Is this even a valid scenrario? > > VM was given 30720MB of memory and we are trying to inflate Balloon to 32G. > At somepoint, all OS free memory will be consumed and it will be heavily > using swap (thus the slowness). Hi Yan, Balloon memory to 30720MB, still has this issue. Thanks, Xiaoling Win2019,win2016 and win10-64 hit this issue, it needs about 20 mins to balloon memory from 2G to 30G. Test win2016 with libvirt, it needs about 13 mins. test pkgs: qemu-kvm-rhev-2.10.0-21.el7_5.10.x86_64 kernel-3.10.0-862.14.4.el7.x86_64 virtio-win-1.9.12-4.el7.iso/virtio-win-prewhql-189 (In reply to xiagao from comment #5) > (In reply to Yan Vugenfirer from comment #4) > > Is this even a valid scenrario? > > > > VM was given 30720MB of memory and we are trying to inflate Balloon to 32G. > > At somepoint, all OS free memory will be consumed and it will be heavily > > using swap (thus the slowness). > > Hi Yan, > Balloon memory to 30720MB, still has this issue. > > Thanks, > Xiaoling That's the problem. We cannot take all the memory from the guest. At some point, the guest will become very slow due to swapping. At least 0.5-1G should be left for the OS to function. So if you use -m 32G, then inflate ballon only up to 31G (In reply to Yan Vugenfirer from comment #7) > (In reply to xiagao from comment #5) > > (In reply to Yan Vugenfirer from comment #4) > > > Is this even a valid scenrario? > > > > > > VM was given 30720MB of memory and we are trying to inflate Balloon to 32G. > > > At somepoint, all OS free memory will be consumed and it will be heavily > > > using swap (thus the slowness). > > > > Hi Yan, > > Balloon memory to 30720MB, still has this issue. > > > > Thanks, > > Xiaoling > > That's the problem. We cannot take all the memory from the guest. At some > point, the guest will become very slow due to swapping. > At least 0.5-1G should be left for the OS to function. > So if you use -m 32G, then inflate ballon only up to 31G I don't think so. Chang balloon from 2G to 32G is not "take memory from guest", we actually bring memory to guest. The operation is to change guest memory from 2G to 32G, it is definitely a commnon scenario for balloon. The issue here is that on some qemu versions(rhel7 qemu reproduced while rhel8 qemu not) and on win10+ guests, the process is quite slow. rhel7 qemu issue, windows OS issue or drvier issue? Not reproduce this issue in RHEL7.9.z with latest pkg. pkg: qemu-kvm-rhev.x86_64 10:2.12.0-48.el7_9.3 kernel-3.10.0-1160.29.1.el7.x86_64 virtio-win-prewhql-199 virtio-win-1.9.12-4.el7.iso Win2019 guest It took about 2mins to balloon memory from 2G to 32G which looks good. (In reply to xiagao from comment #12) > Not reproduce this issue in RHEL7.9.z with latest pkg. > > pkg: > qemu-kvm-rhev.x86_64 10:2.12.0-48.el7_9.3 > kernel-3.10.0-1160.29.1.el7.x86_64 > virtio-win-prewhql-199 > virtio-win-1.9.12-4.el7.iso > Win2019 guest > > It took about 2mins to balloon memory from 2G to 32G which looks good. Did you try with Win2016 guest as well (as the original BZ description)? (In reply to Yvugenfi from comment #13) > (In reply to xiagao from comment #12) > > Not reproduce this issue in RHEL7.9.z with latest pkg. > > > > pkg: > > qemu-kvm-rhev.x86_64 10:2.12.0-48.el7_9.3 > > kernel-3.10.0-1160.29.1.el7.x86_64 > > virtio-win-prewhql-199 > > virtio-win-1.9.12-4.el7.iso > > Win2019 guest > > > > It took about 2mins to balloon memory from 2G to 32G which looks good. > > Did you try with Win2016 guest as well (as the original BZ description)? Win10+ hit this issue from comment 6, although, I tried with Win2016 and didn't reproduce with virtio-win-1.9.12-4.el7.iso and virtio-win-prewhql-199. After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. |