Just in case: $ md5sum ubuntu-12.04.3-server-cloudimg-amd64.vhd.bz2 1043fff5c04978a6088e40fa341c36fa ubuntu-12.04.3-server-cloudimg-amd64.vhd.bz2
That is very odd that you are not able to register it without bunziping it. here is the md5 of the uncompressed vhd: $ md5sum ubuntu-12.04.3-server-cloudimg-amd64.vhd 308d15168d4dfb8be622965f08794a68 ubuntu-12.04.3-server-cloudimg-amd64.vhd This matched the md5 of the template vhd on the secondary store. In case it matters, my management server is running on Ubuntu 12.04.2. Weren't you using a different vhd-util than the one that was linked to from the installer (or am I remembering a different thread)? On Mon, Sep 9, 2013 at 1:19 PM, Dean Kamali <dean.kam...@gmail.com> wrote: > France > Yeah I have done that prior importing it, otherwise it won't let me, I see > that the template has successfully installed, but I'm still getting that > error when I try and deploy new vm. > > I will try to import it directly to xenserver and see if it works. > > >
