Cloudstack managing problems with VMware

The previous paragraph installs Cloudstack and uses it to manage XenServer, which is used to manage VMware. Although the problem has been solved before the big and small, but in the VMware this piece still encountered some trouble.

After creating the resource domain, adding the cluster and host, and storing it, it looks like everything is fine, but the system VM doesn't come up. Look at the log found such as "insuffientcapacity", but do not know which resources are not enough (in the management of XenServer when the VM created by itself does not come, found that the VLAN range is not specified). Look at the interface, the size of the two-level storage display is 0kb, but there is no error when adding level two storage. By looking at the storage through vcenter, the primary storage is already mounted, and level two storage is not actually mounted. See this line again from log "Unable to Unpack/var/cloudstack/mnt/vm/178516920059281.2288ef8e/template/tmpl/1/8/routing-8.ova", But this file does not exist at all, to create a directory and copy the file Systemvm64template-4.5-vmware.ova and rename, or the same as no effect, and then think about is not a permission problem, simply put the directory "/var/cloudstack/ MNT/VM "To writable, this back to level two storage is really normal, the system VM can also start normally." When installing Cloudstack, I did not see where the need to specify "/VAR/CLOUDSTACK/MNT/VM" This directory, this is not considered cloudstack itself problem?

After the system VM, its agent state is not up, it is estimated that the network does not pass. To log in to the system VM to see the network problem, online has said to use this command "vmware:ssh-i/var/cloudstack/management/.ssh/id_rsa-p 3922 [email protected]<private i P Address of ssvm> "This login, but I use the prompt" Permission denied ", there are some re-injected key to solve the problem of the introduction, but I do not bother to toss, directly from the Vcenter console log in. First I searched the system VM password, online several places are said to be *******, but I do not go in, the result changed to "password", suddenly went in. First Ping, not through the view of the routing table, it is true that the routing table problem, delete some items after normal. I think it's supposed to be me. When specifying network information, the exact meaning of some information is not particularly clear, and cloudstack itself is unlikely to have such a big bug.

The system VM is in good condition, uploading the template, but the VM you created does not work. UI prompt is not support "Concurrent operation", log is more detailed, said the template is not downloaded, but my own registration template has been downloaded and ready, and the VMware system template is the same, and on the interface to move it to the top, I thought it would give preference to my template so that the VMS could start. The VM created here does not come, first of all because the virtual router does not come, the virtual router needs a system template, so the system template download does not complete the virtual router, so to solve the problem is the system template. I saw earlier that the virtual router and the system VM are using the same template, but the incoming parameters are different, but why does the virtual router not find the template when the system VM is up? I do not know. Looking at the interface, VMware uses a system template to download slower than a snail, although only more than 200 m, estimated not two or three days to download, so thought will be designated as a URL inside and outside the company. Go straight to see MySQL inside of vm_template table, this list has a URL field, this field is each template, Cloudstack by default all refer to "download.cloud.com". Because I have previously downloaded the template to the local, so the URL changed to "localhost", this brush once downloaded, again create a VM, start normal, finally can happy a bit.

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

Cloudstack managing problems with VMware