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.
(In reply to Gal Hammer from comment #2)
> What are the Windows and blnsvr.exe versions? Thanks.
Windows: win2019
balloon driver and blnsrv.exe:virtio-win-prewhql-162
A patch was posted, waiting to see why the hck-ci fails.
Comment 7Yvugenfi@redhat.com
2018-12-18 09:59:57 UTC
(In reply to Gal Hammer from comment #5)
> A patch was posted, waiting to see why the hck-ci fails.
We had an issue with a test certificate.
The commit is merged with master.
Comment 8Yvugenfi@redhat.com
2018-12-18 10:00:31 UTC
(In reply to Gal Hammer from comment #5)
> A patch was posted, waiting to see why the hck-ci fails.
We had an issue with a test certificate.
The commit is merged with master.
Reproduced this issue with virtio-win-prewhql-162.
Verified this issue with virtio-win-prewhql-168, when balloon service is running, the balloon device can be hot-unplugged successfully.
Steps as comment#0.
Used versions:
kernel-4.18.0-70.el8.x86_64
qemu-kvm-3.1.0-11.module+el8+2747+40c9b77e.x86_64
seabios-bin-1.12.0-1.module+el8+2706+3c6581b6.noarch
Best Regards~
Peixiu
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, 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/RHEA-2019:1997
Description of problem: Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1.boot guest with balloon device: /usr/libexec/qemu-kvm \ -monitor stdio \ -name 'avocado-vt-vm1' \ -sandbox off \ -machine q35 \ -nodefaults \ -device VGA,bus=pcie.0,addr=0x1 \ -device pcie-root-port,id=pcie.0-root-port-5,slot=5,chassis=5,addr=0x5,bus=pcie.0 \ -device qemu-xhci,id=usb1,bus=pcie.0-root-port-5,addr=0x0 \ -device pcie-root-port,id=pcie.0-root-port-6,slot=6,chassis=6,addr=0x6,bus=pcie.0 \ -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pcie.0-root-port-6,addr=0x0 \ -drive id=drive_image1,if=none,snapshot=off,aio=threads,cache=none,format=qcow2,file=/home/kvm_autotest_root/images/win2019-64-virtio-scsi.qcow2 \ -device scsi-hd,id=image1,drive=drive_image1 \ -device pcie-root-port,id=pcie.0-root-port-7,slot=7,chassis=7,addr=0x7,bus=pcie.0 \ -device virtio-net-pci,mac=9a:ac:ad:ae:af:b0,id=id3MOJiK,vectors=4,netdev=idAOrAbG,bus=pcie.0-root-port-7,addr=0x0 \ -netdev tap,id=idAOrAbG,vhost=on,script=/etc/qemu-ifup \ -m 14336 \ -smp 24,maxcpus=24,cores=12,threads=1,sockets=2 \ -cpu 'Skylake-Server',+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 scsi-cd,id=cd1,drive=drive_cd1 \ -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1 \ -vnc :1 \ -rtc base=localtime,clock=host,driftfix=slew \ -boot order=cdn,once=c,menu=off,strict=off \ -enable-kvm \ -qmp tcp:0:4444,server,nowait \ -device pcie-root-port,id=pcie.0-root-port-8,slot=8,chassis=8,addr=0x8,bus=pcie.0 \ -device virtio-balloon-pci,id=balloon0,bus=pcie.0-root-port-8,addr=0x0 2.install balloon service in guest: # blnsrv.exe -i 3.hot-unplug balloon device: (qemu) device_del balloon0 Actual results: balloon device still in guests Expected results: balloon device can be unplug correctly. Additional info: 1. Downgrade driver to build 154, unplug can be finished without any error, so it's a regression bug