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

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.

@nodesocket What tool did you use to export? cli? XOA? XCP-ng Center?
And what tool do you want to use to import?

TGIF...

you need to register to XOA, not to XCP-ng

Error message could be more helpful though.

@bahman have a look here.
https://github.com/vatesfr/xen-orchestra/tree/master/packages/xo-cli

If you want to automate absolutely everything, you need to get a cloud-init ubuntu template up and running and pass cloud-init parameters to it.

Try reinstalling and installing xo-cli again.

Got version v0.11.1

Trying to register I get the following error:

[16:12 02] xoa:jedi$ xo-cli --register http://192.168.0.13 root
Password: ***********
(node:44320) UnhandledPromiseRejectionWarning: TypeError: Converting circular structure to JSON
    --> starting at object with constructor 'ClientRequest'
    |     property 'socket' -> object with constructor 'Socket'
    --- property '_httpMessage' closes the circle
    at JSON.stringify (<anonymous>)
    at prettyFormat (/usr/local/lib/node_modules/xo-cli/node_modules/exec-promise/index.js:32:15)
    at onError (/usr/local/lib/node_modules/xo-cli/node_modules/exec-promise/index.js:48:35)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:44320) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:44320) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[16:12 02] xoa:jedi$

I'm trying to do this on my XOA appliance.
npm 6.14.11
node 14.16.0

Any help is appreciated.

@ivan there isn't a licence restriction on the XOA end, can you specify exactly what runs on your hosts?

XenServer 7.2 might have licence restrictions.
Destination host you didn't specify if XCP-ng or Citrix Hypervisor?

@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
Does

showmount -e 192.168.99.1

work?

No messing around with jumbo frames or something?

@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.