Re: [RFC PATCH v3 4/6] qemucapabilitiestest: Adds Arm CCA support

On Thu, May 29, 2025 at 05:10:48 +, Kazuhiro Abe (Fujitsu) wrote: > > On 5/20/25 17:54, Peter Krempa wrote: > > On Tue, May 20, 2025 at 17:28:26 +0900, Kazuhiro Abe wrote: > > > From: Akio Kakuno > > > > > > - This test was added to check qemu capabilities for Arm > > > CCA support. > > >

[libvirt PATCHv2 7/7] qemu: format pt and xstup on the command line

From: Ján Tomko Signed-off-by: Ján Tomko --- src/qemu/qemu_command.c| 2 ++ tests/qemuxmlconfdata/amd-iommu.x86_64-latest.args | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/src/qemu/qemu_command.c b/src/qemu/qemu_command.c index e2517863b5..8f

[libvirt PATCHv2 6/7] conf: reject some attributes not applicable to intel IOMMU

From: Ján Tomko Signed-off-by: Ján Tomko --- src/conf/domain_validate.c | 9 + 1 file changed, 9 insertions(+) diff --git a/src/conf/domain_validate.c b/src/conf/domain_validate.c index a7e982bec1..9659b8900a 100644 --- a/src/conf/domain_validate.c +++ b/src/conf/domain_validate.c @@ -

[libvirt PATCHv2 5/7] conf: add passthrough and xtsup attributes for IOMMU

From: Ján Tomko For the newly supported AMD device. Signed-off-by: Ján Tomko --- docs/formatdomain.rst | 8 src/conf/domain_conf.c | 30 + src/conf/domain_conf.h | 2 ++ src/conf/schemas/domaincommon.rng | 10

[libvirt PATCHv2 3/7] qemu: add IOMMU model amd

From: Ján Tomko Introduce a new IOMMU device model 'amd', both the parser and the formatter for QEMU because of our enum warnings. https://issues.redhat.com/browse/RHEL-50560 Signed-off-by: Ján Tomko --- docs/formatdomain.rst | 5 ++- src/conf/domain_conf.c

[libvirt PATCHv2 4/7] docs: formatdomain: document intel-only IOMMU attributes

From: Ján Tomko Signed-off-by: Ján Tomko --- docs/formatdomain.rst | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/formatdomain.rst b/docs/formatdomain.rst index 4bd82e4f5f..1fa814931f 100644 --- a/docs/formatdomain.rst +++ b/docs/formatdomain.rst @@ -9065,14 +

[libvirt PATCHv2 2/7] qemu: introduce QEMU_CAPS_PCI_ID

From: Ján Tomko Introduced by QEMU commit f864a3235ea1d1d714b3cde2d9a810ea6344a7b5 the presence of this attribute allows libvirt to specify the alias of the AMDVI-PCI device explicitly. (It was implicit before the introduction of this attribute) Signed-off-by: Ján Tomko --- src/qemu/qemu_capa

[libvirt PATCHv2 0/7] qemu: introduce amd-iommu support

Ján Tomko (7): qemu: introduce QEMU_CAPS_AMD_IOMMU qemu: introduce QEMU_CAPS_PCI_ID qemu: add IOMMU model amd docs: formatdomain: document intel-only IOMMU attributes conf: add passthrough and xtsup attributes for IOMMU conf: reject some attributes not applicable to intel IOMMU qemu:

[libvirt PATCHv2 1/7] qemu: introduce QEMU_CAPS_AMD_IOMMU

From: Ján Tomko Check for the presence of the amd-iommu device, so we can conditionalize probing for its properties. Signed-off-by: Ján Tomko --- src/qemu/qemu_capabilities.c | 2 ++ src/qemu/qemu_capabilities.h | 1 + tests/qemucapabilit

Re: [PATCH] qemu: Fix error when migration with shared TPM storage is unsupported

On a Wednesday in 2025, Jiri Denemark via Devel wrote: From: Jiri Denemark The VIR_ERR_NO_SUPPORT error is supposed to be used for unsupported driver APIs. It is incorrectly used when swtpm does not support migration with shared storage resulting in a rather strange error message: this func

[PATCH] qemu: Fix error when migration with shared TPM storage is unsupported

From: Jiri Denemark The VIR_ERR_NO_SUPPORT error is supposed to be used for unsupported driver APIs. It is incorrectly used when swtpm does not support migration with shared storage resulting in a rather strange error message: this function is not supported by the connection driver: the runn

Re: [PATCH 1/1] NEWS : update NEWS for POWER11 support

Extra space between "NEWS" and ":" On a Wednesday in 2025, Narayana Murty N wrote: Update NEWS.rst with the now added POWER11 processor support Signed-off-by: Narayana Murty N --- NEWS.rst | 4 1 file changed, 4 insertions(+) Reviewed-by: Ján Tomko Jano signature.asc Description: PG

[PATCH v3 2/3] ch: add log level configuration option

Allow a user to set the verbosity of the cloud hypervisor instances by specifying it in the ch.conf configuration file. Signed-off-by: Stefan Kober --- src/ch/ch.conf | 8 src/ch/ch_conf.c | 9 + src/ch/ch_conf.h | 15 +++

[PATCH v3 3/3] NEWS: ch: announce log_level config option

Signed-off-by: Stefan Kober --- NEWS.rst | 5 + 1 file changed, 5 insertions(+) diff --git a/NEWS.rst b/NEWS.rst index 636fcbd573..cfeddd10df 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -17,6 +17,11 @@ v11.4.0 (unreleased) * **New features** + * Allow setting the log level of Cloud Hypervi

[PATCH v3 1/3] ch: Add config file support

Similar to the QEMU driver, the ch driver receives support for configuration files that allows doing certain configuration on the virtchd daemon. The initial use case will be setting the verbosity of the cloud hypervisor instances started by virtchd, but the implementation allows for adding furthe

[PATCH v3 0/3] CH: Add support for a configuration file and log level configuration

Similar to the qemu.conf file that allows QEMU specific configurations we add the possibility to specify a ch.conf file for Cloud Hypervisor configuration. The initial single config option is the log level, which sets the verbosity of the Cloud Hypervisor process. This allows for simpler debugging