All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@hp.com>
To: xen-devel@lists.xensource.com
Cc: Keir Fraser <keir@xensource.com>
Subject: Re: [Xen-staging] [xen-3.1-testing] xend: Fix use of PIFIsPhysical (takes no arguments).
Date: Wed, 02 May 2007 09:24:31 -0600	[thread overview]
Message-ID: <1178119471.28577.46.camel@bling> (raw)
In-Reply-To: <200705021410.l42EAuwL011557@latara.uk.xensource.com>

On Wed, 2007-05-02 at 15:10 +0100, Xen staging patchbot-3.1-testing
wrote:
> # HG changeset patch
> # User Keir Fraser <keir@xensource.com>
> # Date 1178054641 -3600
> # Node ID c1fafdcdb19a781a603988346e49deae07054a54
> # Parent  650007cf390daca81f65311ef203288b6762d9be
> xend: Fix use of PIFIsPhysical (takes no arguments).
> Signed-off-by: Keir Fraser <keir@xensource.com>

   FWIW, I'm seeing a "Exception starting xend: PIF is physical" on
unstable and staging tip (14997) on ia64.  I'll bisect back and figure
out where it came from.  Here's the traceback:

[2007-05-02 08:47:09 5791] INFO (__init__:1072) Xend version: Unknown.
[2007-05-02 08:47:09 5791] ERROR (__init__:1072) Exception starting xend (PIF is physical)
Traceback (most recent call last):
  File "//usr/lib/python/xen/xend/server/SrvDaemon.py", line 345, in run
    servers = SrvServer.create()
  File "//usr/lib/python/xen/xend/server/SrvServer.py", line 254, in create
    root.putChild('xend', SrvRoot())
  File "//usr/lib/python/xen/xend/server/SrvRoot.py", line 40, in __init__
    self.get(name)
  File "//usr/lib/python/xen/web/SrvDir.py", line 82, in get
    val = val.getobj()
  File "//usr/lib/python/xen/web/SrvDir.py", line 52, in getobj
    self.obj = klassobj()
  File "//usr/lib/python/xen/xend/server/SrvNode.py", line 30, in __init__
    self.xn = XendNode.instance()
  File "//usr/lib/python/xen/xend/XendNode.py", line 658, in instance
    inst = XendNode()
  File "//usr/lib/python/xen/xend/XendNode.py", line 168, in __init__
    XendPIF.recreate(pif, pif_uuid)
  File "//usr/lib/python/xen/xend/XendPIF.py", line 208, in recreate
    pif.destroy()
  File "//usr/lib/python/xen/xend/XendPIF.py", line 309, in destroy
    raise PIFIsPhysical()
PIFIsPhysical: PIF is physical

Thanks,

	Alex

-- 
Alex Williamson                             HP Open Source & Linux Org.

       reply	other threads:[~2007-05-02 15:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200705021410.l42EAuwL011557@latara.uk.xensource.com>
2007-05-02 15:24 ` Alex Williamson [this message]
2007-05-02 15:29   ` Re: [Xen-staging] [xen-3.1-testing] xend: Fix use of PIFIsPhysical (takes no arguments) Keir Fraser
2007-05-02 15:46     ` Tom Wilkie
2007-05-02 16:05       ` Alex Williamson
2007-05-02 16:15         ` Tom Wilkie

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=1178119471.28577.46.camel@bling \
    --to=alex.williamson@hp.com \
    --cc=keir@xensource.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.