search for: numa_placement

...ut more domains +there. + +## Guest Placement within libxl ## + +xl achieves automatic NUMA placement because that is what libxl does +by default. No API is provided (yet) for modifying the behaviour of +the placement algorithm. However, if your program is calling libxl, +it is possible to set the `numa_placement` build info key to `false` +(it is `true` by default) with something like the below, to prevent +any placement from happening: + + libxl_defbool_set(&domain_build_info->numa_placement, false); + +Also, if `numa_placement` is set to `true`, the domain must not +have any cpu affinity (i.e.,...

...+ Xenlight.Domain_create_info.oos = None; + Xenlight.Domain_create_info.name = "Test; + } + and b_info = { + Xenlight.Domain_build_info.max_vcpus = 1; + Xenlight.Domain_build_info.avail_vcpus = [| |]; + Xenlight.Domain_build_info.cpumap = [| |]; + Xenlight.Domain_build_info.numa_placement = None; + Xenlight.Domain_build_info.tsc_mode = Xenlight.TSC_MODE_DEFAULT; + Xenlight.Domain_build_info.max_memkb = 1024L; + Xenlight.Domain_build_info.target_memkb = 1024L; + Xenlight.Domain_build_info.video_memkb = 0L; + Xenlight.Domain_build_info.shadow_memkb = 0L; + Xenlight.D...

Matthew Daley (13): libxl: fix unsigned less-than-0 comparison in e820_sanitize libxl: check for xc_domain_setmaxmem failure in libxl__build_pre libxl: correct file open success check in libxl__device_pci_reset libxl: don''t leak p in libxl__wait_for_backend libxl: remove unsigned less-than-0 comparison libxl: actually abort if initializing a ctx''s lock fails libxl: