WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] XM sched-credit

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] XM sched-credit
From: Paul Piscuc <paul.piscuc@xxxxxxxxxx>
Date: Fri, 14 Jan 2011 11:17:27 +0200
Delivery-date: Fri, 14 Jan 2011 09:14:26 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14pre) Gecko/20110113 Lightning/1.0b2 Shredder/3.1.8pre
Hi,

I have modified the sched-credit for one virtual machine, using xm sched-credit -d 0 -w 60000, and the next day Nagios reported some problems on Dom0. Two plugins, that are checking the firewall and smartctl reported "socket timeout after 10 seconds". When I issued the two scripts, one of them took 5 seconds to run, and the other one a few minutes. Here is the first command that took 5 seconds:

/sbin/iptables-save|grep -v '^\*' |grep -v '^#' |grep -v '^COMMIT'|grep -v '^:'|wc -l

When straced, it pauses for a long time in wait4(). When issued several times, it waits a long time on the third or forth grep. The second one does the same in read(). The load on the dom0 is 0.02, ulimit is ok,and there is no waiting time for the cpu. Also, the virtual machines are running smoothly, without high IO, memory or CPU.

Could the problem be generated by the scheduler, that allocated a small weight for the dom0?

Thx in advance,

Paul PISCUC

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>