[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Race with hotplug vif scripts

  • To: xen-devel <Xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Jacob Gorm Hansen <jacobg@xxxxxxx>
  • Date: Sat, 30 Dec 2006 20:18:23 +0100
  • Delivery-date: Sat, 30 Dec 2006 11:18:48 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:subject:from:to:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding:sender; b=UT+E8F8t1jIFyQOdfSyhOCohHfA4Xg0oawBUzXa/re1wPeOmRNBPJegoz9iuumfELVQRue35/hJH/nC8auSE+1y/MyTn8eaDT910+S90NKlyRcQVMp1+gylnOq8enPNlW415QmAbWhb/y63gzkAOGFO6RXZ8YJJLqyFzlEzDG3o=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On Sat, 2006-12-30 at 19:52 +0100, Jacob Gorm Hansen wrote:
> hi,
> I have a domU running a custom HTTP client. As soon as the domain is
> booted and the VIF running it wants to initiate a connection. However, I
> seem to be having a race where the domU starts using the VIF before it
> is completely functional, probably because the hotplug script has not
> completed.
> Currently I just set the frontend to '4', and just wait for the backend
> state to also become '4' (connected), but this does not work in all
> cases. How can I synchronize with the hotplug script, and what is the
> correct sequence of XenBus states?

Ahh never mind, the issue seems to be with TCP connection setup, the
server gets confused due to the shortlived domain reusing the same
source port number over and over. A little randomness fixes the problem.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.