Return-Path: X-Original-To: apmail-cloudstack-users-archive@www.apache.org Delivered-To: apmail-cloudstack-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CB2381194A for ; Thu, 26 Jun 2014 16:16:40 +0000 (UTC) Received: (qmail 85493 invoked by uid 500); 26 Jun 2014 16:16:40 -0000 Delivered-To: apmail-cloudstack-users-archive@cloudstack.apache.org Received: (qmail 85444 invoked by uid 500); 26 Jun 2014 16:16:40 -0000 Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@cloudstack.apache.org Delivered-To: mailing list users@cloudstack.apache.org Received: (qmail 85433 invoked by uid 99); 26 Jun 2014 16:16:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Jun 2014 16:16:39 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of Nitin.Mehta@citrix.com designates 103.14.252.240 as permitted sender) Received: from [103.14.252.240] (HELO SMTP.CITRIX.COM.AU) (103.14.252.240) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Jun 2014 16:16:36 +0000 X-IronPort-AV: E=Sophos;i="5.01,554,1400025600"; d="scan'208";a="7611053" Received: from sinaccessns.citrite.net (HELO SINPEX01CL01.citrite.net) ([10.151.60.9]) by sinpip01.citrite.net with ESMTP; 26 Jun 2014 16:16:09 +0000 Received: from SINPEX01CL02.citrite.net ([169.254.2.107]) by SINPEX01CL01.citrite.net ([169.254.1.37]) with mapi id 14.03.0181.006; Fri, 27 Jun 2014 00:16:08 +0800 From: Nitin Mehta To: "users@cloudstack.apache.org" Subject: Re: trying to upload a bootable VHD Thread-Topic: trying to upload a bootable VHD Thread-Index: AQHPkDeYUXSSEh4CVUO8yIIPjvvh0JuAzUGAgABqxQCAAV/0gA== Date: Thu, 26 Jun 2014 16:16:08 +0000 Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.0.120402 x-originating-ip: [10.13.112.13] Content-Type: text/plain; charset="iso-8859-1" Content-ID: <0289A092ED95D0489C27AAD80EBB87AE@citrix.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-DLP: SIN1 X-Virus-Checked: Checked by ClamAV on apache.org Chris - Please use the wiki [1] in case you see any issues registering your template. That=B9s the one you should use here. [1] -=20 https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM,+templates,+Sec ondary+storage+troubleshooting On 25/06/14 5:16 AM, "chris" wrote: >Thanks. > >My attempt to register a template failed. It sounds like that's the >command >I want though. I'll go back and make sure I didn't do something wrong. > >I thought the dev@ address was for development of CloudStack itself? > > >On Wed, Jun 25, 2014 at 12:54 AM, ilya musayev >> wrote: > >> Chris, >> >> If you intend to boot from this VHD, it should be set as ROOT type. >> >> If you add a template through cloudstack UI or api - registerTemplate, >>it >> is set as type ROOT. >> >> If you use createTemplate, it will create a template from ROOT disk of >> existing VMs ROOT disk. >> >> If you are using "upload volume", then its going to be a DATA disk. >> >> Try posting on dev@cloudstack.apache.org for better answer. >> >> Regards >> ilya >> >> >> >> >> >> On 6/24/14, 10:36 PM, chris wrote: >> >>> I'm trying to use the .NET SDK to upload a bootable VHD to eventually >>>use >>> to deploy a VM. I assume the correct sequence is upload > create >>>template >>> > >>> deploy VM. >>> >>> However, when I upload a volume, there seems to be no way to make that >>> volume bootable (it's has the type DATADISK). Using it to create a >>> template >>> once it's uploaded does not work. An error is thrown stating that that >>> image cannot be used to create a template. >>> >>> I've also tried registering a template, using a URL to the VHD file I >>>want >>> to upload in the process. Unfortunately, nothing seems to happen when I >>> try >>> that. Going through this process also makes me wonder what the >>>difference >>> of createTemplate & registerTemplate are. I get "create", but there's >>>no >>> way to register a created template. If "register" creates one, why >>>bother >>> with "create"? >>> >>> I feel like I'm missing something obvious when failing at this process >>>:) >>> >>> >>