We periodically get failures building the containers due to broken
deps in the repositories.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

The automake 'distcheck' target accidentally passes the '--best' arg to
gzip when decompressing, when it only makes sense for compressing. This
is harmless with the normal gzip impl, but triggers an error with the
busybox gzip.

We have been relying on getting 'gzip' indirectly via an existing pkg
dependency, and recently this changed from the full gzip to a busybox
minimal gzip in openSUSE tumbleweed.

While we could add an explicit gzip dep, we instead take the opportunity
to switch the project over to 'xz'.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

This replaces Fedora 33 with Fedora 35.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

The repo-lockdown service used to run as a bot outside GitHub, but has
now switched to using the GitHub Actions workflow framework. This
requires use of a new configuration file.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

We now use lcitool's manifest feature to generate files.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

This uses the command "lcitool manifest ci/manifest.yml" to re-generate
all existing dockerfiles and gitlab CI config.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

This is to be used with the command "lcitool manifest ci/manifest.yml"
to re-generate all existing dockerfiles and gitlab CI config.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

This platform is no longer supported by libvirt.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

The current docker:dind container has broken default seccomp filter that
results in clone3 being blocked, which in turn breaks Fedora 35 rawhide.

This custom image has a workaround that causes the seccomp filter to
return ENOSYS for clone3 instad of EPERM, thus triggering glibc to
fallback to clone correctly.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

Changes contained in this refresh:
- CentOS 7 is pulled from docker.io registry
- PowerTools repo name regression fix for CentOS Stream
- enhancement for the workaround fix for JDK installation fails on Debian 10
  '-slim' containers
Signed-off-by: Erik Skultety <eskultet@redhat.com>

This makes the dockerfile name match the output container name
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

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

This introduces Fedora 33 and removes some redundant packages.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

Libvirt changed from autotools to meson. All the containers need
refreshing and the CI recipes updated.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

With the introduction of automated CI pipelines, we are now ready to switch
to using merge requests for the project. With this switch we longer wish
to have patches sent to the mailing list, and thus the git-publish
config is removed.
Reviewed-by: Andrea Bolognani <abologna@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

The sandbox build needs to validate two axis

  - A variety of distro versions
  - A variety of libvirt versions

We test a variety of libvirt versions by running a build against the
distro provided libvirt packages. All that is then missing is a build
against the latest libvirt git master, which only needs to be run on
a single distro, for which CentOS 7 is picked as a stable long life
base.
Reviewed-by: Andrea Bolognani <abologna@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

This job uses the shared "check-dco" image to validate that all
commits on a branch in a developer's repo fork have a suitable
Signed-off-by statement present.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

Libvirt uses GitHub as an automated read-only mirror. The goals were to
have a disaster recovery backup for libvirt.org, a way to make it easy
for people to clone their own private copy of libvirt Git, and finally
as a way to interact with apps like Travis.

The project description was set to a message telling people that we
don't respond to pull requests. This was quite a negative message to
potential contributors, and also did not give them any guidance about
the right way to submit to libvirt. Many also missed the description and
submitted issues or pull requests regardless.

It is possible to disable the issue tracker in GitHub, but there is no
way to disable merge requests. Disabling the issue tracker would also
leave the problem of users not being given any positive information
about where they should be reporting instead.

There is a fairly new 3rd party application built for GitHub that
provides a bot which auto-responds to both issues and merge requests,
closing and locking them, with a arbitrary comment:

   https://github.com/apps/repo-lockdown



This commit adds a suitable configuration file for libvirt, which
tries to give a positive response to user's issue/pullreq and guide
them to the desired contribution path on GitLab.
Reviewed-by: Andrea Bolognani <abologna@redhat.com>
Reviewed-by: Pavel Hrdina <phrdina@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

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

Newest GCC warns that the string copying is potentially truncated and
thus not nul terminated.

In file included from /usr/include/string.h:494,
                 from ../../src/Virt_HostSystem.c:23:
In function ‘strncpy’,
    inlined from ‘resolve_host’ at ../../src/Virt_HostSystem.c:55:28,
    inlined from ‘get_fqdn’ at ../../src/Virt_HostSystem.c:92:23,
    inlined from ‘set_host_system_properties’ at ../../src/Virt_HostSystem.c:109:13:
/usr/include/bits/string_fortified.h:106:10: error: ‘__builtin_strncpy’ specified bound 256 equals destination size [-Werror=stringop-truncation]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In function ‘strncpy’,
    inlined from ‘resolve_host’ at ../../src/Virt_HostSystem.c:67:17,
    inlined from ‘get_fqdn’ at ../../src/Virt_HostSystem.c:92:23,
    inlined from ‘set_host_system_properti...

When running autogen.sh we get told twice

   "You may now run make"

Anyone who knows that they must run configure, already knows that they
must run make too. There's no need to tell them, twice.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

The schema files that we actually download & bundle in the tar.gz dist
have removed the clause "for uses consistent with this purpose" which
is good because that clause might be considered a distribution
restriction which could make it a non-free license.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

The "git-publish" tool is a useful git extension for sending patch
series for code review. It automatically creates versioned tags
each time code on a branch is sent, so that there is a record of
each version. It also remembers the cover letter so it does not
need re-entering each time the series is reposted.

With this config file present it is now sufficient[1] to run

  $ git publish

to send all patches in a branch to the list for review, with the
correct subject prefix added for this non-core libvirt module.

[1] Assuming your $HOME/.gitconfig has an SMTP server listed
at least e.g.

   [sendemail]
        smtpserver = smtp.example.com
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

Instead of having to run autogen.sh inside the source directory
first, before moving to a build directory and run configure there,
it's now possible to run everything from the build directory.
Signed-off-by: Andrea Bolognani <abologna@redhat.com>
Reviewed-by: Daniel P. Berrange <berrange@redhat.com>

This is in line with pretty much all libvirt-related projects,
is entirely compatible with the old behavior and will enable
some simplifications in the CI setup.
Signed-off-by: Andrea Bolognani <abologna@redhat.com>
Reviewed-by: Daniel P. Berrange <berrange@redhat.com>

Instead of making the execution of each command dependend on the
success of the previous one, check return values explicitly.
Signed-off-by: Andrea Bolognani <abologna@redhat.com>
Reviewed-by: Daniel P. Berrange <berrange@redhat.com>

The Mercurial repositories are no more, so update the pointer.
Signed-off-by: Andrea Bolognani <abologna@redhat.com>

While the "autoconfiscate" name is very clever and cute, the
de-facto standard name for this kind of script is "autogen", and
deviating from it means having to special-case the libvirt-cim
project when, for example, setting up a CI environment.
Signed-off-by: Andrea Bolognani <abologna@redhat.com>

There's no need to mark a function as inline in the function
declaration. In fact, it causes a compilation error:

  CC       xmlgen.lo
In file included from acl_parsing.h:29:0,
                 from xmlgen.h:26,
                 from capability_parsing.c:37:
list_util.h:67:21: error: inline function ‘list_node_prev_node’ declared but never defined [-Werror]
 inline list_node_t *list_node_prev_node(list_node_t *node);
                     ^
list_util.h:66:14: error: inline function ‘list_node_prev’ declared but never defined [-Werror]
 inline void        *list_node_prev(list_node_t *node);
              ^
list_util.h:64:21: error: inline function ‘list_node_next_node’ declared but never defined [-Werror]
 inline list_node_t *list_node_next_node(list_node_t *node);
                     ^
list_util.h:63:14: error: inline function ‘list_node_next’ declared but never defined [-Werror]
 inline void        *list_node_next(list_node_t *node);
              ^
lis...

Xu Wang authored May 26, 2014 and John Ferlan committed Jun 16, 2014

Add API support for dumpCore field of Memory devices and fix issue in
parse_mem_device() when parsing dumpCore field.
Signed-off-by: Xu Wang <gesaint@linux.vnet.ibm.com>

Xu Wang authored May 27, 2014 and John Ferlan committed Jun 11, 2014

Besides 'disk', 'cdrom', 'floppy' and 'filesystem', there is one
more value 'lun' should be supported by value of device field in
the disk device. So this patch adds it into libvirt-cim. Now device
like <disk type='block' device='lun'> could be operated by class.
Signed-off-by: Xu Wang <gesaint@linux.vnet.ibm.com>

Pavel Hrdina authored May 07, 2014 and John Ferlan committed May 07, 2014

Function controller_protocol_type_IDToStr() returns a const char
and we should abide that.
Signed-off-by: Pavel Hrdina <phrdina@redhat.com>

Add the code and make adjustments to have ControllerPool support

Add the new MOF and modify the build/install to handle.

Xu Wang authored Apr 04, 2014 and John Ferlan committed Apr 04, 2014

Add the various associations to make the KVM_Controller work

Xu Wang authored Mar 25, 2014 and John Ferlan committed Mar 27, 2014

Signed-off-by: Xu Wang <gesaint@linux.vnet.ibm.com>

Xu Wang authored Mar 27, 2014 and John Ferlan committed Mar 27, 2014

Set basic fields for the KVM_Controller instance based on the read XML
from the virtual controller device structure.

Set the various KVM_ControllerRASD fields based on the read XML from
the virtual controller device structure

Xu Wang authored Mar 27, 2014 and John Ferlan committed Mar 27, 2014

Add the mofs and registration to support the Controller Logical Device
and RASD.  The Contoller Logical Device will be a child of the
CIM_Controller class and the Controller RASD will be a child of
the CIM_RASD.

Install the mofs and definitions, but don't yet link things up

Xu Wang authored Mar 17, 2014 and John Ferlan committed Mar 26, 2014

Parse and store the <controller> XML tags.  The generated DeviceID will
be a combination of "controller" + XML device "name" + XML Index "value".
This should be unique enough now and generates "controller:pci:0" or
"controller:usb:0" DeviceID's.

In the future, if support is added for the "<master>" XML child a new
mechanism will need to be put in place since one of those controllers is
designed to have the same name and index - what changes is the function
for the device.
Signed-off-by: John Ferlan <jferlan@redhat.com>

Xu Wang authored Mar 18, 2014 and John Ferlan committed Mar 26, 2014

Add data and strutures for a virtual controller device
Signed-off-by: John Ferlan <jferlan@redhat.com>