[Xen-devel] NUMA config handling bug on reuse of libxl domain config

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Ian Jackson writes ("Re: [PATCH v4 00/35] libxl ao abort request 
(cancellation)"):
> Ian Jackson writes ("[PATCH v4 00/35] libxl ao abort request (cancellation)"):
> > This is v4 of my series to provide support for abandoning a
> > long-running libxl operation.
> 
> I've pushed it here
> 
>   http://xenbits.xen.org/gitweb/?p=people/iwj/xen.git;a=summary
>   git://xenbits.xen.org/people/iwj/xen.git
>      base.ao-abort.v4..wip.ao-abort.v4
> 
> (base.ao-abort is yesterday's staging).

One of the tests failed until I put a workaround in.

The test program:
 - creates and populates a libxl_domain_config
 - calls libxl_domain_create_new
 - destroys the resulting domain with libxl_domain_destroy
 - calls libxl_domain_create_new again with the same config

The result is:

 libxl: error: libxl_dom.c:343:libxl__build_pre: Can run NUMA placement
 only if the domain does not have any NUMA node affinity set already

 libxl: error: libxl_create.c:1174:domcreate_rebuild_done: cannot
 (re-)build domain: -6

My repro case is to use the wip.ao-abort.v4 series, above, with the
following test suite:

  http://xenbits.xen.org/gitweb/?p=people/iwj/ring3-xl-test.git;a=summary
  git://xenbits.xen.org/people/iwj/ring3-xl-test.git
     #t.numa-bug

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel