From: Xen User <xen@theorb.net>
To: xen-devel@lists.sourceforge.net
Subject: extremely slow disk access
Date: Fri, 25 Mar 2005 11:03:42 -0800 [thread overview]
Message-ID: <4244608E.6040301@theorb.net> (raw)
Hi list members,
I have a fresh FC3 with fresh bk clone of xen-2.0.bk. It builds and
installs without complaint.
"/lib/tls" has been moved to "/lib/tls.disabled".
My understanding is that in a stand-alone (no vms running) situation the
performance difference between a standard kernel and a xen enabled
kernel should be roughly the same. Is this correct?
2.6.10-xen0 boots with no errors, but the mouse seems jerky and slow to
respond but is functional.
Networking is up and functional.
The drives are IDE in a raid0 using lvm. The m/b is typical budget x86
with 1GB ram and 1GHz Athlon. It has been in various uses without
failure for a couple years.
As a test I created a logical volume "Main/test" of 1G rw and formatted
it with ext3. The inode creation part took perhaps 1 second but the
journal creation took over 1 minute. I was able to have lunch (and do
the dishes) in the time it took to format 18G.
Reboot into 2.6.9 non-xen and try the same experiment and the entire
process takes less than 2 seconds.
I looked in /proc/interrupts but nothing there seems awry, i.e. no
runaway counts.
Does anyone have any idea what may be wrong or where I should look next?
Thanks for any help,
Mike Wright
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next reply other threads:[~2005-03-25 19:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-25 19:03 Xen User [this message]
2005-03-25 19:07 ` extremely slow disk access Steven Hand
2005-03-25 21:47 ` Xen User
2005-03-25 21:23 ` Nivedita Singhvi
-- strict thread matches above, loose matches on Subject: below --
2005-03-25 20:05 Ian Pratt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4244608E.6040301@theorb.net \
--to=xen@theorb.net \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.