@olivierlambert

Sure, but why cant you guys make it "trivial" in XCP-ng Center? You praise XO so much, but one, it comes with limitations, 2nd its another 3rd party software and 3rd to get full capability it has to be paid, and lastly in order for it to be up to date you need it to have internet access given the license etc.

In short, when you build a closed end system its best to take in what you know or can open and double check. I like XCP-ng and I think you guys have done great job and will hire your system admin in the future but for now certain things have to be achieved and I prefer less systems and those few to work as stated.

Thus, when you mention xe CLI export, it there a tutorial one can view to see the steps?

No, but it wasnt CD related... it was an error due to using NFS over ip with xcp center... it creates some process and seems to loop and from there entire server start to act odd, barely load or shut down any VM.... very bad experience. I know its all about XOA now, but thats the only function of Center so far that created negative feedback.

Had to force restart to reboot VM, however, now it wont start giving me error that "VDI is not available". Can anyone recommend how to resolve it?

@olivierlambert

So to be clear, are there any plans as of right now to support Dockers on xcp-ng natively?

@olivierlambert

Do you know how much those licenses per VM run up?

@olivierlambert

How much development like that would cost?

@olivierlambert

Are there are any time line on when you believe nVidia vGPU can or will be available for xcp-ng servers, or due to proprietary side of nVidia, thats not going to be possible to use at all on xcp-ng platform?

@peder

Thank you. Unfortunately, that machine is in datacenter so dont have physical usb access.

Nevertheless, I found a way to do the conversion. Seems as XenConvert 2.3.1 is capable of doing it, however, its only that version that does it, the rest are all different.

Therefore, issue resolved for conversion, but i'm still wondering if im the only one that had that issue or is it quite common given the system version I have to xcp and the center.

@peder

wait... vhd would work too, doesnt have to be just ova.

I tried running a sniffer on the network and saw no requests on any ports from the system other than whats in use, thus same networking layers are used as for .xva.

So i just drilled ssh access to the machine, so would like to do it via cli, if you can perhaps just share with me the rest of command line to move it to remote storage location such as usb, would greatly appreciate it.

xe vdi-list 
xe vdi-export uuid=the-uuid-of-your-VM filename=filename.vhd format=vhd 
......?

@peder

About the error, to you knowledge does the system utilize any ports different from the one it uses for .xva? Could be a networking issue as its quite tight.

Or perhaps, can it be some form of limitation of the memory and power allocated to machine itself.

Would really like to find out if i'm the only one that has the same issue, or to be exact to find the root of it.