log sent

i'm using flat image backend, tried with (l1 cache (writeback|disabled) + no l2) and with (l1 writeback+l2) but results are the same please note that problem happen only if cloned powered on vm is hosted on starwind lun and is cloned on the same or another lun on the same starwind vsa. Cloning the v...

hi to all, i've double checked my config but i haven't found anything wrong, in fact my config is very simple as there is no: -syncronization (only one node) -multipath ( only one nic) -external network (the host esx communicates with VSA through an internal netwok) to check further i've disabled st...

i'm just trying the product in lab with a simple setup, single esx host 5.5u3 (tried u2 too) starwind vsa (latest build) windows 2008r2 (tried 2012r2 and build with VSA wizard too) hosted on local datastore (serveraid M5015 sata disks in raid 5 but tried LSI2008 in IT mode with single SSD drive too ...

Unfortunately even reinstalling windos from scratch didn't work for me still seeing "Management command: abort task.." on starwind log and "event id 129" on windows event log this behavior shows up immediately when i try to clone a VM on the same LUN... and clone operation last f...

Hi, same issues here, tried to use Starwind (latest build) on Esxi deployed as VSA but under load ISCSI LUN become frozen and system disk error 153 and 129 are showed on VSA event viewer, physical server raid controller doesn't record any error and lun hosting the vsa is working perfectly. tried dif...