On Dec 7, 2006, at 6:16 PM, Hollis Blanchard wrote:
On Thu, 2006-12-07 at 17:11 -0500, poff wrote:
Also today there have been several runs similar to example 2.
I modified python code to skip the 'unpause' at the end of
domain restore. The drill: boot, xend start, xm restore,
then another
I now think the console prints in previous mail are useless.
Example 2 runs while example 3 wedges, yet the prints are
roughly equivalent...
Also today there have been several runs similar to example 2.
I modified python code to skip the 'unpause' at the end of
domain restore. The drill: boot,
On Thu, 2006-12-07 at 17:11 -0500, poff wrote:
Also today there have been several runs similar to example 2.
I modified python code to skip the 'unpause' at the end of
domain restore. The drill: boot, xend start, xm restore,
then another activity eg rebuild tools or search kernel tree,
'xm restore' immediately following boot usually wedges the cpu.
However, xm save followed by xm restore works fine (even when
guest domain and htab are relocated to new memory areas).
^AAA shows: with .plpar_hcall_norets @ c003af78
and .HYPERVISOR_sched_op @
