針對部署Linux虛擬機時的問題進行疑難解答

發行項
08/01/2024

適用於：✔️ Linux VM

注意

本文所參考的 CentOS 是一種 Linux 發行版，且將到達生命周期結束（EOL）。請據以考慮您的使用和規劃。如需詳細資訊，請參閱 CentOS 生命週期結束指引。

當您嘗試建立新的 Azure 虛擬機器 (VM)，常會遇到的錯誤是佈建失敗或配置失敗。

因為不正確的準備步驟，或是因為映像擷取過程中在入口網站選取了錯誤的設定，導致作業系統映像無法載入，就會發生佈建失敗。
當叢集或區域沒有可用的資源或無法支援所要求的 VM 大小，會導致配置失敗的結果。

若本文中未提及您的 Azure 問題，請前往 MSDN 及 Stack Overflow 上的 Azure 論壇。您可以在這些論壇中張貼您的問題，或將問題貼到 Twitter 上的 @AzureSupport。您也可以提交 Azure 支援要求。若要提交支援要求，請在 Azure 支援頁面上，選取 [取得支援]。

徵兆

一般布建失敗案例會在您建立自定義映像之後發生，然後從該映射部署 VM，然後在 VM 狀態顯示 creating時遇到 40 分鐘，您會看到此錯誤訊息：

Provisioning state Provisioning failed. 
OS Provisioning for VM 'sentilo' did not finish in the allotted time. 
The VM may still finish provisioning successfully. Please check provisioning state later. 
Also, make sure the image has been properly prepared (generalized). * Instructions for Windows: https://azure.microsoft.com/documentation/articles/virtual-machines-windows-upload-image/ * Instructions for Linux: https://azure.microsoft.com/documentation/articles/virtual-machines-linux-capture-image/.

或：

Deployment failed. Correlation ID: f9dcb33a-4e6e-45c5-9c9d-b29dd73da2e0. {
  "status": "Failed",
  "error": {
    "code": "ResourceDeploymentFailure",
    "message": "The resource operation completed with terminal provisioning state 'Failed'.",
    "details": [
      {
        "code": "OSProvisioningInternalError",
        "message": "OS Provisioning failed for VM 'iWishThisWouldCreateVM01' due to an internal error: The VM encountered an error during deployment. Please visit https://aka.ms/linuxprovisioningerror for more information on remediation."
      }
    ]
  }
}

接著，您會看到標示為 failed的 VM 狀態。

為何會發生布建失敗？

通常，布建失敗的原因有很多，例如：

遺漏布建 /未正確設定的代理程式

您必須確保代理程式存在且正常運作，您應該使用 cloud-init，或映像不支援此功能，您可以檢閱這些步驟。
不正確的映像組態

我們有有關如何使用 cloud-init 和其他 Azure 映射需求來設定映像的指引，請檢查這一點。

針對佈建失敗進行疑難排解

若要識別布建失敗的原因，您必須從序列記錄開始，您可以使用 Azure 開機診斷來部署 VM。

您必須為 VM 部署已啟用開機診斷的新 VM，且映射失敗，才能存取序列記錄中的布建事件。

# create resource group
resourceGroup=myBrokenImageRG
location=westus2
az group create --name $resourceGroup --location $location
# create storage account
storageacct=mydiagdata$RANDOM
az storage account create \
  --resource-group $resourceGroup \
  --name $storageacct \
  --sku Standard_LRS \
  --location $location
# create VM
vmName=iWishThisWouldCreateVM01
brokenImageName=<ResourceID of brokenImage>
sshPubkeyPath=""
az vm create \
    --resource-group $resourceGroup \
    --name $vmName \
    --image $brokenImageName \
    --admin-username azadmin \
    --ssh-key-value $sshPubkeyPath \
    --boot-diagnostics-storage $storageacct

若要檢視序列記錄檔，您可以移至入口網站，或執行下列命令來下載 serialConsoleLogBlobUri 記錄：

az vm boot-diagnostics get-boot-log-uris --name $vmName --resource-group $resourceGroup

了解系統事件和布建事件的序列記錄檔

第一次建立 VM 時，cloud-init 將會啟動並嘗試掛接 ISO、建立網路連線、設定 VM 建立期間傳遞的屬性、掛接暫時磁碟（在支援的 VM 大小上），以及向 Azure 平臺發出信號，指出初始 OS 設定已完成。

系統事件和重要資訊	序列記錄檔	備註
核心版本和核心版本	`[ 0.000000] Linux version 5.4.0-1031-azure (buildd@lcy01-amd64-021) (gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)) #32~18.04.1-Ubuntu SMP Tue Oct 6 10:03:22 UTC 2020 (Ubuntu 5.4.0-1031.32~18.04.1-azure 5.4.65)`	出現在序列記錄檔的開頭。
核心命令行選項	`[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1031-azure root=UUID=8c0a4742-2f51-40b4-b659-357cfb0bb2a3 ro console=tty1 console=ttyS0 earlyprintk=ttyS0` `[ 0.503399] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1031-azure root=UUID=8c0a4742-2f51-40b4-b659-357cfb0bb2a3 ro console=tty1 console=ttyS0 earlyprintk=ttyS0`	出現在序列記錄檔的開頭。搜尋 `command line:`。
Systemd 版本	`[ 8.626739] systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)`	搜尋 `systemd`。
已達到系統目標	`[ [0;32m OK [0m] Reached target Swap.` `[ [0;32m OK [0m] Reached target User and Group Name Lookups.` `[ [0;32m OK [0m] Reached target Slices.` `[ [0;32m OK [0m] Reached target Local File Systems (Pre).` `[ [0;32m OK [0m] Reached target Local Encrypted Volumes.` `[ [0;32m OK [0m] Reached target Local File Systems.` `[ [0;32m OK [0m] Reached target System Time Synchronized.` `[ [0;32m OK [0m] Reached target Network (Pre).` `[ [0;32m OK [0m] Reached target Network.` `[ [0;32m OK [0m] Reached target Host and Network Name Lookups.` `[ [0;32m OK [0m] Reached target Cloud-config availability.` `[ [0;32m OK [0m] Reached target System Initialization` `[ [0;32m OK [0m] Reached target Timers.` `[ [0;32m OK [0m] Reached target Paths.` `[ [0;32m OK [0m] Reached target Network is Online.` `[ [0;32m OK [0m] Reached target Remote File Systems (Pre).` `[ [0;32m OK [0m] Reached target Remote File Systems.` `[ [0;32m OK [0m] Reached target Sockets.` `[ [0;32m OK [0m] Reached target Basic System.` `[ [0;32m OK [0m] Reached target Login Prompts.`	搜尋 `Reached target`。
跨不同發行版的一般系統網路目標	`[ [0;32m OK [0m] Reached target Network (Pre).` `[ [0;32m OK [0m] Reached target Network.` `[ [0;32m OK [0m] Reached target Network is Online.`	搜尋 `Reached target Network`。
Ubuntu 的深入網路狀態和網路目標，以及系統網路管理所在的 `systemd-network`散發版本。	`Starting Network Time Synchronization...` `[ [0;32m OK [0m] Started Network Time Synchronization.` `Starting Initial cloud-init job (pre-networking)...` `[ [0;32m OK [0m] Started Initial cloud-init job (pre-networking).` `[ [0;32m OK [0m] Reached target Network (Pre).` `Starting Network Service...` `[ [0;32m OK [0m] Started Network Service.` `Starting Wait for Network to be Configured...` `Starting Network Name Resolution...` `[ [0;32m OK [0m] Started Network Name Resolution.` `[ [0;32m OK [0m] Reached target Network.` `[ [0;32m OK [0m] Reached target Host and Network Name Lookups.` `[ [0;32m OK [0m] Started Wait for Network to be Configured.` `[ [0;32m OK [0m] Reached target Network is Online.` `Starting Dispatcher daemon for systemd-networkd...` `[ [0;32m OK [0m] Started Dispatcher daemon for systemd-networkd.`	`network`搜尋或 `networkd`。
RHEL/CentOS 的深入網路狀態和網路目標，以及系統網路管理的 `Network Manager`散發版本。	`Starting Read and set NIS domainname from /etc/sysconfig/network...` `[ [32m OK [0m] Started Read and set NIS domainname from /etc/sysconfig/network.` `Starting Import network configuration from initramfs...` `[ [32m OK [0m] Started Import network configuration from initramfs.` `Starting Initial cloud-init job (pre-networking)...` `[ [32m OK [0m] Started Initial cloud-init job (pre-networking).` `[ [32m OK [0m] Reached target Network (Pre).` `Starting Network Manager...` `[ [32m OK [0m] Started Network Manager.` `Starting Network Manager Wait Online...` `Starting Network Manager Script Dispatcher Service...` `[ [32m OK [0m] Started Network Manager Script Dispatcher Service.` `[ [32m OK [0m] Started Network Manager Wait Online.` `Starting LSB: Bring up/down networking...` `[ [32m OK [0m] Started LSB: Bring up/down networking.` `[ [32m OK [0m] Reached target Network.` `[ [32m OK [0m] Reached target Network is Online.`	`network`搜尋或 `Network Manager`。
SUSE/SLES 的深入網路狀態和網路目標，以及系統網路管理所在的 `Wicked`散發版本。	`Starting Initial cloud-init job (pre-networking)...` `[ [0;32m OK [0m] Reached target Host and Network Name Lookups.` `[ [0;32m OK [0m] Started Initial cloud-init job (pre-networking).` `[ [0;32m OK [0m] Reached target Network (Pre).` `Starting wicked DHCPv6 supplicant service...` `Starting wicked DHCPv4 supplicant service...` `Starting wicked AutoIPv4 supplicant service...` `[ [0;32m OK [0m] Started wicked DHCPv6 supplicant service.` `[ [0;32m OK [0m] Started wicked DHCPv4 supplicant service.` `[ [0;32m OK [0m] Started wicked AutoIPv4 supplicant service.` `Starting wicked network management service daemon...` `[ [0;32m OK [0m] Started wicked network management service daemon.` `Starting wicked network nanny service...` `[ [0;32m OK [0m] Started wicked network nanny service.` `Starting wicked managed network interfaces...` `[ [0;31m* [0;1;31m* [0m [0;31m* [0m] A start job is running for wicked m…etwork interfaces (22s / no limit)` `[K[ [0;31m* [0;1;31m* [0m [0;31m* [0m] A start job is running for wicked m…etwork interfaces (28s / no limit)` `[K[ [0;31m* [0;1;31m* [0m [0;31m* [0m] A start job is running for wicked m…etwork interfaces (32s / no limit)` `[K[ [0;32m OK [0m] Started wicked managed network interfaces.` `[ [0;32m OK [0m] Reached target Network.` `[ [0;32m OK [0m] Reached target Network is Online.`	`network`搜尋或 `wicked`。
開機觸達足以讓 cloud-init 啟動嗎？	`Starting Initial cloud-init job (pre-networking)...` `Starting Initial cloud-init job (metadata service crawler)...`	搜尋 `Starting Initial cloud-init job`。
已達到 Cloud-init 版本和 cloud-init 階段	`[ 22.446387] cloud-init[703]: Cloud-init v. 20.3-2-g371b392c-0ubuntu1~18.04.1 running 'init-local' at Wed, 28 Oct 2020 17:46:30 +0000. Up 21.23 seconds.` `[ 28.357120] cloud-init[837]: Cloud-init v. 20.3-2-g371b392c-0ubuntu1~18.04.1 running 'init' at Wed, 28 Oct 2020 17:46:34 +0000. Up 24.52 seconds.` `[ 50.421009] cloud-init[1445]: Cloud-init v. 20.3-2-g371b392c-0ubuntu1~18.04.1 running 'modules:config' at Wed, 28 Oct 2020 17:46:57 +0000. Up 48.21 seconds.` `[ 51.338792] cloud-init[1541]: Cloud-init v. 20.3-2-g371b392c-0ubuntu1~18.04.1 running 'modules:final' at Wed, 28 Oct 2020 17:47:00 +0000. Up 51.01 seconds.` `[ 51.366837] cloud-init[1541]: Cloud-init v. 20.3-2-g371b392c-0ubuntu1~18.04.1 finished at Wed, 28 Oct 2020 17:47:01 +0000. Datasource DataSourceAzure [seed=/dev/sr0]. Up 51.32 seconds`	搜尋 `Cloud-init v`。
網路介面（NIC）、NIC 狀態（向上/向下）和 NIC IP 位址。顯示是否已正確設定和指派 NIC IP 位址。 IP 位址指派可以透過 DHCP 動態或靜態設定。	`[ 28.381544] cloud-init[837]: ci-info: ++++++++++++++++++++++++++++++++++++++Net device info+++++++++++++++++++++++++++++++++++++++` `[ 28.396781] cloud-init[837]: ci-info: +--------+------+-----------------------------+---------------+--------+-------------------+` `[ 28.416501] cloud-init[837]: ci-info: \| Device \| Up \| Address \| Mask \| Scope \| Hw-Address \|` `[ 28.427493] cloud-init[837]: ci-info: +--------+------+-----------------------------+---------------+--------+-------------------+` `[ 28.446544] cloud-init[837]: ci-info: \| eth0 \| True \| 10.0.0.4 \| 255.255.255.0 \| global \| 00:0d:3a:c6:17:d5 \|` `[ 28.460031] cloud-init[837]: ci-info: \| eth0 \| True \| fe80::20d:3aff:fec6:17d5/64 \| . \| link \| 00:0d:3a:c6:17:d5 \|` `[ 28.476415] cloud-init[837]: ci-info: \| lo \| True \| 127.0.0.1 \| 255.0.0.0 \| host \| . \|` `[ 28.487962] cloud-init[837]: ci-info: \| lo \| True \| ::1/128 \| . \| host \| . \|` `[ 28.498191] cloud-init[837]: ci-info: +--------+------+-----------------------------+---------------+--------+-------------------+`	`ci-info`搜尋或 `Net device info`。
IP 路由（IPv4 和 IPv6）。顯示各種端點的IP路由，例如 VNet 子網、Azure 端點（`168.63.129.16`）和 Azure 實例元資料伺服器/IMDS 端點（`169.254.169.254`）。	`[ 28.508190] cloud-init[837]: ci-info: ++++++++++++++++++++++++++++++Route IPv4 info+++++++++++++++++++++++++++++++` `[ 28.522189] cloud-init[837]: ci-info: +-------+-----------------+----------+-----------------+-----------+-------+` `[ 28.531173] cloud-init[837]: ci-info: \| Route \| Destination \| Gateway \| Genmask \| Interface \| Flags \|` `[ 28.549782] cloud-init[837]: ci-info: +-------+-----------------+----------+-----------------+-----------+-------+` `[ 28.562896] cloud-init[837]: ci-info: \| 0 \| 0.0.0.0 \| 10.0.0.1 \| 0.0.0.0 \| eth0 \| UG \|` `[ 28.571653] cloud-init[837]: ci-info: \| 1 \| 10.0.0.0 \| 0.0.0.0 \| 255.255.255.0 \| eth0 \| U \|` `[ 28.580192] cloud-init[837]: ci-info: \| 2 \| 168.63.129.16 \| 10.0.0.1 \| 255.255.255.255 \| eth0 \| UGH \|` `[ 28.587633] cloud-init[837]: ci-info: \| 3 \| 169.254.169.254 \| 10.0.0.1 \| 255.255.255.255 \| eth0 \| UGH \|` `[ 28.600728] cloud-init[837]: ci-info: +-------+-----------------+----------+-----------------+-----------+-------+` `[ 28.611117] cloud-init[837]: ci-info: +++++++++++++++++++Route IPv6 info+++++++++++++++++++` `[ 28.619534] cloud-init[837]: ci-info: +-------+-------------+---------+-----------+-------+` `[ 28.629292] cloud-init[837]: ci-info: \| Route \| Destination \| Gateway \| Interface \| Flags \|` `[ 28.638596] cloud-init[837]: ci-info: +-------+-------------+---------+-----------+-------+` `[ 28.647791] cloud-init[837]: ci-info: \| 1 \| fe80::/64 \| :: \| eth0 \| U \|` `[ 28.660622] cloud-init[837]: ci-info: \| 3 \| local \| :: \| eth0 \| U \|` `[ 28.670776] cloud-init[837]: ci-info: \| 4 \| ff00::/8 \| :: \| eth0 \| U \|` `[ 28.691506] cloud-init[837]: ci-info: +-------+-------------+---------+-----------+-------+`	搜尋 `ci-info`、 `Route IPv4 info`或 `Route IPv6 info`。
VM 上使用者的 SSH 授權金鑰。 `authorized_keys` SSH 中的檔案會指定 SSH 金鑰，可用來登入已設定檔案的用戶帳戶。	`ci-info: ++++++++++++++++++++++++++Authorized keys from /home/azureuser/.ssh/authorized_keys for user azureuser+++++++++++++++++++++++++++` `ci-info: +---------+-------------------------------------------------------------------------------------------------+---------+---------+` `ci-info: \| Keytype \| Fingerprint (sha256) \| Options \| Comment \|` `ci-info: +---------+-------------------------------------------------------------------------------------------------+---------+---------+` `ci-info: \| ssh-rsa \| 88:b0:2a:ce:f5:91:49:a2:01:07:a4:e5:db:b3:8c:3e:7e:1f:52:83:53:3c:83:4f:a3:a7:17:13:65:a3:47:e2 \| - \| - \|` `ci-info: +---------+-------------------------------------------------------------------------------------------------+---------+---------+`	搜尋 `Authorized keys`。
SSH 主機金鑰產生。主機金鑰是用來驗證 SSH 通訊協定中電腦的密碼編譯金鑰。主機金鑰是金鑰組，通常是使用 RSA、DSA 或 ECDSA 演算法。公用主機金鑰會儲存在 SSH 用戶端上及/或散發至 SSH 用戶端，而私鑰則儲存在 SSH 伺服器上。	`Starting OpenSSH Server Key Generation...` `[ [32m OK [0m] Started OpenSSH Server Key Generation.` `[ 40.437735] cloud-init[837]: Generating public/private rsa key pair.` `[ 40.451048] cloud-init[837]: Your identification has been saved in /etc/ssh/ssh_host_rsa_key.` `[ 40.473777] cloud-init[837]: Your public key has been saved in /etc/ssh/ssh_host_rsa_key.pub.` `[ 40.489730] cloud-init[837]: The key fingerprint is:` `[ 40.501705] cloud-init[837]: SHA256:NGxA6sf9EAMtczaFSBSJqiGkafEZuPUykNLxefbXofM root@myVmName` `[ 40.686610] cloud-init[837]: Generating public/private dsa key pair.` `[ 40.712350] cloud-init[837]: Your identification has been saved in /etc/ssh/ssh_host_dsa_key.` `[ 40.721901] cloud-init[837]: Your public key has been saved in /etc/ssh/ssh_host_dsa_key.pub.` `[ 40.721966] cloud-init[837]: The key fingerprint is:` `[ 40.722011] cloud-init[837]: SHA256:QjoxEw9PNOg0P3LW6wnSZzjsfQQ4vhW8S0dAuNWkWHM root@myVmName` `[ 40.722606] cloud-init[837]: Generating public/private ecdsa key pair.` `[ 40.722650] cloud-init[837]: Your identification has been saved in /etc/ssh/ssh_host_ecdsa_key.` `[ 40.722690] cloud-init[837]: Your public key has been saved in /etc/ssh/ssh_host_ecdsa_key.pub.` `[ 40.722734] cloud-init[837]: The key fingerprint is:` `[ 40.722774] cloud-init[837]: SHA256:BaFqan71k4blzY8TQrLQOavMWoKHgUDgxEAuB0ouJCo root@myVmName` `[ 41.063239] cloud-init[837]: Generating public/private ed25519 key pair.` `[ 41.091125] cloud-init[837]: Your identification has been saved in /etc/ssh/ssh_host_ed25519_key.` `[ 41.120794] cloud-init[837]: Your public key has been saved in /etc/ssh/ssh_host_ed25519_key.pub.` `[ 41.154126] cloud-init[837]: The key fingerprint is:` `[ 41.157135] cloud-init[837]: SHA256:KsKfIKjwGpMgbYYved5v5oNE6v6eeUwI4AxeeigXk14 root@myVmName`	搜尋 `Generating public/private`、 `Your identification has been saved in`、 `The key fingerprint is:`或 `SHA`。
傾印 SSH 主機金鑰指紋。	`<14>Oct 28 17:47:00 ec2: #############################################################` `<14>Oct 28 17:47:00 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----` `<14>Oct 28 17:47:00 ec2: 1024 SHA256:QjoxEw9PNOg0P3LW6wnSZzjsfQQ4vhW8S0dAuNWkWHM root@myVmName (DSA)` `<14>Oct 28 17:47:00 ec2: 256 SHA256:BaFqan71k4blzY8TQrLQOavMWoKHgUDgxEAuB0ouJCo root@myVmName (ECDSA)` `<14>Oct 28 17:47:00 ec2: 256 SHA256:KsKfIKjwGpMgbYYved5v5oNE6v6eeUwI4AxeeigXk14 root@myVmName (ED25519)` `<14>Oct 28 17:47:00 ec2: 2048 SHA256:NGxA6sf9EAMtczaFSBSJqiGkafEZuPUykNLxefbXofM root@myVmName (RSA)` `<14>Oct 28 17:47:00 ec2: -----END SSH HOST KEY FINGERPRINTS-----` `<14>Oct 28 17:47:00 ec2: #############################################################`	搜尋 `BEGIN SSH HOST KEY FINGERPRINTS` 與 `END SSH HOST KEY FINGERPRINTS`。
傾印 SSH 主機金鑰。	`-----BEGIN SSH HOST KEY KEYS-----` `ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBFzu1pBMlq3g/8ztkQo+ZukigmLzQ02/ogL7Xe8aKjbuM8q4ibo1kWnXB0UuGkGE0DotVyBQsoyUNorTj96G2Xo= root@myVmName` `ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIIbGOVk/IMfL+RZBDo6YlfbKncVTIBy7wSrqL5ixX6yZ root@myVmName` `ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDnH5sIIEFi2ne6CMk1jscVQ289i4idOMJt3WwzHR1lOgJf9kPY+WzmFw71Ai9ZEpqSTpYWxgt+z26ujxAE3R1LvOn1QKetlsPLT5FH8oIZESXmYDb/KL/4k81aDelzko1Xipk5SSai8LeX1qglKUEyGevht9S+QQTHK8Ed++UDzNidCk02iAdhpX/0E5d09NE4r+v5wAojOazLnq6JaESYV07SI7rBOGO7hCdSrQwWodYnhyTQRP3FbqjUeNRqBl3uqlH3+rgMAAPsCpToFTCperTRmyBrCbspzpxIpQSEFbf639EL/7Cst/Ff2ND0D0zVAaSdrmFZisYUcO+VRanZ root@myVmName` `-----END SSH HOST KEY KEYS-----`	搜尋 `BEGIN SSH HOST KEY KEYS` 與 `END SSH HOST KEY KEYS`。
SSH 伺服器是否啟動？	`Starting OpenBSD Secure Shell server...` `[ [0;32m OK [0m] Started OpenBSD Secure Shell server.` `Starting OpenSSH server daemon...` `[ [32m OK [0m] Started OpenSSH server daemon.` `Starting OpenSSH Daemon...` `[ [0;32m OK [0m] Started OpenSSH Daemon.`	搜尋 `Secure Shell server`、 `OpenSSH server daemon`或 `OpenSSH Daemon`。
是否允許使用者工作階段和使用者登入？ VM 是否顯示使用者登入提示？	`Starting Accounts Service...` `Starting Permit User Sessions...` `Starting Login Service...` `[ [0;32m OK [0m] Started Permit User Sessions.` `[ [0;32m OK [0m] Started Login Service.` `[ [0;32m OK [0m] Reached target Login Prompts.` `[ [0;32m OK [0m] Started Accounts Service.` `Ubuntu 18.04.5 LTS myVmName ttyS0` `myVmName login:`	搜尋 `Accounts Service`、 `Permit User Sessions`、 `Login Service`、 `Login Prompts`和 `login:`。
Azure Linux 代理程式已成功啟動嗎？	`[ [0;32m OK [0m] Started Azure Linux Agent.` `2020/10/28 17:46:52.082569 INFO Daemon Azure Linux Agent Version:2.2.45`	搜尋 `Azure Linux Agent`。
從 Azure Linux 代理程式的觀點來看，VM 是否已順利完成布建？布建成功之後，Azure Linux 代理程式是否啟動 VM 擴充功能處理程式？如果 Azure Linux 代理程式偵測到 VM 布建成功，則只會啟動 VM 擴充功能處理程式。	`2020/10/28 17:46:52.586765 INFO Daemon Finished provisioning`	搜尋 `INFO Daemon Finished provisioning`。
序列記錄檔中是否有任何錯誤、失敗或例外狀況？	在序列記錄中搜尋 `fail`、 `error`、 `warn`和 `exception` 。

常見錯誤

已停用的 UDF 模組

錯誤在序列記錄檔中：

[   10.855501] cloud-init[732]: Cloud-init v. 20.4.1-0ubuntu1~18.04.1 running 'init-local' at Thu, 28 Jan 2021 23:43:02 +0000. Up 10.68 seconds.
[   10.869581] cloud-init[732]: 2021-01-28 23:43:03,097 - azure.py[WARNING]: /dev/sr0 was not mountable
[   10.875608] cloud-init[732]: 2021-01-28 23:43:03,106 - azure.py[ERROR]: No Azure metadata found
[   10.885776] cloud-init[732]: 2021-01-28 23:43:03,107 - azure.py[ERROR]: Could not crawl Azure metadata: No Azure metadata found
[   14.634117] cloud-init[732]: 2021-01-28 23:43:06,876 - azure.py[WARNING]: Reported failure to Azure fabric.

waagent.log錯誤：

"UDF driver Blocklisted 2020/09/11 19:16:40.240016 ERROR Daemon Provisioning failed: [ProtocolError] [CopyOvfEnv] Error mounting dvd: [OSUtilError] Failed to mount dvd deviceInner error: [mount -o ro -t udf,iso9660 /dev/sr0 /mnt/cdrom/secure] returned 32: mount: /mnt/cdrom/secure: wrong fs type, bad option, bad superblock on /dev/sr0, missing codepage or helper program, or other error."

原因：UDF 驅動程式未載入核心中，這是 VM 布建的必要專案，請參閱映射需求。

第一次在 Azure 上布建 VM 時，Azure 主機會將「布建 cdrom iso 磁碟」呈現給 VM。此布建磁碟通常會透過 /dev/sr0 向 VM 呈現。在布建磁碟內，有一個布建指令清單，其中包含 VM 的布建資訊。 VM 內布建代理程式預期會掛接布建磁碟、讀取布建指令清單，並據以布建 VM。

由於布建磁碟是 cdrom iso disk，因此核心需要Linux UDF驅動程式才能成功掛接此磁碟。這在Linux映像上的Microsoft文件中參考。針對此 VM，記錄表示布建磁碟無法掛接，導致 VM 布建失敗。最有可能的原因是遺失或封鎖的 UDF 驅動程式。

解決方案：確定 UDF 驅動程式已設定為在核心中載入。

要封鎖UDF驅動程式的常見方式是透過內的 /etc/modprobe.d/組態。請與客戶/映像擁有者合作，以確保Linux UDF驅動程式存在且未遭到封鎖。如需封鎖/解除封鎖核心驅動程式，請參閱這篇文章。

VM 標籤的 Unicode 字元問題

cloud-init.log錯誤：

  File "/usr/lib/python2.7/site-packages/cloudinit/sources/DataSourceAzure.py", line 1316, in _get_metadata_from_imds
    except json.decoder.JSONDecodeError:
AttributeError: 'module' object has no attribute 'JSONDecodeError'

原因：這是因為 VM 標籤具有非 ascii 字元，且 cloud-init 的版本早於 20.3。

解決方案：使用或確定您的映像支援 cloud-init 20.3 或更新版本，或從 VM 標籤中移除非 ascii 字元。

密碼與 Unicode 字元

cloud-init.log錯誤：

File "/usr/lib/python2.7/site-packages/cloudinit/sources/DataSourceAzure.py", line 1153, in encrypt_pass
    return crypt.crypt(password, salt_id + util.rand_str(strlen=16))
  File "/usr/lib64/python2.7/crypt.py", line 55, in crypt
    return _crypt.crypt(word, salt)
UnicodeEncodeError: 'ascii' codec can't encode characters in position 10-11: ordinal not in range(128)

原因：這是因為所提供的密碼有不支援的字元（非 ascii）。

解決方案：提供只有 ascii 字元的密碼。

Dhclient 許可權

cloud-init.log錯誤 ：

Command: ['/var/tmp/cloud-init/cloud-init-dhcp-yd8mvxud/dhclient', '-1', '-v', '-lf', '/var/tmp/cloud-init/cloud-init-dhcp-yd8mvxud/dhcp.leases', '-pf', '/var/tmp/cloud-init/cloud-init-dhcp-yd8mvxud/dhclient.pid', 'eth0', '-sf', '/bin/true']
Exit code: -
Reason: [Errno 13] Permission denied: b'/var/tmp/cloud-init/cloud-init-dhcp-yd8mvxud/dhclient'

原因：舊版 cloud-init（20.3 版之前）藉由在內/var/tmp複製和執行dhclient來執行 DHCP。如果 /var/tmp VM 掛接為 noexec （沒有執行），則 DHCP 會因為沒有在內/var/tmp執行的許可權而dhclient失敗。

Cloud-init 版本 >= 20.3 包含一個修正程式，它會回溯並執行 dhclient 「依預設」（如果沒有許可權問題， /var/tmp 則不要複製並執行它）。

解決方案：對於執行 20.3 版舊版 cloud-init 的 VM，請設定 VM，使其 /var/tmp 未掛接為 noexec。或者，將 VM 的 cloud-init 套件升級至版本 >= 20.3。

注意

dhclient cloud-init 22.4 和更新版本中已解決許可權問題。如需詳細資訊，請參閱 cloud-init 問題 3956。

取得更多記錄

如果您發現需要更多來自 VM 的記錄來了解問題，您可以使用已製作映像的使用者，透過序列主控台透過 SSH 連線到 VM。如果您沒有使用者進行模擬，則可以使用使用者重新建立映像，或使用 AZ VM 修復工具，將無法布建的 VM OS 磁碟掛接到另一個 VM。

az vm repair create  \
    --resource-group $resourceGroup \
    --name $vmName \
    --repair-username repairadm \
    --repair-password AnotherPassword123! \
    --repair-vm-name repairVM \
    --verbose

瞭解cloud-init.log

當您能夠存取 cloud-init 記錄時，請檢閱 cloud-init 疑難解答檔。

收集活動記錄

若要開始進行疑難解答，請收集活動記錄，以識別與問題相關聯的錯誤。下列連結包含要遵循之程式的詳細資訊。

檢視部署作業

檢視活動記錄以管理 Azure 資源

取得支援

如果您已參考指引，但仍無法針對您的問題進行疑難解答，您可以開啟支援案例。這樣做時，請選取正確的產品和支援主題，這麼做將會與正確的支援小組互動。

選取案例產品：

Product Family: Azure
Product: Virtual Machine Running (Window\Linux)
Support Topic: <COMPLETE>
Support Subtopic: <COMPLETE>

與我們連絡，以取得說明

如果您有問題或需要相關協助，請建立支援要求，或詢問 Azure community 支援。您也可以向 Azure 意見反應社群提交產品意見反應。

共用方式為