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

Hi,

This is not a direct answer to your question, but here is a script I used (using Sensu to execute/monitor it):
https://paste.iondev.lu/?59090add7694827a#3TH1vYxNjpz2ZWz4fUNSj4L4brJVRJTMRH9szbk1x8EB

FYI, I had the issue again.
XOA Current version: 5.78.0

Reboot the XOA VM fixed the issue.

MM

Upgrade to latest solved the issue. But funnily enough, after the downgrade it's showing correctly on 5.75.0 too.

#weird #close

I know of Warhammer 40k, but I don't know who did the snapshot in 55k:

In XCP-ng Center, they look ok.

XOA is 5.75.0 #stable

Known issue?

@reinvtv It's a little bit of wasted resourced, but just have a few Xen Orchestra's running... just for this task.

IT is the job where you have to find a workaround for problems you can't fix yourself.

@wade_solarch Short answer: try to avoid that.

Back in the old XenServer days, you had to manually change the cpu feature flags so it would work at all.

https://xcp-ng.org/docs/requirements.html#pool-requirements
This confirms that you can't mix Intel & AMD in a pool

https://xcp-ng.org/docs/requirements.html#pool-requirements
This explains Heterogeneous pools a little

I updated XOA to 5.66 2 days ago and it messed up with my delta backups.

Instead of 2 hours it took 20 hours yesterday and same thing again today.

I don't see any notes in the changelogs that would explain this.

Anyone else?

@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."
      ]
    }