Error deploying from template

[jayolsen]

When deploying from a Windows 2008 64bit template we get this error messge part way through and it fails.

"number of virtual devices exceeds the maximum for a given controller"

The template is on a thin provisioned disk and we are deploying as thick, should that matter? I saw one post about changing the virtual network but that isn't related to our problem.

This is on vSphere vCenter with ESX4 hosts.

[krowczynski]

This messege number of virtual devices exceeds the maximum for a given controller tells probably the solution.

How many nics, controller e.g. are configured?

[jayolsen]

That is what I thought at first also but I checked and nothing over the maximums, plus if I convert the template to a VM it powers on fine.

[Anders_Gregerse]

I'm experiencing the same problem if I change the hardware configuration for the vm (like changing the vlan for the nic) during the deployment.

[admin]

According to http://kb.vmware.com/kb/1003097 the total number of PCI devices cannot exceed six

Rick Blythe

Social Media Specialist

VMware Inc.

[jayolsen]

Yes we are not exceeding that and also when we convert the template to a VM it does power on and is usuable.

[MattG]

KB Article: 1016221

Cloning a virtual machine in vSphere fails with the error Number of

virtual devices exceeds the maximum for a

given controller

Symptoms

You are experiencing these

issues when cloning a virtual machine (or deploying from a template):

• Cloning fails at
  approximately 90% on the vSphere client with an error message:
  
  Number of virtual devices
  exceeds the maximum for a given controller

Resolution

This issue occurs when the following check

box is selected as a cloning option in vCenter 4.0 and vCenter 4.0

Update 1:

Edit Virtual hardware (Experimental)

To

resolve this issue, clone the virtual machine again, without

selecting the Edit Virtual hardware (Experimental)option.

If you find this information useful, please award points for "correct" or "helpful".

[Dave_McD]

The question I have to ask is, why is it still 'experimental'? It has been like this for several upgrades now, isn't it time it was either approved or scrapped?

[ejward]

I tested it when deploying from a template and it does come up when choosing to modify hardware.  Weird, it used to work.  My issue is that I get it when cloning a running VM.