mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2025-02-22 19:32:19 +00:00
news: Update for libvirt 6.2.0
Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
This commit is contained in:
parent
29fc9e96a9
commit
2476bd9d74
@ -55,6 +55,27 @@
|
|||||||
automatically.
|
automatically.
|
||||||
</description>
|
</description>
|
||||||
</change>
|
</change>
|
||||||
|
<change>
|
||||||
|
<summary>
|
||||||
|
qemu: Add virtiofs support
|
||||||
|
</summary>
|
||||||
|
<description>
|
||||||
|
This feature, introduced in QEMU 4.2, is a more modern alternative
|
||||||
|
to virtio-9p, which is exposed through the same
|
||||||
|
<code><filesystem/></code> element.
|
||||||
|
</description>
|
||||||
|
</change>
|
||||||
|
<change>
|
||||||
|
<summary>
|
||||||
|
admin: Support reloading TLS certificates
|
||||||
|
</summary>
|
||||||
|
<description>
|
||||||
|
After renewing TLS certificates, it was usually necessary to restart
|
||||||
|
libvirtd for the new ones to be loaded: now the same result can be
|
||||||
|
obtained without restarting the daemon by using <code>virt-admin
|
||||||
|
server-update-tls</code>.
|
||||||
|
</description>
|
||||||
|
</change>
|
||||||
</section>
|
</section>
|
||||||
<section title="Removed features">
|
<section title="Removed features">
|
||||||
<change>
|
<change>
|
||||||
@ -70,6 +91,29 @@
|
|||||||
</change>
|
</change>
|
||||||
</section>
|
</section>
|
||||||
<section title="Improvements">
|
<section title="Improvements">
|
||||||
|
<change>
|
||||||
|
<summary>
|
||||||
|
qemu: Don't compare local and remote hostnames on migration
|
||||||
|
</summary>
|
||||||
|
<description>
|
||||||
|
This check was introduced to prevent same-host migration, but did
|
||||||
|
not work as expected when multiple libvirtd instances were running
|
||||||
|
on the same host but in different containers. With this release, the
|
||||||
|
host UUID (which should be unique to the container) is checked
|
||||||
|
instead.
|
||||||
|
</description>
|
||||||
|
</change>
|
||||||
|
<change>
|
||||||
|
<summary>
|
||||||
|
qemu: Use per-VM event loops
|
||||||
|
</summary>
|
||||||
|
<description>
|
||||||
|
Instead of using a single even loop to process communication with
|
||||||
|
the QEMU monitor and guest agent, create a separate one for each VM.
|
||||||
|
This helps with scalability and prevents scenarios where a single
|
||||||
|
malfunctioning VM could affect all those running on the same host.
|
||||||
|
</description>
|
||||||
|
</change>
|
||||||
</section>
|
</section>
|
||||||
<section title="Bug fixes">
|
<section title="Bug fixes">
|
||||||
<change>
|
<change>
|
||||||
@ -90,6 +134,16 @@
|
|||||||
QEMU-4.2.
|
QEMU-4.2.
|
||||||
</description>
|
</description>
|
||||||
</change>
|
</change>
|
||||||
|
<change>
|
||||||
|
<summary>
|
||||||
|
Don't generate machine names containing dots
|
||||||
|
</summary>
|
||||||
|
<description>
|
||||||
|
Even though the guest name containing dots is not a problem for
|
||||||
|
libvirt itself, we need to strip them out when registering with
|
||||||
|
machined because of the latter's requirements.
|
||||||
|
</description>
|
||||||
|
</change>
|
||||||
</section>
|
</section>
|
||||||
</release>
|
</release>
|
||||||
<release version="v6.1.0" date="2020-03-03">
|
<release version="v6.1.0" date="2020-03-03">
|
||||||
|
Loading…
x
Reference in New Issue
Block a user