[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RFC PATCH] gitlab: add a binary build to project registry

From: Alex Bennée
Subject: Re: [RFC PATCH] gitlab: add a binary build to project registry
Date: Wed, 22 Jun 2022 15:43:54 +0100
User-agent: mu4e 1.7.27; emacs 28.1.50

Peter Maydell <peter.maydell@linaro.org> writes:

> On Wed, 22 Jun 2022 at 13:33, Alex Bennée <alex.bennee@linaro.org> wrote:
>> There have been requests from other projects such LKFT to have
>> "official" docker images with pre-built QEMU binaries. These could
>> then be consumed by downstream CI systems by pulling directly from the
>> qemu-project container registry. The final image could then be run by
>> doing:
>>   docker run --rm -it \
>>     registry.gitlab.com/qemu-project/qemu/qemu/debian-amd64-binaries \
>>     /opt/bin/qemu-system-aarch64 $ARGS
>> To keep the build time down we skip user-mode, documents, plugins and
>> a selection of the more esoteric hardware emulations. Even so it still
>> takes over an hour to build and install everything.
>> This is very much an RFC for now as we have traditionally not provided
>> binaries for our users except for the slightly special case of
>> Windows. As currently structured this will rebuild the binaries on
>> every merge but we could change the generation rules to only trigger
>> for tagged or stable branch pushes. We also wouldn't be testing these
>> binaries so we are basically assuming they are OK by the nature of
>> being built from master which in theory never breaks.
> I'm a bit uncertain about providing "official" docker images
> or other pre-built binaries, because it might give the impression
> that these are OK to use with KVM, when in fact they won't necessarily
> get security fixes in a timely manner, and almost all users of QEMU for
> KVM purposes are better off with the distro QEMU.

Do we have any sort of idea how long it takes from a CVE being fixed in
a distro kernel to the eventual merge of a patch in master?

Anyway the main use case for this is emulation where we want to get new
features under -cpu max into the CI loops as soon as possible. I think
the LKFT guys are testing KVM as well though and again want to see new
KVM features as soon as possible.

I'm not proposing these images are uploaded to docker.io so less likely
to be hit by the default:

  docker run qemu:latest

(they instead get 6 year old things packages by someone calling
themselves qemu: https://hub.docker.com/u/qemu)

> thanks
> -- PMM

Alex Bennée

reply via email to

[Prev in Thread] Current Thread [Next in Thread]