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:
In some windows 7 and XP guests, blnsrv.exe is pegged at 100% cpu usage. Killing this process in the task manager gets the VM to normal.
There are no errors reported in the logs.
Have asked Customer to disable this service altogether.
Why is this process using 100% cpu? What information can we get to find out the reason?
How do we proceed?
Version-Release number of selected component (if applicable):
RHEV 3.1
Vadim,
I am attaching the qemu VM logs for the VMs in question for information on qemu command line.
We have requested the Customer for the output of the remaining commands.
Will upload it as soon as we get them.
blnsrv.exe which is used for memory statistis is *not* officially supported in RHEL6 according to https://bugzilla.redhat.com/show_bug.cgi?id=798139 .And Virt-QE do not testing the driver/app we do not support
So we should remove it from rhev-guest-tools-iso .
Mike
I can not reproduce this issue on virtio-win-prewhql-65
Steps:
1.Start VM on RHEVM3.2
2.blnsrv -i
Actual Results:
Guest works fine
Vadim ,Could you view my steps above ? Any idea how can I reproduce this bug ?
Thanks,
Mike
(In reply to Mike Cao from comment #8)
> I can not reproduce this issue on virtio-win-prewhql-65
>
> Steps:
> 1.Start VM on RHEVM3.2
> 2.blnsrv -i
>
> Actual Results:
> Guest works fine
>
>
> Vadim ,Could you view my steps above ? Any idea how can I reproduce this bug
> ?
>
Hi Mike,
I have no idea, which additional steps should be taken in order to see
this bug. (I personally have never seen it on any of my systems
In my understanding there was only one reason why we could get 100%
CPU consumption when we fail to get memory statistics and run into
busy loop. I have fixed this problem falling into sleep even in
WMI query has failed. I was thinking that maybe if QE can reproduce
this problem we will be able to perform some sort of live debugging
exercises on this problem.
Thaks,
Vadim.
> Thanks,
> Mike
(In reply to Mike Cao from comment #11)
> Hi,Anitha Udgiri
>
> Since QE can not reproduce this isuse .Could you ask customer try to fixed
> version blnsrv in the bug attachment ?
>
> Thanks a lot,
> Mike
Mike,
We have asked the Customer if they are willing to try it in their environment and will provide this version upon their positive response.
~Anitha
(In reply to Miya Chen from comment #13)
> Hi Anitha, is there any news from customer? Thanks.
Hello,
Unfortunately, the Customer has not responded back on our request and the case appears "closed" on account of inactivity for a long period.
I will ask the case owner to reach out the Customer again and check their feedback/response.