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/
Home Products Support Community News


Re: [Xen-users] gettimeofday and endless looping

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] gettimeofday and endless looping
From: "John Wells" <groups@xxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 15 Nov 2005 15:12:25 -0500 (EST)
Delivery-date: Tue, 15 Nov 2005 20:00:24 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
Importance: Normal
In-reply-to: <33833.>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <33833.>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: SquirrelMail/1.4.3a-9.EL3.TL1
John Wells said:
> Guys,
> We're having a similar problem to that documented, but not resolved, here:
> http://lists.xensource.com/archives/html/xen-users/2005-08/msg00110.html

Heh...ok, well, we rebooted the box, and of course the problem went away.

However, now I notice my problem description is wrong. I connected via
strace to the now working process and note that it also continuously spits
out gettimeofday messages, but that intermixed are calls to poll:

gettimeofday({1132084397, 346225}, NULL) = 0xen.xend.server import SrvDaemon
gettimeofday({1132084397, 346536}, NULL) = 0= SrvDaemon.instance()
poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=6, events=POLLIN},
{fd=10, events=POLLIN}, {fd=15, events=POLLIN}, {fd=18, events=POLLIN}],
6, 178) = 0
gettimeofday({1132084397, 534960}, NULL) = 0
gettimeofday({1132084397, 535283}, NULL) = 0

So apparently, whatever our problem was caused by led to this poll() call
not being called.

Anyone have any ideas what I might look at? I'm hunting down the SrvDaemon
code currently to try get some insight, but if you have any ideas in the
meantime it would be appreciated.


Xen-users mailing list

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