Hi Team, Could we please get an ETA on when the review will be completed? We
would greatly appreciate it if the review could be completed as soon as
possible. Apologies for the urgency, but we have a dependency on these changes.
Thank you for your understanding!
Best regards,
Harikumar R
On 2025-03-11 14:03, Peter Krempa wrote:
On Tue, Mar 11, 2025 at 13:49:10 +0100, Shalini Chellathurai Saroja
wrote:
Update the replies and xml files for QEMU 9.2.0 on s390x based on
the released QEMU tag v9.2.0 with commit Id
ae35f033b874c627d81d51070187fbf55f0bf1a7.
Signed-off-by: Shalini Chel
On Wed, Mar 12, 2025 at 08:15:12 -, Harikumar Rajkumar wrote:
> Hi Team, Could we please get an ETA on when the review will be completed?
No, not really. In the patches I went through I updated the docs to
mention 11.2.0. I hope I will not have to update it further.
It depends on how the rest
Thank you for the update. I understand that the review process is complex, and
the feature potentially requiring ongoing maintenance. I appreciate the effort
and work that has been invested so far.
On Wed, Feb 19, 2025 at 22:27:12 +0530, Harikumar Rajkumar wrote:
> From: Chun Feng Wu
>
> extract common methods from "qemuDomainSetBlockIoTune" to be reused
> by throttle handling later, common methods include:
> * "qemuDomainValidateBlockIoTune", which is to validate that PARAMS
> contains o
Builds for Linux without libnl is broken since commit
582f0966f9b9e2148d8887d072364e2a91aed000 because
src/util/virnetdevbridge.c refers to virNetlinkBridgeVlanFilterSet().
A fundamental problem here is that nobody tests such builds. Netlink is
a critical part of Linux networking so developers may
The 'transform' attribute of 'bitmaps' was added in qemu-6.0, thus
we can assume all qemus we're willing to use support it.
Signed-off-by: Peter Krempa
---
src/qemu/qemu_migration.c | 10 ++
1 file changed, 2 insertions(+), 8 deletions(-)
diff --git a/src/qemu/qemu_migration.c b/src/qem
The capability is no logner used as all qemus support it.
Signed-off-by: Peter Krempa
---
src/qemu/qemu_capabilities.c | 3 +--
src/qemu/qemu_capabilities.h | 2 +-
tests/qemucapabilitiesdata/caps_10.0.0_s390x.xml | 1 -
tests/qemuc
The QAPIfication of objects removed the extra warapper object which we
were adding in the monitor code to simplify the other callers.
Now that we support only qemus which don't require this we can drop the
support code.
Signed-off-by: Peter Krempa
---
src/qemu/qemu_monitor.c | 27 +
All supported qemus have this and we already deleted alternate code.
Retire the feature flag.
Signed-off-by: Peter Krempa
---
src/qemu/qemu_capabilities.c | 3 +--
src/qemu/qemu_capabilities.h | 2 +-
tests/qemucapabilitiesdata/caps_10.0.0_
All supported qemu versions now support this. Retire the capability.
Signed-off-by: Peter Krempa
---
src/qemu/qemu_capabilities.c | 6 ++
src/qemu/qemu_capabilities.h | 2 +-
tests/qemucapabilitiesdata/caps_10.0.0_s390x.xml | 1
The capability is no longer used as all qemus already support the
feature.
Signed-off-by: Peter Krempa
---
src/qemu/qemu_capabilities.c | 3 +--
src/qemu/qemu_capabilities.h | 2 +-
tests/qemucapabilitiesdata/caps_10.0.0_s390x.xml |
On Wed, Mar 12, 2025 at 05:31:14PM +0100, Peter Krempa wrote:
> The QAPIfication of objects removed the extra warapper object which we
s/warapper/wrapper/
> were adding in the monitor code to simplify the other callers.
>
> Now that we support only qemus which don't require this we can drop the
'-object' was qapified (meaning it supports JSON props) in qemu-6.0,
thus now that we require qemu-6.2 we can drop the compatibility code.
Signed-off-by: Peter Krempa
---
src/qemu/qemu_command.c | 19 +++
1 file changed, 3 insertions(+), 16 deletions(-)
diff --git a/src/qemu/qem
The capability always exists in qemu and is no longer checked.
Signed-off-by: Peter Krempa
---
src/qemu/qemu_capabilities.c | 9 +
src/qemu/qemu_capabilities.h | 2 +-
tests/qemucapabilitiesdata/caps_10.0.0_s390x.xml | 1 -
It may be desirable to treat transient VMs differently from persistent
VMs. For example, while performing managed save on persistent VMs makes
sense, the same not usually true of transient VMs, since by their
nature they will have no config to restore from.
This also lets us fix a long standing pr
'blockdev-reopen' is supported since qemu-6.1, thus we can now remove
the interlocks.
Document the change to 'mirror' as this patch removes the last clue why
we overwrite the mirror's readonly state to false unconditionally.
Signed-off-by: Peter Krempa
---
src/qemu/qemu_blockjob.c | 11 +-
Currently automatic VM managed save is only performed in session
daemons, on desktop session close, or host OS shutdown request.
With this change it is possible to control shutdown behaviour for
all daemons. A recommended setup might be:
auto_shutdown_try_save = "persistent"
auto_shutdown_try
This series starts the work needed to obsolete the libvirt-guests.sh
script which has grown a surprisingly large amount of functionality.
Currently the virt daemons will acquire inhibitors to delay OS shutdown
when VMs are running. The libvirt-guests.service unit can be used to
call libvirt-guests
Currently the session daemon will try a managed save on all VMs,
leaving them running if that fails.
This limits the managed save just to persistent VMs, as there will
usually not be any way to restore transient VMs later.
It also enables graceful shutdown and then forced poweroff, should
save fa
When performing auto-shutdown of running domains, there is now the
option to mark them as "autostart once", so that their state is
restored on next boot. This applies on top of the traditional
autostart flag.
Reviewed-by: Peter Krempa
Signed-off-by: Daniel P. Berrangé
---
src/hypervisor/domain
> On Thu, Feb 20, 2025 at 11:35:01AM -, honglei.wang(a)smartx.com wrote:
>
> The first approach can be rewritten to the second one and is only an
> easier to write way. I would suggest we use the second one and we can
> add a functionality which will rewrite the first one to the second one
>
On a Wednesday in 2025, Peter Krempa wrote:
While we show the example in the docs we don't have an example XML for
exrecrcising the parser/formatter and schema.
exercising
Signed-off-by: Peter Krempa
---
.../backup-pull-unix.xml | 22 ++
.../backup-pull-u
---
base-commit: e5299ddf86121d3c792ca271ffcb54900eb19dc3
change-id: 20250312-linux-30e6e1af51a5
Best regards,
--
Akihiko Odaki
virnetlink provides stub functions when libnl is not available, but this
approach caused a few problems:
- Commit 582f0966f9b9e2148d8887d072364e2a91aed000 broke builds without
libnl for Linux because virNetlinkBridgeVlanFilterSet() lacked a stub.
- A call to virNetlinkEventServiceStopAll() stub
While we show the example in the docs we don't have an example XML for
exrecrcising the parser/formatter and schema.
Signed-off-by: Peter Krempa
---
.../backup-pull-unix.xml | 22 ++
.../backup-pull-unix.xml | 23 +++
test
When a domain is marked for autostart, it will be started on every
subsequent host OS boot. There may be times when it is desirable to
mark a domain to be autostarted, on the next boot only.
Thus we add virDomainSetAutostartOnce / virDomainGetAutostartOnce.
An alternative would have been to overl
Allow users to control how many seconds libvirt waits for QEMU
shutdown before force powering off a guest.
Reviewed-by: Peter Krempa
Signed-off-by: Daniel P. Berrangé
---
src/qemu/libvirtd_qemu.aug | 1 +
src/qemu/qemu.conf.in | 6 ++
src/qemu/qemu_conf.c
This is a move of the code that currently exists in the QEMU
driver, into the common layer that can be used by multiple
drivers.
The code currently supports performing managed save of all
running guests, ignoring any failures.
Reviewed-by: Peter Krempa
Signed-off-by: Daniel P. Berrangé
---
src
Bypassing cache can make save performance more predictable and avoids
trashing the OS cache with data that will not be read again.
Reviewed-by: Peter Krempa
Signed-off-by: Daniel P. Berrangé
---
src/hypervisor/domain_driver.c | 7 +--
src/hypervisor/domain_driver.h | 1 +
2 files changed, 6
The next patch will be introducing a new callback, so rename the method
to virNetDaemonSetLifecycleCallbacks to reflect the more general usage.
Signed-off-by: Daniel P. Berrangé
---
src/libvirt_remote.syms| 2 +-
src/remote/remote_daemon.c | 6 +++---
src/rpc/virnetdaemon.c | 10 +-
If shutting down running VMs at host shutdown, it can be useful to
automatically start them again on next boot. This adds a config
parameter 'auto_shutdown_restore', which defaults to enabled, which
leverages the autostart once feature.
Reviewed-by: Peter Krempa
Signed-off-by: Daniel P. Berrangé
Reviewed-by: Peter Krempa
Signed-off-by: Daniel P. Berrangé
---
src/qemu/qemu_driver.c | 97 ++
1 file changed, 97 insertions(+)
diff --git a/src/qemu/qemu_driver.c b/src/qemu/qemu_driver.c
index 3932640b79..3b74a98685 100644
--- a/src/qemu/qemu_driver.c
On Wed, Feb 19, 2025 at 22:27:13 +0530, Harikumar Rajkumar wrote:
> From: Chun Feng Wu
>
> ThrottleGroup lifecycle implementation, note, in QOM, throttlegroup name is
> prefixed with
> "throttle-" to clearly separate throttle group objects into their own
> namespace.
> * "qemuDomainSetThrottleG
The preserving of state (ie running VMs) requires a fully functional
daemon and hypervisor driver. If any part has started shutting down
then saving state may fail, or worse, hang.
The current shutdown sequence does not guarantee safe ordering, as
we synchronize with the state saving thread only a
Since processing running VMs on OS shutdown can take a while, it is
beneficial to send systemd status messages about the progress.
The systemd status is a point-in-time message, with no ability to
look at the history of received messages. So in the systemd status
we include the progress informatio
This is maintained in the same way as the autostart flag, using a
symlink. The difference is that instead of '.xml', the symlink
suffix is '.xml.once'. The link is also deleted immediately after
it has been read.
Signed-off-by: Daniel P. Berrangé
---
src/conf/domain_conf.c | 7 ++-
Currently the remote daemon code is responsible for calling virStateStop
in a background thread. The virNetDaemon code wants to synchronize with
this during shutdown, however, so the virThreadPtr must be passed over.
Even the limited synchronization done currently, however, is flawed and
to fix th
It is not documented what the various virStateNNN methods are each
responsible for doing and the names give little guidance either.
Provide some useful documentation comments to explain the intended
usage of each.
Signed-off-by: Daniel P. Berrangé
---
src/libvirt.c | 44 +
The service unit "TimeoutStopSec" setting controls how long systemd
waits for a service to stop before aggressively killing it, defaulting
to 30 seconds if not set.
When we're processing shutdown of VMs in response to OS shutdown, we
very likely need more than 30 seconds to complete this job, and
The call to preserve state (ie running VMs) is triggered in response to
the desktop session dbus terminating (session daemon), or logind sending
a "PrepareForShutdown" signal. In the case of the latter, daemons
should only save their state, not actually exit yet. Other things on the
system may stil
The daemons are wired up to shutdown in responsible to UNIX process
signals, as well as in response to login1 dbus signals, or loss of
desktop session. The latter two options can optionally preserve state
(ie running VMs).
In non-systemd environments, as well as for testing, it would be useful
to
Currently the virStateStop method is only wired up to run save for
the unprivileged daemons, so there is no functional change.
IOW, session exit, or host OS shutdown will trigger VM managed saved
for QEMU session daemon, but not the system daemon.
This changes the daemon code to always run virSta
The recent bump of minimum qemu version resulted into some capabilities
always being present. I've noticed one while doing a review and from
there I removed a few others, mostly storage related ones as well.
Peter Krempa (17):
qemuBuildCompatDeprecatedCommandLine: Assume that
QEMU_CAPS_COMPA
Bumping minimum version of qemu to 6.2 means that the '-compat' option
is now always supported.
As we were unable to detect it in any other way we based this capability
on QEMU_CAPS_OBJECT_JSON.
Signed-off-by: Peter Krempa
---
src/qemu/qemu_command.c | 12 ++--
1 file changed, 2 inserti
It was used to convert JSON arrays in legacy -object commandline
conversion. Since we now exclusively use JSON with -object, this
infrastructure is no longer needed.
Signed-off-by: Peter Krempa
---
src/libvirt_private.syms| 1 -
src/util/virqemu.c | 36 -
The flat mode of 'query-named-block-nodes' is supported since qemu-5.0.
Signed-off-by: Peter Krempa
---
src/qemu/qemu_monitor.c | 1 -
src/qemu/qemu_monitor_json.c | 2 +-
src/qemu/qemu_monitor_priv.h | 2 --
3 files changed, 1 insertion(+), 4 deletions(-)
diff --git a/src/qemu/qemu_monito
The function now serves no real purpose.
Signed-off-by: Peter Krempa
---
src/qemu/qemu_block.c| 3 ---
src/qemu/qemu_domain.c | 14 --
src/qemu/qemu_domain.h | 4
src/qemu/qemu_driver.c | 6 --
src/qemu/qemu_snapshot.c | 4
5 files changed, 31 deletions(-)
qemu supports the @allow-write-only-overlay feature since qemu-5.0.
Remove the alternate code paths.
Signed-off-by: Peter Krempa
---
src/qemu/qemu_block.c| 1 -
src/qemu/qemu_blockjob.c | 9 +++--
src/qemu/qemu_driver.c | 20 ++--
3 files changed, 9 insertions(+), 21
The support for incremental backup (not the backup api itself) was gated
on support for migrating bitmaps. As the ability to migrate bitmaps was
added in qemu-6.0 we can now assume that all supported qemu versions
support incremental backup.
Remove the interlocking.
Signed-off-by: Peter Krempa
-
Hi
On Fri, Mar 7, 2025 at 7:03 PM Martin Kletzander wrote:
>
> On Tue, Feb 18, 2025 at 02:16:25PM +0400, marcandre.lur...@redhat.com wrote:
> >From: Marc-André Lureau
> >
> >Wire the external server RDP support with QEMU.
> >
> >Check the configuration, allocate a port, start the process
> >and
Hi
On Fri, Mar 7, 2025 at 3:58 PM Martin Kletzander wrote:
>
> On Tue, Feb 18, 2025 at 02:16:10PM +0400, marcandre.lur...@redhat.com wrote:
> >From: Marc-André Lureau
> >
> >Without an error message, it can be tedious to figure out failure to
> >start, just fall-through the generic range error.
'blockdev-reopen' is supported since qemu-6.1. Since we now don't have
any code using this capability we can retire it.
Signed-off-by: Peter Krempa
---
src/qemu/qemu_capabilities.c | 6 ++
src/qemu/qemu_capabilities.h | 2 +-
tests/qemu
Hi
On Fri, Mar 7, 2025 at 6:11 PM Martin Kletzander wrote:
>
> On Tue, Feb 18, 2025 at 02:16:20PM +0400, marcandre.lur...@redhat.com wrote:
> >From: Marc-André Lureau
> >
> >Currently, if dbus-daemon writes on errfd, it will SIGPIPE.
> >
> >Signed-off-by: Marc-André Lureau
> >---
> > src/qemu/q
The auto shutdown code can currently only perform managed save,
which may fail in some cases, for example when PCI devices are
assigned. On failure, shutdown inhibitors remain in place which
may be undesirable.
This expands the logic to try a sequence of operations
* Managed save
* Graceful shu
Now that we dropped support for old qemus which didn't support JSON
props for -object we can retire the capability.
Signed-off-by: Peter Krempa
---
src/qemu/qemu_capabilities.c | 3 +--
src/qemu/qemu_capabilities.h | 2 +-
tests/qemucapabil
56 matches
Mail list logo