This service will be undergoing maintenance at 00:00 UTC, 2016-08-01. It is expected to last about 1 hours

Bug 237453

Summary: Xenstored slowing system down even with paused domains
Product: [Fedora] Fedora Reporter: Adam Huffman <bloch>
Component: xenAssignee: Daniel Berrange <berrange>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6CC: bstein, katzj, xen-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-26 19:06:16 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:

Description Adam Huffman 2007-04-23 06:28:39 EDT
Description of problem:

This morning I have found my machine to be very slow and it seems xenstored is
the culprit.  I have two active domUs so I paused them via virt-manager to see
if that would alleviate the problem but it doesn't seem to have made much
difference.  System load is currently 4 and all disk I/O operations are very slow.

Version-Release number of selected component (if applicable):
xen-3.0.3-8.fc6.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

The Linux domU is using LVM partitions, the other one is using file-backed
storage in /var/lib/xen/images
Comment 1 Daniel Berrange 2007-04-23 08:03:09 EDT
Known problem reported upstream:

http://lists.xensource.com/archives/html/xen-devel/2006-10/msg00487.html

Not aware of any current work to re-writing XenStored to not suck yet :-(
Comment 2 Daniel Berrange 2007-04-25 15:44:45 EDT
The performance problems are even worse  in Xen 3.0.5   

http://lists.xensource.com/archives/html/xen-devel/2007-04/msg00663.html 

I am experimenting with ways to address it....
Comment 3 Chris Lalancette 2008-02-26 19:06:16 EST
This report targets FC6, which is now end-of-life.

Please re-test against Fedora 7 or later, and if the issue persists, open a new bug.

Thanks