mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-12-24 14:45:24 +00:00
f81ee7b549
Downstream CI recently encountered failures of libxlxml2domconfigtest when building libvirt packages against Xen 4.17 rc3 packages. The test fails on vnuma_hvm config, where suddently the actual json produced by libxl_domain_config_to_json() contains a 'pnode' entry in the 'vnuma_nodes' list, which is absent in the expected json. It appears the test has thus far passed by luck. E.g. I was able to make the test pass in the failing environment by changing the meson buildtype from debugoptimized to debug. When a VM config contains vnuma settings, libxlMakeVnumaList() checks if the number of requested vnuma nodes exceeds the number of physical nodes. The number of physical nodes is retrieved with libxl_get_physinfo(), which can return wildly different results in the context of unit tests. This change mocks libxl_get_physinfo() to return consistent results. All fields of the libxl_physinfo struct are set to 0 except nr_nodes, which is set to 6 to ensure the vnuma_hvm configuration is properly tested. Signed-off-by: Jim Fehlig <jfehlig@suse.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com> |
||
---|---|---|
.. | ||
basic-hvm.json | ||
basic-hvm.xml | ||
basic-pv.json | ||
basic-pv.xml | ||
basic-pvh.json | ||
basic-pvh.xml | ||
cpu-shares-hvm.json | ||
cpu-shares-hvm.xml | ||
fullvirt-acpi-slic.json | ||
fullvirt-acpi-slic.xml | ||
fullvirt-cpuid-legacy-nest.json | ||
fullvirt-cpuid-legacy-nest.xml | ||
fullvirt-cpuid.json | ||
fullvirt-cpuid.xml | ||
max-eventchannels-hvm.json | ||
max-eventchannels-hvm.xml | ||
max-gntframes-hvm.json | ||
max-gntframes-hvm.xml | ||
moredevs-hvm.json | ||
moredevs-hvm.xml | ||
multiple-ip.json | ||
multiple-ip.xml | ||
variable-clock-hvm.json | ||
variable-clock-hvm.xml | ||
vnuma-hvm-legacy-nest.json | ||
vnuma-hvm-legacy-nest.xml | ||
vnuma-hvm.json | ||
vnuma-hvm.xml |