On Fri, 2007-01-12 at 19:41 -0500, Amos Waterland wrote:
On Fri, Jan 12, 2007 at 05:45:03PM -0600, Hollis Blanchard wrote:
We seem to have an IPI problem, which causes vcpu_pause() to hang the
system. The following patch, tested on JS20 and JS21, illustrates it.
Before dom0 starts, IPIs
On Fri, 2007-01-12 at 20:34 -0500, Jimi Xenidis wrote:
I just built clean xenppc-unstable.hg (assuming it has the issues you
state below) and all IPI ^A*3 tests (esp 't' and 'd') work just fine
on my maple
What about xm destroy? I can boot fine and start a domU, but xm destroy
locks my system
On Mon, 2007-01-15 at 11:23 -0600, Hollis Blanchard wrote:
On Fri, 2007-01-12 at 19:41 -0500, Amos Waterland wrote:
On Fri, Jan 12, 2007 at 05:45:03PM -0600, Hollis Blanchard wrote:
We seem to have an IPI problem, which causes vcpu_pause() to hang the
system. The following patch, tested
I mentioned that I accidentally pushed an upstream merge to
xenppc-unstable while it's still broken. There are a couple broken
things. First, DomU console stops mid-string early in boot. Could be an
event channel problem with the ring buffer; haven't investigated.
We seem to have an IPI problem,
Please check if you linux kernel is up to date.
I just built clean xenppc-unstable.hg (assuming it has the issues you
state below) and all IPI ^A*3 tests (esp 't' and 'd') work just fine
on my maple
I created an NFS domain and Did get:
(XEN) Assertion '!cpu_isset(nxt, cpu_core_map[cpu])'
