From mboxrd@z Thu Jan  1 00:00:00 1970
From: Lon Hohberger <lhh@redhat.com>
Date: Mon, 19 Sep 2011 16:32:55 -0400
Subject: [Cluster-devel] [fence-virt PATCH] fix handling
	of	VIR_DOMAIN_EVENT_STARTED
In-Reply-To: <4E6F1809.8020300@intellilink.co.jp>
References: <4E6F1809.8020300@intellilink.co.jp>
Message-ID: <4E77A6F7.5090607@redhat.com>
List-Id: <cluster-devel.redhat.com>
To: cluster-devel.redhat.com
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

On 09/13/2011 04:44 AM, Kazunori INOUE wrote:

> I attached the patch for this problem.
> 
> * Modified to send a SIGHUP to the primary thread from the secondary
>    thread detects the start of the VM, and
>    the primary thread is modified so as to select() the requests from
>    the VM which started.

That's certainly one way of doing it.  I might have used
'pthread_cond_singal'.

> * Also, when four VM(s) are started simultaneously,
>    poll()<in event_thread()@server/virt-serial.c>  could not handle
>    all the boot.
>    Therefore, I revised it to call domainStarted()/domainStopped() in
>    myDomainEventCallback1().

You're using pthread_kill, so what I suspect happens is 4 SIGHUPs are
coming in very quickly, causing more modification to be required.

I'll look at this a bit more with Marek.

-- Lon