Re: [PATCH v1] tests: add capabilities for QEMU 10.0.0 on s390x

2025-04-30 Thread Shalini Chellathurai Saroja
On 2025-04-23 09:38, Peter Krempa wrote: On Tue, Jan 21, 2025 at 16:33:03 +0100, Shalini Chellathurai Saroja wrote: Let us introduce the xml and reply files for QEMU 10.0.0 on s390x. Notable changes: - new s390-ccw-virtio-10.0 machine type - old machine types (2.4 - 2.8) dropped - n

Re: [RFC PATCH 0/3] single-binary: make QAPI generated files common

2025-04-30 Thread Pierrick Bouvier
On 4/29/25 12:57 PM, Pierrick Bouvier wrote: On 4/29/25 2:35 AM, Philippe Mathieu-Daudé wrote: If a distro wants to name a binary 'qemu-kvm' it can drop the -target option and hard-wire its target_info() to a distro-specific TargetInfo implementation, or &target_info_x86_64_system. Having upd

Re: [RFC PATCH 0/3] single-binary: make QAPI generated files common

2025-04-30 Thread Pierrick Bouvier
On 4/29/25 10:40 PM, Thomas Huth wrote: On 29/04/2025 21.48, Pierrick Bouvier wrote: ... I'm not keen to have a default target set, but it's a personal opinion based on fear of "implicit smart choice hurts", so I'll be happy to change my mind with a good argument for it. No default target, ple

Re: [RFC PATCH 0/3] single-binary: make QAPI generated files common

2025-04-30 Thread Pierrick Bouvier
On 4/29/25 2:35 AM, Philippe Mathieu-Daudé wrote: If a distro wants to name a binary 'qemu-kvm' it can drop the -target option and hard-wire its target_info() to a distro-specific TargetInfo implementation, or &target_info_x86_64_system. Having updated my Debian stable to next stable (trixie)

Re: [RFC PATCH 0/3] single-binary: make QAPI generated files common

2025-04-30 Thread Pierrick Bouvier
On 4/29/25 2:20 AM, Thomas Huth wrote: On 29/04/2025 10.23, Markus Armbruster wrote: ... I don't wish to derail this thread, but we've been dancing around the question of how to best fix the target for some time. I think we should talk about it for real. Sure, and no problem about that, that

Re: [RFC PATCH 0/3] single-binary: make QAPI generated files common

2025-04-30 Thread Pierrick Bouvier
On 4/29/25 1:37 AM, Daniel P. Berrangé wrote: On Tue, Apr 29, 2025 at 09:43:24AM +0200, Markus Armbruster wrote: Pierrick Bouvier writes: After looking at the introspection code, I don't see any major blocker. We need to keep some of existing "if", as they are based on config-host, and should

Re: [RFC PATCH 0/3] single-binary: make QAPI generated files common

2025-04-30 Thread Pierrick Bouvier
On 4/29/25 12:43 AM, Markus Armbruster wrote: Pierrick Bouvier writes: On 4/25/25 11:21 PM, Markus Armbruster wrote: Trouble is some uses of the second kind are in QAPI conditionals. I can see three options: (1) Drop these conditionals. (2) Replace them by run-time checks. (3) Have target

libvirt-11.3.0 release candidate 2

2025-04-30 Thread Jiri Denemark via Devel
I have just tagged v11.3.0-rc2 in the repository and pushed signed tarballs to https://download.libvirt.org/ Please give the release candidate some testing and in case you find a serious issue which should have a fix in the upcoming release, feel free to reply to this thread to make sure the issue

Re: [PATCH v2 4/5] docs/about/removed-features: auto-generate a note for versioned machine types

2025-04-30 Thread Thomas Huth via Devel
On 29/04/2025 15.15, Daniel P. Berrangé wrote: We remove versioned machine types on a fixed schedule. This allows us to auto-generate a paragraph in the removed-features.rst document that always has accurate version info. Signed-off-by: Daniel P. Berrangé --- docs/about/removed-features.rst |

Re: [PATCH v2 4/5] docs/about/removed-features: auto-generate a note for versioned machine types

2025-04-30 Thread Cédric Le Goater via Devel
On 4/30/25 12:16, Thomas Huth via Devel wrote: On 29/04/2025 15.15, Daniel P. Berrangé wrote: We remove versioned machine types on a fixed schedule. This allows us to auto-generate a paragraph in the removed-features.rst document that always has accurate version info. Signed-off-by: Daniel P. B