It is possible that you may see the error “Failed to configure virtual machine <machine name>.” or “Failed to create virtual machine <machine name>.” in scenarios where you are attempting to use the A5, A6 or A7 VM sizes. The three scenarios where this can occur are:
- Resize of an existing VM that is of any size other than A5, A6 or A7
- Creation of a new VM of size A5, A6 or A7 in a virtual network created before 4/16/2013
- Adding a new A5, A6 or A7 VM to an existing cloud service
The reason that this error occurs is because some of the physical hosts used in Windows Azure do not support the new larger VM sizes.
The method to work around the problem will depend on the specific scenario:
- Resize VM to A5/A6/A7 failure - Delete the existing VM
but keep the disks. Then redeploy a new VM of size A5, A6 or A7 using the previous OS disk and any disks from the original VM. If other VMs are deployed in the same cloud service as the VM to be resized, those VMs will also need to be deleted and then
redeploy the new VM as a larger size as the first VM for the new Cloud Service.
- Add A5, A6, or A7 VM to existing virtual network failure - Create a new virtual network, and then deploy the A5/A6/A7 VM to this virtual network. All virtual networks created after 4/15/2013 support A5/A6/A7 sizes if the region
supports high memory VMs, which all Virtual Machine regions do.
- Add A5, A6, or A7 VM to existing cloud service failure - Delete the existing cloud service along with any VMs in the cloud service, then deploy the A5/A6/A7 into a newly created cloud service. Finally recreate any original VMs in the
cloud service by using the OS disk and any data disks to create new VMs in the newly deployed cloud service.
For more information on VM sizes for the Windows Azure Virtual Machines feature, see Virtual Machine and Cloud Service Sizes for Windows Azure.
Messages posted to this forum are provided "AS IS" with no warranties