From: Olaf Hering <olaf@aepfle.de>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: vif backend configuration times out
Date: Tue, 7 Aug 2012 17:25:03 +0200 [thread overview]
Message-ID: <20120807152502.GA24503@aepfle.de> (raw)
In-Reply-To: <1344318133.24794.16.camel@dagon.hellion.org.uk>
On Tue, Aug 07, Ian Campbell wrote:
> 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?
I think there is a difference between the two kernels. The pvops kernel
goes into state 2 right away (I cant tell from repeated xenstore-ls runs
if it had also state 1).
The sles11 kernel remains in state 1. Did the expectations of libxl
change recently? xl create used to work not too long ago.
xm does not work either, so the change is most likely in the scripts.
Olaf
next prev parent reply other threads:[~2012-08-07 15:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 17:39 vif backend configuration times out Olaf Hering
2012-08-07 5:42 ` Ian Campbell
2012-08-07 15:25 ` Olaf Hering [this message]
2012-08-07 15:33 ` Ian Campbell
2012-08-08 17:28 ` Olaf Hering
2012-08-09 8:32 ` Ian Campbell
2012-08-09 14:34 ` Olaf Hering
2012-08-10 7:41 ` Olaf Hering
2012-08-10 12:59 ` Olaf Hering
2012-08-14 10:18 ` Ian Campbell
2012-08-14 11:30 ` Olaf Hering
2012-08-14 13:04 ` Ian Campbell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120807152502.GA24503@aepfle.de \
--to=olaf@aepfle.de \
--cc=Ian.Campbell@citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).