Bug 968944 - libvirt on windows will increase the number of handle limitless
libvirt on windows will increase the number of handle limitless
Status: CLOSED DEFERRED
Product: Virtualization Tools
Classification: Community
Component: libvirt (Show other bugs)
unspecified
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Libvirt Maintainers
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-05-30 06:29 EDT by changyoushi
Modified: 2016-04-09 19:30 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-04-09 19:30:50 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description changyoushi 2013-05-30 06:29:59 EDT
Description of problem:

    when i using the libvirt client on windows7 to connect libvirtd on rhev5.5
   of course , i do some call to get vm information and data, but i found number of handle my the simple test is increase limitless .
      
     i using the virsh tool in windows, when i execute a command , the number of handle increase limitless also 


Version-Release number of selected component (if applicable):
  client libvirt 0.8.4
the version of libvirt using by   libvirtd on rhev5.5 is  0.9.0

How reproducible:


Steps to Reproduce:
1.intall  libvirt client in win7
2. run my simple test
3. the number of handle create by my text.exe increase limitless
4. i watch the number of handle using windows task manager tool
5. the number of handle large than 1m

Actual results:


Expected results:


Additional info:
Comment 1 Cole Robinson 2016-04-09 19:30:50 EDT
Sorry this never received a response. I don't have a windows setup to test so I can't confirm if this is fixed or not. Given the age of the bug, closing as DEFERRED, but if anyone can still reproduce with latest libvirt, please file a new bug and we can triage from there

Note You need to log in before you can comment on or make changes to this bug.