@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: 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.

@abatex I solved the problem by removing the external hard drive that I use for backup windows backup.

The update is now available for everyone https://xcp-ng.org/blog/2021/01/28/security-issue-in-sudo/

@ricardowec I completely second @olivierlambert here. Although there is potential for security issues with an OS that loses support, a hypervisor should be treated with extreme caution anyway. I personally never expose a hypervisor in any capacity directly to the internet (for inbound traffic anyway ). This practice alongside using very specific and often highly customised software packages should keep everything running smooth. On top of all this, the underlying kernel, storage systems and such are all custom, so there is nothing really to worry about I will be completely open when I admin that I am very new to XCP-NG, but the team seem to be really responsive if you have an issue. I have never seen such fast reply's, even from an unnamed big brand competitor who charge us $$$ for support.