Skip to content
Snippets Groups Projects
  1. Jan 14, 2022
  2. Jan 12, 2022
  3. Jan 08, 2022
  4. Jan 05, 2022
  5. Dec 21, 2021
  6. Dec 18, 2021
  7. Dec 17, 2021
  8. Dec 15, 2021
  9. Dec 10, 2021
  10. Nov 22, 2021
  11. Nov 19, 2021
  12. Nov 17, 2021
  13. Nov 16, 2021
    • Cleber Rosa's avatar
      Jobs based on custom runners: add CentOS Stream 8 · d7c2e2b3
      Cleber Rosa authored
      
      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: default avatarCleber Rosa <crosa@redhat.com>
      Signed-off-by: default avatarAlex Bennée <alex.bennee@linaro.org>
      Reviewed-by: default avatarWillian Rampazzo <willianr@redhat.com>
      Tested-by: default avatarWillian Rampazzo <willianr@redhat.com>
      Message-Id: <20211111160501.862396-2-crosa@redhat.com>
      Message-Id: <20211115142915.3797652-6-alex.bennee@linaro.org>
      d7c2e2b3
    • Kevin Wolf's avatar
      docs: Deprecate incorrectly typed device_add arguments · 4d8b0f0a
      Kevin Wolf authored
      
      While introducing a non-QemuOpts code path for device creation for JSON
      -device, we noticed that QMP device_add doesn't check its input
      correctly (accepting arguments that should have been rejected), and that
      users may be relying on this behaviour (libvirt did until it was fixed
      recently).
      
      Let's use a deprecation period before we fix this bug in QEMU to avoid
      nasty surprises for users.
      
      Signed-off-by: default avatarKevin Wolf <kwolf@redhat.com>
      Message-Id: <20211111143530.18985-1-kwolf@redhat.com>
      Reviewed-by: default avatarMarkus Armbruster <armbru@redhat.com>
      Reviewed-by: default avatarDaniel P. Berrangé <berrange@redhat.com>
      Signed-off-by: default avatarKevin Wolf <kwolf@redhat.com>
      Message-Id: <20211115145409.176785-12-kwolf@redhat.com>
      Signed-off-by: default avatarHanna Reitz <hreitz@redhat.com>
      4d8b0f0a
  14. Nov 11, 2021
  15. Nov 10, 2021
Loading