You first choose VM type between a container or a server.
The form automatically changes.
Server VM Proxmox config tab:
Advanced options could also be modified in Server VM Proxmox config tab.
N.B.: There's a bug in foreman/webpack/assets/javascripts/jquery.ui.custom_spinners.js file. The minimum counter spinner is set to 1 and not 0. It is used in device disk storage field so if you put 0, it could show 1 instead.
Main options:
CPU options:
Memory options:
You can add/update/remove 3 types of storages:
Hard disk (any),
CDROM (only once):
Cloud-init (only once):
And when a cloud-init drive has been saved (with the host) then you can update cloud-init options:
OS options:
OS tab with build from network (default):
Network server interface tab:
Identifier is required. You must set net[n] with n an integer.
If not, a default one is set for you.
The container form slightly differs from the server one:
- OS template is required
- advanced options are slightly different
Container VM Proxmox config tab:
You can add (many) mount points:
Network interface container tab:
Update config is available.
You can also change a host (server or container) into an image, i.e. a template in Proxmox.
You update a host. You check the box Create image? to true and save it. Here is container template sample:
The image is then available in the list of compute resource images tab:
You create an image from your compute ressource:
If previously you didn't created a template vm, the list of vmids is replaced by a single input:
It is not recommended to create an image without a valid vmid template in proxmox.
Then you can make linked clones of this image. To do so, you create a new host and in OS tab you choose build from image and choose the available image:
The the vm is cloned by proxmox in a new VM. The name starts with Copy of image-name.
You can list hosts in foreman:
And you can check it in Proxmox Web interface too:
VM (container) tab when vm is a template. Templated? is true:
VM (server) tab when vm is not a template. Templated? is false:
You can start and stop a vm:
You can not run a template vm.
When vm is running, you can open a noVNC console on it:
