Re: Error attaching an uploaded VHD volume to a VM

2013-10-01 Thread bala sundaram
Hi, My bad. The volume which i used is shared not local. When creating a new instance selecting custom size for disk creates a volume of type shared(disk offerings are created as local). I dont have a shared storage??? Any way it is a different issue. Will try with a local volume again. Than

RE: Error attaching an uploaded VHD volume to a VM

2013-09-30 Thread Sanjeev Neelarapu
To: users@cloudstack.apache.org Subject: Re: Error attaching an uploaded VHD volume to a VM Hi Shanker, Sorry for the late response. This option 'Storage - Volumes -> volume_name -> Migrate Volume To Another Primary Storage' is only shown only for the disk that is already th

Re: Error attaching an uploaded VHD volume to a VM

2013-09-30 Thread bala sundaram
Hi Shanker, Sorry for the late response. This option 'Storage - Volumes -> volume_name -> Migrate Volume To Another Primary Storage' is only shown only for the disk that is already there in a primary storage(Correct me if wrong). A newly uploaded disk which resides in the secondary storage will

Re: Error attaching an uploaded VHD volume to a VM

2013-09-26 Thread Shanker Balan
On 26-Sep-2013, at 4:47 PM, bala sundaram wrote: > Hi shanker, > > We didnt migrate the disks between hypervisors/storage pools. We > downloaded it, while uploading it back the storage type is changed to > shared. So were not able to attach it the vm. > > "*Cannot attach volume since there are

Re: Error attaching an uploaded VHD volume to a VM

2013-09-26 Thread bala sundaram
Hi shanker, We didnt migrate the disks between hypervisors/storage pools. We downloaded it, while uploading it back the storage type is changed to shared. So were not able to attach it the vm. "*Cannot attach volume since there are no shared storage pools in the VM's cluster to copy the upload

Re: Error attaching an uploaded VHD volume to a VM

2013-09-25 Thread Shanker Balan
On 26-Sep-2013, at 7:48 AM, bala sundaram wrote: > Hi Shanker, > >You are right. We dont hava a shared storage. The Vm is in the local > disk of the hypervisor. We a shared primary storage that is used only by > the system vms. Are you able to migrate the volume to local storage and attach t

Re: Error attaching an uploaded VHD volume to a VM

2013-09-25 Thread bala sundaram
Hi Shanker, You are right. We dont hava a shared storage. The Vm is in the local disk of the hypervisor. We a shared primary storage that is used only by the system vms. Thanks and Regards, bala On Wed, Sep 25, 2013 at 7:49 PM, Shanker Balan wrote: > On 25-Sep-2013, at 7:36 PM, Shanker Bal

Re: Error attaching an uploaded VHD volume to a VM

2013-09-25 Thread Shanker Balan
On 25-Sep-2013, at 7:36 PM, Shanker Balan wrote: > On 23-Sep-2013, at 10:41 PM, iliyas shirol wrote: > >> Greetings ! >> >> We downloaded a DATA disk volume (on Local Storage) of VM-1 running in a >> particular zone to a webserver DOCROOT and again uploaded as a new volume >> using the 'Upload V

Re: Error attaching an uploaded VHD volume to a VM

2013-09-25 Thread Dean Kamali
please share your log file on pastebin On Wed, Sep 25, 2013 at 10:06 AM, Shanker Balan wrote: > On 23-Sep-2013, at 10:41 PM, iliyas shirol > wrote: > > > Greetings ! > > > > We downloaded a DATA disk volume (on Local Storage) of VM-1 running in a > > particular zone to a webserver DOCROOT and

Re: Error attaching an uploaded VHD volume to a VM

2013-09-25 Thread Shanker Balan
On 23-Sep-2013, at 10:41 PM, iliyas shirol wrote: > Greetings ! > > We downloaded a DATA disk volume (on Local Storage) of VM-1 running in a > particular zone to a webserver DOCROOT and again uploaded as a new volume > using the 'Upload Volume' feature in the webUI. > > Now when we're trying to a

Error attaching an uploaded VHD volume to a VM

2013-09-23 Thread iliyas shirol
Greetings ! We downloaded a DATA disk volume (on Local Storage) of VM-1 running in a particular zone to a webserver DOCROOT and again uploaded as a new volume using the 'Upload Volume' feature in the webUI. Now when we're trying to attach this volume to a new VM say VM-2 we're encountering the be