- docs: Document CPU clusters
- docs: Improve documentation for CPU topology
- tests: Verify handling of CPU clusters in QMP data
- qemu: Make monitor aware of CPU clusters
- qemu: Use CPU clusters for guests
- qemu: Introduce QEMU_CAPS_SMP_CLUSTERS
- conf: Allow specifying CPU clusters
- conf: Report CPU clusters in capabilities XML
- tests: Add hostcpudata for machine with CPU clusters
- cpu_map: add kunpeng-920 features to arm features
- cpu/aarch64: enable host-model cpu for AArch64 architecture
- conf/domain_conf: pin the retry_interval and retry_timeout parameters to xml
- nodedev: fix potential heap use after free
- libvirt/conf: Set default values of retry fileds
- qemu: Support 'retry' BLOCK_IO_ERROR event.
- libvirt: Add 'retry' support for error policy
- vdpa: support vdpa device migrate
- vdpa: support vdpa device hot plug/unplug
- hostdev:Introduce vDPA device to hostdev subsystem as a new subtype
- node_device: fix leak of DIR*
- migration/multifd-pin: support migration multifd thread pin
- migration/multifd-pin: add qemu monitor callback functions
- migration/migration-pin: add domainMigrationPid for qemuMonitorCallbacks
- migration/migration-pin: add migrationpin for migration parameters
- migration/migration-pin: add qemu monitor callback functions
- migration/migration-pin:add some migration/multiFd params
- qemu: add pointer check in qemuMonitorLastError
- qemu: fix a concurrent operation situation
- test/commandtest: skip the test4 if the testcase is run in the container env
Signed-off-by: Jiabo Feng <fengjiabo1@huawei.com>
Currently the default values of retry_interval and retry_timeout are set
to -1, when 'driver' option exists without retry fileds. It conflicts
with the default values when the 'driver' option does not exist.
So let's set default values of retry_interval and retry_timeout to 0 when
retry policy is not enabled.
Signed-off-by: Jiahui Cen <cenjiahui@huawei.com>
