A VM with hardware profiles in private cloud
Do NOT change the Abiquo tag in public cloud
Do not change the Abiquo platform's tag on a VM in public cloud provider (e.g. on an AWS instance) because you could break the link between Abiquo and the VM. If the link is broken, you will not be able to manage the VM with Abiquo.
The DVD functionality has been replaced with the ISO functionality.
The Unique Identifier of the VM
The Name of the VM. Defaults to the VM template name
|Fully qualified domain name||Optionally enter the fully qualified domain name (FQDN) of the VM. You can edit this value before you deploy the VM. If you don't enter a FQDN, the platform will automatically generate one. The hostname will be the VM name (format ABQ-uuid) or another Abiquo identifier (format ABQ-id). The domain will be the domain value of the private or external networks that the VM belongs to, or localdomain. After you deploy the VM, if you change the value in the operating system, then Abiquo will synchronize and obtain the new value.|
The enterprise and user that owns the VM
|Guest initial password||Generate an initial root or Administrator password for the VM and email it to the owner. You can change this value before you deploy the VM. See Guest setup|
The number of CPUs. You may only change this value when the VM is undeployed or stopped or when using hot add/reconfigure. Requires the privilege to Edit VM details. The virtual datacenter and enterprise allocation limits will be checked when you enter this number. The number of CPUs available in the hypervisors will be checked when the VM is deployed or restarted. Read-only value when hardware profiles are used.
|Cores per socket||The number of cores per socket. The number of CPUs must be divisible by the number of cores per socket. Not shown when hardware profiles are used.|
The amount of RAM. Select MB or GB. You may only change this value when the VM is undeployed or stopped, or with hot add/reconfigure. Requires privilege Edit VM details privilege. The virtual datacenter and enterprise allocation limits will be checked when you enter this number. The number of CPUs available in the hypervisors will be checked when the VM is deployed or restarted. Read-only value when hardware profiles are used.
|Enable Remote Access||Hypervisors with Remote Access Support only. Enable remote access on this VM. If the VM was created without remote access enabled on the hypervisor, it will be enabled. If you disable remote access, the configuration will remain but you cannot access it via the eye icon. Abiquo does not support remote access through Docker attach.|
Remote Access to the VM by VNC may be Not Available, usually because the VM is not deployed. If it is available and you have the View datacenter details privilege, the Remote Access IP and Port will be displayed.
Remote Access Password
To open the remote access window to your VM from the eye button on the control panel, you must enter this password. By default Abiquo will generate a random password for your VM. To change the password, enter a maximum of 8 characters that are alphanumeric characters only, i.e. [a..z][A..Z][0..9].
If you delete the password, the screen requesting the password will not appear. On ESXi hypervisors, if you set a password and later delete it, the password will be blank, not null. The screen requesting the password will appear, and you should press <Enter> to continue.
If the VM is deployed when you change the password, the change will be applied when you save the VM.
|Show password||Optionally mark the checkbox to show the remote access password|
|SSH user / password||The default user and password from the VM template|
ESX/ESXi only - If Remote Access is Available, you can select the keyboard type for remote access through the eye button for ESXi hypervisors
A description of the VM. The default value is copied from the VM template
|Hardware profile||If your provider uses hardware profiles, select a hardware profile for the VM|
|Created||Date and time that the VM was created|