hi,
I just noticed that my vif setup code from buscreate no longer works
after upgrading to 3.0.3. Is there anywhere I can find documentation on
the current state of the Xenstore protocol for VIF setup? My current
code is below:
sprintf(s,"%s/handle",frontend);
sprintf(s2,"%d",uuid);
xs_w(s, s2);
sprintf(s,"%s/mac",frontend);
xs_w(s, "aa:00:00:11:a6:02");
sprintf(s, "%s/backend-id", frontend);
xs_w(s, "0");
sprintf(s,"%s/backend",frontend);
xs_w(s, backend );
sprintf(s, "%s/state", frontend);
xs_w(s, "1");
xs_end();
xs_begin();
sprintf(s,"%s/handle",backend);
sprintf(s2,"%d",uuid);
xs_w(s, s2);
sprintf(s,"%s/mac",backend);
xs_w(s, "aa:00:00:11:a6:02");
sprintf(s,"%s/script",backend);
xs_w(s, "");
sprintf(s,"%s/frontend",backend);
xs_w(s, frontend );
sprintf(s,"%s/frontend-id",backend);
sprintf(s2,"%d",domid);
xs_w(s, s2 );
sprintf(s, "%s/state", backend);
xs_w(s, "1");
xs_end();
Thanks,
Jacob
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
On Mon, Nov 20, 2006 at 11:35:43PM +0100, Jacob Gorm Hansen wrote:> hi, > > I just noticed that my vif setup code from buscreate no longer works > after upgrading to 3.0.3. Is there anywhere I can find documentation on > the current state of the Xenstore protocol for VIF setup? My current > code is below:Nothing changed, AFAIR. What''s the nature of your failure? Ewan. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Mon, 2006-11-20 at 22:43 +0000, Ewan Mellor wrote:> On Mon, Nov 20, 2006 at 11:35:43PM +0100, Jacob Gorm Hansen wrote: > > > hi, > > > > I just noticed that my vif setup code from buscreate no longer works > > after upgrading to 3.0.3. Is there anywhere I can find documentation on > > the current state of the Xenstore protocol for VIF setup? My current > > code is below: > > Nothing changed, AFAIR. What''s the nature of your failure? >The domU logs the following in dmesg: XENBUS: Timeout connecting to device: device/vif/11600 (state 0) Thanks, Jacob _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 20/11/06 11:19 pm, "Jacob Gorm Hansen" <jacobg@diku.dk> wrote:>> Nothing changed, AFAIR. What''s the nature of your failure? >> > > The domU logs the following in dmesg: > XENBUS: Timeout connecting to device: device/vif/11600 (state 0)I''d stick xenstored into logging mode and create a guest using the python tools. Then see what nodes are now written by xend (might need to extend the logging to make it clear who writes what into the store). I can''t think of anything essential that''s been added though. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Tue, 2006-11-21 at 00:19 +0100, Jacob Gorm Hansen wrote:> The domU logs the following in dmesg: > XENBUS: Timeout connecting to device: device/vif/11600 (state 0)Turns out Xenstored was hosed, a reboot seems to have cured it. Thanks, Jacob _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel