So if you change the name to something similar to what I suggest above they work fine. As I say in that post I have been considering changing the names so they work OOTB with PVE.

FYI though they aren't PVE templates; they're generic OVZ templates - that's why I initially chose to keep their names to the standard TKL filenaming convention.

If you've already uploaded them, no need to rename and reupload. They're where they should be, just need to be renamed. Either use SSH or a SFTP client such as Filezilla to connect to your PVE server and you'll find the template(s) in /var/lib/vz/template/cache They'll then show up in the PVE WebUI.

Although if you're really keen you could just wget it straight from SF to your PVE server.

Then you may as well rename it on your desktop. Then upload it to your PVE server. You can use the WebUI or SFTP into the folder I mentioned above.

Like you say it would be great if you could download direct from SF but that is not likely as the SF urls change from time-to-time and PVE have their own appliance repository. There were discussions at one point between PVE and TKL devs re hosting TKL appliance templates in the PVE 'marketplace'. The discussions were positive but unfortunately the priorities of TKL and PVE are in different directions so it never came to fruition. Who knows what the future will bring though.

[edit] Sorry just read your post again and realised that you were getting stuck with uploadingbto PVE. I was sure that the templates upload fine as they are, although perhaps PVE now checks the filename complies before accepting them? Try renaming them on your desktop or upload via SFTP as I said above.

But not on the other one I administer (same templates & same PVE version). So I'm not sure what it is but I assumed that there was something wrong with that particular host. Some OVZ guests also display some other strange behaviour. I'm jumping to conclusions, but it seems interesting to me that you are experiencing the same thing with resolv.conf.

I don't understand exactly what the problem is, but internet doesn't work initially for the appliances on that host. On the PVE host that has problems I noticed that there seems to be something wrong with the resolv.conf file. The workaround involves deleting the file and IIRC I manually recreated it and all good after that.

Still, seems strange because the appliance templates work fine on the other PVE host I have.

Looks like you've done some good initial research but despite the fact that I can see the potential merits, the likelihood of someone taking your info and turning it into an appliance at this stage seems unlikely anytime soon. I've had a quick browse over your links and found that a number of them don't work and some of the more straightforwad instructions are aimed at install on Windows (from what I can gather).

And with the upcoming release of Ubuntu 12.04 (which will be the basis for TKL v12.x) the TKL core devs will be very busy boys. Plus with the huge amount of already completed patches for addition to the TKL library, the likelihood of them having time to develop this themselves is probably slim to noe anytime soon.

That's not to say that someone else mightn't come along and do this is, but obviously you won't be able to rely on that either.

So bottom line is that if you want to see this done, then you're going to have to be willing to do what it takes to get it happening. You've made a good start with the documentation on the dev wiki, but I'd also be inclined to start a new thread in the 'general' section (although that's entirely up to you).

I think the next step would be to start trying to install it and get it working. If you carefully document every step then even if you hit a wall, someone else will have something to work with and you may even be able to get some assistance from others. Once you have it working as expected (at least basically) then try to get the process working directly from the commandline (still carefully documenting as you go). Once you get to that point a script to automate the process is really easy and by extension the creation of a TKLPatch is pretty straight forward. I'm happy to provide as much help as I can but I have a heap on at the moment and also have a lot of unfinished TKL projects that really need to be tidied up.

But OVZ templates are very cut down and are missing compnents that are required when running in other mediums. If you have the original patch it would probably be better to just apply the patch to the ISO directly (rather than try to create an ISO from the OVZ).

Unless of course you mean OVF?! Which your mention of VirtualBox makes me think you may mean (OVZ is an acronym for Open VirtualiZation and is a type of container virtualisation). OVF on the other hand is a config file for virtualisation platforms like VirtualBox and VMware products.

So if you are speaking of OVF then yes it can be done. Alon wrote a blog post about it sometime ago. It was for the old legacy version of TKL though so you may need to modify it.

As for your OpenERP appliance patch, sure post it here in the general section of the forums (new thread) and tag it with 'tklpatch'.