That is expected behavior. We will store whatever format provided by user in registering a template to S3. Currently uncompressing is done when the template is copied from s3 to primary storage if NFS staging is enabled. In your case, since you are not using NFS staging, some code has to be added to uncompress when it is copied from S3 to primary storage when NFS caching is disabled.
Thanks -min On 6/26/13 10:00 AM, "Donal Lafferty" <donal.laffe...@citrix.com> wrote: >I noticed that the system VM template is stored in S3 as a .bz2. E.g. as >a .vhd.bz2 when using a Hyper-V hypervisor. > >Naturally, you can't run a bz2. Nor can you make a thin copy of it, say >if it's a downloaded as a TEMPLATE to a primary storage pool. > >Should it be uncompressed before it goes into S3, when it is copied from >S3 to primary storage, or when a volume is created from the TEMPLATE? >