Re: [PATCH 0/6] qemu: Allow control of deprecation behaviour

On Thu, Apr 01, 2021 at 00:36:52 +0200, Martin Kletzander wrote: > On Fri, Mar 19, 2021 at 07:33:48PM +0100, Peter Krempa wrote: > > For debugging purposes it's very useful to disable all deprecated > > commands and fields in qemu. This series implements a qemu.conf knob and > > a qemu namespace element to control this. > > > > The implementation tries to be very conservative to allow downgrades of > > qemu and such without breaking the startup of the VM. > > > > The intention is that developers and CI deployments use the 'crash' > > option to catch any unexpected qemu disappearance. > > > > Note that this applies on top of my series for -object QAPIfication. > > > > Based on Markus' -compat series which was now merged to upstream qemu. > > > > Peter Krempa (6): > > docs/drvqemu: Convert to RST > > I wanted to review the output of this first patch side-by-side so that I > do not have to go through all the markup hell. But when I tried looking > for the artefacts from any possible pipeline this could have run through > I was greeted with a "get off my lawn" message. So if you are okay with > me just skimming through the first patch (after reviewing the rest of da > patch series), then with the mentioned fixes, this is for you (xkcd#276) Oops!, despite criticising the same thing last time [1] I actually didn't (forgot to?) push the branch to gitlab so that artifacts would be present. https://pipo.sk.gitlab.io/-/libvirt/-/jobs/1145757051/artifacts/website/d...

[1] https://listman.redhat.com/archives/libvir-list/2021-March/msg00602.html