I run my CloudStack lab environment on 2 Mac Minis running on ESXi 5.5. For a long time, I had faced the issue where tagged VLAN traffic between my CentOS/Ubuntu guest VMs simply refused to work.
Apache CloudStack works with a variety of hypervisors and a single CloudStack cloud deployment can have multiple hypervisors implementations. Some of the more popular hypervisors supported by CloudStack are Linux KVM, XenServer and VMware vSphere.
It is a generally perceived that the Cloud Management Platform (CloudStack) does magical things to support guest operating systems like Windows, Linux or BSD on the hypervisor hosts. In reality, CloudStack is just a consumer of the hypervisor’s capabilities. The ability of CloudStack to provision various guest operating systems is directly dependent on the hypervisor used.
Not all hypervisors are created equal and there-in lies the problem. Depending on the hypervisor vendor and the hypervisor version, the latest and greatest Operating System might have full, minimal or no support at all by the hypervisor.
As of CloudStack 4.2, the listOsTypes API returns the following list of Operating Systems as supported…
The CloudStack “Virtual Router” provides “Private DNS” services for guest instances. The hostnames can be set from the Add Instance creation wizard or directly via the deployVirtualMachine API call.
Instances that are created with the “Name” (Optional) parameter will have it’s forward and reverse DNS entry set to the user defined value. In the screenshot below, the newly launched instance has its “Name” set to “Tiny4”.