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

[Xen-devel] Race with hotplug vif scripts

  • To: xen-devel <Xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Jacob Gorm Hansen <jacobg@xxxxxxx>
  • Date: Sat, 30 Dec 2006 19:52:48 +0100
  • Delivery-date: Sat, 30 Dec 2006 10:53:02 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:subject:from:to:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding:sender; b=c5PzoFexyk1fLuUTkLCMtIOchYLM5w5iBQGjCMdBC+PKikX4FpdhMp9eOsiiEA91lcCxzsfuZ5Q21a8y34efWrSMygcpX3jN0Gt3/qwYNnrWsQKZ0LSvPAHQ/VStSvmC8J+R8DNYPM1ZIB9dqOpOEukboQ7tWv8ehg8waWskrzc=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>


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

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?


Xen-devel mailing list



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