Wow, thanks for the quick answer AND the solution. Frankly, I'm impressed.
Nothing to report on this hack then ? No side effects ? (except the fact that the state is not persisted, which is irrelevent anyways...)
Luc
-----Message d'origine----- De : Daniel P. Berrange [mailto:berrange@redhat.com] Envoyé : 25 avril 2007 15:38 À : Boudreau Luc Cc : fedora-xen@redhat.com Objet : Re: [Fedora-xen] Xen 3.0.4...
On Wed, Apr 25, 2007 at 03:31:49PM -0400, Boudreau Luc wrote:
Correct me if I'm wrong, but considering this :
FC6 ships with Xen 3.0.3 with xen-kernel version 2.6.20
Xen 3.0.3 has a serious performance bug (see
http://lists.xensource.com/archives/html/xen-devel/2006-10/msg00487.html )
This bug is fixed in Xen 3.0.4
No it isn't. The performance bug is actually at least x2 worse in Xen 3.0.4
http://lists.xensource.com/archives/html/xen-devel/2007-04/msg00663.html
If you want immediate relief from xenstore performance problems in 3.0.3, the quick *hack* is to add this in /etc/init.d/xend
if [ -d /dev/shm ]; then if [ ! -d /dev/shm/xenstored ]; then mkdir /dev/shm/xenstored chcon system_u:object_r:xenstored_var_lib_t /dev/shm/xenstored/ mount --bind /dev/shm/xenstored /var/lib/xenstored fi fi
Immediately after the 'modprobe netloop' line in the start() function. This stops xenstored I/O hitting your disk, by moving it into a ramdisk. There's no need to keep xenstored state around between reboots so this is a reasonably safe hack. I'm experimenting with more long term fixes.
Dan.