XenServer does not like it if the timestamp in the vhd metadata is in the future. This can happen when templates are created in a timezone that is ahead and made available to an XS that is in an earlier timezone..
On 2/27/14, 8:00 AM, "Daan Hoogland" <daan.hoogl...@gmail.com> wrote: >LS, > >Why do we use faketime in the template conversion for xen? It seems >unnecessary. > >$ faketime 2010-01-01 vhd-util convert -s 0 -t 1 -i img.raw -o >stagefixed.vhd >Fail to get source file size. >Fail to convert RAW disk to VHD fixed disk. > >$ faketime 2014-01-01 vhd-util convert -s 0 -t 1 -i img.raw -o >stagefixed.vhd >Fail to get source file size. >Fail to convert RAW disk to VHD fixed disk. > >$ vhd-util convert -s 0 -t 1 -i img.raw -o stagefixed.vhd >NOTE: For better performance, we will do the overwritten convert! >Done! Convert to stagefixed.vhd. > >the second call of faketime is not in the way, so I don't mind that one;) > >-- >Daan
