Cannot start vApps after add VM success from vApp catalog

[tu_ha]

Hi all,

I add new VM from vApp catalog successfuly but cannot start VM (Power on VM) .

Information Activity Task Details: Unable to perform this action. Contact your cloud administrator.

and information in vCenter :  Power On virtual machine  1733531289-RHEL_temp  No host is compatible with the

How to start my vApp ?

Thanks.

[sjoglekar]

If you login as a system administrator and try the same operation, you will see the complete error message. This will most probably tell you what is going wrong.

Thanks,

Sangeeta

[tu_ha]

Thank for your reply.

When login by cloud admin, i show this messasge :

The Windows Sysprep deployment package is missing files for certain versions of Windows. Contact your cloud administrator. The following VMs cannot

be started: "vApp Win2003_x64'".

Althrough i deploymented sysgrep :

[root@vcloud sysprep]# ll
total 20
drwxrwxrwx 2 root root 4096 Aug 12 11:39 win2000
drwxrwxrwx 2 root root 4096 Aug 12 15:29 win2k3
drwxrwxrwx 2 root root 4096 Aug 12 15:29 win2k3_64
drwxrwxrwx 2 root root 4096 Aug 12 11:39 winxp
drwxrwxrwx 2 root root 4096 Aug 12 11:39 winxp_64

[root@vcloud sysprep]# cd win2k3_64/

[root@vcloud win2k3_64]# pwd
/root/sysprep/win2k3_64
[root@vcloud win2k3_64]# ll
total 2728
-rw-r--r-- 1 root root  540310 Mar 24  2005 deploy.chm
-rw-r--r-- 1 root root  197632 Mar 24  2005 factory.exe
-rw-r--r-- 1 root root   11272 Mar 24  2005 readme.txt
-rw-r--r-- 1 root root 1028255 Mar 24  2005 ref.chm
-rwxrwxrwx 1 root root   35328 Mar 24  2005 setupcl.exe
-rw-r--r-- 1 root root  668672 Mar 24  2005 setupmgr.exe
-rwxrwxrwx 1 root root  133120 Mar 24  2005 sysprep.exe
-rw-r--r-- 1 root root  135680 Mar 24  2005 wfinf_guide.doc

/opt/vmware/cloud-director/deploymentPackageCreator/createSysprepPackage.sh /root/sysprep

service vmware-vcd restart

so, how to resolve ?

Thanks.

[jasonboche]

I ran into a similar situation where a vApp would not start because vCloud Director 1.5 couldn't find the right sysprep files for Windows XP x64.  I had previously provided the correct sysprep files based on http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100559... and then ran createSysprepPackage.sh which completed successfully.

What's odd is that the MS site http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=8287 talks about that version of sysprep being for Windows Server 2003 SP2 x64 (and not XP x64).

So then I grabbed an XP x64 CD and copied the contents of deploy.cab to the vCD server and reran createSysprepPackage.sh which completed successfully.  Still had the same error trying to power on the vApp.

I then tried service vmware-vcd restart but it failed to shut down the service.

I then rebooted the vCD server which resolved the issue.  Unfortunately, I don't know if the fix was the server reboot, the replacement sysprep files from the XP x64 CD, or both.

Jas

[admin]

This is usually due to no hosts having hte host agent.  I think I saw this at another customer and a reboot of the hosts resovled it to reset the vCD agent.  Or not all hosts are on the same DVSwitch or seeing the same storage.