kbase: Document minimal libvirt version for NUMA-less virtiofs

Using virtiofs without NUMA was implemented in v6.9.0-rc1~161 but
our kbase document only mentions QEMU version which may confuse
users.

Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>

diff --git a/docs/kbase/virtiofs.rst b/docs/kbase/virtiofs.rst
index 01440420d76dfae9accaf3442a18748ca51697c9..c0bc07a68d2106fe902f1156a36d9a23c50105a5 100644 (file)
--- a/docs/kbase/virtiofs.rst
+++ b/docs/kbase/virtiofs.rst
@@ -25,8 +25,9 @@ means that QEMU needs to allocate the backing memory for all the guest
 RAM as shared memory. As of QEMU 4.2, it is possible to explicitly
 specify a memory backend when specifying the NUMA topology. This
 method is however only viable for machine types that do support
-NUMA. As of QEMU 5.0.0, it is possible to specify the memory backend
-without NUMA (using the so called memobject interface).
+NUMA. As of QEMU 5.0.0 and libvirt 6.9.0, it is possible to
+specify the memory backend without NUMA (using the so called
+memobject interface).
 
 Either of the following: