[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-devel] Re: [Xen-staging] [xen-3.1-testing] xend: Fix use ofPIFIsPhysical (takes no arguments).
I am running on a Unisys ES7000 with changeset 15006, and I still see this problem. I believe it only happens when I stop the server, reconfigure the amount of host processors and RAM, and then reboot. [2007-05-03 13:49:19 4204] INFO (SrvDaemon:331) Xend Daemon started [2007-05-03 13:49:19 4204] INFO (SrvDaemon:335) Xend changeset: Wed May 02 15:27:10 2007 +0100 15006:b5cfbc8f7d2c. [2007-05-03 13:49:19 4204] INFO (SrvDaemon:342) Xend version: Unknown. [2007-05-03 13:49:21 4204] ERROR (SrvDaemon:353) Exception starting xend (PIF is physical) Traceback (most recent call last): File "/home/unisys/xen-3.1-testing.hg/dist/install/usr/lib64/python/xen/xend/ server/SrvDaemon.py", line 345, in run servers = SrvServer.create() File "/home/unisys/xen-3.1-testing.hg/dist/install/usr/lib64/python/xen/xend/ server/SrvServer.py", line 254, in create root.putChild('xend', SrvRoot()) File "/home/unisys/xen-3.1-testing.hg/dist/install/usr/lib64/python/xen/xend/ server/SrvRoot.py", line 40, in __init__ self.get(name) File "/home/unisys/xen-3.1-testing.hg/dist/install/usr/lib64/python/xen/web/S rvDir.py", line 82, in get val = val.getobj() File "/home/unisys/xen-3.1-testing.hg/dist/install/usr/lib64/python/xen/web/S rvDir.py", line 52, in getobj self.obj = klassobj() File "/home/unisys/xen-3.1-testing.hg/dist/install/usr/lib64/python/xen/xend/ server/SrvNode.py", line 30, in __init__ self.xn = XendNode.instance() File "/home/unisys/xen-3.1-testing.hg/dist/install/usr/lib64/python/xen/xend/ XendNode.py", line 658, in instance inst = XendNode() File "/home/unisys/xen-3.1-testing.hg/dist/install/usr/lib64/python/xen/xend/ XendNode.py", line 168, in __init__ XendPIF.recreate(pif, pif_uuid) File "/home/unisys/xen-3.1-testing.hg/dist/install/usr/lib64/python/xen/xend/ XendPIF.py", line 208, in recreate pif.destroy() File "/home/unisys/xen-3.1-testing.hg/dist/install/usr/lib64/python/xen/xend/ XendPIF.py", line 309, in destroy raise PIFIsPhysical() PIFIsPhysical: PIF is physical Thanks, Sue Krysan Linux Systems Group Unisys Corporation -----Original Message----- From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Tom Wilkie Sent: Wednesday, May 02, 2007 12:16 PM To: Alex Williamson Cc: Pascal Bouchareine; Keir Fraser; xen-devel; Tom Wilkie Subject: Re: [Xen-devel] Re: [Xen-staging] [xen-3.1-testing] xend: Fix use ofPIFIsPhysical (takes no arguments). 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@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |