|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] Re: [Xen-staging] [xen-3.1-testing] xend: Fix use ofPIFI
On 3/5/07 20:25, "Krysan, Susan" <KRYSANS@xxxxxxxxxx> wrote:
> 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.
Xen-unstable c/s 15006, I assume?
In that case your xend hasn't been properly re-installed: line 208 in your
Python backtrace changed from pif.destroy() to XendBase.destroy() in
changeset 15000. That was the fix for this bug. :-)
-- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- RE: [Xen-devel] Re: [Xen-staging] [xen-3.1-testing] xend: Fix use ofPIFIsPhysical (takes no arguments)., Krysan, Susan
- Re: [Xen-devel] Re: [Xen-staging] [xen-3.1-testing] xend: Fix use ofPIFIsPhysical (takes no arguments).,
Keir Fraser <=
- [Xen-devel] Numa=on broken?, Subrahmanian, Raj
- Re: [Xen-devel] Numa=on broken?, Ryan Harper
- RE: [Xen-devel] Numa=on broken?, Subrahmanian, Raj
- RE: [Xen-devel] Numa=on broken?, Subrahmanian, Raj
- Re: [Xen-devel] Numa=on broken?, Ryan Harper
- Re: [Xen-devel] Numa=on broken?, Ryan Harper
- RE: [Xen-devel] Numa=on broken?, Subrahmanian, Raj
- RE: [Xen-devel] Numa=on broken?, Subrahmanian, Raj
- Re: [Xen-devel] Numa=on broken?, Ryan Harper
|
|
|
|
|