已知问题:Azure Stack Hub 上的 VMKnown issues: VMs on Azure Stack Hub

你可以在本文中找到在使用虚拟机 (VM) 和规模集时排查 Azure Stack Hub 计算资源提供程序期间出现的已知问题。You can find known issues for troubleshooting the Azure Stack Hub compute resource provider when working with virtual machines (VM)s and scale sets in this article.

门户不显示正确的 VM 名称Portal doesn't show correct VM name

  • 适用于Applicable
    此问题适用于所有版本。This issue applies to all releases.
  • 原因Cause
    在概述边栏选项卡中查看 VM 的详细信息时,计算机名称显示为“(不可用)”。When viewing details of a VM in the overview blade, the computer name shows as (not available). 显示是针对从专用磁盘/磁盘快照创建的 VM 设计的。The display is by design for VMs created from specialized disks/disk snapshots.
  • 修正Remediation
    在门户中,选择“设置” > “属性” 。In the portal select Settings > Properties.
  • 出现次数Occurrence
    通用Common

门户上的 NVv4 VM 大小NVv4 VM size on portal

  • 适用于Applicable
    此问题适用于 Azure Stack Hub 版本 2002 及更高版本。This issue applies to Azure Stack Hub release 2002 and later.
  • 原因Cause
    完成 VM 创建体验后,你将看到 VM 大小:NV4as_v4。When going through the VM creation experience, you will see the VM size: NV4as_v4. 拥有基于 AMD MI25 的 Azure Stack Hub GPU 预览版所需的硬件的客户可以成功部署 VM。Customers who have the hardware required for the AMD MI25-based Azure Stack Hub GPU preview are able to have a successful VM deployment. 所有其他客户将无法使用此 VM 大小部署 VM。All other customers will have a failed VM deployment with this VM size.
  • 修正Remediation
    无。None.
  • 出现次数Occurrence
    通用Common

VM 启动诊断VM boot diagnostics

  • 适用于Applicable
    此问题适用于所有支持的版本。This issue applies to all supported releases.
  • 原因Cause
    创建新的虚拟机 (VM) 时,可能会显示以下错误:无法启动虚拟机 'vm-name'。When creating a new virtual machine (VM), the following error might be displayed: Failed to start virtual machine 'vm-name'. 错误:无法更新 VM 'vm-name' 的串行输出设置。Error: Failed to update serial output settings for VM 'vm-name'. 如果在 VM 上启用了启动诊断,但删除了启动诊断存储帐户,则会发生该错误。The error occurs if you enable boot diagnostics on a VM, but delete your boot diagnostics storage account.
  • 修正Remediation
    使用先前使用的相同名称重新创建存储帐户。Recreate the storage account with the same name you previously used.
  • 出现次数Occurrence
    通用Common

找不到 VM 诊断存储帐户VM diagnostics storage account not found

  • 适用于Applicable
    此问题适用于所有支持的版本。This issue applies to all supported releases.
  • 原因Cause
    尝试启动“已停止-解除分配”的虚拟机时,可能会显示以下错误:找不到 VM 诊断存储帐户 'diagnosticstorageaccount'。When trying to start a stop-deallocated virtual machine, the following error might be displayed: VM diagnostics Storage account 'diagnosticstorageaccount' not found. 请确保未删除存储帐户。Ensure storage account is not deleted. 如果尝试在启用了启动诊断的情况下启动 VM,但引用的启动诊断存储帐户被删除,则会发生此错误。The error occurs if you attempt to start a VM with boot diagnostics enabled, but the referenced boot diagnostics storage account is deleted.
  • 修正Remediation
    使用先前使用的相同名称重新创建存储帐户。Recreate the storage account with the same name you previously used.
  • 出现次数 常用Occurrence Common

已消耗的计算配额Consumed compute quota

  • 适用于Applicable
    此问题适用于所有支持的版本。This issue applies to all supported releases.
  • 原因 Cause
    创建新虚拟机时,可能会收到一则错误消息,例如“此订阅在此位置的区域 vCPU 总数已达到上限。When creating a new virtual machine, you may receive an error such as This subscription is at capacity for Total Regional vCPUs on this location. 此订阅使用了所有可用的 50 个区域 vCPU”。This subscription is using all 50 Total Regional vCPUs available. 这表示可用的核心配额总计已达到上限。This indicates that the quota for total cores available to you has been reached.
  • 修正Remediation
    请求操作员提供配额更高的附加计划。Ask your operator for an add-on plan with additional quota. 更改当前计划的配额将不起作用,也不会反映提高的配额。Changing the current plan's quota will not work or reflect increased quota.
  • 出现次数Occurrence
    极少Rare

虚拟机规模集Virtual machine scale set

  • 适用于Applicable
    此问题适用于所有支持的版本。This issue applies to all supported releases.
  • 原因Cause
    在四节点的 Azure Stack Hub 环境中进行修补和更新时出现故障。Create failures during patch and update on four-node Azure Stack Hub environments. 在包含三个容错域的可用性集中创建 VM 以及创建虚拟机规模集实例失败,在一个四节点 Azure Stack Hub 环境中进行更新时出现 FabricVmPlacementErrorUnsupportedFaultDomainSize 错误。Creating VMs in an availability set of three fault domains and creating a virtual machine scale set instance fails with a FabricVmPlacementErrorUnsupportedFaultDomainSize error during the update process on a four-node Azure Stack Hub environment.
  • 修正Remediation
    可以在包含两个容错域的可用性集中成功创建单一 VM。You can create single VMs in an availability set with two fault domains successfully. 但是,在四节点 Azure Stack Hub 部署中进行更新时,仍然不能创建规模集实例。However, scale set instance creation is still not available during the update process on a four-node Azure Stack Hub deployment.
  • 出现次数Occurrence
    极少Rare

后续步骤Next steps

了解有关 Azure Stack Hub VM 功能的详细信息。Learn more about Azure Stack Hub VM features.