There was a recent commit on Github dealing with NFS mounts. Suggest that you rebuild with the latest source and then try setting up the NFS storage again.

https://manpages.debian.org/testing/systemd/hostnamectl.1.en.html

hostnamectl set-hostname mymachine

If it's not, it's a bug

@fluffy-bunny Use this to get your VBDs from each VM

xe vm-param-get param-name=VBDs uuid=<vm-uuid>

Then to get the name of each VDI file use this

xe vbd-param-get param-name=vdi-uuid uuid=<vbd-uuid>

But as olivier said, it is much easier to just use XO's disk view of the VM you want, then use the "copy" button to copy its VDI name.

Correct, I made changes to pfSense to be my DHCP and DNS Resolver, so had to make that change to the NFS Settings to reflect the Domain Name.

Thanks for your help!...

Seen this too late today but I will give it a whirl tomorrow! Will let know how it went.

@olivierlambert
I posted my issue building on FreeBSD here:
https://xcp-ng.org/forum/topic/3788/issue-with-building-xo-from-source-on-freebsd

Maybe its better so this doesn't go too offtopic. regarding this question its solved!

Now you can even replace the cert via XO web UI (see https://xen-orchestra.com/blog/xen-orchestra-5-52/#xcpngxenserverhostscertificatesmanager)

@Rocky

I'm a little confused I guess. I have a PIF section. There is nothing under my Private Network area.

If migration failed, there's a reason. It's usually stable.

Obviously, because your hosts weren't in the pool, a different CPU model can be the problem (they are automatically adapted if they are in the same pool).

I don't this we support UFS right now.

If I remember correctly, we got:

FAT NTFS ext xfs LVM based

That updated my Netdata package from 1.23 to 1.26, and now the plugin is working. Thanks!

I figured it out! Below is my working configuration for Windows AD including Group Syncing.

@kevdog Not at all, it made us aware that our vendor config was no longer relevant

Thank your for your report!

No worries, it happens

X-O Server is 5.51.1 and XO-Web is 5.51.0.

Hi,

Remotes and SRs aren't managed the same way by XO.

XO is connected directly to the remotes to do some read/write operations, unlike SRs which is connected to them via XCP-ng.

So the SRs aren't directly managed by XO, but are managed using the XCP-ngs' XAPI and we are limited to what the XAPI provides as information.

Hi,

FreeBSD install was already documented officially: https://xen-orchestra.com/docs/installation.html#freebsd You could have test to use HTTP instead of HTTPS to see if perfs are improved New XO backup code will come in few releases that will speed up things Quiesce snapshot: it's not needed for Linux VMs because of the disk driver automatically handling this.

Hi @olivierlambert , cool. Thank you. That makes clear for me now.

Andy

Cancel that! I found the keys icon for sending the combo just above console.....