Re: vif backend configuration times out

[Ian Campbell <Ian.Campbell@citrix.com>]

On Mon, 2012-08-06 at 18:39 +0100, Olaf Hering wrote:
> With current xen-unstable 25733:353bc0801b11 the attached hvm.cfg does
> not start anymore with a SLES11SP2 dom0 kernel, but it starts if I run a
> 3.5 pvops dom0 kernel. I have no modifications other than the stubdom -j
> patch.
> 
> The output from this command is attached:
> xl -vvvv create -d -f /root/xenpaging/sles11sp2_full_xenpaging_local.cfg 2>&1 | tee xl-create-`uname -r`.txt &
> 
> Any ideas how to fix this timeout error?

The tools are waiting for the backend to move from state 1
(XenbusStateInitialising) to state 2 (XenbusStateInitWait). A backend
driver typically makes that transition at the end of its probe function
-- what is the SLES11SP2 netback waiting for? Or is it failing to init,
in which case perhaps there is an error node in XS?

> 
> Olaf
> 
> ...
> libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x62bf88 wpath=/local/domain/0/backend/vif/2/0/state token=3/1: event epath=/local/domain/0/backend/vif/2/0/state
> libxl: debug: libxl_event.c:600:devstate_watch_callback: backend /local/domain/0/backend/vif/2/0/state wanted state 2 still waiting state 1
> libxl: debug: libxl_event.c:614:devstate_timeout: backend /local/domain/0/backend/vif/2/0/state wanted state 2  timed out
> libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch w=0x62bf88 wpath=/local/domain/0/backend/vif/2/0/state token=3/1: deregister slotnum=3
> libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch w=0x62bf88: deregister unregistered
> libxl: error: libxl_device.c:858:device_backend_callback: unable to disconnect device with path /local/domain/0/backend/vif/2/0
> libxl: error: libxl_create.c:1070:domcreate_attach_pci: unable to add nic devices
> ...