|
|
|
|
|
|
|
|
|
|
xen-users
Re: [Xen-users] default CPU for 2nd domain...
> > The default CPU for the first domU is wrong for SMP machines. Dead wrong
> > if there are only the two domains. dom0 and the first domU end up on
> > hyperthreads of the first CPU. At least under 2.0.5 ....
Default allocation is already smarter under 3.0-unstable.
> > and I frankly
> > didn't realize that XEN doesn't seem to move domains between "CPUs".
> > Once a domain has been assigned a "CPU" it is stuck there until/unless
> > someone moves it with "xm pincpu"
Yep.
> > You can have two busy dom's sharing one CPU and the other CPU
> > effectively idle. I hope and believe this will be fixed under 3.0 ?
>
> Does anybody know for certain if 3.0 will have a more intelligent CPU
> balancing system?
It will; in addition to the improved default allocation already available
Stephan has code that tries to move vCPUs around in order to optimise the
performance of the machine.
Cheers,
Mark
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|