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.
It's not very clear which case causes this regression.
Can you mention which host causes the problem to reproduce? Or does host system not matter?
Can you mention which guest causes the problem to reproduce? Or does the guest not matter?
A matrix of host and guest OSes and results will make the picture clearer.
Thanks.
(In reply to comment #2)
> It's not very clear which case causes this regression.
>
> Can you mention which host causes the problem to reproduce? Or does host
> system not matter?
>
> Can you mention which guest causes the problem to reproduce? Or does the
> guest not matter?
>
> A matrix of host and guest OSes and results will make the picture clearer.
>
> Thanks.
_____________________________________
|host | guest | results |
|________|__________|________________|
| | win2012 | failed[1] |
|rhel7 |__________|________________|
| | rhel7 | pass[2] |
|________|__________|________________|
| | win2012 | pass[1] |
| |__________|________________|
|rhel6.4 | rhel7 | pass[2] |
|________|__________|________________|
failed[1]:After step2 ,change balloon size from 6114 to 2000,use 80sec.75M/s-->slower
pass[1]:After step2 ,change balloon size from 6114 to 2000,use 45sec.120M/s
pass[2]:Balloon size change very fast
Talk with amit ,closed this bug now ,wait rhel7 virtio-win package come out,test again.If have same problem.then reopen.
thanks
<flang> OK in case something wrong .let me tried test again? if get same results .maybe we can closed this bug first , wait rhel7 virtio-win package come out ,retest again,if have same problem then reopen .
<amit> sure
(In reply to langfang from comment #5)
> Talk with amit ,closed this bug now ,wait rhel7 virtio-win package come
> out,test again.If have same problem.then reopen.
>
> thanks
>
> <flang> OK in case something wrong .let me tried test again? if get same
> results .maybe we can closed this bug first , wait rhel7 virtio-win package
> come out ,retest again,if have same problem then reopen .
> <amit> sure
Hi, Amit and flang
As we have no rhel7 virtio-win package, so let's re-open this bug? Some other guys hit same problem as well. Please correct me if I'm wrong.
Thanks,
Qunfang
Test on latest version:
Host:
# uname -r
3.10.0-64.el7.x86_64
# rpm -q qemu-kvm-rhev
qemu-kvm-rhev-1.5.3-30.el7.x86_64
Results:
Guest:win2012-64/rhel7
______________________________________
|host | guest | results |
|________|__________|________________|
| | win2012 | pass[1] |
|rhel7 |__________|________________|
| | rhel7 | pass[2] |
|________|__________|________________|
pass[1]:Change balloon size from 6114 to 2000,use 29sec. 130M/s
Pass[2]:Balloon size change very fast,need about 2 sec.
According to above test ,seem the results same as on rhel6 test . Please see comment3 test on rhel6.4.
It is not so surprising that RHEL guest balloons faster than a windows guest. Probably Windows accesses and maps more memory, and the ballooning has more work to do. It would be interesting to try to balloon after running something that accesses memory (on the RHEL guest), and then sleeps while the memory is still allocated.