Libguestfs - Aug 2018 - [PATCH nbdkit] vddk: Document issue with out of memory errors

Note this fix is incomplete / not ready for upstream:

(1) We haven't definitively proven this is the issue.  Mor is
still investigating and producing the proof.

(2) We will need to make a similar change to virt-v2v documentation.

Rich.

Thanks: Mor Kalfon, Tomáš Golembiovský.
---
 plugins/vddk/nbdkit-vddk-plugin.pod | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)

diff --git a/plugins/vddk/nbdkit-vddk-plugin.pod
b/plugins/vddk/nbdkit-vddk-plugin.pod
index 7e7053c..57a371a 100644
--- a/plugins/vddk/nbdkit-vddk-plugin.pod
+++ b/plugins/vddk/nbdkit-vddk-plugin.pod
@@ -325,6 +325,35 @@ For VMs with multiple disks, it would be nice to map the
disk names to
 NBD export names.  However nbdkit core will need to be extended to
 support this.
 
+=head2 Out of memory errors
+
+In the verbose log you may see errors like:
+
+ nbdkit: vddk[3]: error: [NFC ERROR] NfcFssrvrProcessErrorMsg:
+ received NFC error 5 from server: Failed to allocate the
+ requested 2097176 bytes
+
+This seems especially common when there are multiple parallel
+connections open to the VMware server.
+
+These can be caused by resource limits set on the VMware server.  You
+can increase the limit for the NFC service by editing
+F</etc/vmware/hostd/config.xml> and adjusting the
+C<E<lt>maxMemoryE<gt>> setting:
+
+ <nfcsvc>
+   <path>libnfcsvc.so</path>
+   <enabled>true</enabled>
+   <maxMemory>50331648</maxMemory>
+   <maxStreamMemory>10485760</maxStreamMemory>
+ </nfcsvc>
+
+and restarting the C<hostd> service:
+
+ # /etc/init.d/hostd restart
+
+For more information see L<https://bugzilla.redhat.com/1614276>.
+
 =head1 SEE ALSO
 
 L<nbdkit(1)>,
-- 
2.18.0