@olivierlambert Thanks! I did that and now it is just works.
Thanks for the help!
@olivierlambert Thanks! I did that and now it is just works.
Thanks for the help!
Wow - you guys where right. I had a Raspberry pi running with that address on my network. Sorry for the inconvenience and thanks for your help.
@olivierlambert Thanks! I did that and now it is just works.
Thanks for the help!
@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!
@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 ~]#
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 Okay - and once again. Thanks for your help.
@jedimarcus By the way, my pfSense box has an intel 4x1Gb ethernet card. Would it be preferred/best practice to connect one of the pfSense NICs directly to an available NIC on my XCP-NG host and then assign this specific NIC to the exposed VMs? Or shouldn't I bother?
Thanks
@jedimarcus Thanks for your reply. Yes, you answer my question. I don't need to physical separated hosts VLAN is sufficient.
Thanks a lot for taken your time to answer my questions.
I'm a homelab'er enjoying learning and tinkering with networking and servers, and still learning a lot so please bear over with my trivial question.
Now the time has come where I might want to create some VMs that I would like to expose to the internet, if I do not put my whole network into a huge security risk.
My kids plays minecraft and I think it would a fun project to give them a server for them and their friends to join. Furthermore I would like to host a simpel webserver for a presentation site (wordpress).
My setup is as follows:
However, before I proceed my project I have the following question/considerations:
What I understand is that I should create a DMZ for servers exposed to the internet and that these servers should be on a separat physical network.
So I guess that having the server VMs on a separated VLAN in XCP-NG is not secure enough? Or would you consider having the server VMs on the same XCP-NG host secure enough as long as their NIC are separated on VLANS? Or should I purchase another host for the exposed servers? Or is it even the recommendation that I acutally get another WAN connection into my home to compeletely separate the networks?
I understand that nothing is 100% secure but would you please share your thoughts and considerations on exposing servers as a homelab'er provides a significant security risk? Is this something other homelab'ers do or is hosting servers only a thing established and professional companies should do?
I know that this question could be posted on other forums but I thought that as I'm running XCP-NG I might as well ask here.
Thanks in advance for comments and replies.
I found the solution. I had to press enter during the boot to boot into the "CD-ROM drive".
I'm sorry for this novel question, but have trouble finding a solution for this issue.
I have created a Windows 10 VM in XO but when it boots for the first time it boots directly into the UEFI Interactive Shell.

I have tried to change boot firmware to bios and uefi. I have also tried to delete the VM and recreated it using bios boot option in the setup screen. But without any luck.
Any help is highly appreciated.
I'm running XCP-NG 8.2 on a Dell r630.