Re: Xen2 bailout: "Aieee! CPU0 is toast..."

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Mon, Sep 03, 2007 at 11:39:23PM +0200, Johan Ihren wrote:
> Runs like a charm. Upgrade to xen3 was very straightforward and not  
> much trouble.
> 
> One question, though...
> 
> In Xen2 I've sometimes done the CPU allocation manually becaue the  
> Xen2 scheduler has seemed, well, less than perfect for my  
> applications. It is then very useful to be able to examine the result  
> in the "CPU" column in the output from "xm list". Where do I find  
> information about which domU was allocated to which CPU in Xen3? That  
> information seems to be missing from both "xm list" and "xm top".

The xen3 scheduler is dynamic, and can move a domain from one CPU to another
depending on the load of each CPUs (which Xen2 couldn't do), so maybe the issue
you had with Xen2 won't show up here. But if you really need to you can
tell Xen on which Cpus a domU is allowed to run, e.g.:
cpus = '2-5'
(this is on a 8-way server; this domU is allowed to run on CPUs 2 to 5 and
won't have access to cpus 0, 1, 7 or 8).

-- 
Manuel Bouyer, LIP6, Universite Paris VI.           
Manuel.Bouyer%lip6.fr@localhost
     NetBSD: 26 ans d'experience feront toujours la difference
--