https://github.com/xcp-ng/xcp/wiki/FreeNAS-as-Storage-Repository-(SR)

Did you: Check the All dirs option

@ivan I asked almost the same question some time ago (it was 8.2 to 7.5).

Don't try to mess around:

• Install XOA/XOCE
• Connect it to the 2 pools
• Create a remote for you backup
• Backup the VM to that remote (8.1 Pool)
• Restore the VM (to the 7.5 Pool)
• That should work without an issue

There is certainly another way, but XOA is your golden hammer, use that one, instead of the rusty shovel next to it. It will make your life so much easier.

@runevn I think that comes down to personal preference... my XCP-ng boxes have 9 NICs XD

Any solution is OK if bandwidth is not the issue.

@runevn if you aware that there is no 100% security, that's a good start.

You can have VMs in different networks on the same XCP-ng hosts, that's why you have VLANs and stuff.

Just create a VLAN "DMZ" for your publicly exposed VMs and route and firewall that in pfsense accordingly.

Since your dom0 and other VMs will be in another VLAN "Home Network" or whatever, there will not be a major issue.

I'm not sure what's the main "security" concern you want to address with your question.

2 VM's on the same XCP-ng Hosts in 2 different VLAN => not a security issue (unless a zero day flaw is found I guess).

Your pfsense might be a security issue too, if that's compromised, no matter what the setup behind looks like is exposed.

So final words on your question in the topic:
"No"

@mistercutter /var/crash ?

Isn't this related to crash reports?

Right-Click => Remove crash reports?

@runevn
Does

showmount -e 192.168.99.1

work?

No messing around with jumbo frames or something?

What commands did you try?

Running

xe vm-param-cleaner uuid=<vm_uuid> param-name=blocked-operations

Will unset most of the fields and in a quick test I saw that I could reboot the machine again.

Maybe setting something to false is just not enough.

Does your XO VM have an IP address in the same range as the NFS storage?

NFS doesn't need to be aware of your VLAN, that should all be a layer below.

From your XO VM, can you run:

showmount -e <freenas ip>

@LEB-ID Yes, in XO > Settings > Servers should only have a single entry.

Once connected

XO > Home > Hosts should display your 2 servers

@pdonias I did an update to Netbox 2.11.12 and it works now, so I don't need to tamper with my XOA.

@pdonias 2.9.9
Might that be too old?

...

    "body": {
      "name": "[TMP] Xen Orchestra Netbox plugin test - klcecdwwuqj",
      "slug": "xo-test-klcecdwwuqj",
      "description": "This type has been created by Xen Orchestra's Netbox plugin test. If it hasn't been properly deleted, you may delete it manually."
    },
    "error": {
      "name": [
        "Ensure this field has no more than 50 characters."
      ]
    }

Whenever I "Test Plugin" my Netbox config I get the following error, even after setting up valid SSL Cert (#letsencrypt)

For some odd reason, the sync did go through though... once at least... I see my VMs in Netbox (no IP adresses though).

Any easy way to debug this on XOA end? I don't see logs on Netbox (at all) to debug there either, that's why I'm asking here.

PS: Netbox sounds like a great tool but it's overwhelming... I hope that filling it up with lots of data from XOA will help as a big first step instead of starting from scratch. Netbox Plugin +1

\o/

You don't happen to have an example handy? Even if it's not PHP.

Either the libraries I'm trying are or my brain is too much used to REST to get the JSON RPC working.

Before wasting too much time trying to get this working, can someone just confirm that it should work? Can I connect to xo-server with JsonRPC using PHP? Or are there some websocket reasons why this can't work?

On the cli of your XCP-ng host, what does the following command output:

showmount -e 192.168.1.1

I can confirm.

• Template from Hub
• New SSH key selection in User/Profile screen of XOA
• Create new VM with SSH key selected
• Login over ssh with

ssh debian@<ip>

• Success

@cg You are aware that XOA is just a VM that you can reboot.

As a matter of fact, I did it this morning (even halted it for maintenance).

Of course it's weird since you are "killing" the interface you are currently using.