Document the addition of vsock.

Signed-off-by: Ján Tomko <jtomko@redhat.com>
---
 docs/news.xml | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/docs/news.xml b/docs/news.xml
index 453ac1d02a..a2829eff6a 100644
--- a/docs/news.xml
+++ b/docs/news.xml
@@ -113,6 +113,15 @@
           libvirt has done as well.
         </description>
       </change>
+      <change>
+        <summary>
+          qemu: add support for vhost-vsock-device
+        </summary>
+        <description>
+          A new vsock device was introduced, allowing communication between
+          the guest and the host via the AF_VSOCK family.
+        </description>
+      </change>
     </section>
     <section title="Improvements">
       <change>
-- 
2.16.1

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

On Fri, Jun 01, 2018 at 13:36:05 +0200, Ján Tomko wrote:
> Document the addition of vsock.
> 
> Signed-off-by: Ján Tomko <jtomko@redhat.com>
> ---
>  docs/news.xml | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> diff --git a/docs/news.xml b/docs/news.xml
> index 453ac1d02a..a2829eff6a 100644
> --- a/docs/news.xml
> +++ b/docs/news.xml
> @@ -113,6 +113,15 @@
>            libvirt has done as well.
>          </description>
>        </change>
> +      <change>
> +        <summary>
> +          qemu: add support for vhost-vsock-device

I think the more interresting part is the AF_VSOCK transport than the
device itself.

> +        </summary>
> +        <description>
> +          A new vsock device was introduced, allowing communication between
> +          the guest and the host via the AF_VSOCK family.
> +        </description>
> +      </change>

ACK, our news are not regular-human-friendly anyways.
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list