Xen devel - May 2007 - Re: [Xen-staging] [xen-3.1-testing] xend: Fix use of PIFIsPhysical (takes no arguments).

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.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On 2/5/07 16:24, "Alex Williamson" <alex.williamson@hp.com>
wrote:
>    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:
Thanks. Tom is going to prepare a fix.

 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Checked in a fix, and a fix for that fix.

cset number 15001.

Cheers

Tom

ps did you do something weird like turn the box off, remove a network  
card, and turn it back on?  Thats the only way I can think of this  
bug getting triggered...  Or this could be related to the networks  
scripts not  being run when xend is started.

On 2 May 2007, at 16:29, Keir Fraser wrote:
>
>
>
> On 2/5/07 16:24, "Alex Williamson" <alex.williamson@hp.com>
wrote:
>
>>    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:
>
> Thanks. Tom is going to prepare a fix.
>
>  -- Keir
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On Wed, 2007-05-02 at 16:46 +0100, Tom Wilkie wrote:
> Checked in a fix, and a fix for that fix.
> 
> cset number 15001.
   Confirmed, Thanks!
> ps did you do something weird like turn the box off, remove a network  
> card, and turn it back on?  Thats the only way I can think of this  
> bug getting triggered...  Or this could be related to the networks  
> scripts not  being run when xend is started.
   Removing a NIC from a powered off box doesn''t seem so weird to me,
but no, the hardware config did not change at all.  The only interesting
config is that one port of a dual port e1000 NIC is hidden from dom0
using "pciback.hide=(0000:01:02.1)".  Otherwise it''s a
standard Debian
Etch system netbooting xen & xenlinux w/ matching tools locally built
and installed.  Thanks,

	Alex

-- 
Alex Williamson                             HP Open Source & Linux Org.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On 2 May 2007, at 17:05, Alex Williamson wrote:
> On Wed, 2007-05-02 at 16:46 +0100, Tom Wilkie wrote:
>> Checked in a fix, and a fix for that fix.
>>
>> cset number 15001.
>
>    Confirmed, Thanks!
>
>> ps did you do something weird like turn the box off, remove a network
>> card, and turn it back on?  Thats the only way I can think of this
>> bug getting triggered...  Or this could be related to the networks
>> scripts not  being run when xend is started.
>
>    Removing a NIC from a powered off box doesn''t seem so weird to
me,
> but no, the hardware config did not change at all.  The only  
> interesting
> config is that one port of a dual port e1000 NIC is hidden from dom0
> using "pciback.hide=(0000:01:02.1)".  Otherwise it''s a
standard Debian
> Etch system netbooting xen & xenlinux w/ matching tools locally built
> and installed.  Thanks,
Okay, if you weren''t changing the cards then it must have been the  
previous bug mentioned by Pascal Bouchareine.

I''ve check in a fix for that too, cset 15002

Cheers

Tom
>
> 	Alex
>
> -- 
> Alex Williamson                             HP Open Source & Linux  
> Org.
>

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel