Configure Guest KVM networking from host or qemu agent

Oct 25, 2017
6
1
3
54
We have Proxmox 4.4 up and running with 3 hosting nodes and 6 ceph nodes. Everything works great, including HA. We even have HostBill (a hosting automation system) configured where it creates both containers and VM's in ProxMox. When HostBill creates a container, it takes an available IP from the HostBill IPAM module and sends it to the ProxMox API when creating the container and networking is automatically configured in the container and it runs as it should.

However, the problem we have is with KVM VM's. HostBill is sending data to the ProxMox API and it builds and starts the VM. Networking is not available for the VM until someone manually logs into it from the ProxMox control panel and configures networking. This is problematic when trying to run a Fully Automated system.

We have a number of workarounds that we believe will help us get around this issue, but they all add more complexity which is never a good thing. We have and are currently using other virtualization systems which can configure networking within a VM by means of an agent.

Is there a way or are there plans on implementing anything in the future that would allow both Windows and Linux VM's to be able to have their networking configured from the host node possibly with an agent (qemu)? This would be very helpful for people wanting to use ProxMox in a fully automated hosting / provisioning system.
 
We have Proxmox 4.4 up and running with 3 hosting nodes and 6 ceph nodes. Everything works great, including HA. We even have HostBill (a hosting automation system) configured where it creates both containers and VM's in ProxMox. When HostBill creates a container, it takes an available IP from the HostBill IPAM module and sends it to the ProxMox API when creating the container and networking is automatically configured in the container and it runs as it should.

However, the problem we have is with KVM VM's. HostBill is sending data to the ProxMox API and it builds and starts the VM. Networking is not available for the VM until someone manually logs into it from the ProxMox control panel and configures networking. This is problematic when trying to run a Fully Automated system.

We have a number of workarounds that we believe will help us get around this issue, but they all add more complexity which is never a good thing. We have and are currently using other virtualization systems which can configure networking within a VM by means of an agent.

Is there a way or are there plans on implementing anything in the future that would allow both Windows and Linux VM's to be able to have their networking configured from the host node possibly with an agent (qemu)? This would be very helpful for people wanting to use ProxMox in a fully automated hosting / provisioning system.

there are plans for cloud-init or qemu-fwconfig support (follow pve-devel if you are interested in this ;)), but nothing that is done yet. you can of course automate such a setup procedure yourself (e.g. via kickstart/preseed, customized install media, remote access, scripts that configure upon first boot, ...)
 
I joined and am now following pve-devel. It does look like Cloudinit will work and is something that will be released with ProxMox in the hopefully near future. I assume this will only be available on PVE 5.x?

If so, now may be the time to upgrade our ProxMox environment to the latest Ceph and then upgrade to PVE 5.x.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!