[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH for 4.7] doc: document that Domain-0 can't be migrated across cpupools

On 09/05/16 10:36, Andrew Cooper wrote:
> On 09/05/2016 09:29, Juergen Gross wrote:
>> Domain-0 is always member of Pool-0 (or, to be precise: of the cpuppol
>> with cpupool-id 0). Document this in the xl man page.
>> Signed-off-by: Juergen Gross <jgross@xxxxxxxx>
> Out of interest, why?
> Is this a limitation of the current implementation, or something which
> couldn't be made to work?
> Given that it is all just vcpus and linked lists in the end, I can't see
> why this should necessarily be the case.

Main reason was to keep cpu hotplugging simple. New cpus are always
added to Pool-0 and should be available to dom0 immediately without
having to move them to another cpupool.

It could be changed, of course. But I don't see any advantage in
allowing to move dom0 to another cpupool, while the code would be
more complicated.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.