Bug 730493 - virt-manager renders xen domUs unusable on usage, slow in general
Summary: virt-manager renders xen domUs unusable on usage, slow in general
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Virtualization Tools
Classification: Community
Component: virt-manager
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Cole Robinson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-13 17:14 UTC by Alexander Bienzeisler
Modified: 2011-08-23 19:51 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-23 19:51:02 UTC


Attachments (Terms of Use)
live situation screenshot (411.22 KB, image/png)
2011-08-13 17:15 UTC, Alexander Bienzeisler
no flags Details

Description Alexander Bienzeisler 2011-08-13 17:14:30 UTC
Description of problem:

when virt-manager is running, xenstored is taking a lot of cpu (which it shouldn't), guest systems are very slow, general usage of virt-manager feels very slow compared to earlier versions

Version-Release number of selected component (if applicable):

0.9.0

How reproducible:

launch virt-manager with xen 4.1.1

Steps to Reproduce:
1. run virt-manager
2. check top on dom0
3. ???
4. nonprofit
  
Actual results:

slow guests, slow virt-manager, xenstored cpu usage ~50% (way above expected)

Expected results:

none of the above

Additional info:

Comment 1 Alexander Bienzeisler 2011-08-13 17:15:33 UTC
Created attachment 518156 [details]
live situation screenshot

Comment 2 Cole Robinson 2011-08-23 18:33:58 UTC
Is this a regression compared to a previous virt-manager version, or is this your first time trying virt-manager?

Comment 3 Cole Robinson 2011-08-23 19:51:02 UTC
We talked on IRC, Alexander ran a bisect and narrowed down the issue, and I pushed a fix!

http://git.fedorahosted.org/git?p=virt-manager.git;a=commit;h=9dc799af9c3d4fab926ee41685d68642c95593fe

Thanks for the help!


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