Can't add NFS Remote

[runevn]

I have a NFS share that I have tried to add as a remote. I can add it and it stays as enabled but with a red warning icon besides and in the log I have the error below.

remote.test
{
  "id": "874b15c5-e92a-4503-9efd-e5459406b101"
}
{
  "shortMessage": "Command failed with exit code 32: mount -o vers=3 -t nfs 192.168.99.1:/mnt/storagepool/vmbackup /run/xo-server/mounts/874b15c5-e92a-4503-9efd-e5459406b101",
  "command": "mount -o vers=3 -t nfs 192.168.99.1:/mnt/storagepool/vmbackup /run/xo-server/mounts/874b15c5-e92a-4503-9efd-e5459406b101",
  "exitCode": 32,
  "stdout": "",
  "stderr": "mount.nfs: Connection timed out",
  "failed": true,
  "timedOut": false,
  "isCanceled": false,
  "killed": false,
  "message": "Command failed with exit code 32: mount -o vers=3 -t nfs 192.168.99.1:/mnt/storagepool/vmbackup /run/xo-server/mounts/874b15c5-e92a-4503-9efd-e5459406b101
mount.nfs: Connection timed out",
  "name": "Error",
  "stack": "Error: Command failed with exit code 32: mount -o vers=3 -t nfs 192.168.99.1:/mnt/storagepool/vmbackup /run/xo-server/mounts/874b15c5-e92a-4503-9efd-e5459406b101
mount.nfs: Connection timed out
    at makeError (/home/rvn/xen-orchestra/node_modules/execa/lib/error.js:59:11)
    at handlePromise (/home/rvn/xen-orchestra/node_modules/execa/index.js:114:26)
    at NfsHandler._sync (/home/rvn/xen-orchestra/@xen-orchestra/fs/src/_mount.js:64:7)
    at NfsHandler.sync (/home/rvn/xen-orchestra/@xen-orchestra/fs/src/abstract.js:316:5)
    at _class2.getRemoteHandler (/home/rvn/xen-orchestra/packages/xo-server/src/xo-mixins/remotes.js:76:9)
    at _class2.testRemote (/home/rvn/xen-orchestra/packages/xo-server/src/xo-mixins/remotes.js:97:11)
    at Api.callApiMethod (/home/rvn/xen-orchestra/packages/xo-server/src/xo-mixins/api.js:304:20)"
}

I'm running the community edition (build from source) of XO (xo-server 5.76.0) and (xo-web 5.78.1). I have two other NFS shares (ISO SR and a NFS SR) on this XO that works fine.

XO is running on a Debian 10 VM with the nfs-common package installed.

Any idea of what cause the error?

[jedimarcus]

@runevn
Does

showmount -e 192.168.99.1

work?

No messing around with jumbo frames or something?

[runevn]

@jedimarcus - thanks for your reply. No jumbo frames

[08:00 vmhost ~]# showmount -e 192.168.99.1
Export list for 192.168.99.1:
/mnt/storagepool/vmbackup  192.168.99.0
/mnt/storagepool/vmstorage 192.168.99.0
/mnt/storagepool/nfs-share 192.168.99.0
/mnt/storagepool/isodisk   192.168.99.0
[08:00 vmhost ~]# 

[runevn]

@jedimarcus maybe I found the error. I ran showmount -e 192.168.99.1
on my XCP-NG host and not on my XO VM. So I guess that this is the issue?

However, NFS server (TrueNAS 192.168.99.1/30) is directly connected (no switch inbetween) to my XCP-NG host (192.168.99.2/30) on eth1.

This might be a stupid question but, how should I add the NIC to my XO VM?

If I add/create eth1 to the XO VM what IP should I assign to it?

Because both XCP-NG and TrueNAS are directly connected. I guess that giving the XO VM the IP of 192.168.99.2 will conflict with XCP-NG's IP? Or are there something that I'm totally missing here? ... there probably is

Once again, thanks for your help I really appreciate it!

[olivierlambert]

A remote is mounted from XO virtual Appliance (XOA), not from your host.

So you need to add an interface in that network, and create a fixed IP that can reach your TrueNas.

[runevn]

@olivierlambert Thanks! I did that and now it is just works.

Thanks for the help!