Plans for the next release

2022-02-15 Thread Jiri Denemark
We are getting close to the next release of libvirt. To aim for the release on Mar 01 I suggest entering the freeze on Wednesday Feb 23 and tagging RC2 on Friday Feb 25. I hope this works for everyone. Jirka

[PATCH v5 8/9] virsh: Add mode option to domdirtyrate-calc virsh api

2022-02-15 Thread huangy81
From: Hyman Huang(黄勇) Extend domdirtyrate-calc virsh api with mode option, either of these three options "page-sampling,dirty-bitmap,dirty-ring" can be specified when calculating dirty page rate. Signed-off-by: Hyman Huang(黄勇) --- docs/manpages/virsh.rst| 7 +--

[PATCH v5 2/9] qemu_capabilities: Introduce QEMU_CAPS_CALC_DIRTY_RATE capability

2022-02-15 Thread huangy81
From: Hyman Huang(黄勇) calc-dirty-rate command was introduced since qemu >=5.2.0. Introduce QEMU_CAPS_CALC_DIRTY_RATE capability definition. Signed-off-by: Hyman Huang(黄勇) --- src/qemu/qemu_capabilities.c | 2 ++ src/qemu/qemu_capabilities.h | 1 +

[PATCH v5 7/9] qemu_driver: Extend flags parameter of virDomainStartDirtyRateCalc

2022-02-15 Thread huangy81
From: Hyman Huang(黄勇) Extend flags parameter of virDomainStartDirtyRateCalc as a superset of virDomainDirtyRateCalcFlags, parse the flags and handle it correspondingly in qemuDomainStartDirtyRateCalc. Signed-off-by: Hyman Huang(黄勇) --- src/qemu/qemu_driver.c | 23 ++- 1

[PATCH v5 4/9] qemu_capabilities: Introduce QEMU_CAPS_DIRTYRATE_MODE capability

2022-02-15 Thread huangy81
From: Hyman Huang(黄勇) mode option of calc-dirty-rate command since qemu >=6.2.0. Introduce QEMU_CAPS_DIRTYRATE_MODE capability definition. Signed-off-by: Hyman Huang(黄勇) --- src/qemu/qemu_capabilities.c | 2 ++ src/qemu/qemu_capabilities.h | 1 +

[PATCH v5 9/9] qemu_driver: Add calc_mode for dirtyrate statistics

2022-02-15 Thread huangy81
From: Hyman Huang(黄勇) Add calc_mode for dirtyrate statistics retured by virsh domstats --dirtyrate api, also add vcpu dirtyrate if dirty-ring mode was used in last measurement. Signed-off-by: Hyman Huang(黄勇) --- src/libvirt-domain.c | 6 + src/qemu/qemu_driver.c | 22

[PATCH v5 3/9] qemu_driver: Probe capability before calculating dirty page rate

2022-02-15 Thread huangy81
From: Hyman Huang(黄勇) Probing QEMU_CAPS_CALC_DIRTY_RATE capability in advance in case of failure when calculating dirty page rate. Signed-off-by: Hyman Huang(黄勇) --- src/qemu/qemu_driver.c | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/src/qemu/qemu_driver.c

[PATCH v5 6/9] qemu_driver: Add mode parameter to qemuDomainStartDirtyRateCalc

2022-02-15 Thread huangy81
From: Hyman Huang(黄勇) Add mode parameter to qemuDomainStartDirtyRateCalc API, 'mode' option of 'calc-dirty-rate' command was introduced since qemu >= 6.2. Signed-off-by: Hyman Huang(黄勇) --- src/qemu/qemu_driver.c | 3 ++- src/qemu/qemu_monitor.c | 5 +++-- src/qemu/qemu_monitor.h

[PATCH v5 1/9] qemu: Refactor dirty page rate calculation status implementation

2022-02-15 Thread huangy81
From: Hyman Huang(黄勇) For any virTypedParameter API normal practice is to use a string to expose the data, not the rather enum integer value. So let's drop the virDomainDirtyRateStatus in public header file and introduce internal enum def qemuMonitorDirtyRateStatus to describe the dirty page

[PATCH v5 0/9] support mode option for dirtyrate calculation

2022-02-15 Thread huangy81
From: Hyman Huang(黄勇) v5: - [PATCH v5 9/9]: Fix alignment error in qemuDomainGetStatsDirtyRate. v4: - Rebase the master - [PATCH v4 1/9]: Refactor dirty page rate calculation status implementation, display calc_status as string when 'virsh domstats

[PATCH v5 5/9] include: Introduce virDomainDirtyRateCalcFlags

2022-02-15 Thread huangy81
From: Hyman Huang(黄勇) Introduce virDomainDirtyRateCalcFlags to get ready for adding mode parameter to qemuDomainStartDirtyRateCalc. Signed-off-by: Hyman Huang(黄勇) --- include/libvirt/libvirt-domain.h | 13 + 1 file changed, 13 insertions(+) diff --git

[PATCH v4 7/9] qemu_driver: Extend flags parameter of virDomainStartDirtyRateCalc

2022-02-15 Thread huangy81
From: Hyman Huang(黄勇) Extend flags parameter of virDomainStartDirtyRateCalc as a superset of virDomainDirtyRateCalcFlags, parse the flags and handle it correspondingly in qemuDomainStartDirtyRateCalc. Signed-off-by: Hyman Huang(黄勇) --- src/qemu/qemu_driver.c | 23 ++- 1

[PATCH v4 3/9] qemu_driver: Probe capability before calculating dirty page rate

2022-02-15 Thread huangy81
From: Hyman Huang(黄勇) Probing QEMU_CAPS_CALC_DIRTY_RATE capability in advance in case of failure when calculating dirty page rate. Signed-off-by: Hyman Huang(黄勇) --- src/qemu/qemu_driver.c | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/src/qemu/qemu_driver.c

[PATCH v4 4/9] qemu_capabilities: Introduce QEMU_CAPS_DIRTYRATE_MODE capability

2022-02-15 Thread huangy81
From: Hyman Huang(黄勇) mode option of calc-dirty-rate command since qemu >=6.2.0. Introduce QEMU_CAPS_DIRTYRATE_MODE capability definition. Signed-off-by: Hyman Huang(黄勇) --- src/qemu/qemu_capabilities.c | 2 ++ src/qemu/qemu_capabilities.h | 1 +

[PATCH v4 5/9] include: Introduce virDomainDirtyRateCalcFlags

2022-02-15 Thread huangy81
From: Hyman Huang(黄勇) Introduce virDomainDirtyRateCalcFlags to get ready for adding mode parameter to qemuDomainStartDirtyRateCalc. Signed-off-by: Hyman Huang(黄勇) --- include/libvirt/libvirt-domain.h | 13 + 1 file changed, 13 insertions(+) diff --git

[PATCH v4 1/9] qemu: Refactor dirty page rate calculation status implementation

2022-02-15 Thread huangy81
From: Hyman Huang(黄勇) For any virTypedParameter API normal practice is to use a string to expose the data, not the rather enum integer value. So let's drop the virDomainDirtyRateStatus in public header file and introduce internal enum def qemuMonitorDirtyRateStatus to describe the dirty page

[PATCH v4 9/9] qemu_driver: Add calc_mode for dirtyrate statistics

2022-02-15 Thread huangy81
From: Hyman Huang(黄勇) Add calc_mode for dirtyrate statistics retured by virsh domstats --dirtyrate api, also add vcpu dirtyrate if dirty-ring mode was used in last measurement. Signed-off-by: Hyman Huang(黄勇) --- src/libvirt-domain.c | 6 + src/qemu/qemu_driver.c | 22

[PATCH v4 8/9] virsh: Add mode option to domdirtyrate-calc virsh api

2022-02-15 Thread huangy81
From: Hyman Huang(黄勇) Extend domdirtyrate-calc virsh api with mode option, either of these three options "page-sampling,dirty-bitmap,dirty-ring" can be specified when calculating dirty page rate. Signed-off-by: Hyman Huang(黄勇) --- docs/manpages/virsh.rst| 7 +--

[PATCH v4 0/9] support mode option for dirtyrate calculation

2022-02-15 Thread huangy81
From: Hyman Huang(黄勇) v4: - Rebase the master - [PATCH v4 1/9]: Refactor dirty page rate calculation status implementation, display calc_status as string when 'virsh domstats --dirtyrate' api return. - [PATCH v4 3/9]: Adjust the 'cap check' block before

[PATCH v4 6/9] qemu_driver: Add mode parameter to qemuDomainStartDirtyRateCalc

2022-02-15 Thread huangy81
From: Hyman Huang(黄勇) Add mode parameter to qemuDomainStartDirtyRateCalc API, 'mode' option of 'calc-dirty-rate' command was introduced since qemu >= 6.2. Signed-off-by: Hyman Huang(黄勇) --- src/qemu/qemu_driver.c | 3 ++- src/qemu/qemu_monitor.c | 5 +++-- src/qemu/qemu_monitor.h

[PATCH v4 2/9] qemu_capabilities: Introduce QEMU_CAPS_CALC_DIRTY_RATE capability

2022-02-15 Thread huangy81
From: Hyman Huang(黄勇) calc-dirty-rate command was introduced since qemu >=5.2.0. Introduce QEMU_CAPS_CALC_DIRTY_RATE capability definition. Signed-off-by: Hyman Huang(黄勇) --- src/qemu/qemu_capabilities.c | 2 ++ src/qemu/qemu_capabilities.h | 1 +

Re: [PULL 0/3] Block patches

2022-02-15 Thread Peter Maydell
On Mon, 14 Feb 2022 at 17:44, Stefan Hajnoczi wrote: > > The following changes since commit cc5ce8b8b6be83e5fe3b668dbd061ad97c534e3f: > > Merge remote-tracking branch 'remotes/legoater/tags/pull-ppc-20220210' into > staging (2022-02-13 20:33:28 +) > > are available in the Git repository

[libvirt PATCH 05/10] tests: don't permit NVRAM path when using firmware auto-select

2022-02-15 Thread Daniel P . Berrangé
When using we still parse the path, but completely ignore it, replacing any user provided content with a custom generated path. This makes sense since when undefining the guest, the code to cleanup NVRAM also uses the same generated path. Instead of silently ignoring user config, we should

[libvirt PATCH 03/10] tests: add test case for NVRAM with template

2022-02-15 Thread Daniel P . Berrangé
This demonstrates that /usr/share/OVMF/OVMF_CODE.fd gets expanded to give a per-VM NVRAM path. Signed-off-by: Daniel P. Berrangé --- .../bios-nvram-template.x86_64-latest.args| 37 +++ .../qemuxml2argvdata/bios-nvram-template.xml | 21 +++

[libvirt PATCH 00/10] Cleanup and test more firmware handling scenarios

2022-02-15 Thread Daniel P . Berrangé
There are a mind bending number of possible ways to configure the firmware with/without NVRAM. Only a small portion are tested and many error scenarios are silently ignored. This series attempts to get coverage of every possible XML config scenario and report explicit errors in all invalid

[libvirt PATCH 09/10] conf: move nvram parsing into virDomainLoaderDefParseXML

2022-02-15 Thread Daniel P . Berrangé
The virDomainLoaderDef struct contains fields for both and elements, so it makes sense to parse them in the same method, just like we'll format them in the same method. Signed-off-by: Daniel P. Berrangé --- src/conf/domain_conf.c | 92 ++ 1 file

[libvirt PATCH 08/10] conf: switch nvram parsing to use XML node / property helpers

2022-02-15 Thread Daniel P . Berrangé
Instead of using XPath, parse the using the XML node and property helpers so the code is consistent with the parsing of . Signed-off-by: Daniel P. Berrangé --- src/conf/domain_conf.c | 17 + 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/src/conf/domain_conf.c

[libvirt PATCH 06/10] qemu: inline code for filling in per-VM NVRAM path

2022-02-15 Thread Daniel P . Berrangé
Before creating a NVRAM path, the qemuDomainNVRAMPathGenerate method checks whether the config is using the old style firmware approach. This check is redundant in one of the two callers. By inlining the check into the other caller, it makes it clearer to understand that the NVRAM path filling is

[libvirt PATCH 04/10] conf: validate NVRAM template usage with R/W loader binary

2022-02-15 Thread Daniel P . Berrangé
The QEMU driver will populate the template to the nvram file any time it sees both the template and nvram paths present. It will auto-generate a nvram path per-VM if not provided by the user, but only if the loader is marked R/O. So with a R/O loader we have these possible scenarios - No NVRAM

[libvirt PATCH 10/10] conf: stop ignoring / with firmware auto-select

2022-02-15 Thread Daniel P . Berrangé
Currently if the firmware attribute is set then we silently ignore most of the and element configs. This changes the code so that we always fully parse the and but then use a post-parse method to explicitly reject invalid combinations. Signed-off-by: Daniel P. Berrangé ---

[libvirt PATCH 07/10] conf: rename struct field for NVRAM template

2022-02-15 Thread Daniel P . Berrangé
This is to make it explicit that the template only applies to the NVRAM store, not the main loader binary, even if the loader is writable. Signed-off-by: Daniel P. Berrangé --- src/conf/domain_conf.c | 10 +- src/conf/domain_conf.h | 2 +- src/qemu/qemu_firmware.c | 8

[libvirt PATCH 02/10] tests: add explicit test case for pflash loader lacking path

2022-02-15 Thread Daniel P . Berrangé
The following is expected to raise an error: because no path to the pflash loader is given and there is no default built-in. Signed-off-by: Daniel P. Berrangé --- tests/qemuxml2argvdata/bios-nvram-no-path.err | 1 + tests/qemuxml2argvdata/bios-nvram-no-path.xml | 19

[libvirt PATCH 01/10] qemu: fix bad indentation for qemuDomainNVRAMPathFormat

2022-02-15 Thread Daniel P . Berrangé
Signed-off-by: Daniel P. Berrangé --- src/qemu/qemu_domain.c | 4 ++-- src/qemu/qemu_domain.h | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/src/qemu/qemu_domain.c b/src/qemu/qemu_domain.c index c764f6296c..4e9c845f68 100644 --- a/src/qemu/qemu_domain.c +++

Re: [libvirt PATCH v2 1/1] meson: Check for os-release's ID_LIKE in addition to ID

2022-02-15 Thread Andrea Bolognani
On Thu, Jan 27, 2022 at 12:00:18PM +0100, Andrea Bolognani wrote: > This makes it possible to reduce the number of cases we have to > consider, because 'sles' declares itself to be like 'suse' and > both 'rhel' and 'centos' declare themselves to be like 'fedora'. > > We have to move the check for

Re: [PATCH] openrc: Make init scripts executable on install

2022-02-15 Thread Andrea Bolognani
On Tue, Feb 15, 2022 at 05:26:51PM +0100, Michal Privoznik wrote: > When installing openrc init scripts, we take whatever mode the > generated files are in an copy them under /etc/init.d/. This is > not ideal, because those files are not executable and they should > be. > > Resolves:

Re: [PATCH] openrc: Make init scripts executable on install

2022-02-15 Thread Ani Sinha
On Tue, Feb 15, 2022 at 21:57 Michal Privoznik wrote: > When installing openrc init scripts, we take whatever mode the > generated files are in an copy them under /etc/init.d/. This is > not ideal, because those files are not executable and they should > be. > > Resolves:

[PATCH] openrc: Make init scripts executable on install

2022-02-15 Thread Michal Privoznik
When installing openrc init scripts, we take whatever mode the generated files are in an copy them under /etc/init.d/. This is not ideal, because those files are not executable and they should be. Resolves: https://gitlab.com/libvirt/libvirt/-/issues/250 Signed-off-by: Michal Privoznik ---

Re: [PATCH] tests: Drop domcaps test data for qemu < 2.11

2022-02-15 Thread Peter Krempa
On Tue, Feb 15, 2022 at 16:19:51 +0100, Michal Privoznik wrote: > The minimal supported version of QEMU is 2.11. And after > capabilities for older QEMUs were dropped in > v7.3.0-17-g184de10c1d we have some domaincapsdata/ files that are > never read. This is because domaincapstest uses >

[PATCH] tests: Drop domcaps test data for qemu < 2.11

2022-02-15 Thread Michal Privoznik
The minimal supported version of QEMU is 2.11. And after capabilities for older QEMUs were dropped in v7.3.0-17-g184de10c1d we have some domaincapsdata/ files that are never read. This is because domaincapstest uses testQemuCapsIterate() which iterates over qemucapabilitiesdata/caps_*.xml files.

[libvirt PATCH v2] Make systemd unit ordering more robust

2022-02-15 Thread Martin Kletzander
Since libvirt-guests script/service can operate on various URIs and we do support both socket activation and traditional services, the ordering should be specified for all the possible sockets and services. Also remove the Wants= dependency since do not want to start any service. We cannot know

Re: [libvirt PATCH] Make systemd unit ordering more robust

2022-02-15 Thread Michal Prívozník
On 2/15/22 12:12, Martin Kletzander wrote: > Since libvirt-guests script/service can operate on various URIs and we do > support both socket activation and traditional services, the ordering should > be > specified for all the possible sockets and services. > > Also remove the Wants= dependency

[PATCH 17/17] qemu: capabilities: Retire QEMU_CAPS_STORAGE_WERROR and QEMU_CAPS_USB_STORAGE_WERROR

2022-02-15 Thread Peter Krempa
Signed-off-by: Peter Krempa --- src/qemu/qemu_capabilities.c | 12 ++-- src/qemu/qemu_capabilities.h | 4 ++-- tests/qemucapabilitiesdata/caps_3.1.0.ppc64.xml | 2 -- tests/qemucapabilitiesdata/caps_3.1.0.x86_64.xml | 2 --

[PATCH 15/17] qemu: capabilities: Retire QEMU_CAPS_OVERCOMMIT

2022-02-15 Thread Peter Krempa
Signed-off-by: Peter Krempa --- src/qemu/qemu_capabilities.c | 3 +-- src/qemu/qemu_capabilities.h | 2 +- tests/qemucapabilitiesdata/caps_3.1.0.ppc64.xml | 1 - tests/qemucapabilitiesdata/caps_3.1.0.x86_64.xml | 1 -

[PATCH 09/17] qemu: capabilities: Remove tautological version checks

2022-02-15 Thread Peter Krempa
Some version checks no longer make sense as the minimum supported qemu is now qemu-3.1. Signed-off-by: Peter Krempa --- src/qemu/qemu_capabilities.c | 10 +- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/src/qemu/qemu_capabilities.c b/src/qemu/qemu_capabilities.c index

[PATCH 06/17] tests: qemucapabilities: Remove qemu-2.12 test data

2022-02-15 Thread Peter Krempa
Upcoming patches will raise the minimum required qemu version to 3.1. Signed-off-by: Peter Krempa --- .../caps_2.12.0.aarch64.replies | 19577 - .../caps_2.12.0.aarch64.xml | 329 - .../caps_2.12.0.ppc64.replies | 23072

[PATCH 12/17] qemu: capabilities: Retire QEMU_CAPS_CHARDEV_FD_PASS_COMMANDLINE

2022-02-15 Thread Peter Krempa
Signed-off-by: Peter Krempa --- src/qemu/qemu_capabilities.c | 3 +-- src/qemu/qemu_capabilities.h | 2 +- tests/qemucapabilitiesdata/caps_3.1.0.ppc64.xml | 1 - tests/qemucapabilitiesdata/caps_3.1.0.x86_64.xml | 1 -

[PATCH 14/17] qemu: command: Always assume QEMU_CAPS_OVERCOMMIT

2022-02-15 Thread Peter Krempa
Starting with qemu-3.1 we always have the '-overcommit' argument and use it instead of '-realtime'. Remove the capability check and fix all fake-caps tests. Signed-off-by: Peter Krempa --- src/qemu/qemu_command.c| 10 ++

[PATCH 05/17] tests: qemucapabilities: Remove qemu-2.11 test data

2022-02-15 Thread Peter Krempa
Upcoming patches will raise the minimum required qemu version to 3.1. Signed-off-by: Peter Krempa --- .../caps_2.11.0.s390x.replies | 18237 --- .../caps_2.11.0.s390x.xml | 2593 -- .../caps_2.11.0.x86_64.replies| 19525

[PATCH 11/17] qemu: Always assume QEMU_CAPS_CHARDEV_FD_PASS_COMMANDLINE

2022-02-15 Thread Peter Krempa
All qemu versions now support FD passing either directly or via FDset. Assume that we always have this capability so that we can simplify chardev handling in many cases. Signed-off-by: Peter Krempa --- src/qemu/qemu_process.c| 14 +++---

[PATCH 08/17] qemu: Formally deprecate support for qemu < 3.1

2022-02-15 Thread Peter Krempa
As of April 23 2022, Ubuntu 20.04 will be out for two years, which means we no longer have to support Ubuntu 18.04 along with qemu-2.11 shipped with it. This then brings the minimum qemu version we have to support to qemu-3.1: Debian 10/Stable: 3.1 OpenSUSE Leap 15.3: 5.2 Ubuntu

[PATCH 16/17] qemu: Always assume QEMU_CAPS_STORAGE_WERROR

2022-02-15 Thread Peter Krempa
All supported QEMUs now accept werror/rerror as argument for the frontend disk device, so we can remove the old code. Signed-off-by: Peter Krempa --- src/qemu/qemu_command.c | 34 +++--- src/qemu/qemu_command.h | 3 +-- src/qemu/qemu_hotplug.c | 3 +-- 3 files

[PATCH 13/17] qemu: capabilities: Retire QEMU_CAPS_QUERY_CPU_MODEL_EXPANSION_MIGRATABLE

2022-02-15 Thread Peter Krempa
The flag was based on a version check which no longer made sense. Remove the flag by replacing it's only use by an arch-check which is equivalent at this point. Signed-off-by: Peter Krempa --- src/qemu/qemu_capabilities.c | 10 ++ src/qemu/qemu_capabilities.h

[PATCH 04/17] qemuxml2agvtest: Retire tests based on qemu-3.0

2022-02-15 Thread Peter Krempa
Upcoming patches will raise the minimum required qemu version to 3.1. Signed-off-by: Peter Krempa --- .../cpu-host-model.x86_64-3.0.0.args | 36 --- .../mlock-off.x86_64-3.0.0.args | 31 .../mlock-on.x86_64-3.0.0.args| 31

[PATCH 02/17] qemuxml2agvtest: Retire tests based on qemu-2.11

2022-02-15 Thread Peter Krempa
Upcoming patches will raise the minimum required qemu version to 3.1. Signed-off-by: Peter Krempa --- .../cpu-host-model.x86_64-2.11.0.args | 36 -- ...ics-vnc-auto-socket-cfg.x86_64-2.11.0.args | 34 - ...raphics-vnc-auto-socket.x86_64-2.11.0.args | 32

[PATCH 03/17] qemuxml2agvtest: Retire tests based on qemu-2.12

2022-02-15 Thread Peter Krempa
Upcoming patches will raise the minimum required qemu version to 3.1. Signed-off-by: Peter Krempa --- .../cpu-host-model.x86_64-2.12.0.args | 36 -- .../disk-error-policy-s390x.s390x-2.12.0.args | 35 -- .../disk-error-policy.x86_64-2.12.0.args | 37

[PATCH 10/17] qemu: capabilities: Remove probing of QEMU_CAPS_NUMA via 'query-command-line-options'

2022-02-15 Thread Peter Krempa
For modern qemu versions we use the presence of 'set-numa-node' qmp command. Signed-off-by: Peter Krempa --- src/qemu/qemu_capabilities.c | 1 - 1 file changed, 1 deletion(-) diff --git a/src/qemu/qemu_capabilities.c b/src/qemu/qemu_capabilities.c index 35bf07142a..43880d24e7 100644 ---

[PATCH 01/17] ci: Drop Ubuntu 1804

2022-02-15 Thread Peter Krempa
As of April 23 2022, Ubuntu 20.04 will be out for two years, which per our platform support policy means we no longer have to support Ubuntu 18.04. Signed-off-by: Peter Krempa --- ci/containers/ubuntu-1804.Dockerfile | 108 --- ci/gitlab.yml| 16

[PATCH 07/17] tests: qemucapabilities: Remove qemu-3.0 test data

2022-02-15 Thread Peter Krempa
Upcoming patches will raise the minimum required qemu version to 3.1. Signed-off-by: Peter Krempa --- .../caps_3.0.0.ppc64.replies | 23945 .../qemucapabilitiesdata/caps_3.0.0.ppc64.xml | 1073 - .../caps_3.0.0.riscv32.replies| 14919 --

[PATCH for 8.3.0 00/17] qemu: Stop supporting Ubuntu 1804-ancient qemus

2022-02-15 Thread Peter Krempa
As of April 23 2022, Ubuntu 20.04 will be out for two years, which per our platform support policy means we no longer have to support Ubuntu 18.04. The supported platforms thus will have the following qemu versions: Debian 10/Stable: 3.1 OpenSUSE Leap 15.3: 5.2 Ubuntu

Re: [PATCH 1/5] lib: Introduce 'virDomainQemuMonitorCommandWithFiles'

2022-02-15 Thread Peter Krempa
On Thu, Feb 03, 2022 at 18:23:25 +0100, Michal Prívozník wrote: > On 2/3/22 15:51, Peter Krempa wrote: > > This API has the same semantics as 'virDomainQemuMonitorCommand' but > > accepts file descriptors which are then forwarded to qemu. > > > > Signed-off-by: Peter Krempa > > --- > >

Re: [PATCH v2 0/3] src: use virDomainJobData

2022-02-15 Thread Jiri Denemark
On Fri, Feb 11, 2022 at 14:49:04 +0100, Kristina Hanicova wrote: > v1 is here: > https://listman.redhat.com/archives/libvir-list/2022-January/msg00958.html > > diff to v1: > * rebase onto the current master > > (bellow are the ones suggested by Jirka, thanks) > * removed check if callbacks

[libvirt PATCH] Make systemd unit ordering more robust

2022-02-15 Thread Martin Kletzander
Since libvirt-guests script/service can operate on various URIs and we do support both socket activation and traditional services, the ordering should be specified for all the possible sockets and services. Also remove the Wants= dependency since do not want to start any service. We cannot know