@tony random VM's, not on the same SR.

@olivierlambert ah ok ok, sorry..😅

@julien-f

Apologies, I'm not sure how to do that, but it seems easier to run the server as root instead of these workarounds.

Just change HTTP in the Settings/server to connect to your pools with http://<IP> that's it 🙂

Just a quick FYI, XOA means "Xen Orchestra virtual Appliance" and it's only available via https://xen-orchestra.com or auto deploy. That's the only one with pro support 🙂

I think it's already planned in XO 6 (you might find the issue on GH)

Perfect! Enjoy XCP-ng! 🙂

Thin will have an active disk only the size used. So instead of using 100GiB, you are using 10GiB, and with a snap, only 10GiB and few KiB.

Okay so it's indeed a certificate issue on your side. Double check your certs. Sometimes, you need to have a cert file with the intermediate authority.

@jmccoy555 I updated both the XO deployments to current code just now. Both were the same BTW before.

one still asks for the SR on every migration. One does not.

[info] Updating xen-orchestra from '4bed8eb86' to '175be4482'

I would REALLY like to figure this out. Annoying.

Thanks

Tim

yes, I have no problem with commit before.
For now I'm on commit 65e62018e6aeabf64cf9def01ad043dfbdff5c18 and all is ok,

@pdonias

So I've dug into the issue and written a few workarounds which will tide me over until a fix comes out - appreciate your work on this.

I've added a few features in, too. The plugin now:

Allows the choice of whether IPv4, IPv6 or Both types of IPs are synchronised Allows you to enter in tags which will deem a VM to be "ignored" if they have one of these tags Allows you to enter in text which if the name label contains it, it will also be ignored (we have a use case where we have several VMs which are decommissioned but are kept in XCP for various reasons as well as our backup process which maintains a series of VMs with the prefix XCP-BACKUP, which we don't want kept in Netbox) Allows you to configure the ID of the configured VRF in Netbox (if needed) that the particular IP ranges relate to Synchronises the platform that the VM is running Brings across all the tags and puts them into Netbox (this is for our monitoring solution, OpenNMS, which uses Netbox to generate its requisitions and categories to automate the provisioning process)

I will submit these changes back into the Git repo tomorrow when I'm back in the office and you can have a look and see what you want to use. 🙂

@_danielgurgel if you mean basic backup, it's XVA export for both. The only different is in a back case, you are writing the file in a remote instead of sending it to your browser.

Reping @nraynaud

Any opinion @julien-f ?

@zevgeny Detached backups are backup files present on remotes but not related to any existing backup jobs or schedules.

Restoring the XO config in the new install should properly recreate the backup jobs and avoid this issue.

Full backup is using XVA, so it's covering your need 🙂 In other word, use XO 🙂

Yes, as soon you imported the config, be sure that your old XO is down 🙂