Re: [PATCH] apparmor: Add support for local profile customizations

2023-06-22 Thread Jim Fehlig
On 6/22/23 11:08, Jim Fehlig wrote: On 6/22/23 08:50, Andrea Bolognani wrote: On Thu, Jun 08, 2023 at 10:37:43AM -0600, Jim Fehlig wrote: On 6/8/23 08:11, Andrea Bolognani wrote: Note that the Debian package has included this patch[1] for many years, and while it partially overlaps with what

[PATCH v2 5/5] migration: Deprecate old compression method

2023-06-22 Thread Juan Quintela
Signed-off-by: Juan Quintela --- docs/about/deprecated.rst | 8 +++ qapi/migration.json | 102 -- migration/options.c | 13 + 3 files changed, 86 insertions(+), 37 deletions(-) diff --git a/docs/about/deprecated.rst

[PATCH v2 1/5] migration: Use proper indentation for migration.json

2023-06-22 Thread Juan Quintela
We broke it with dirtyrate limit patches. Signed-off-by: Juan Quintela --- qapi/migration.json | 67 ++--- 1 file changed, 33 insertions(+), 34 deletions(-) diff --git a/qapi/migration.json b/qapi/migration.json index 6ff39157ba..ad8cc57071 100644 ---

[PATCH v2 3/5] migration: migrate 'blk' command option is deprecated.

2023-06-22 Thread Juan Quintela
Set the 'block' migration capability to 'true' instead. Signed-off-by: Juan Quintela --- docs/about/deprecated.rst | 7 +++ qapi/migration.json | 10 +++--- migration/migration.c | 5 + 3 files changed, 19 insertions(+), 3 deletions(-) diff --git

[PATCH v2 2/5] migration: migrate 'inc' command option is deprecated.

2023-06-22 Thread Juan Quintela
Set the 'block_incremental' migration parameter to 'true' instead. Signed-off-by: Juan Quintela --- docs/about/deprecated.rst | 7 +++ qapi/migration.json | 12 ++-- migration/migration.c | 6 ++ 3 files changed, 23 insertions(+), 2 deletions(-) diff --git

[PATCH v2 4/5] migration: Deprecate block migration

2023-06-22 Thread Juan Quintela
It is obsolete. It is better to use driver-mirror with NBD instead. CC: Kevin Wolf CC: Eric Blake CC: Stefan Hajnoczi CC: Hanna Czenczek Signed-off-by: Juan Quintela --- docs/about/deprecated.rst | 10 ++ qapi/migration.json | 30 +-

[PATCH v2 0/5] Migration deprecated parts

2023-06-22 Thread Juan Quintela
On this v2: - dropped -incoming deprecation Paolo came with a better solution using keyvalues. - skipped field is already ready for next pull request, so dropped. - dropped the RFC bits, nermal PATCH. - Assessed all the review comments. - Added indentation of migration.json. - Used the

Re: [RFC 4/6] migration: Deprecate -incoming

2023-06-22 Thread Juan Quintela
Peter Xu wrote: > On Thu, Jun 22, 2023 at 11:22:56AM +0200, Thomas Huth wrote: >> Then simply forbid "migrate_set_parameter multifd-channels ..." if the uri >> has been specified on the command line? > > Yeah, actually already in a pull (even though the pr may need a new one..): > >

Re: [RFC 4/6] migration: Deprecate -incoming

2023-06-22 Thread Juan Quintela
Peter Xu wrote: > On Mon, Jun 12, 2023 at 10:51:08PM +0200, Juan Quintela wrote: >> Peter Xu wrote: >> > On Mon, Jun 12, 2023 at 09:33:42PM +0200, Juan Quintela wrote: >> >> Only "defer" is recommended. After setting all migation parameters, >> >> start incoming migration with "migrate-incoming

Re: [RFC 6/6] migration: Deprecated old compression method

2023-06-22 Thread Juan Quintela
Daniel P. Berrangé wrote: > On Mon, Jun 12, 2023 at 09:33:44PM +0200, Juan Quintela wrote: >> Signed-off-by: Juan Quintela >> --- >> docs/about/deprecated.rst | 8 >> qapi/migration.json | 92 --- >> migration/options.c | 13 ++ >> 3

Re: [RFC 6/6] migration: Deprecated old compression method

2023-06-22 Thread Juan Quintela
Thomas Huth wrote: > On 12/06/2023 21.33, Juan Quintela wrote: >> Signed-off-by: Juan Quintela >> --- >> docs/about/deprecated.rst | 8 >> qapi/migration.json | 92 --- >> migration/options.c | 13 ++ >> 3 files changed, 79

Re: [RFC 4/6] migration: Deprecate -incoming

2023-06-22 Thread Peter Xu
On Thu, Jun 22, 2023 at 05:33:29PM +0100, Daniel P. Berrangé wrote: > On Thu, Jun 22, 2023 at 11:54:43AM -0400, Peter Xu wrote: > > I can try to move the todo even higher. Trying to list the initial goals > > here: > > > > - One extra phase of handshake between src/dst (maybe the time to boost >

Re: [RFC 5/6] migration: Deprecate block migration

2023-06-22 Thread Juan Quintela
Stefan Hajnoczi wrote: > On Mon, Jun 12, 2023 at 09:33:43PM +0200, Juan Quintela wrote: >> It is obsolete. It is better to use driver_mirror+NBD instead. >> >> CC: Kevin Wolf >> CC: Eric Blake >> CC: Stefan Hajnoczi >> CC: Hanna Czenczek >> >> Signed-off-by: Juan Quintela >> >> --- >>

Re: [RFC 4/6] migration: Deprecate -incoming

2023-06-22 Thread Juan Quintela
Juan Quintela wrote: > Only "defer" is recommended. After setting all migation parameters, > start incoming migration with "migrate-incoming uri" command. > > Signed-off-by: Juan Quintela Nack myself. Dropped on next submissiong. keyfile properties suggested by paolo is a much better

Re: [RFC 3/6] migration: migrate 'blk' command option is deprecated.

2023-06-22 Thread Juan Quintela
Daniel P. Berrangé wrote: > On Mon, Jun 12, 2023 at 09:33:41PM +0200, Juan Quintela wrote: >> Use 'migrate_set_capability block true' instead. >> >> Signed-off-by: Juan Quintela >> --- >> docs/about/deprecated.rst | 7 +++ >> qapi/migration.json | 11 +++ >>

Re: [RFC 2/6] migration: migrate 'inc' command option is deprecated.

2023-06-22 Thread Juan Quintela
Daniel P. Berrangé wrote: > On Mon, Jun 12, 2023 at 09:33:40PM +0200, Juan Quintela wrote: >> Use 'migrate_set_parameter block_incremental true' instead. >> >> Signed-off-by: Juan Quintela >> --- >> docs/about/deprecated.rst | 7 +++ >> qapi/migration.json | 11 +-- >>

Re: [RFC 1/6] migration: skipped field is really obsolete.

2023-06-22 Thread Juan Quintela
Daniel P. Berrangé wrote: > On Mon, Jun 12, 2023 at 09:33:39PM +0200, Juan Quintela wrote: >> Has return zero for more than 10 years. Just mark it deprecated. > > Specifically we introduced the field in 1.5.0 > > commit f1c72795af573b24a7da5eb52375c9aba8a37972 > Author: Peter Lieven > Date:

Re: [PATCH] apparmor: Add support for local profile customizations

2023-06-22 Thread Jim Fehlig
On 6/22/23 08:50, Andrea Bolognani wrote: On Thu, Jun 08, 2023 at 10:37:43AM -0600, Jim Fehlig wrote: On 6/8/23 08:11, Andrea Bolognani wrote: Note that the Debian package has included this patch[1] for many years, and while it partially overlaps with what you've added here, I see that local

Re: [RFC 4/6] migration: Deprecate -incoming

2023-06-22 Thread Daniel P . Berrangé
On Thu, Jun 22, 2023 at 11:54:43AM -0400, Peter Xu wrote: > I can try to move the todo even higher. Trying to list the initial goals > here: > > - One extra phase of handshake between src/dst (maybe the time to boost > QEMU_VM_FILE_VERSION) before anything else happens. > > - Dest shouldn't

Re: [RFC 4/6] migration: Deprecate -incoming

2023-06-22 Thread Paolo Bonzini
On Thu, Jun 22, 2023 at 5:26 PM Peter Xu wrote: > PS: we may want to postpone this to be later than migration_object_init(), > when/if there's a real patch. Yes, that's true. > > > The only incompatibility is for people who are using "," in an URI, > > > which is rare and only an issue for the

Re: [RFC 4/6] migration: Deprecate -incoming

2023-06-22 Thread Peter Xu
On Thu, Jun 22, 2023 at 10:59:58AM +0100, Daniel P. Berrangé wrote: > On Thu, Jun 22, 2023 at 10:52:12AM +0200, Juan Quintela wrote: > > Paolo Bonzini wrote: > > > On 6/12/23 22:51, Juan Quintela wrote: > > >>> Shall we just leave it there? Or is deprecating it helps us in any > > >>> form? > >

Re: [RFC 4/6] migration: Deprecate -incoming

2023-06-22 Thread Peter Xu
On Thu, Jun 22, 2023 at 11:22:56AM +0200, Thomas Huth wrote: > Then simply forbid "migrate_set_parameter multifd-channels ..." if the uri > has been specified on the command line? Yeah, actually already in a pull (even though the pr may need a new one..):

Re: [RFC 4/6] migration: Deprecate -incoming

2023-06-22 Thread Peter Xu
On Thu, Jun 22, 2023 at 12:01:55PM +0200, Juan Quintela wrote: > Paolo Bonzini wrote: > > On 6/22/23 10:52, Juan Quintela wrote: > >> User friendliness. > >> The problem is that if you use more than two channels with multifd, on > >> the incoming side, you need to do: > > > > You're sacrificing

Re: [PATCH] apparmor: Add support for local profile customizations

2023-06-22 Thread Andrea Bolognani
On Thu, Jun 08, 2023 at 10:37:43AM -0600, Jim Fehlig wrote: > On 6/8/23 08:11, Andrea Bolognani wrote: > > Note that the Debian package has included this patch[1] for many > > years, and while it partially overlaps with what you've added here, I > > see that local overrides for abstractions are

Re: [libvirt PATCH 2/9] src: remote deps on ip[6]tables/firewalld.service from systemd units

2023-06-22 Thread Daniel P . Berrangé
On Thu, Jun 22, 2023 at 04:00:50PM +0200, Peter Krempa wrote: > On Wed, Jun 21, 2023 at 14:32:25 +0100, Daniel P. Berrangé wrote: > > The unit files both have After=network.target, and this in turn implies > > After=network-pre.target. Both iptables.service & ip6tables.service have > >

Re: [libvirt PATCH 7/9] util: relax requirement for logind to be running

2023-06-22 Thread Andrea Bolognani
On Thu, Jun 22, 2023 at 09:49:41AM +0100, Daniel P. Berrangé wrote: > On Thu, Jun 22, 2023 at 10:23:57AM +0200, Peter Krempa wrote: > > On Wed, Jun 21, 2023 at 14:32:30 +0100, Daniel P. Berrangé wrote: > > > +/* > > > + * Want to use logind if: > > > + * - logind is already running >

Re: [libvirt PATCH 2/9] src: remote deps on ip[6]tables/firewalld.service from systemd units

2023-06-22 Thread Peter Krempa
On Wed, Jun 21, 2023 at 14:32:25 +0100, Daniel P. Berrangé wrote: > The unit files both have After=network.target, and this in turn implies > After=network-pre.target. Both iptables.service & ip6tables.service have > Before=network-pre.target since Fedora >= 35 and RHEL >= 8.4. Is this also true

[PATCH 0/4] qemu: Allow 'maxMemory' without 'slots' and fix slot validation for virtio-mem

2023-06-22 Thread Peter Krempa
First patch reworks memory specification to use the explicit 'size' parameter (since qemu v2.0.0-179-g6e1d3c1c85), the reset modifies memory hotplug related checks to properly handle non-DIMM devices which don't require DIMM slots. Peter Krempa (4): qemu_command: Always use modern syntax of

[PATCH 4/4] qemuxml2(argv|xml)test: Add case for validating proper DIMM slot validation

2023-06-22 Thread Peter Krempa
Add a config where both DIMM and non-DIMM devices are used so that it validates that only DIMMs require memory slots. Signed-off-by: Peter Krempa --- ...memory-hotplug-multiple.x86_64-latest.args | 46 ++ .../memory-hotplug-multiple.xml | 89 ++

[PATCH 2/4] qemu_domain: Properly validate count of memory slots

2023-06-22 Thread Peter Krempa
Memory slots are required only for DIMM-like devices, while other devices defined via such as virtio-mem may use the PCI bus and thus do not require/consume a memory slot. Fix the validation code to calculate the required count of memory devices only for DIMMs and NVDIMMs. Signed-off-by: Peter

[PATCH 3/4] conf: Allow omitting 'slots' attribute of

2023-06-22 Thread Peter Krempa
Memory slots are required only for DIMM-like devices, but the maximum memory address space is relevant also for other non-DIMM memory devices such as virtio-mem. Allow configurations where no slots are added. Signed-off-by: Peter Krempa --- src/conf/domain_conf.c |

Re: [PATCH] spec: Drop numad usage on fedora 39+

2023-06-22 Thread Andrea Bolognani
On Thu, Jun 08, 2023 at 08:53:17AM +0200, Martin Kletzander wrote: > On Mon, Jun 05, 2023 at 12:10:03PM +0200, Michal Prívozník wrote: > > On 5/23/23 19:31, Cole Robinson wrote: > > > +%if 0%{?fedora} >= 39 > > > +# numad is retired in fedora 39+, upstream is dead > > > +%define with_numad

Re: [RFC 4/6] migration: Deprecate -incoming

2023-06-22 Thread Paolo Bonzini
On 6/22/23 10:52, Juan Quintela wrote: User friendliness. The problem is that if you use more than two channels with multifd, on the incoming side, you need to do: You're sacrificing user-friendliness for the 99.99% that don't use multifd, for an error (i.e. it's not even fixing the issue)

Re: [RFC 4/6] migration: Deprecate -incoming

2023-06-22 Thread Juan Quintela
Paolo Bonzini wrote: > On 6/22/23 10:52, Juan Quintela wrote: >> User friendliness. >> The problem is that if you use more than two channels with multifd, on >> the incoming side, you need to do: > > You're sacrificing user-friendliness for the 99.99% that don't use > multifd, for an error (i.e.

Re: [RFC 4/6] migration: Deprecate -incoming

2023-06-22 Thread Daniel P . Berrangé
On Thu, Jun 22, 2023 at 10:52:12AM +0200, Juan Quintela wrote: > Paolo Bonzini wrote: > > On 6/12/23 22:51, Juan Quintela wrote: > >>> Shall we just leave it there? Or is deprecating it helps us in any form? > >> See the patches two weeks ago when people complained that lisen(.., num) > >> was

Re: [RFC 4/6] migration: Deprecate -incoming

2023-06-22 Thread Thomas Huth
On 22/06/2023 10.52, Juan Quintela wrote: Paolo Bonzini wrote: On 6/12/23 22:51, Juan Quintela wrote: Shall we just leave it there? Or is deprecating it helps us in any form? See the patches two weeks ago when people complained that lisen(.., num) was too low. And there are other

Re: [libvirt PATCH 9/9] util: add logging about node suspend availability

2023-06-22 Thread Daniel P . Berrangé
On Thu, Jun 22, 2023 at 10:27:15AM +0200, Peter Krempa wrote: > On Wed, Jun 21, 2023 at 14:32:32 +0100, Daniel P. Berrangé wrote: > > Signed-off-by: Daniel P. Berrangé > > --- > > src/util/virnodesuspend.c | 3 +++ > > 1 file changed, 3 insertions(+) > > > > diff --git

Re: [RFC 4/6] migration: Deprecate -incoming

2023-06-22 Thread Juan Quintela
Paolo Bonzini wrote: > On 6/12/23 22:51, Juan Quintela wrote: >>> Shall we just leave it there? Or is deprecating it helps us in any form? >> See the patches two weeks ago when people complained that lisen(.., num) >> was too low. And there are other parameters that work the same way >> (that I

Re: [PATCH 3/3] virGlobalInit: Make glib init its own global state

2023-06-22 Thread Daniel P . Berrangé
On Thu, Jun 22, 2023 at 11:10:25AM +0200, Michal Privoznik wrote: > On Wed, Jun 21, 2023 at 5:30 PM Daniel P. Berrangé > wrote: > > > > On Wed, Jun 21, 2023 at 04:09:11PM +0200, Michal Privoznik wrote: > > > This should not be needed, but here's what's happening: > > > virStrToLong_*() family of

Re: [PATCH 3/3] virGlobalInit: Make glib init its own global state

2023-06-22 Thread Michal Privoznik
On Wed, Jun 21, 2023 at 5:30 PM Daniel P. Berrangé wrote: > > On Wed, Jun 21, 2023 at 04:09:11PM +0200, Michal Privoznik wrote: > > This should not be needed, but here's what's happening: > > virStrToLong_*() family of functions was switched from strtol*() > > to g_ascii_strtol*() in order to

Re: [libvirt PATCH 9/9] util: add logging about node suspend availability

2023-06-22 Thread Peter Krempa
On Wed, Jun 21, 2023 at 14:32:32 +0100, Daniel P. Berrangé wrote: > Signed-off-by: Daniel P. Berrangé > --- > src/util/virnodesuspend.c | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/src/util/virnodesuspend.c b/src/util/virnodesuspend.c > index 01f387d6fa..91a7f10eb9 100644 > ---

Re: [libvirt PATCH 5/9] rpc: automatically raise max file limit in all daemons

2023-06-22 Thread Peter Krempa
On Wed, Jun 21, 2023 at 14:32:28 +0100, Daniel P. Berrangé wrote: > None of our daemons use select(), so it is safe to raise the max file > limit to its maximum on startup. > > https://gitlab.com/libvirt/libvirt/-/issues/489 > Signed-off-by: Daniel P. Berrangé > --- > src/rpc/virnetdaemon.c | 3

Re: [libvirt PATCH 7/9] util: relax requirement for logind to be running

2023-06-22 Thread Daniel P . Berrangé
On Thu, Jun 22, 2023 at 10:23:57AM +0200, Peter Krempa wrote: > On Wed, Jun 21, 2023 at 14:32:30 +0100, Daniel P. Berrangé wrote: > > Historically we wanted to check if logind was actually running, not > > merely activatable, because on systems where systemd is installed, > > but the OS is booted

Re: [RFC 4/6] migration: Deprecate -incoming

2023-06-22 Thread Paolo Bonzini
On 6/21/23 09:08, Thomas Huth wrote:   if (strcmp(incoming, "defer") != 0) { +    warn_report("-incoming %s is deprecated, use -incoming defer and " +    " set the uri with migrate-incoming.", incoming);   qmp_migrate_incoming(incoming, _err);  

Re: [RFC 4/6] migration: Deprecate -incoming

2023-06-22 Thread Paolo Bonzini
On 6/12/23 22:51, Juan Quintela wrote: Shall we just leave it there? Or is deprecating it helps us in any form? See the patches two weeks ago when people complained that lisen(.., num) was too low. And there are other parameters that work the same way (that I convenientely had forgotten). So

Re: [libvirt PATCH 8/9] src: remove dep on systemd-logind.service from unit files

2023-06-22 Thread Peter Krempa
On Wed, Jun 21, 2023 at 14:32:31 +0100, Daniel P. Berrangé wrote: > After the previous commit we no longer require that logind is actually > running, it merely has to be activatable. > > https://gitlab.com/libvirt/libvirt/-/issues/489 > Signed-off-by: Daniel P. Berrangé > --- >

Re: [libvirt PATCH 1/9] src: remove After=local-fs.target from systemd units

2023-06-22 Thread Daniel P . Berrangé
On Thu, Jun 22, 2023 at 09:27:48AM +0200, Peter Krempa wrote: > On Wed, Jun 21, 2023 at 14:32:24 +0100, Daniel P. Berrangé wrote: > > All services are ordered after local-fs.target unless they have set > > DefaultDependencies=no, which we do not do. > > > >

Re: [libvirt PATCH 6/9] src: set max open file limit to match systemd >= 240 defaults

2023-06-22 Thread Peter Krempa
On Wed, Jun 21, 2023 at 14:32:29 +0100, Daniel P. Berrangé wrote: > Since systemd 240, all services get an open file hard limit of > 500k, and a soft limit of 1024. This limit means apps are safe > to use select() by default which is limited to 1024 FDs. Apps > which don't use select() are

Re: [libvirt PATCH 4/9] util: add helper for raising the max files limit

2023-06-22 Thread Peter Krempa
On Wed, Jun 21, 2023 at 14:32:27 +0100, Daniel P. Berrangé wrote: > Historically the max files limit for processes has always been 1024, > because going beyond this is incompatible with the select() function. > None the less most apps these days will use poll() so should not be > limited in this

Re: [libvirt PATCH 7/9] util: relax requirement for logind to be running

2023-06-22 Thread Peter Krempa
On Wed, Jun 21, 2023 at 14:32:30 +0100, Daniel P. Berrangé wrote: > Historically we wanted to check if logind was actually running, not > merely activatable, because on systems where systemd is installed, > but the OS is booted into non-systemd init, we want to fallback to > pm-utils. > >

Re: [libvirt PATCH 1/9] src: remove After=local-fs.target from systemd units

2023-06-22 Thread Peter Krempa
On Wed, Jun 21, 2023 at 14:32:24 +0100, Daniel P. Berrangé wrote: > All services are ordered after local-fs.target unless they have set > DefaultDependencies=no, which we do not do. > > https://gitlab.com/libvirt/libvirt/-/issues/489 > Signed-off-by: Daniel P. Berrangé > --- >

Re: [libvirt PATCH 3/9] util: remove pointless wrappers for setrlimit/getrlimit

2023-06-22 Thread Peter Krempa
On Wed, Jun 21, 2023 at 14:32:26 +0100, Daniel P. Berrangé wrote: > These wrappers added no semantic difference over calling the system > function directly. > > Signed-off-by: Daniel P. Berrangé > --- > src/util/virprocess.c | 22 ++ > 1 file changed, 2 insertions(+), 20