Apparmor profiles in /etc/apparmor.d/ are config files that can and should
be replaced on package upgrade, which introduces the potential to overwrite
any local changes. Apparmor supports local profile customizations via
/etc/apparmor.d/local/ [1].
This change makes the support explicit by adding
Requires recent qemu with support for the virtio-blk-vhost-vdpa device
and the ability to pass a /dev/fdset/N path for the vdpa path (8.1.0)
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1900770
---
src/qemu/qemu_block.c | 20 --
src/qemu/qemu_domain.c
Check whether the qemu binary supports the vdpa block driver. We can't
rely simply on the existence of the virtio-blk-vhost-vdpa block driver
since the first releases of qemu didn't support fd-passing for this
driver. So we have to check for the 'fdset' feature on the driver
object. This feature wi
vDPA block devices will also need the same consideration for memlock
limits as other vdpa devices, so consider these devices when calculating
memlock limits.
Signed-off-by: Jonathon Jongsma
---
src/qemu/qemu_domain.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git
vDPA block devices can be configured as follows:
Signed-off-by: Jonathon Jongsma
---
docs/formatdomain.rst | 19 +--
src/ch/ch_monitor.c | 1 +
src/conf/domain_conf.c| 7 +++
src/conf/schemas/domaincommon.rng | 13
qemuInterfaceVDPAConnect() was a helper function for connecting to the
vdpa device file. But in order to support other vdpa devices besides
network interfaces (e.g. vdpa block devices) make this function a bit
more generic.
Signed-off-by: Jonathon Jongsma
---
src/qemu/qemu_command.c | 23 +
see https://bugzilla.redhat.com/show_bug.cgi?id=1900770.
Jonathon Jongsma (5):
conf: add ability to configure a vdpa block disk device
qemu: add virtio-blk-vhost-vdpa capability
qemu: make vdpa connect function more generic
qemu: consider vdpa block devices for memlock limits
qemu: Imple
On 6/6/23 11:31, Peter Krempa wrote:
> Peter Krempa (2):
> qemumonitorjsontest: Work around deprecation of 'vcpu' argument of
> 'trace-event-get-state'
> qemucapabilitiestest: Add data for the qemu-8.1
>
> .../domaincapsdata/qemu_8.1.0-q35.x86_64.xml | 286 +
> .../domaincapsdata/qemu_
Qemu 8.1.0 will have a new qcow2 option named discard-no-unref.
https://gitlab.com/qemu-project/qemu/-/commit/42a2890a76f4783cd1c212f27856edcf2b5e8a75
Enabling this option wil change the way qemu handles guest discards
inside the qcow2 image and will highly improve the fragmentation within
the qco
Qemu 8.1.0 will add discard_no_unref option for qcow2 images.
When this option is enabled (default=false), then it will no longer
unreference clusters when guest does a discard, but it will just free
the blocks (useful for incremental backups for example) and pass the
discard to the lower layer.
T
Signed-off-by: Jean-Louis Dupond
---
NEWS.rst | 2 ++
1 file changed, 2 insertions(+)
diff --git a/NEWS.rst b/NEWS.rst
index b1cccee4fa..deac80aec2 100644
--- a/NEWS.rst
+++ b/NEWS.rst
@@ -19,6 +19,8 @@ v9.5.0 (unreleased)
* **Improvements**
+ * qemu: Change the discard-no-unref value via
'trace-event-get-state' was used for testing schema validation as it had
simple arguments. Now 'vcpu' is optional and deprecated. Fix the test so
that it won't break with upcoming qemu-8.1.
Drop the 'all-attrs' case, as it's not not really testing anything
special and for the 'missing mandatory at
Peter Krempa (2):
qemumonitorjsontest: Work around deprecation of 'vcpu' argument of
'trace-event-get-state'
qemucapabilitiestest: Add data for the qemu-8.1
.../domaincapsdata/qemu_8.1.0-q35.x86_64.xml | 286 +
.../domaincapsdata/qemu_8.1.0-tcg.x86_64.xml | 287 +
tests/domaincapsda
13 matches
Mail list logo