Removed old OSes:

    - Debian 11
    - Fedora 40, Fedora 41

Added new OSes:

    - AlmaLinux 10
    - CentOS Stream 10
    - Debian 13
    - Fedora 42, Fedora 43

Signed-off-by: Pavel Hrdina <phrdina@redhat.com>

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

Regenerate with libvirt commit v12.0.0-206-gdbdaf22b63 to pick up the constants
for histogram statistics.

Signed-off-by: Peter Krempa <pkrempa@redhat.com>

Expose the fields accessed via VIR_DOMAIN_STATS_BLOCK_SUFFIX_LATENCY_HISTOGRAM_
constants as DomainStatsBlockLatencyHistogram.

Signed-off-by: Peter Krempa <pkrempa@redhat.com>

Signed-off-by: Peter Krempa <pkrempa@redhat.com>

When "//export someMethod" is used, the Go method with the listed
name is exported in the global linker namespace. If multiple Go
modules export "someMethod" they will clash at link time.

To address this, all exported Go methods will gain a 'virGo'
prefix to scope them to libvirt's typical C namespace. The matching
C helpers will also gain 'virGo' for consistency, even if they are
static.

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

When "//export someMethod" is used, the Go method with the listed
name is exported in the global linker namespace. If multiple Go
modules export "someMethod" they will clash at link time.

To address this, all exported Go methods will gain a 'virGo'
prefix to scope them to libvirt's typical C namespace. The matching
C helpers will also gain 'virGo' for consistency, even if they are
static.

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

When "//export someMethod" is used, the Go method with the listed
name is exported in the global linker namespace. If multiple Go
modules export "someMethod" they will clash at link time.

To address this, all exported Go methods will gain a 'virGo'
prefix to scope them to libvirt's typical C namespace. The matching
C helpers will also gain 'virGo' for consistency, even if they are
static.

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

When "//export someMethod" is used, the Go method with the listed
name is exported in the global linker namespace. If multiple Go
modules export "someMethod" they will clash at link time.

To address this, all exported Go methods will gain a 'virGo'
prefix to scope them to libvirt's typical C namespace. The matching
C helpers will also gain 'virGo' for consistency, even if they are
static.

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

When "//export someMethod" is used, the Go method with the listed
name is exported in the global linker namespace. If multiple Go
modules export "someMethod" they will clash at link time.

To address this, all exported Go methods will gain a 'virGo'
prefix to scope them to libvirt's typical C namespace. The matching
C helpers will also gain 'virGo' for consistency, even if they are
static.

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

When "//export someMethod" is used, the Go method with the listed
name is exported in the global linker namespace. If multiple Go
modules export "someMethod" they will clash at link time.

To address this, all exported Go methods will gain a 'virGo'
prefix to scope them to libvirt's typical C namespace. The matching
C helpers will also gain 'virGo' for consistency, even if they are
static.

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

When "//export someMethod" is used, the Go method with the listed
name is exported in the global linker namespace. If multiple Go
modules export "someMethod" they will clash at link time.

To address this, all exported Go methods will gain a 'virGo'
prefix to scope them to libvirt's typical C namespace. The matching
C helpers will also gain 'virGo' for consistency, even if they are
static.

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

When "//export someMethod" is used, the Go method with the listed
name is exported in the global linker namespace. If multiple Go
modules export "someMethod" they will clash at link time.

To address this, all exported Go methods will gain a 'virGo'
prefix to scope them to libvirt's typical C namespace. The matching
C helpers will also gain 'virGo' for consistency, even if they are
static.

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

When "//export someMethod" is used, the Go method with the listed
name is exported in the global linker namespace. If multiple Go
modules export "someMethod" they will clash at link time.

To address this, all exported Go methods will gain a 'virGo'
prefix to scope them to libvirt's typical C namespace. The matching
C helpers will also gain 'virGo' for consistency, even if they are
static.

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

When "//export someMethod" is used, the Go method with the listed
name is exported in the global linker namespace. If multiple Go
modules export "someMethod" they will clash at link time.

To address this, all exported Go methods will gain a 'virGo'
prefix to scope them to libvirt's typical C namespace. The matching
C helpers will also gain 'virGo' for consistency, even if they are
static.

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

When "//export someMethod" is used, the Go method with the listed
name is exported in the global linker namespace. If multiple Go
modules export "someMethod" they will clash at link time.

To address this, all exported Go methods will gain a 'virGo'
prefix to scope them to libvirt's typical C namespace. The matching
C helpers will also gain 'virGo' for consistency, even if they are
static.

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>