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.
Fang,
it looks almost like a duplicate of BZ#750695, but with a different summary.
Am I missing anything?
Regardless, it will be assigned to RHEL6.3
Thanks.
(In reply to comment #2)
> Fang,
> it looks almost like a duplicate of BZ#750695, but with a different summary.
> Am I missing anything?
> Regardless, it will be assigned to RHEL6.3
> Thanks.
I don't think it is a bug ,at least not a virtio-win bug . Because RHEL guest also hit this ,re-assign to qemu-kvm component and add amit in cc list .
(In reply to comment #3)
> (In reply to comment #2)
> > Fang,
> > it looks almost like a duplicate of BZ#750695, but with a different summary.
> > Am I missing anything?
> > Regardless, it will be assigned to RHEL6.3
> > Thanks.
>
> I don't think it is a bug ,at least not a virtio-win bug . Because RHEL guest
> also hit this ,re-assign to qemu-kvm component and add amit in cc list .
Absolutely right. It's the expected behaviour by design.
Best,
Vadim.
I think this is a bug: management software may not come to know when a balloon value gets applied. I think we should fix this.
The fix for bug 725621 will also fix this issue. So unless there's any objection, I'll do this and mark this bug as a dup of the other one.
> I think this is a bug: management software may not come to know when a balloon
> value gets applied. I think we should fix this
That's not really a bug - it is a feature request.
Setting balloon target has always been disconnected from the actual applied balloon limit, so if you want to know the actual balloon value you have to explicitly query it when you want to know. The guest OS can change its actual balloon limit up or down at will.
It would, however, be useful if QMP has an async event to notify a mgmt application whenever the actual balloon level changes. This would avoid the need for the mgmt app to periodically poll 'query-balloon'.