[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] Re: Race condition leading to VMError : Device 0 not connected
Oops forgot the attachment. Now attached. /Jd --- jd <jdsw2002@xxxxxxxxx> wrote: > Hi > We have a client that shows and updates the > current > dom status periodically. When I issue a kill to a > dom, > the next call to xend.domains(1) fails with the > VMError. > > It seems that Xen is still in the process of killing > and the xend.domains call is trying to get > information > and seeing some partial stuff, leading to this > problem. > > This particularly happens when vif is set with mac > address and bridge specification. > > See attached stack trace and xm info to get idea > about > the environment. > > Is this a known problem ? Any patches available ? > > Any workaround that can be coded in the client ? > (I have tried some lame waits.. but there is another > thread that runs into this.) > > Thanks > /Jd > > > > ____________________________________________________________________________________ > Shape Yahoo! in your own image. Join our Network > Research Panel today! > http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 > > > > ____________________________________________________________________________________ Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more. http://mobile.yahoo.com/go?refer=1GNXIC Attachment:
xen_dev_not_connected_problem Attachment:
xen_dev_not_connected_problem_xm_info _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |