使用VmProvisioningTimeout自定义映像部署失败 [英] Custom image deployment is failing with VmProvisioningTimeout

查看:88
本文介绍了使用VmProvisioningTimeout自定义映像部署失败的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

大家好,

我们在使用我们的通用Windows 10映像在Stack中工作时遇到了一些麻烦。我们创建的图片具有以下属性:

we are having some trouble getting our generalized Windows 10 image to work in Stack. The image we've created has the following properties:


  • Windows 10 1803 x64
  • 根据  https:// docs预先配置的设置.microsoft.com / zh-CN / azure / virtual-machines / windows / prepare-for-upload-vhd-image
  • 使用" sysprep / generalize /unattend:ourunattend.xml"
  • 上传了VHD并根据https://docs.microsoft.com/en-us/azure/virtual-machines/windows/upload-generalized-managed

Ourunattend.xml 定义了一个自动登录和一些要运行的post-specialize-tasks任务,包括到AD域的连接(堆栈外部)以及安装Azure VM代理MSI(WindowsAzureVmAgent.2.7.41491.885_180531-1125.fre)。

Ourunattend.xml defines an autologin and a number of post-specialize-tasks to be run, including a join to an AD domain (external to the stack) and the installation of the Azure VM agent MSI (WindowsAzureVmAgent.2.7.41491.885_180531-1125.fre).

使用Powershell在Stack中部署新机器时(基本上使用来自https://docs.microsoft.com/en-us/azure/azure-stack/user的组件) / azure-stack-quick-create-vm-windows-powershell),我们可以看到使用此图像的副本创建的VM并且
已成功启动。随后的autologon和post-specialize任务需要一段时间(约30分钟),但最终成功完成(包括域加入)。然而,所得到的VM被设置为状态"失败"。一段时间后,使用VmProvisioningTimeout
。来自Azure堆栈门户的错误详细信息:

When deploying a new machine in Stack using Powershell (basically using components from https://docs.microsoft.com/en-us/azure/azure-stack/user/azure-stack-quick-create-vm-windows-powershell), we can see the VM being created using a copy of this image and started successfully. The subsequent autologon and post-specialize tasks are taking a while (~ 30 minutes) but are finally completing successfully (including the domain join). The resulting VM however is being set into the status "Failed" with VmProvisioningTimeout after a while. Error detail information from the Azure Stack portal:

此虚拟机可以使用其他错误信息:

推荐答案

您可以尝试不从脚本中安装代理,让我们看看它是如何进行的。 Azure Stack应该在部署时注入代理。
Can you try not installing the agent from your script, and let's see how that goes. Azure Stack should inject an agent at deployment time.


这篇关于使用VmProvisioningTimeout自定义映像部署失败的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆