Feature request

[RootSec]

Add VM templates for QEMU (KVM) like for LXC most panels has that feature but Proxmox not, so client need to run manual install with ISO or to custom code own cloud init so thats broken lmao proxmox has a lot features but this one thats more important than others not, also add feature to add subnet direct in Proxmox instead putting single ip on creating and configuring every time gateway and other.

 

[Dunuin]

Add VM templates for QEMU (KVM) like for LXC most panels has that feature but Proxmox not, also add feature to add subnet direct in Proxmox instead putting single ip on creating and configuring every time gateway and other.

There are cloud-init and clones. Thats more or less like templates for VMs. You just need to create the "templates" yourself first.

 

[RootSec]

There are cloud-init and clones. Thats more or less like templates for VMs. You just need to create the "templates" yourself first.

but its not templates, why is than added LXC templates feature instead manual install ? Also lets say you are hosting provider and your customer need to reinstall their VPS lmao this is only reason why is nobody are using for hosting only for personal use and hostings that has their custom solutions for deploying KVM on Proxmox like Livingbots.

 

[LnxBil]

but its not templates, why is than added LXC templates feature instead manual install ?

How would you manually install a LX(C) container? To my knowledge, there exist no install process for this from a customer perspective. You just boostrap / untar a stripped down install and you're good to go.

For KVM/QEMU there is what @Dunuin said and it works flawlessly. What else do you want?

 

[RootSec]

How would you manually install a LX(C) container? To my knowledge, there exist no install process for this from a customer perspective. You just boostrap / untar a stripped down install and you're good to go.

For KVM/QEMU there is what @Dunuin said and it works flawlessly. What else do you want?

I said that just to compare. If you will use shit LXC container yes its easy . No reason to not add and KVM templates like for LXC if has for one why not for both. Most people dont use LXC.

 

[Dunuin]

I don't get your point.

If you want to run the same VM multiple times without setting up everything again you can clone VMs.

If you dont want to manually install and configure a new VM you can use cloud-init so stuff like IPs, network, users and so on are automatically setup using a cloudinit script.

If you want to run a application turnkey ready without needing to know whats going on you can install a appliance.

Combine an appliance with cloud-init and clones and you got the same as LXC templates just for VMs.

So whats the feature that a LXC template can do what you are missing because it is not possible with an appliance, cloud-init or clones?

And I don't think no one uses LXCs...if you read the theads here in the forum it looks like most people will only use VMs if a LXC wont work because Unix/Windows is needed.

 

[RootSec]

So you want to every time to setup cloud-init instead just going in wizard and choose OS? No point having LXC templates but KVM/QEMU not. Cloud-init is optional feature for KVM, but LXC templates are not you must use them so why not to have and for KVM instead setting up cloud-init?

 

[Dunuin]

- KVM can run hundreds of OSs and LXC only one (no matter what linux you choose, you always use the hosts kernel)
- each OS would need its own code to setup things (would be funny to have a template for TempleOS )
- with KVM you need install that OS first, you can't just copy files over like with LXCs
- the host has no access to the KVM guest OS, so you can only do what the qemu-guest-agent allows you to do
- not every OS supports a headless/unattended installation

I have no idea how KVM templates could be possible at all.

 

[LnxBil]

I have no idea how KVM templates could be possible at all.

I only see the manual way and limit the possibilities. We did something similar with netboot and a lot of configuration over the decades, but it works as is should be and just installs what we want. This can be easily used in big ISP setups and e.g. hetzner uses exactly that for real hardware, so why not use it for VMs? Yet the solution has to fit your problem.

I personally don't use templates that often, because they have to be patched to be on par with the automatic install via netboot. This is also a PITA if you have a lot of them. I created some infrastructure for our LX(C) container templates that patches them regularely and rebuild the pve template files. For KVM and thei template counterpart, I don't use them as templates. For Linux, I just reinstall from a local mirror and the install takes 3-5minutes. For Windows VMs I just have a KVM which gets its regular updates and can be cloned from after running sysprep after cloning.

 

[RootSec]

Lmao, you two guys never used Virtualizor or SolusVM ? How they can implement templates for KVM in their shit panel ? Just look more on other solutions that are in production use. And why is that needed, Just because you're used to manually adjusting everything, doesn't mean that there are developers who would like to do billing or something else with proxmox. And KVM templates exist because you haven't heard and you're limited doesn't mean there are others. So if it exists for LXC which would not exist for KVM but you too much shit and use maybe only on a couple of servers or one so your ear hurts if there is that option. And for each OS distribution is an apt / yum update and upgrade option so I don't know what complicates like you fell from Mars. Just be real and I don't know why you compare LXC and KVM, when no one asked.

 

[RootSec]

And yes every OS support copying preinstalled KVM vHDD. Also and changing password can be done without direct access to KVM server on Linux and Windows but that is not requested features.

 

[RootSec]

Just because you're old-fashioned doesn't mean others have to be.

 

[RootSec]

Introduce self first than write. If you will dont write something smart dont write you are making just spam post.

 

[Dunuin]

In contrast to Virtualizor and SolusVM, Proxmox VE is open source. So if you know how to do it right, why not spend your time to add that feature yourself and do a commit instead of trolling here in the forums?

Btw...no staff member will add a feature because someone in the forums askes for it. If you really want a feature you should create a account in the bug tracker and post it there as an "enhancement" request.

And no one said that KVM templates would be stupid, I'm just thinking it isn't worth the effort. Its way too much initial work to implement it and it always will be alot of work because you would need to patch these templates every several days (which you don't have with LXCs, because these templates will be maintained by the community that created the guest OS). So its alot of work for very little benefit (because most things can already done using cloning, cloud-init and so on) and the developers time could be spend better on other stuff like SDN and so on.

 

[RootSec]

I know to do but not in Perl that use Proxmox. Why to patch templates when you can do dist-upgrade or similar just main version need also paid panels dont patch them, OpenStack is also open source and they have and 500 features that Proxmox doesnt, but I dont like it because I used most Proxmox. I will better write for OpenStack API panel that will look better, than integrate in Proxmox with unsupported templates.