Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Version-Release number of selected component (if applicable):
virtio-win-prewhql-145
3.10.0-855.el7.x86_64
qemu-kvm-rhev-2.10.0-21.el7.x86_64&qemu-kvm-1.5.3-156.el7.x86_64
How reproducible:
1/20
Steps to Reproduce:
1.boot win10-64 guest with 8G mem:
/usr/libexec/qemu-kvm \
-name 'avocado-vt-vm1' \
-sandbox off \
-machine pc \
-nodefaults \
-vga std \
-device nec-usb-xhci,id=usb1,bus=pci.0,addr=0x3 \
-drive id=drive_image1,if=none,snapshot=off,aio=threads,cache=none,format=qcow2,file=/home/kvm_autotest_root/images/win10-64-virtio.qcow2 \
-device virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,bus=pci.0,addr=0x4 \
-m 8192 \
-smp 16,maxcpus=16,cores=8,threads=1,sockets=2 \
-cpu 'Broadwell',+kvm_pv_unhalt,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time \
-drive id=drive_cd1,if=none,snapshot=off,aio=threads,cache=none,media=cdrom,file=/home/kvm_autotest_root/iso/windows/winutils.iso \
-device ide-cd,id=cd1,drive=drive_cd1,bootindex=1,bus=ide.0,unit=0 \
-device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \
-vnc :0 \
-rtc base=localtime,clock=host,driftfix=slew \
-boot menu=off,strict=off,order=cdn,once=c \
-enable-kvm \
-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 \
-monitor stdio
2.balloon memory to 2048
(qemu) balloon 2048
3.balloon memory to 7990
(qemu) balloon 7990
4.reboot guest in guest
5.check balloon value after guest reboot
(qemu) info balloon
6.balloon memory to 4096
(qemu) balloon 4096
Actual results:
After step5 and step6, balloon value keep still at 8190:
(qemu) info balloon
balloon: actual=8190
Expected results:
balloon value should be 7990 after reboot and can be change to 4096 after step6
Additional info:
1.After another reboot, balloon works normally.
2.Did not hit this issue on linux guest for now(try 30 times)
Recently we run test for virtio-win-1.9.12-2.el7.iso(balloon driver version: 177)
Hit this issue again in win8-32/64,win8.1-32/64,win2012-64/r2 again.
Almost 1/10 hit this issue.
host version:
qemu-kvm-rhev-2.12.0-48.el7.x86_64
kernel-3.10.0-1154.el7.x86_64
So I will reopen this bug to track this issue.
Hi developer,
Do we want to fix this in RHEL8.2.1, but as RHEL8.2.1 is released on the 13th of July
,I propose to defer to the later version, what do you think?
Thanks,
xiagao
Hit this issue again recently:
161-Host_RHEL.m7.u9.qcow2.virtio_blk.up.virtio_net.Guest.Win8.x86_64.io-github-autotest-qemu.balloon_check.balloon_evict.balloon-reboot/
158-Host_RHEL.m7.u9.qcow2.virtio_scsi.up.virtio_net.Guest.Win8.x86_64.1.io-github-autotest-qemu.balloon_check.balloon_evict.balloon-reboot/
210-Host_RHEL.m7.u9.qcow2.virtio_blk.up.virtio_net.Guest.Win10.x86_64.io-github-autotest-qemu.balloon_check.balloon_enlarge.balloon-reboot/
pkg version:
virtio-win-1.9.14-1.el7.iso
kernel-3.10.0-1160.6.1.el7.x86_64
qemu-kvm-rhev-2.12.0-48.el7_9.1.x86_64
seabios-bin-1.11.0-2.el7.noarch
Comment 55RHEL Program Management
2021-01-08 07:27:56 UTC
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.
Comment 56Yvugenfi@redhat.com
2021-01-12 09:46:54 UTC
Tried 50 times with the latest pre-whql driver virtio-win-prewhql-0.1-193 but didn't hit this issue so far, But still need to continue to reproduce it, more times and compare the old version. keep reproducing.
Continue to reproduce 300 times on win2012/win8.1-64 with virtio-win-1.9.12-2.el7.iso and win10-64 with the latest virtio-win-prewhql-193.iso ,still couldn't reproduce this bz.
Description of problem: Version-Release number of selected component (if applicable): virtio-win-prewhql-145 3.10.0-855.el7.x86_64 qemu-kvm-rhev-2.10.0-21.el7.x86_64&qemu-kvm-1.5.3-156.el7.x86_64 How reproducible: 1/20 Steps to Reproduce: 1.boot win10-64 guest with 8G mem: /usr/libexec/qemu-kvm \ -name 'avocado-vt-vm1' \ -sandbox off \ -machine pc \ -nodefaults \ -vga std \ -device nec-usb-xhci,id=usb1,bus=pci.0,addr=0x3 \ -drive id=drive_image1,if=none,snapshot=off,aio=threads,cache=none,format=qcow2,file=/home/kvm_autotest_root/images/win10-64-virtio.qcow2 \ -device virtio-blk-pci,id=image1,drive=drive_image1,bootindex=0,bus=pci.0,addr=0x4 \ -m 8192 \ -smp 16,maxcpus=16,cores=8,threads=1,sockets=2 \ -cpu 'Broadwell',+kvm_pv_unhalt,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time \ -drive id=drive_cd1,if=none,snapshot=off,aio=threads,cache=none,media=cdrom,file=/home/kvm_autotest_root/iso/windows/winutils.iso \ -device ide-cd,id=cd1,drive=drive_cd1,bootindex=1,bus=ide.0,unit=0 \ -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \ -vnc :0 \ -rtc base=localtime,clock=host,driftfix=slew \ -boot menu=off,strict=off,order=cdn,once=c \ -enable-kvm \ -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 \ -monitor stdio 2.balloon memory to 2048 (qemu) balloon 2048 3.balloon memory to 7990 (qemu) balloon 7990 4.reboot guest in guest 5.check balloon value after guest reboot (qemu) info balloon 6.balloon memory to 4096 (qemu) balloon 4096 Actual results: After step5 and step6, balloon value keep still at 8190: (qemu) info balloon balloon: actual=8190 Expected results: balloon value should be 7990 after reboot and can be change to 4096 after step6 Additional info: 1.After another reboot, balloon works normally. 2.Did not hit this issue on linux guest for now(try 30 times)