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

Yes, as my cloud-init doesn't work like I want it to, I can live with manually creating the VM.

But it would be cool to be able to automate stuff afterwards, which in my case would be adding a network interface.

VM

Yes, in xo-cli I see vif.connect vif.set ... would be lying saying it's intuitive what to do here to reach my goal.

I'll start off by clicking through XOA for the moment.

Before I try to search for something that doesn't exist yet:

• Can I create a new network interface via REST API?

Not the big JS developer here, but I wanted to contribute.

My dev setup is working as far as I can run yarn start in the packages/xo-server directory.
This puts Xen Orchestra running and working on port 8088 as I configured.

Now for developing, I used to do something like "yarn dev" to have the project running in dev mode with hot reload and stuff like that, but running "yarn dev" gives me some output, but I see no server running on 8088 or any other port:

jedi@thefang:~/git/xen-orchestra/packages/xo-server$ yarn dev
yarn run v1.22.21
$ cross-env NODE_ENV=development yarn run _build --watch
$ index-modules --index-file index.mjs src/api src/xapi/mixins src/xo-mixins && babel --delete-dir-on-start --keep-file-extension --source-maps --out-dir=dist/ src/ --watch
index generated src/xo-mixins/index.mjs
index generated src/api/index.mjs
index generated src/xapi/mixins/index.mjs
Successfully compiled 148 files with Babel (1035ms).
The watcher is ready.

Any tips?

MM

Some time ago I read "ZFS - the billion dollar file system" and the more time I spend with it, the more I think that's true

I'm using zfs & syncoid to pull my XOA backups to another location of a 1Gb/s link:

---------------  Mon 21 Feb 2022 08:00:01 - syncing  -------------
Sending incremental tank/mbox5/xoa-vm-backup@syncoid_iron.ion.lu_2022-02-20:08:00:02-GMT01:00 ... syncoid_iron.ion.lu_2022-02-21:08:00:02-GMT01:00 (~ 1392.4 GB):
---------------  Mon 21 Feb 2022 10:19:27 - done  -------------

183.37MB/s over 1Gbit/s Link sounds great.

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