[libvirt] [PATCH for 6.0.0] news: Document <disk type='nvme'/>

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 <disk/> with the <source/> + pointing to the <code>/dev/nvmeXXXX</code>. The other was using PCI + assignment via <hostdev/> 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 <disk type='nvme'/>. + </description> + </change> </section> <section title="Removed features"> <change> -- 2.24.1

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 <disk/> with the <source/>
Extra whitespace here. Reviewed-by: Andrea Bolognani <abologna@redhat.com> -- Andrea Bolognani / Red Hat / Virtualization
participants (2)
-
Andrea Bolognani
-
Michal Privoznik