[PATCH] NEWS: Fix indentation
by Andrea Bolognani
Signed-off-by: Andrea Bolognani <abologna(a)redhat.com>
---
Pushed as trivial.
NEWS.rst | 39 ++++++++++++++++++++-------------------
1 file changed, 20 insertions(+), 19 deletions(-)
diff --git a/NEWS.rst b/NEWS.rst
index c0a6d180a2..dc40602c72 100644
--- a/NEWS.rst
+++ b/NEWS.rst
@@ -176,10 +176,10 @@ v9.6.0 (2023-08-01)
* ``CVE-2023-3750``: Fix race condition in storage driver leading to a crash
- In **libvirt-8.3** a bug was introduced which in rare cases could cause
- ``libvirtd`` or ``virtstoraged`` to crash if multiple clients attempted to
- look up a storage volume by key, path or target path, while other clients
- attempted to access something from the same storage pool.
+ In **libvirt-8.3** a bug was introduced which in rare cases could cause
+ ``libvirtd`` or ``virtstoraged`` to crash if multiple clients attempted to
+ look up a storage volume by key, path or target path, while other clients
+ attempted to access something from the same storage pool.
* **Improvements**
@@ -1983,17 +1983,17 @@ v7.1.0 (2021-03-01)
* qemu: Fix disk quiescing rollback when creating external snapshots
- If the qemu guest agent call to freeze filesystems failed when creating
- an external snapshot with ``VIR_DOMAIN_SNAPSHOT_CREATE_QUIESCE`` flag the
- filesystems would be unconditionally thawed. This could cause problems when
- the filesystems were frozen by an explicit call to ``virDomainFSFreeze``
- since the guest agent then rejects any further freeze attempts once are
- filesystems frozen, an explicit freeze followed by a quiesced snapshot
- would fail and thaw filesystems.
+ If the qemu guest agent call to freeze filesystems failed when creating
+ an external snapshot with ``VIR_DOMAIN_SNAPSHOT_CREATE_QUIESCE`` flag the
+ filesystems would be unconditionally thawed. This could cause problems when
+ the filesystems were frozen by an explicit call to ``virDomainFSFreeze``
+ since the guest agent then rejects any further freeze attempts once are
+ filesystems frozen, an explicit freeze followed by a quiesced snapshot
+ would fail and thaw filesystems.
- Users are also encouraged to use ``virDomainFSFreeze/Thaw`` manually instead
- of relying on ``VIR_DOMAIN_SNAPSHOT_CREATE_QUIESCE`` if they need finer
- grained control.
+ Users are also encouraged to use ``virDomainFSFreeze/Thaw`` manually instead
+ of relying on ``VIR_DOMAIN_SNAPSHOT_CREATE_QUIESCE`` if they need finer
+ grained control.
* cgroups: Fix how we setup and configure cgroups on hosts with systemd
@@ -2155,11 +2155,12 @@ v6.10.0 (2020-12-01)
* qemu: Enable client TLS certificate validation by default for ``chardev``,
``migration``, and ``backup`` servers.
- The default value if qemu.conf options ``chardev_tls_x509_verify``,
- ``migrate_tls_x509_verify``, or ``backup_tls_x509_verify`` are not specified
- explicitly in the config file and also the ``default_tls_x509_verify`` config
- option is missing are now '1'. This ensures that only legitimate clients
- access servers, which don't have any additional form of authentication.
+ The default value if qemu.conf options ``chardev_tls_x509_verify``,
+ ``migrate_tls_x509_verify``, or ``backup_tls_x509_verify`` are not
+ specified explicitly in the config file and also the
+ ``default_tls_x509_verify`` config option is missing are now '1'. This
+ ensures that only legitimate clients access servers, which don't have any
+ additional form of authentication.
* qemu: Introduce "migrate_tls_force" qemu.conf option
--
2.43.0
5 months, 2 weeks
[PATCH] NEWS: Fix vertical spacing
by Andrea Bolognani
Signed-off-by: Andrea Bolognani <abologna(a)redhat.com>
---
Pushed as trivial.
NEWS.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/NEWS.rst b/NEWS.rst
index 29b977565b..c0a6d180a2 100644
--- a/NEWS.rst
+++ b/NEWS.rst
@@ -89,6 +89,7 @@ v9.9.0 (2023-11-01)
The ``virsh create --console`` now tries to connect to the guest console
before starting the vCPUs.
+
v9.8.0 (2023-10-02)
===================
@@ -131,6 +132,7 @@ v9.8.0 (2023-10-02)
Now libvirt validates more values of virtio-mem and virtio-pmem devices,
e.g. overlapping memory addresses or alignment.
+
v9.7.0 (2023-09-01)
===================
@@ -2549,7 +2551,6 @@ v6.6.0 (2020-08-02)
management applications may wish to override this behaviour. This is now
possible via new ``cow`` element.
-
* **Improvements**
* esx: Change the NIC limit for recent virtualHW versions
@@ -2574,7 +2575,6 @@ v6.6.0 (2020-08-02)
instead of all possible CPUs are returned making these APIs consistent with
the behavior of ``vcpuinfo``.
-
* **Bug fixes**
* virdevmapper: Don't use libdevmapper to obtain dependencies
--
2.43.0
5 months, 2 weeks
Release of libvirt-9.10.0
by Jiri Denemark
The 9.10.0 release of both libvirt and libvirt-python is tagged and
signed tarballs and source RPMs are available at
https://download.libvirt.org/
https://download.libvirt.org/python/
Thanks everybody who helped with this release by sending patches,
reviewing, testing, or providing feedback. Your work is greatly
appreciated.
* New features
* Introduce pipewire audio backend
The QEMU hypervisor driver now allows setting ``pipewire`` backend for
``<audio/>`` device.
* Improvements
* Adapt to qemu's use of protocol drivers in QCOW2 'backing file format' field
QEMU allows creating images where the 'backing file format' is actually a
protocol name such as 'file'/'host_device'/'nbd'/etc.. Adapt libvirt to
properly handle such images and don't assume automatic format probing is
necessary, which is in many cases forbidden due to security implications.
* Bug fixes
* qemu: Fix setup of images on hotplug of disk
Internal image metadata was not setup correctly which could cause some disk
hotplug configurations (namely those including backing images) to fail.
* qemu: Fix qemu crash when reverting an internal snapshot
Libvirt attempted to start qemu with wrong arguments when attempting to
revert to an internal snapshot causing qemu to crash.
* qemu: Fix hotplug of empty cdrom
Empty cdrom drive couldn't be hotplugged as libvirt wanted to setup the
storage backing it unconditionally.
Enjoy.
Jirka
5 months, 2 weeks
[PATCH 0/2] Report better error message with no socket to connect to
by Martin Kletzander
When opening a libvirt connection with no URI set and no daemon running the
error message might be confusing at times, so these patches are trying to
mitigate such confusion.
Martin Kletzander (2):
Report first tried socket from remoteProbeSystemDriverFromSocket
Report better error message in remoteGetUNIXSocket
src/remote/remote_daemon_dispatch.c | 2 +-
src/remote/remote_sockets.c | 22 ++++++++++++++++++----
src/remote/remote_sockets.h | 2 +-
3 files changed, 20 insertions(+), 6 deletions(-)
--
2.43.0
5 months, 2 weeks
[PATCH] NEWS: Mention image probing, snaphsot and hotplug fixes
by Peter Krempa
Signed-off-by: Peter Krempa <pkrempa(a)redhat.com>
---
NEWS.rst | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/NEWS.rst b/NEWS.rst
index f12734c2a1..9739bcdc36 100644
--- a/NEWS.rst
+++ b/NEWS.rst
@@ -24,8 +24,30 @@ v9.10.0 (unreleased)
* **Improvements**
+ * Adapt to qemu's use of protocol drivers in QCOW2 'backing file format' field
+
+ QEMU allows creating images where the 'backing file format' is actually a
+ protocol name such as 'file'/'host_device'/'nbd'/etc.. Adapt libvirt to
+ properly handle such images and don't assume automatic format probing is
+ necessary, which is in many cases forbidden due to security implications.
+
* **Bug fixes**
+ * qemu: Fix setup of images on hotplug of disk
+
+ Internal image metadata was not setup correctly which could cause some disk
+ hotplug configurations (namely those including backing images) to fail.
+
+ * qemu: Fix qemu crash when reverting an internal snapshot
+
+ Libvirt attempted to start qemu with wrong arguments when attempting to
+ revert to an internal snapshot causing qemu to crash.
+
+ * qemu: Fix hotplug of empty cdrom
+
+ Empty cdrom drive couldn't be hotplugged as libvirt wanted to setup the
+ storage backing it unconditionally.
+
v9.9.0 (2023-11-01)
===================
--
2.43.0
5 months, 2 weeks
[PATCH for 9.9.0] qemuProcessStartWithMemoryState: Don't start qemu with '-loadvm SNAP' and '-incoming defer' together
by Peter Krempa
A bug in qemuProcessStartWithMemoryState caused that we would start qemu
with '-loadvm SNAP' and '-incoming defer' together. qemu doesn't expect
that and crashes on an assertion failure [1].
[1]: https://issues.redhat.com/browse/RHEL-16782
Fixes: 8a88d3e5860881f430e528d3e5e8d6455ded4d1d
Resolves: https://issues.redhat.com/browse/RHEL-17841
Signed-off-by: Peter Krempa <pkrempa(a)redhat.com>
---
src/qemu/qemu_process.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/src/qemu/qemu_process.c b/src/qemu/qemu_process.c
index f32e82bbd1..fc05b4b24f 100644
--- a/src/qemu/qemu_process.c
+++ b/src/qemu/qemu_process.c
@@ -8196,6 +8196,7 @@ qemuProcessStartWithMemoryState(virConnectPtr conn,
VIR_AUTOCLOSE intermediatefd = -1;
g_autoptr(virCommand) cmd = NULL;
g_autofree char *errbuf = NULL;
+ const char *migrateFrom = NULL;
int rc = 0;
if (data) {
@@ -8207,6 +8208,8 @@ qemuProcessStartWithMemoryState(virConnectPtr conn,
&errbuf, &cmd) < 0) {
return -1;
}
+
+ migrateFrom = "stdio";
}
/* No cookie means libvirt which saved the domain was too old to mess up
@@ -8220,7 +8223,7 @@ qemuProcessStartWithMemoryState(virConnectPtr conn,
priv->disableSlirp = true;
if (qemuProcessStart(conn, driver, vm, cookie ? cookie->cpu : NULL,
- asyncJob, "stdio", *fd, path, snapshot,
+ asyncJob, migrateFrom, *fd, path, snapshot,
VIR_NETDEV_VPORT_PROFILE_OP_RESTORE,
start_flags) == 0)
*started = true;
--
2.43.0
5 months, 2 weeks
