Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
---
 docs/news.xml | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/docs/news.xml b/docs/news.xml
index acb63709da..e9863dacf3 100644
--- a/docs/news.xml
+++ b/docs/news.xml
@@ -106,6 +106,22 @@
           hostname and the information stored in its TLS certificate.
         </description>
       </change>
+      <change>
+        <summary>
+          qemu: Allow accessing NVMe disks directly
+        </summary>
+        <description>
+          Before this release there were two ways to configure a NVMe disk for
+          a domain.  The first was using &lt;disk/&gt; with the &lt;source/&gt;
+          pointing to the <code>/dev/nvmeXXXX</code>. The other was using PCI
+          assignment via &lt;hostdev/&gt; element. Both have their
+          disadvantages: the former adds latency of file system and block
+          layers of the host kernel, the latter prohibits domain migration. In
+          this release the third way of configuring NVMe disk is added which
+          combines the advantages and drops disadvantages of the previous two
+          ways. It's accessible via &lt;disk type='nvme'/&gt;.
+        </description>
+      </change>
     </section>
     <section title="Removed features">
       <change>
-- 
2.24.1

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

On Tue, 2020-01-14 at 09:25 +0100, Michal Privoznik wrote:
> +      <change>
> +        <summary>
> +          qemu: Allow accessing NVMe disks directly
> +        </summary>
> +        <description>
> +          Before this release there were two ways to configure a NVMe disk for
> +          a domain.  The first was using &lt;disk/&gt; with the &lt;source/&gt;

Extra whitespace here.

Reviewed-by: Andrea Bolognani <abologna@redhat.com>

-- 
Andrea Bolognani / Red Hat / Virtualization

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list