query-cpu-model-expansion may report an array of deprecated properties.
This array is optional, and may not be supported for a particular
architecture or reported for a particular CPU model. If the output is
present, then capture it and store in a qemuMonitorCPUModelInfo struct
for later use.
The
Add support for libvirt to query and cache an array of deprecated CPU features
(aka CPU properties) for the host-model. This data is queried via a full
query-cpu-model-expansion and cached in the QEMU capabilities file. This
model expansion will depend on the availability of the "deprecated-props
Add a new a attribute, deprecated_features='on|off' to the
element. This is used to toggle features flagged as deprecated on the
CPU model on or off. When this attribute is paired with 'on',
deprecated features will not be filtered. When paired with 'off', any
CPU features that are flagged as d
Refactor the CPU Model parsing functions within
qemuMonitorJSONGetCPUModelExpansion. The new functions,
qemuMonitorJSONParseCPUModelExpansionData and
qemuMonitorJSONParseCPUModelExpansion invoke the functions they
replace and leave room for a subsequent patch to handle parsing the
(optional) depre
Add QEMU_CAPS_QUERY_CPU_MODEL_EXPANSION_DEPRECATED_PROPS for detecting
if query-cpu-model-expansion can report deprecated CPU model properties.
QEMU introduced this capability in 9.1 release. Add flag and deprecated
features to the capabilities test data for QEMU 9.1 and 9.2 replies/XML
since it c
Add a new flag, --disable-deprecated-features, to the domcapabilities
command. This will modify the output to show the 'host-model' CPU
with features flagged as deprecated paired with the 'disable' policy.
virsh domcapabilities --disable-deprecated-features
Signed-off-by: Collin Walling
---
do
On a Tuesday in 2024, Michal Privoznik wrote:
When moving function and/or renaming them sometimes corresponding
change to corresponding header file is not done. This leaves us
with functions that are declared in header files, but nowhere
implemented. Drop such declarations.
Signed-off-by: Michal
On a Tuesday in 2024, Michal Privoznik wrote:
The function the comment is referring to is
virNetServerClientPrivNew() not virNetServerClintPrivNew(). The
latter doesn't even exist.
Signed-off-by: Michal Privoznik
---
src/rpc/virnetserverclient.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion
When moving function and/or renaming them sometimes corresponding
change to corresponding header file is not done. This leaves us
with functions that are declared in header files, but nowhere
implemented. Drop such declarations.
Signed-off-by: Michal Privoznik
---
These were identified by a bash
On a Tuesday in 2024, Martin Kletzander wrote:
When qemuDomainDeleteDevice() gets "DeviceNotFound" error it is a
special case as we're trying to remove a device which does not exists
any more. Such occasion is indicated by the return value -2.
Callers of the aforementioned function ought to bas
The function the comment is referring to is
virNetServerClientPrivNew() not virNetServerClintPrivNew(). The
latter doesn't even exist.
Signed-off-by: Michal Privoznik
---
src/rpc/virnetserverclient.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/rpc/virnetserverclient.h
When qemuDomainDeleteDevice() gets "DeviceNotFound" error it is a
special case as we're trying to remove a device which does not exists
any more. Such occasion is indicated by the return value -2.
Callers of the aforementioned function ought to base their behaviour on
the return value. However n
On Tue, Nov 12, 2024 at 02:10:31PM +0100, Ján Tomko wrote:
On a Monday in 2024, Martin Kletzander wrote:
When qemuDomainDeleteDevice() gets "DeviceNotFound" error it is a
special case as we're trying to remove a device which does not exists
any more. Such occasion is indicated by the return val
On a Monday in 2024, Martin Kletzander wrote:
When qemuDomainDeleteDevice() gets "DeviceNotFound" error it is a
special case as we're trying to remove a device which does not exists
any more. Such occasion is indicated by the return value -2.
Callers of the aforementioned function ought to base
Hi Peter,
On Mon, 2024-11-11 at 09:48 +0100, Peter Krempa wrote:
> On Fri, Nov 08, 2024 at 15:58:35 -0300, Georgia Garcia wrote:
> > Some rules are generated dynamically during boot and added to the
> > AppArmor policy. An example of that is macvtap devices that call the
> > AppArmorSetFDLabel hoo
On Tue, Nov 12, 2024 at 09:14:22AM +0100, Michal Prívozník wrote:
> On 11/1/24 23:31, John Levon wrote:
> > John Levon (2):
> > test_driver: provide basic disk hotplug support
> > test_driver: provide basic disk hotunplug support
> >
> > src/test/test_driver.c | 276 +
On Tue, Nov 12, 2024 at 10:59:20AM +0100, Martin Kletzander wrote:
> As requested on the libvirt users list I am adding this mention to the
> apps page.
>
> Reported-by: Erik Huelsmann
> Signed-off-by: Martin Kletzander
> ---
> docs/apps.rst | 5 +
> 1 file changed, 5 insertions(+)
>
> dif
As requested on the libvirt users list I am adding this mention to the
apps page.
Reported-by: Erik Huelsmann
Signed-off-by: Martin Kletzander
---
docs/apps.rst | 5 +
1 file changed, 5 insertions(+)
diff --git a/docs/apps.rst b/docs/apps.rst
index 443c888c4d5d..b2168f9599bb 100644
--- a/d
On Tue, Nov 12, 2024 at 09:12:06AM +, Daniel P. Berrangé wrote:
> On Mon, Nov 11, 2024 at 09:27:00AM +0100, Martin Kletzander wrote:
> > > +Virtio device models
> > > +
> > > +
> > > +Virtio devices come in several variants, some of which are only
> > > applicable to
> > >
On Tue, Nov 12, 2024 at 09:05:38 +0100, Martin Kletzander wrote:
> This switches to newer freebsd 14.1 and implements the new RUN_PIPELINE
> behaviour introduced by Daniel.
>
> Signed-off-by: Martin Kletzander
> ---
> As far as I understand this does not need any change in the CI/CD settings in
>
On Mon, Nov 11, 2024 at 09:27:00AM +0100, Martin Kletzander wrote:
> On Thu, Nov 07, 2024 at 06:34:49PM +0100, Andrea Bolognani wrote:
> > When virtio-(non-)transitional models were introduced, the
> > documentation was updated to include them; at the same time,
> > language was introduced indicati
On 11/1/24 23:31, John Levon wrote:
> Signed-off-by: John Levon
> ---
> src/test/test_driver.c | 114 -
> 1 file changed, 112 insertions(+), 2 deletions(-)
>
> diff --git a/src/test/test_driver.c b/src/test/test_driver.c
> index b7e36e8451..789b1a 1006
On 11/1/24 23:31, John Levon wrote:
> Add some basic plumbing, based on the qemu driver.
>
> Signed-off-by: John Levon
> ---
> src/test/test_driver.c | 162 -
> 1 file changed, 161 insertions(+), 1 deletion(-)
>
> diff --git a/src/test/test_driver.c b/src
On 11/1/24 23:31, John Levon wrote:
> John Levon (2):
> test_driver: provide basic disk hotplug support
> test_driver: provide basic disk hotunplug support
>
> src/test/test_driver.c | 276 -
> 1 file changed, 273 insertions(+), 3 deletions(-)
>
Sorry
This switches to newer freebsd 14.1 and implements the new RUN_PIPELINE
behaviour introduced by Daniel.
Signed-off-by: Martin Kletzander
---
As far as I understand this does not need any change in the CI/CD settings in
gitlab, but I do not have access to those.
ci/cirrus/freebsd-14.vars |
25 matches
Mail list logo
