I'd like to get first to build our XO Packer plugin, that will help us a load to build those So as soon we got it, we'll create more templates, including Fedora

I've set up a test-environment and indeed it worked. Commvault was (is?) checking for specific version/agent string when connecting to XS/CHV/XCP-ng and in older versions refused to connect to XCP-ng. I successfully installed the agent on a proxy-vm (it uses a proxy to ro-mount the VM-VHDs and backup the content), connected the pool, delivered the VM-inventory and also ran a successful backup: [image: 1666711412304-171c0956-e3e2-4fb9-a93b-48a2be6751bb-grafik.png] In other words: If you're using Commvault (11.28+) you're not any longer locked on Citrix.

So as everyone could spot, XenServer is now a dedicated business unit inside Cloud Software Group. Funnily enough, they are back with the old name, and are more independent. IMHO, that's good news, and we hope to continue to develop our partnership with them!

It is, and it's XOSTOR

Don't get me wrong: constructive feedback is ALWAYS welcome This is just the pricing "cards", but there's already the information that you have initial setup assistance, upgrade help and direct access to XCP-ng devs. Sounds more than just "send us an email when you need". What would you have wrote then? Also, regarding not paying the project but hire people to contribute on it: I'm very fine with it!

@KPS Hi. This thread is now inactive sop please open a new thread dedicated to your issue.

You can import the VHD file via our REST API, see https://xen-orchestra.com/docs/restapi.html#vdi-import

Great. Thanks for checking this.

Well, I would say it's not directly an "upstream", it's a bit more another "downstream" from Xen and XAPI project (at least that's the idea). It's far too early to answer about XenServer, plus the fact I'm not in Citrix board So I can't tell. I know it's generating revenue, so as long there's money, things won't disappear into thin air (support contracts and so on).

Not that far, because we are not using 4.13 as it was for the initial release: there's multiple backport from upstream since then (so it's more recent than that in terms of code base) there's also XenServer/XCP patches on top of it But yes, it's not using the latest Xen upstream version, for various reasons (also as 8.2 is an LTS, we try to be conservative in terms of new versions/features, stability is more important than latest Xen features). Finally, Xen ABI isn't stable (yet), so having a more recent Xen version also means breaking stuff with other components inside XCP-ng (XAPI/xenopsd)

8.2.1 will be around with various improvements in a matter of weeks. But I don't think that's your true problem/question here. Regarding your issue, I don't see any obvious way without digging further on why the dom0 can't mount (I bet on a network init problem in the dom0)

There you go: [image: 1641632888383-ubnttemp.png] It's available right now in your XOA, Hub section. Please test and report. Note: there's a last thing we need to fix, but it's cosmetic only (VM/template name ends with "71" because we forgot to remove it before export)

They closed their patches from direct access, I'm moderately happy to change XO patch code for CH.

@axiom00 No I was not able to get it working.