Most likely this timeout is set to 20 min at present 
"vmware.vcenter.session.timeout". If you use full clones on vmware set it to at 
least 1 hour. Actual cloning time depends on the size of the root disk and 
speed of your storage array.

Thanks,
Sergey

On 4/28/20, 11:29 AM, "Andrija Panic" <andrija.pa...@gmail.com> wrote:

    Attachments are (afaik) stripped when you send email to ML (but I got it,
    NFS v3, so not relevant/VMFS)

    Increase all limits to "-1" as already suggested by Marc-Andre and if it
    still fails, please paste full management logs on the pastebin or similar
    (or attach the management-server.log on some external service)

    Regards,
    Andrija

    On Tue, 28 Apr 2020 at 15:44, pradeep pal <pspa...@hotmail.com> wrote:

    > Hi All,
    >
    > If we do these changes. any impact in production?
    >
    > @Andrija Panic <andrija.pa...@gmail.com>, Please find the VMFS version
    > screenshot.
    >
    > One more thing When we create VMs through the template, the template is
    > successfully copied on secondary storage, but when it goes on primary
    > storage the VM creation failed.
    >
    > Regards
    > Pradeep
    >
    > ------------------------------
    > *From:* Andrija Panic <andrija.pa...@gmail.com>
    > *Sent:* Sunday, April 26, 2020 7:32 PM
    > *To:* users <users@cloudstack.apache.org>
    > *Subject:* Re: Unable to create VM through 100 and 200 GB temaplate.
    >
    > A proper log, or perhaps (if this is what you tried to share) a
    > screenshot uploaded online would be better.
    >
    > Which VMFS version?
    >
    > regards,
    >
    > On Sat, 25 Apr 2020 at 19:01, pradeep pal <pspa...@hotmail.com> wrote:
    >
    > > Hi All,
    > >
    > > We have built a new  VMware cluster in existing CloudStack infra. But
    > when
    > > we create new machines with 100 and 200 GB template. always we get this
    > > error.
    > >
    > >
    > > Clone virtual machine
    > > Status:
    > > The task was canceled by a user.
    > > Initiator: VSPHERE.LOCAL\Administrator
    > > Target:
    > > 271152f909563b3f954b87539960261e
    > > Server: xx.xx.xx.xx
    > > Related events:
    > > 04/25/2020, 9:07:42 AM
    > >
    > > Removed ROOT-5420
    > > on xx.xx.xx.xx
    > > from HOSTDC1
    > > 04/25/2020, 9:07:42 AM
    > >
    > > Cannot clone 271152f909563b3f954b87539960261e
    > > :
    > > 04/25/2020, 8:46:59 AM
    > >
    > > Assign a new instance UUID (502dd00e-baf0-9342-0e31-a635e9bacc48) to
    > > ROOT-5420
    > > 04/25/2020, 8:46:59 AM
    > >
    > > Assigned new BIOS UUID (422d4f0d-fb3d-3ae9-8710-77eac2aa06f5) to
    > ROOT-5420
    > > on xx.xx.xx.xx
    > > in HOSTDC1
    > > 04/25/2020, 8:46:59 AM
    > >
    > > Cloning 271152f909563b3f954b87539960261e
    > > on host xx.xx.xx.xx
    > > in HOSTDC1
    > > to ROOT-5420 on host 10.106.13.103
    > > 04/25/2020, 8:46:59 AM
    > >
    > > Task: Clone virtual machine
    > >
    > > kindly help us in this case.
    > >
    > > Thanks
    > > Pradeep
    > >
    >
    >
    > --
    >
    > Andrija Panić
    >


    -- 

    Andrija Panić

Reply via email to