On 24/12/2019 13:04, Paul Durrant wrote: > The value of 'rover' is the value at which Xen will start searching for an > unused domid if none is specified. Currently it is only updated when a > domid is automatically chosen, rather than specified by the caller, which > makes it very hard to describe Xen's rationale in choosing domids in an > environment where some domain creations have specified domids and some > don't. > This patch always updates 'rover' after a successful creation, even in the > case that domid is specified by the caller. This ensures that, if Xen > automatically chooses a domid for a subsequent domain creation it will > always be the next available value after the domid of the most recently > created domain. > > Signed-off-by: Paul Durrant <pdurr...@amazon.com>
This behaviour is deliberate, if not obvious. Lots of things break when domid's overflow. The current behaviour means that an overflow won't occur until all domids have been used. Domid reuse is a massive swamp which someone is going to fix at some point... ~Andrew _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
