Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 237453 - Xenstored slowing system down even with paused domains
Xenstored slowing system down even with paused domains
Product: Fedora
Classification: Fedora
Component: xen (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Berrange
Depends On:
  Show dependency treegraph
Reported: 2007-04-23 06:28 EDT by Adam Huffman
Modified: 2008-02-26 19:06 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-02-26 19:06:16 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
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):

How reproducible:

Steps to Reproduce:
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:


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   


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.


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