###
KVM Forum 2025
September 4-5, 2025
Milan, Italy
https://kvm-forum.qemu.org/
###
KVM Forum is an annual event that brings together developers and users,
discussing the state of Linux virtualization technology and planning for
the challenges ahead
As discussed in https://gitlab.com/libvirt/libvirt/-/issues/757.
I'm not quite sure about using a long-only-option, since that's
a first in virsh. But OTOH this option seems too insignificant
to also use one of the precious short option characters for it.
Please check and let me know what you th
In scripts repeated execution of virsh can result in a lot of
journal noise when pkttyagent gets registered with polkitd each
time.
Resolves: https://gitlab.com/libvirt/libvirt/-/issues/757
---
NEWS.rst| 4
docs/manpages/virsh.rst | 8
tools/virsh.c | 13
From: QiangWei Zhang
Variable 'master' needs to be free because it will be reassigned in
virNetDevOpenvswitchInterfaceGetMaster().
The leaked stack:
Direct leak of 11 byte(s) in 1 object(s) allocated from:
#0 0x7f7dad8ba6df in __interceptor_malloc (/lib64/libasan.so.8+0xba6df)
#1 0x7f7dad715728
On Mon, May 05, 2025 at 23:09:52 +0200, Jens Schmidt via Devel wrote:
Since you domain uses DMARC protections, in order to properly honour
your autorship you need to set the following git option:
git config --global format.forceInBodyFrom true
https://www.libvirt.org/submitting-patches.html#git-
On Tue, May 06, 2025 at 10:47:34 +0800, liu.son...@zte.com.cn wrote:
> From: QiangWei Zhang
>
> Variable 'master' needs to be free because it will be reassigned in
> virNetDevOpenvswitchInterfaceGetMaster().
>
> The leaked stack:
> Direct leak of 11 byte(s) in 1 object(s) allocated from:
> #0 0x
On Tue, May 06, 2025 at 10:47:34 +0800, liu.son...@zte.com.cn wrote:
> From: QiangWei Zhang
>
> Variable 'master' needs to be free because it will be reassigned in
> virNetDevOpenvswitchInterfaceGetMaster().
>
> The leaked stack:
> Direct leak of 11 byte(s) in 1 object(s) allocated from:
> #0 0x
On 05/05/25 5:37 PM, Daniel Henrique Barboza wrote:
On 5/5/25 5:58 AM, Andrea Bolognani wrote:
On Tue, Apr 29, 2025 at 05:41:43PM +0200, Jiří Denemark wrote:
On Tue, Apr 29, 2025 at 13:03:12 +0100, Daniel P. Berrangé wrote:
On Tue, Apr 29, 2025 at 01:42:22PM +0200, Peter Krempa wrote:
On
This reverts commit c9fd2d9a48ee3c195cf83cc611b87b09f02f0013.
When we introduced the specialized machine type deprecation policy, we
allow automatic deprecation to take effect immediately, but blocked the
automatic deletion of machine types for 2 releases. This ensured we
complied with the histori
Since we deprecate and remove versioned machine types on a fixed
schedule, we can automatically ensure that the docs reflect the
latest version info, rather than requiring manual updates on each
dev cycle.
The first patch in this series removes the hack which postponed
automatic removal of version
When VERSION is set to a development snapshot (micro >= 50), or a release
candidate (micro >= 90) we have an off-by-1 in determining deprecation
and deletion thresholds for versioned machine types. In such cases we need
to use the next major/minor version in threshold checks.
This adapts the depre
If we change the deprecation logic in include/hw/boards.h, we must make
a corresponding change to docs/conf.py and docs/about/deprecated.rst.
Add comments to these files as a warning to future maintainers to keep
these files in sync.
Reviewed-by: Thomas Huth
Signed-off-by: Daniel P. Berrangé
---
We deprecate versioned machine types on a fixed schedule. This allows us
to auto-generate a paragraph in the deprecated.rst document that always
has accurate version info.
Signed-off-by: Daniel P. Berrangé
---
docs/about/deprecated.rst | 7 +++
docs/conf.py | 33 +++
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 | 10 ++
docs/conf.py|
Add check for networks which were previously
neglected (as opposed to explicit PCI hostdev devices), so that they can
be granted the necessary permissions for PCI device access. The network
type lookup in-turn requires the helper to read libvirt.conf
Downstream bug https://bugs.debian.org/cgi-bin
I'm working on a fix for a bug whereby apparmor permissions aren't
granted to allow a PCI SR-IOV virtual function to be used in a kvm guest
when the VF is defined via a forward type='hostdev' network (as per the
'hostdev' option documented here:
https://libvirt.org/formatnetwork.html#connectivity )
Signed-off-by: Tim Small
---
src/security/virt-aa-helper.c | 7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/src/security/virt-aa-helper.c b/src/security/virt-aa-helper.c
index e3802c18be..fa69245324 100644
--- a/src/security/virt-aa-helper.c
+++ b/src/security/virt-aa-he
On Mon, May 05, 2025 at 09:07:52AM -0300, Daniel Henrique Barboza wrote:
>
>
> On 5/5/25 5:58 AM, Andrea Bolognani wrote:
> > On Tue, Apr 29, 2025 at 05:41:43PM +0200, Jiří Denemark wrote:
> > > On Tue, Apr 29, 2025 at 13:03:12 +0100, Daniel P. Berrangé wrote:
> > > > On Tue, Apr 29, 2025 at 01:4
On a Monday in 2025, Peter Krempa via Devel wrote:
From: Peter Krempa
Document the '--once' option and how it combines with the setting
without '--once'.
Resolves: https://issues.redhat.com/browse/RHEL-89414
Signed-off-by: Peter Krempa
---
docs/manpages/virsh.rst | 10 +++---
1 file change
Enum variable of type qemuMigrationCapability is checked for zero in
src/qemu/qemu_migration_params.c:729.
"if (item->optional) { ..."
Actualy, QEMU_MIGRATION_CAP_XBZRLE enum constant has value 0.
Thus, all uninitialized .optinnal fields of the static array
qemuMigrationParamsFlagMap[] will be im
From: QiangWei Zhang
Variable 'master' needs to be free because it will be reassigned in
virNetDevOpenvswitchInterfaceGetMaster().
The leaked stack:
Direct leak of 11 byte(s) in 1 object(s) allocated from:
#0 0x7f7dad8ba6df in __interceptor_malloc (/lib64/libasan.so.8+0xba6df)
#1 0x7f7da
From: QiangWei Zhang
Variable 'master' needs to be free because it will be reassigned in
virNetDevOpenvswitchInterfaceGetMaster().
The leaked stack:
Direct leak of 11 byte(s) in 1 object(s) allocated from:
#0 0x7f7dad8ba6df in __interceptor_malloc (/lib64/libasan.so.8+0xba6df)
#1 0x7f7dad715728
On a Monday in 2025, Peter Krempa via Devel wrote:
From: Peter Krempa
If either of the autostart settings is enabled the VM will be
autostarted. Attempt to clarify that.
Signed-off-by: Peter Krempa
---
src/libvirt-domain.c | 26 --
1 file changed, 16 insertions(+), 10 d
On Tue, May 06, 2025 at 17:08:18 +0300, Dmitry Frolov wrote:
> Enum variable of type qemuMigrationCapability is checked for zero in
> src/qemu/qemu_migration_params.c:729.
>
> "if (item->optional) { ..."
>
> Actualy, QEMU_MIGRATION_CAP_XBZRLE enum constant has value 0.
> Thus, all uninitialized .
On 06/05/2025 18.00, Daniel P. Berrangé wrote:
Since we deprecate and remove versioned machine types on a fixed
schedule, we can automatically ensure that the docs reflect the
latest version info, rather than requiring manual updates on each
dev cycle.
The first patch in this series removes the
This submission has Chinese character issues and has been abandoned. It has
been resent.
26 matches
Mail list logo
