Would it be possible to attach your management server log? This will usually give a pretty good idea of which part of cloudstack is causing the error. I assume you have restarted the cloud management service after changing the config?
Marty On Thursday, August 15, 2013, Kirk Kosinski wrote: > Which hypervisor are you using? For XenServer and vSphere the max > virtual disk size (VHD and VMDK, respectively) is ~2 TB. For a VMFS > datastore on vSphere, the version and block size can limit it further, > so check the VMware docs. For KVM (QCOW2) it is apparently much larger > [1]. > > Best regards, > Kirk > > [1] http://rwmj.wordpress.com/2011/10/03/maximum-qcow2-disk-size/ > > On 08/10/2013 06:21 PM, Kirk Jantzer wrote: > > I'm not entirelty certain about CS, but I do not some of the earlier > > hypervisors (xenserver, kvm, esx 4) only support datastores up to 2TB > > (minus 512B). to get around this in the guest, you could present multiple > > 2TB volumes, then raid them together in a raid-0. > > > > > > On Sat, Aug 10, 2013 at 6:39 PM, Andrei Mikhailovsky > > <and...@arhont.com<javascript:;> > >wrote: > > > >> Hello guys, > >> > >> I am trying to setup a guest vm volume with larger than 2TB. I've > changed > >> the custom.diskoffering.size.max variable to 10000 instead of 2000 and > >> tried to create a 4TB volume. Before doing that i've restarted the > >> management server. While creating a new volume I had an error message > >> complaining that the volume is over 2000GB. > >> > >> Is there something that I am missing? Or does the CS has a built in > limit > >> of 2TB per disk volume? > >> > >> thanks > >> > >> Andrei > >> > >> > > > > >
