[libvirt] [PATCH for 5.1.0] news: Update for 5.1.0 release
Michal Privoznik
mprivozn at redhat.com
Thu Feb 28 10:43:56 UTC 2019
Not exhaustive list of new features, improvements and bugfixes.
Signed-off-by: Michal Privoznik <mprivozn at redhat.com>
---
docs/news.xml | 201 ++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 201 insertions(+)
diff --git a/docs/news.xml b/docs/news.xml
index 9c5ae7e8a3..813f1a93e3 100644
--- a/docs/news.xml
+++ b/docs/news.xml
@@ -69,8 +69,104 @@
Model Specific Registers (MSRs) reads and writes.
</description>
</change>
+ <change>
+ <summary>
+ qemu: add support for encrypted VNC TLS keys
+ </summary>
+ <description>
+ Use the password stored in the secret driver under the uuid
+ specified by the vnc_tls_x509_secret_uuid option in qemu.conf.
+ </description>
+ </change>
+ <change>
+ <summary>
+ Add storage pool namespace options
+ </summary>
+ <description>
+ Allow for adjustment of RBD configuration options via Storage
+ Pool XML Namespace adjustments.
+ </description>
+ </change>
+ <change>
+ <summary>
+ qemu: Add support for setting post-copy migration bandwidth
+ </summary>
+ <description>
+ Users can now limit the bandwidth of post-copy migration, e.g.
+ via <code>virsh migrate --postcopy-bandwidth</code>.
+ </description>
+ </change>
</section>
<section title="Improvements">
+ <change>
+ <summary>
+ Create private chains for virtual network firewall rules
+ </summary>
+ <description>
+ Historically firewall rules for virtual networks were added
+ straight into the base chains. This works but has a number of
+ bugs and design limitations. To address them, libvirt now puts
+ firewall rules into its own chains.
+ </description>
+ </change>
+ <change>
+ <summary>
+ Detect CEPH and GPFS as shared FS
+ </summary>
+ <description>
+ When starting a migration libvirt does some sanity checks to
+ make sure domain will be able to run on destination. One of
+ requirements is that disk has to either be migrated too or
+ live on network filesystem. CEPH and GPFS weren't detected as
+ a network filesystem.
+ </description>
+ </change>
+ <change>
+ <summary>
+ Advertise network MTU via DHCP when specified
+ </summary>
+ <description>
+ If network MTU is set and the network has DHCP enabled,
+ advertise the MTU in DHCP transaction too so that clients can
+ adjust their link accordingly.
+ </description>
+ </change>
+ <change>
+ <summary>
+ Allocate qemu memory at the configured NUMA nodes from start
+ </summary>
+ <description>
+ Libvirt used to just start qemu, let it allocate memory for
+ the guest and then use CGroups to move the memory to
+ configured NUMA nodes. This is suboptimal as huge chunks of
+ memory have to be moved. Moreover, this relies on ability to
+ move memory later which is not always true. Set process
+ affinity corretly from the start so that memory is allocated
+ on the configured nodes from the beginning.
+ </description>
+ </change>
+ <change>
+ <summary>
+ Support for newer wireshark
+ </summary>
+ <description>
+ Wireshark supports out of tree builds of dissectors since its
+ 2.5.0 release. Adapt libvirt to that. This affects minimal
+ required version then too.
+ </description>
+ </change>
+ <change>
+ <summary>
+ More use of VIR_AUTOFREE() and friends
+ </summary>
+ <description>
+ Usuaully, this would be viewed as an internal change that
+ should not concern users. However, since libvirt is written in
+ memory unsafe language some memory leaks might have been
+ actually fixed by using VIR_AUTOFREE(). It is definitely step
+ towards defensive programming.
+ </description>
+ </change>
</section>
<section title="Bug fixes">
<change>
@@ -133,6 +229,111 @@
attribute of the network bridge element).
</description>
</change>
+ <change>
+ <summary>
+ Refresh block jobs on daemon restart
+ </summary>
+ <description>
+ In case the daemon is restarted it now fetches new state of
+ blockjobs. This means that libvirt does not lose track of
+ block jobs anymore.
+ </description>
+ </change>
+ <change>
+ <summary>
+ qemu: Fix i6300esb watchdog hotplug on Q35
+ </summary>
+ <description>
+ Due to a bug libvirt was not allocating PCI address for
+ watchdog device nor it was telling it to qemu. This lead qemu
+ to chose one (the lowest one) which might not be hotpluggable.
+ </description>
+ </change>
+ <change>
+ <summary>
+ lxc: Don't reboot host on virDomainReboot
+ </summary>
+ <description>
+ If the container is really a simple one (init is just bash and
+ the whole root is passed through) then virDomainReboot and
+ virDomainShutdown would reboot or shutdown the host. The
+ solution is to use different method to reboot or shutdown the
+ container in that case (e.g. signal).
+ </description>
+ </change>
+ <change>
+ <summary>
+ rpc: Various stream fixes
+ </summary>
+ <description>
+ One particular race was fixed, one locking problem and error
+ reporting from streams was made better.
+ </description>
+ </change>
+ <change>
+ <summary>
+ qemu: Fix guestfwd hotplug/hotunplug
+ </summary>
+ <description>
+ Unaware to libvirt developers whether somebody actually uses
+ guestfwd, it's hotplug and hotunplug was fixed. Libvirt used
+ to use incorrect monitor command.
+ </description>
+ </change>
+ <change>
+ <summary>
+ qemu: Forbid cdroms on virtio bus
+ </summary>
+ <description>
+ Attempting to create an empty virtio-blk drive or attempting
+ to eject it results into an error. Forbid configurations
+ where users would attempt to use cdroms in virtio bus.
+ </description>
+ </change>
+ <change>
+ <summary>
+ qemu: Use 'raw' for 'volume' disks without format
+ </summary>
+ <description>
+ Storage pools might want to specify format of the image when
+ translating the volume thus libvirt can't add any default
+ format when parsing the XML. Add an explicit format when
+ starting the VM and format is not present neither by user
+ specifying it nor by the storage pool translation function.
+ </description>
+ </change>
+ <change>
+ <summary>
+ qemu: domain: Assume 'raw' default storage format also for network storage
+ </summary>
+ <description>
+ Post parse callback adds the 'raw' type only for local files.
+ Remote files can also have backing store (even local) so we
+ should do this also for network backed storage.
+ </description>
+ </change>
+ <change>
+ <summary>
+ qemu: Fix block job progress reporting and advocate for READY event
+ </summary>
+ <description>
+ In some cases qemu can get to 100% and still not reach the
+ synchronised phase. Initiating a pivot in that case will fail.
+ Therefore it is strongly adviced to wait for
+ VIR_DOMAIN_BLOCK_JOB_READY event which does not suffer from
+ this problem.
+ </description>
+ </change>
+ <change>
+ <summary>
+ qemu: Don't format image properties for empty -drive
+ </summary>
+ <description>
+ If a -drive has no image, using image properties makes qemu
+ whine that they should not be used. Stop formatting attributes
+ like cache/readonly/... in that case.
+ </description>
+ </change>
</section>
</release>
<release version="v5.0.0" date="2019-01-15">
--
2.19.2
More information about the libvir-list
mailing list