From 01efbc62c453a52ccd3c7ca9edcb85242207967f Mon Sep 17 00:00:00 2001 From: Geoffrey McRae Date: Fri, 8 Mar 2024 18:34:22 +1100 Subject: [PATCH] [doc] fix typos (again) --- doc/ivshmem_kvmfr.rst | 2 +- doc/ivshmem_shm.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/ivshmem_kvmfr.rst b/doc/ivshmem_kvmfr.rst index 450f99f3..15732304 100644 --- a/doc/ivshmem_kvmfr.rst +++ b/doc/ivshmem_kvmfr.rst @@ -109,7 +109,7 @@ You should now also have the character device ``/dev/kvmfr0`` If you start the VM prior to loading the module, QEMU will create the file ``/dev/kvmfr0`` as a regular file. You can confirm if this has happened by - running ``ls -l /dev/kvmfr0`` and checking if the filesize is greater then + running ``ls -l /dev/kvmfr0`` and checking if the file size is greater then zero, or the permissions do not start with ``c``. If this has occurred, you must delete the file and reload the module. diff --git a/doc/ivshmem_shm.rst b/doc/ivshmem_shm.rst index 234e5933..15794c5e 100644 --- a/doc/ivshmem_shm.rst +++ b/doc/ivshmem_shm.rst @@ -6,7 +6,7 @@ IVSHMEM with standard shared memory This method is here for those that can not use the KVMFR kernel module. Please be aware that as a result you will not be able to take advantage of your GPUs -abilit to access memory via it's hardware DMA engine if you use this method. +ability to access memory via it's hardware DMA engine if you use this method. Add the following to your libvirt machine configuration inside the 'devices' section by running ``virsh edit `` where ```` is the name of