7d97d7af9e
This test was generated on a guest with the following NUMA
configuration:
<numa>
<cell id='0' cpus='0-23' memory='4194304' unit='KiB' discard='yes'>
<cache level='1' associativity='direct' policy='writeback'>
<size value='10' unit='KiB'/>
<line value='8' unit='B'/>
</cache>
<cache level='2' associativity='full' policy='writethrough'>
<size value='128' unit='KiB'/>
<line value='16' unit='B'/>
</cache>
</cell>
<cell id='1' memory='2097152' unit='KiB'>
<cache level='1' associativity='direct' policy='writeback'>
<size value='10' unit='KiB'/>
<line value='8' unit='B'/>
</cache>
</cell>
<interconnects>
<latency initiator='0' target='0' type='access' value='5'/>
<latency initiator='0' target='0' type='read' value='6'/>
<latency initiator='0' target='0' type='write' value='7'/>
<latency initiator='0' target='1' type='access' value='10'/>
<latency initiator='0' target='1' type='read' value='11'/>
<latency initiator='0' target='1' type='write' value='12'/>
<bandwidth initiator='0' target='0' type='access' value='204800' unit='KiB'/>
<bandwidth initiator='0' target='0' type='read' value='205824' unit='KiB'/>
<bandwidth initiator='0' target='0' type='write' value='206848' unit='KiB'/>
<bandwidth initiator='0' target='0' cache='1' type='access' value='208896' unit='KiB'/>
<bandwidth initiator='0' target='0' cache='1' type='read' value='209920' unit='KiB'/>
<bandwidth initiator='0' target='0' cache='1' type='write' value='210944' unit='KiB'/>
<bandwidth initiator='0' target='1' type='access' value='102400' unit='KiB'/>
<bandwidth initiator='0' target='1' type='read' value='103424' unit='KiB'/>
<bandwidth initiator='0' target='1' type='write' value='104448' unit='KiB'/>
<bandwidth initiator='0' target='1' cache='1' type='access' value='105472' unit='KiB'/>
<bandwidth initiator='0' target='1' cache='1' type='read' value='106496' unit='KiB'/>
<bandwidth initiator='0' target='1' cache='1' type='write' value='107520' unit='KiB'/>
</interconnects>
</numa>
The sysfs content was also copied over from the VM but only those
files which are accessed in the test are stored in the repo.
Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
Reviewed-by: Martin Kletzander <mkletzan@redhat.com>
Libvirt API for virtualization
Libvirt provides a portable, long term stable C API for managing the virtualization technologies provided by many operating systems. It includes support for QEMU, KVM, Xen, LXC, bhyve, Virtuozzo, VMware vCenter and ESX, VMware Desktop, Hyper-V, VirtualBox and the POWER Hypervisor.
For some of these hypervisors, it provides a stateful management daemon which runs on the virtualization host allowing access to the API both by non-privileged local users and remote users.
Layered packages provide bindings of the libvirt C API into other languages including Python, Perl, PHP, Go, Java, OCaml, as well as mappings into object systems such as GObject, CIM and SNMP.
Further information about the libvirt project can be found on the website:
License
The libvirt C API is distributed under the terms of GNU Lesser General Public License, version 2.1 (or later). Some parts of the code that are not part of the C library may have the more restrictive GNU General Public License, version 2.0 (or later). See the files COPYING.LESSER and COPYING for full license terms & conditions.
Installation
Instructions on building and installing libvirt can be found on the website:
https://libvirt.org/compiling.html
Contributing
The libvirt project welcomes contributions in many ways. For most components the best way to contribute is to send patches to the primary development mailing list. Further guidance on this can be found on the website:
https://libvirt.org/contribute.html
Contact
The libvirt project has two primary mailing lists:
- libvirt-users@redhat.com (for user discussions)
- libvir-list@redhat.com (for development only)
Further details on contacting the project are available on the website: