Several questions appear after reading the explanation from your side. 1. What is the type of storage you use? What is the RAID configuration? 2. Could you show the part of the script where you configured Sync interfaces? I am afraid there could be an issue with that parameter, so we need to make su...

George,

I believe at the moment you would need to have SMB or local access to the XenServer VM disk to be able to convert it. Nevertheless, I will make sure to pass this request to R&D for them to analyze possibilities of adding the scenario you mentioned to the main screen options.

You are welcome. Feel free to post back any future questions.

You are welcome. It's nice you made it work finally.

Unfortunately, at present I do not have any exact ETA. This should be a matter of several weeks, I believe.

VDO related documentation is not yet available, as there are some UI glitches related to VDO operation, particularly from-time-to-time issues with 512b block size emulation at the stage of VDO device creation. Documentation related to feature is going to be published once a fix is available. Feel fr...

My first step would be installed the corresponding drivers in the VM.

Communication will be done via the corresponding ticket. We will update the community when it's resolved.

Here is the document that is publicly available in our Resource LIbrary:
https://www.starwindsoftware.com/resour ... r-vsphere/

Unfortunately, the logs were submitted too late and the part we were interested in had gone because of log rotation. One more issue seen in your environment is constant resync of StarWind disks. It happens every 3 seconds. To avoid any similar situation, make sure to adjust the following settings: 1...

You will not be able to create a VDO device on top of a disk smaller than 5GB. See screenshots from my lab: This looks to be a limitation from RedHat, although I was not able to find anything like that in their VDO documentation.

Could you collect the logs from your system using StarWind Log Collector and submit them to us?

The two options selected by you are optional, while the bottom one is mandatory ("Use 512 Byte emulation" - not selected in your case). Enable it and try the same action.

There is no publicly available instruction at the moment, as this is something users are not supposed to play with. Wrong actions when changing device priority settings may result in incorrect behavior of the software at the moment when you would rely on its correct behavior. Could you give us more ...

Try disabling the mentioned service and rerun the steps. That service is not used in your environment anyway.