<feed xmlns='http://www.w3.org/2005/Atom'>
<title>qemu/scripts/ci, branch or1k</title>
<subtitle>QEMU development tree</subtitle>
<id>https://git.zx2c4.com/qemu/atom/scripts/ci?h=or1k</id>
<link rel='self' href='https://git.zx2c4.com/qemu/atom/scripts/ci?h=or1k'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/qemu/'/>
<updated>2022-05-07T05:46:58Z</updated>
<entry>
<title>build: move vhost-scsi configuration to Kconfig</title>
<updated>2022-05-07T05:46:58Z</updated>
<author>
<name>Paolo Bonzini</name>
<email>pbonzini@redhat.com</email>
</author>
<published>2022-04-20T15:34:03Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/qemu/commit/?id=d13b200253cbd9cb933a1cfead9106abd564ae4a'/>
<id>urn:sha1:d13b200253cbd9cb933a1cfead9106abd564ae4a</id>
<content type='text'>
vhost-scsi and vhost-user-scsi are two devices of their own; it should
be possible to enable/disable them with --without-default-devices, not
--without-default-features.  Compute their default value in Kconfig to
obtain the more intuitive behavior.

Reviewed-by: Marc-André Lureau &lt;marcandre.lureau@redhat.com&gt;
Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;
</content>
</entry>
<entry>
<title>build: move vhost-vsock configuration to Kconfig</title>
<updated>2022-05-07T05:46:58Z</updated>
<author>
<name>Paolo Bonzini</name>
<email>pbonzini@redhat.com</email>
</author>
<published>2022-04-20T15:34:02Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/qemu/commit/?id=9972ae314fc38b7e47ee7ccdbc8556b7cad8a930'/>
<id>urn:sha1:9972ae314fc38b7e47ee7ccdbc8556b7cad8a930</id>
<content type='text'>
vhost-vsock and vhost-user-vsock are two devices of their own; it should
be possible to enable/disable them with --without-default-devices, not
--without-default-features.  Compute their default value in Kconfig to
obtain the more intuitive behavior.

Reviewed-by: Marc-André Lureau &lt;marcandre.lureau@redhat.com&gt;
Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;
</content>
</entry>
<entry>
<title>Replacing CONFIG_VNC_PNG with CONFIG_PNG</title>
<updated>2022-04-27T05:50:28Z</updated>
<author>
<name>Kshitij Suri</name>
<email>kshitij.suri@nutanix.com</email>
</author>
<published>2022-04-08T07:13:34Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/qemu/commit/?id=95f8510ef428f988897176b9585b8ba1432f939f'/>
<id>urn:sha1:95f8510ef428f988897176b9585b8ba1432f939f</id>
<content type='text'>
Libpng is only detected if VNC is enabled currently. This patch adds a
generalised png option in the meson build which is aimed to replace use of
CONFIG_VNC_PNG with CONFIG_PNG.

Signed-off-by: Kshitij Suri &lt;kshitij.suri@nutanix.com&gt;

Reviewed-by: Daniel P. Berrangé &lt;berrange@redhat.com&gt;
Message-Id: &lt;20220408071336.99839-2-kshitij.suri@nutanix.com&gt;

[ kraxel: add meson-buildoptions.sh updates ]
[ kraxel: fix centos8 testcase ]
[ kraxel: update --enable-vnc-png too ]

Signed-off-by: Gerd Hoffmann &lt;kraxel@redhat.com&gt;

--enable-vnc-png fixup

Signed-off-by: Gerd Hoffmann &lt;kraxel@redhat.com&gt;
</content>
</entry>
<entry>
<title>scripts/ci: allow for a secondary runner</title>
<updated>2022-02-28T16:42:12Z</updated>
<author>
<name>Alex Bennée</name>
<email>alex.bennee@linaro.org</email>
</author>
<published>2022-02-25T17:20:11Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/qemu/commit/?id=9c3b52245570a17b876d7eecbf7714cc5959ed0f'/>
<id>urn:sha1:9c3b52245570a17b876d7eecbf7714cc5959ed0f</id>
<content type='text'>
Some HW can run multiple architecture profiles so we can install a
secondary runner to build and run tests for those profiles. This
allows setting up secondary service.

Signed-off-by: Alex Bennée &lt;alex.bennee@linaro.org&gt;
Acked-by: Richard Henderson &lt;richard.henderson@linaro.org&gt;
Message-Id: &lt;20220225172021.3493923-9-alex.bennee@linaro.org&gt;
</content>
</entry>
<entry>
<title>scripts/ci: add build env rules for aarch32 on aarch64</title>
<updated>2022-02-28T16:42:07Z</updated>
<author>
<name>Alex Bennée</name>
<email>alex.bennee@linaro.org</email>
</author>
<published>2022-02-25T17:20:10Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/qemu/commit/?id=93c9aeede659a5675fa0eee5991521434c2b198a'/>
<id>urn:sha1:93c9aeede659a5675fa0eee5991521434c2b198a</id>
<content type='text'>
At least the current crop of Aarch64 HW can support running 32 bit EL0
code. Before we can build and test we need a minimal set of packages
installed. We can't use "apt build-dep" because it currently gets
confused trying to keep two sets of build-deps installed at once.
Instead we install a minimal set of libraries that will allow us to
continue.

Signed-off-by: Alex Bennée &lt;alex.bennee@linaro.org&gt;
Reviewed-by: Richard Henderson &lt;richard.henderson@linaro.org&gt;
Message-Id: &lt;20220225172021.3493923-8-alex.bennee@linaro.org&gt;
</content>
</entry>
<entry>
<title>drop libxml2 checks since libxml is not actually used (for parallels)</title>
<updated>2022-02-09T12:08:42Z</updated>
<author>
<name>Michael Tokarev</name>
<email>mjt@tls.msk.ru</email>
</author>
<published>2022-02-04T20:43:17Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/qemu/commit/?id=9e8be4c546ce8469ca9702715bf8f198d604b685'/>
<id>urn:sha1:9e8be4c546ce8469ca9702715bf8f198d604b685</id>
<content type='text'>
For a long time, we assumed that libxml2 is necessary for parallels
block format support (block/parallels*). However, this format actually
does not use libxml [*]. Since this is the only user of libxml2 in
whole QEMU tree, we can drop all libxml2 checks and dependencies too.

It is even more: --enable-parallels configure option was the only
option which was silently ignored when it's (fake) dependency
(libxml2) isn't installed.

Drop all mentions of libxml2.

[*] Actually the basis for libxml use were introduced in commit
    ed279a06c53 ("configure: add dependency") but the implementation
    was never merged:
    https://lore.kernel.org/qemu-devel/70227bbd-a517-70e9-714f-e6e0ec431be9@openvz.org/

Signed-off-by: Michael Tokarev &lt;mjt@tls.msk.ru&gt;
Reviewed-by: Stefan Hajnoczi &lt;stefanha@redhat.com&gt;
Message-Id: &lt;20220119090423.149315-1-mjt@msgid.tls.msk.ru&gt;
Tested-by: Philippe Mathieu-Daudé &lt;f4bug@amsat.org&gt;
Reviewed-by: Philippe Mathieu-Daudé &lt;f4bug@amsat.org&gt;
[PMD: Updated description and adapted to use lcitool]
Reviewed-by: Thomas Huth &lt;thuth@redhat.com&gt;
Signed-off-by: Philippe Mathieu-Daudé &lt;f4bug@amsat.org&gt;
Signed-off-by: Alex Bennée &lt;alex.bennee@linaro.org&gt;
Message-Id: &lt;20220121154134.315047-5-f4bug@amsat.org&gt;
Reviewed-by: Vladimir Sementsov-Ogievskiy &lt;vsementsov@virtuozzo.com&gt;
Message-Id: &lt;20220204204335.1689602-9-alex.bennee@linaro.org&gt;
</content>
</entry>
<entry>
<title>block/file-posix: Simplify the XFS_IOC_DIOINFO handling</title>
<updated>2022-01-12T13:09:04Z</updated>
<author>
<name>Thomas Huth</name>
<email>thuth@redhat.com</email>
</author>
<published>2021-12-15T12:58:24Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/qemu/commit/?id=a5730b8bd3675f484ed0eacea052452048eeb35d'/>
<id>urn:sha1:a5730b8bd3675f484ed0eacea052452048eeb35d</id>
<content type='text'>
The handling for the XFS_IOC_DIOINFO ioctl is currently quite excessive:
This is not a "real" feature like the other features that we provide with
the "--enable-xxx" and "--disable-xxx" switches for the configure script,
since this does not influence lots of code (it's only about one call to
xfsctl() in file-posix.c), so people don't gain much with the ability to
disable this with "--disable-xfsctl".
It's also unfortunate that the ioctl will be disabled on Linux in case
the user did not install the right xfsprogs-devel package before running
configure. Thus let's simplify this by providing the ioctl definition
on our own, so we can completely get rid of the header dependency and
thus the related code in the configure script.

Suggested-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;
Signed-off-by: Thomas Huth &lt;thuth@redhat.com&gt;
Message-Id: &lt;20211215125824.250091-1-thuth@redhat.com&gt;
Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;
</content>
</entry>
<entry>
<title>Jobs based on custom runners: add CentOS Stream 8</title>
<updated>2021-11-16T16:19:53Z</updated>
<author>
<name>Cleber Rosa</name>
<email>crosa@redhat.com</email>
</author>
<published>2021-11-15T14:29:14Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/qemu/commit/?id=d7c2e2b3f447133175be5817663147d1309bde2d'/>
<id>urn:sha1:d7c2e2b3f447133175be5817663147d1309bde2d</id>
<content type='text'>
This introduces three different parts of a job designed to run
on a custom runner managed by Red Hat.  The goals include:

  a) propose a model for other organizations that want to onboard
     their own runners, with their specific platforms, build
     configuration and tests.

  b) bring awareness to the differences between upstream QEMU and the
     version available under CentOS Stream, which is "A preview of
     upcoming Red Hat Enterprise Linux minor and major releases".

  c) because of b), it should be easier to identify and reduce the gap
     between Red Hat's downstream and upstream QEMU.

The components of this custom job are:

  I) OS build environment setup code:

     - additions to the existing "build-environment.yml" playbook
       that can be used to set up CentOS/EL 8 systems.

     - a CentOS Stream 8 specific "build-environment.yml" playbook
       that adds to the generic one.

 II) QEMU build configuration: a script that will produce binaries with
     features as similar as possible to the ones built and packaged on
     CentOS stream 8.

III) Scripts that define the minimum amount of testing that the
     binaries built with the given configuration (point II) under the
     given OS build environment (point I) should be subjected to.

 IV) Job definition: GitLab CI jobs that will dispatch the build/test
     jobs (see points #II and #III) to the machine specifically
     configured according to #I.

Signed-off-by: Cleber Rosa &lt;crosa@redhat.com&gt;
Signed-off-by: Alex Bennée &lt;alex.bennee@linaro.org&gt;
Reviewed-by: Willian Rampazzo &lt;willianr@redhat.com&gt;
Tested-by: Willian Rampazzo &lt;willianr@redhat.com&gt;
Message-Id: &lt;20211111160501.862396-2-crosa@redhat.com&gt;
Message-Id: &lt;20211115142915.3797652-6-alex.bennee@linaro.org&gt;
</content>
</entry>
<entry>
<title>Jobs based on custom runners: docs and gitlab-runner setup playbook</title>
<updated>2021-07-14T13:31:48Z</updated>
<author>
<name>Cleber Rosa</name>
<email>crosa@redhat.com</email>
</author>
<published>2021-07-09T14:29:28Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/qemu/commit/?id=40de78c284b14a54fbdde78d588ddb6d766f2a5f'/>
<id>urn:sha1:40de78c284b14a54fbdde78d588ddb6d766f2a5f</id>
<content type='text'>
To have the jobs dispatched to custom runners, gitlab-runner must
be installed, active as a service and properly configured.  The
variables file and playbook introduced here should help with those
steps.

The playbook introduced here covers the Linux distributions and
has been primarily tested on OS/machines that the QEMU project
has available to act as runners, namely:

 * Ubuntu 20.04 on aarch64
 * Ubuntu 18.04 on s390x

But, it should work on all other Linux distributions.  Earlier
versions were tested on FreeBSD too, so chances of success are
high.

Signed-off-by: Cleber Rosa &lt;crosa@redhat.com&gt;
Signed-off-by: Alex Bennée &lt;alex.bennee@linaro.org&gt;
Tested-by: Willian Rampazzo &lt;willianr@redhat.com&gt;
Tested-by: Alex Bennée &lt;alex.bennee@linaro.org&gt;
Reviewed-by: Willian Rampazzo &lt;willianr@redhat.com&gt;
Reviewed-by: Wainer dos Santos Moschetta &lt;wainersm@redhat.com&gt;
Reviewed-by: Alex Bennée &lt;alex.bennee@linaro.org&gt;
Message-Id: &lt;20210630012619.115262-4-crosa@redhat.com&gt;
Message-Id: &lt;20210709143005.1554-4-alex.bennee@linaro.org&gt;
</content>
</entry>
<entry>
<title>Jobs based on custom runners: build environment docs and playbook</title>
<updated>2021-07-14T13:31:48Z</updated>
<author>
<name>Cleber Rosa</name>
<email>crosa@redhat.com</email>
</author>
<published>2021-07-09T14:29:27Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/qemu/commit/?id=159c5d177bf6f0caf1efb85b850b200ac7043c49'/>
<id>urn:sha1:159c5d177bf6f0caf1efb85b850b200ac7043c49</id>
<content type='text'>
To run basic jobs on custom runners, the environment needs to be
properly set up.  The most common requirement is having the right
packages installed.

The playbook introduced here covers the QEMU's project s390x and
aarch64 machines.  At the time this is being proposed, those machines
have already had this playbook applied to them.

Signed-off-by: Cleber Rosa &lt;crosa@redhat.com&gt;
Signed-off-by: Alex Bennée &lt;alex.bennee@linaro.org&gt;
Tested-by: Alex Bennée &lt;alex.bennee@linaro.org&gt;
Tested-by: Willian Rampazzo &lt;willianr@redhat.com&gt;
Reviewed-by: Wainer dos Santos Moschetta &lt;wainersm@redhat.com&gt;
Reviewed-by: Willian Rampazzo &lt;willianr@redhat.com&gt;
Reviewed-by: Alex Bennée &lt;alex.bennee@linaro.org&gt;
Message-Id: &lt;20210630012619.115262-3-crosa@redhat.com&gt;
Message-Id: &lt;20210709143005.1554-3-alex.bennee@linaro.org&gt;
</content>
</entry>
</feed>
