ESXI 變更密碼 失敗 - 發生一般系統錯誤: Weak password: is based on the old one. *** passwd: Authentication token manipulation error

 環境:

esxi

異常狀況:

無法變更，會出現錯誤

解決過程:

在系統裡的進階設定，裡面有一個Security.PasswordQualityControl 參數。

在裡面加入 similar-permit ，存檔後馬上生效，就可以變更密碼了。

Commvault 備份虛擬機 突然變的很慢

環境:

Commvault 備份虛擬機

異常狀況:

對新的虛擬機做第一次備份，可能容量比較大，過程中又有其他的備份，造成效能問題，最後就停住多個小時後，手動取消。

但後來要重新備份時，傳輸速度變超級慢，速度大概只剩之前的1/7~8，重開機也一樣。

解決過程:

後來發現之前備份失敗後，虛擬機上有一份snapshot沒被移除，先在esxi上，把那份snapshot刪除後，重新備份，就正常了。

Environment:

Commvault (VM Backup)

Issue:

When performing the first backup of a new virtual machine, the data size was relatively large. During the process, other backup jobs were also running, causing performance issues. Eventually, the job became unresponsive and was manually canceled after several hours.

After that, when attempting to run the backup again, the transfer speed became extremely slow, dropping to about 1/7–1/8 of the original speed. Restarting the system did not resolve the issue.

Resolution:

It was later discovered that after the failed backup, a snapshot remained on the virtual machine and was not removed.

By logging into ESXi and deleting the leftover snapshot, then running the backup again, the performance returned to normal.

ESXI 無法開啟虛擬機器 xxx的電源。開啟模組 monitorloop 的電源失敗

  環境:

ESXI  

Synology active backup business

異常狀況:

用Synology active backup business備份的虛擬機，還原到其他esxi後，開機出現錯誤。

解決過程:

原機配置了較高的CPU與RAM，還原後，目的esxi上資源不足，無法開機，把虛擬機的CPU與RAM調低後，就可以正常開機

Environment:

ESXi
Synology Active Backup for Business

Issue:

After restoring a virtual machine using Synology Active Backup for Business to another ESXi host, the VM fails to power on and shows an error.

Resolution:

The original VM was configured with relatively high CPU and RAM.
After restoration, the target ESXi host did not have sufficient resources to support that configuration.

By reducing the VM’s CPU and RAM allocation, the virtual machine was able to power on normally.

ESXI VMFS 增加容量失敗-無法變更主機組態。

 環境:

ESXI 6.7

異常狀況:

底層硬碟RAID擴充完一顆新硬碟後，要在ESXI上也對儲存區進行擴充。

在web console上操作，對著要擴充的datastore ，選擇"增加容量"。

再來選擇"擴充現有..........."。

第三步，要先在分割之前的圖，點選vmfs區塊，然後就會出現一個調整新增容量的設定，選擇要把新增的硬碟，擴充多少容量到vmfs中。

按下完成後，就會出現錯誤，試了很多次，擴充不同的容量，都一樣錯誤:

說明:延伸 VMFS 資料存放區範圍的容量

狀態:失敗 - 無法變更主機組態。

解決過程:

用指令的方式擴充，就成功了。

Environment:

ESXi 6.7

Issue:

After expanding the underlying RAID by adding a new disk, the datastore also needs to be extended in ESXi.

When performing the operation via the web console:

1. Select the datastore and choose “Increase capacity”
2. Then select “Expand existing…”
3. In the partition layout screen, select the VMFS partition, and adjust how much of the newly added space should be allocated to VMFS

However, after clicking Finish, the following error occurs regardless of the size selected:

• Description: Extend VMFS datastore capacity
• Status: Failed – Unable to change the host configuration

Resolution:

Expanding the datastore using the command line (CLI) was successful.

HP ESXI 6.5 升級7.0 U3

原本的ESXI是HP專用6.5版，為了安裝比較新的win server os，要升級ESXI。

目前ESXI已無免費版，所以是去HP的官網下載裡面最新版本的ESXI(https://support.broadcom.com/c/portal/login?formDate=1742174666301&saveLastPath=false&redirect=%2Fgroup%2Fecx%2Fproductfiles%3FsubFamily%3DVMware%2520vSphere%26displayGroup%3DVMware%2520vSphere%2520-%2520Enterprise%2520Plus%26release%3D7.0%26os%3D%26servicePk%3D202621%26language%3DEN&idpEntityId=https%3A%2F%2Faccess.broadcom.com%2Fdefault)

升級方式

1.先把iso做成開機usb，插上server。

2.server重開機，讀取usb。

3.在安裝選項的地方，選擇升級esxi。

4.安裝完成重開機。

時間很快，不到15分鐘就好了，但有一個地方要注意的事，升級後，之前使用的6.5免費版授權序號就不能用了，登入esxi web console時，就會提示目前是60天試用版。

這時只要在輸入7.0免費版的esxi序號啟動就行了，這個序號沒有分是不是用在某一廠牌伺服器專用的esxi，只要是7.0都通用。

The original ESXi was an HP-specific version of 6.5. To install a newer Windows Server OS vm, an ESXi upgrade is required.

Since ESXi no longer offers a free version, the latest version was downloaded from HP’s official website:
HP ESXi Download.

Upgrade Process:

1. Create a bootable USB from the ISO and plug it into the server.
2. Reboot the server and boot from the USB.
3. In the installation options, select "Upgrade ESXi."
4. After installation, reboot the server.

The upgrade is fast, taking less than 15 minutes. However, one important thing to note is that after upgrading, the previous ESXi 6.5 free license will no longer work. When logging into the ESXi web console, it will indicate that the current version is a 60-day trial.

To resolve this, simply enter a free ESXi 7.0 license key to activate it. This key is not brand-specific and works for any ESXi 7.0 installation.

ESXI 7.0 安裝好WINDOWS 2019 無法使用ctrl alt del

剛裝好一台 ESXI 7.0，在上面建好一台win2019的虛擬機後，要傳送ctrl +alt +del做登入時，都沒反應。

之前也遇過，不過那是做了windows更新，裝到了vmtool造成的，這次卻是裝好win2019就沒辮法登入了。

後來發現是因為裝好後，通常都會直接選擇"開啟瀏覽器主控台"，然後操作，有時後傳送ctrl +alt +del會失效。

改用"啟動遠端主管台"來傳送ctrl +alt +del，就可以了。

Just installed an ESXi 7.0 server, and after setting up a Windows Server 2019 virtual machine on it, I found that pressing ctrl + alt + del to log in doesn't work.

I've encountered a similar issue before, usually caused by Windows updates or installing VMtools. However, this time, even after setting up Windows Server 2019, I couldn't log in.

Later, I realized that after installation, I typically chose "Open Browser Console" directly, and sometimes sending ctrl + alt + del wouldn't work.

Switching to "Launch Remote Console" to send ctrl + alt + del solved the issue.

VMWARE匯入OVA失敗-硬體系列 vmx-18 不受支援

在新建虛擬機，從esxi要匯入一個 ova檔時，最後一步出現錯誤:硬體系列 vmx-18 不受支援

原因是此ova是比較新的esxi建的，現在要匯入到比較舊的esxi所以無法支援，只要在esxi升級就行了。

When creating a new virtual machine, an error occurs in the last step when importing an ova file from ESXi: "Hardware series vmx-18 is not supported."

The reason for this error is that the ova was created with a newer version of ESXi and is now being imported to an older version of ESXi, which does not support the vmx-18 hardware series. The solution is to upgrade ESXi to a version that supports the vmx-18 hardware series.

ESXi 6.5 的windows 2012虛擬機傳送ctrl alt del沒反應

在ESXi 6.5架設了一台windows 2012虛擬機，開啟了遠端桌面連線的功能，都可以使用，接著安裝了vmtool重開機後，使用chrome透過esxi的web console要登入主機時，傳送ctrl alt del沒反應。

使用遠端桌面連線，輸入完帳號密碼後，也都連不上，非常奇怪。

查了一下google，vmware有一篇文章是說要升級esxi，這個就先不考慮。

在經過一些測試後發現，是透過windows update進行更新時，會有一個vmware的套件，安裝了這個後，才會有傳送ctrl alt del沒反應的問題，所以在做windows update時不要裝這個套件就好了。

I have set up a Windows 2012 virtual machine on ESXi 6.5 and enabled the Remote Desktop Connection feature, which was working fine. Then I installed vmtools and rebooted the virtual machine. After that, when I tried to log in to the host using Chrome via ESXi's web console and sent Ctrl+Alt+Del, there was no response.

I also tried using Remote Desktop Connection, but after entering the username and password, I couldn't connect, which is very strange.

After searching on Google, I found an article from VMware suggesting upgrading ESXi, but for now, I'm not considering that option.

After some testing, I discovered that when updating through Windows Update, there is a VMware package that, when installed, causes the issue with Ctrl+Alt+Del not working. So, when performing Windows Update, it's advisable not to install this package.

win虛擬機無法正常運作 開機出現錯誤 0xC0000017

 今天把一台esxi的虛擬機做還原後，開機出現錯誤，錯誤代碼是0xC0000017，還說什麼系統檔案可能有錯誤，安全模式或回複到上次正常啟動都沒用。

最後就進設定看，發現，記憶體設定只有16m，好小啊，調成16g後，就可以正常開機了，虛驚一場。

Unable to Boot Win Virtual Machine - Error 0xC0000017

Today, after restoring a virtual machine on ESXi, I encountered an error during the boot process. The error code was 0xC0000017, indicating a possible issue with the system files. I tried starting in Safe Mode and even attempted to revert to the last known good configuration, but none of these options resolved the problem.

In a final attempt to troubleshoot, I accessed the settings and discovered that the memory allocation was set to a mere 16MB. It was a surprisingly low value. After adjusting it to 16GB, the virtual machine was able to boot up successfully. It turned out to be a false alarm, and the issue was resolved.

DELL R740 安裝esxi 6.7 找不到硬碟

在一台新買進來的DELL R740要安裝ESXI6.7時，居然一直找不到內建的硬碟。

已在IDRAC裡確認RAID5的虛擬硬碟已建立了，但在裝ESXI時就是找不到。

後來就上網亂找，發現DELL官網有出ESXI6.7的安裝檔，居然就可以了，實在有點麻煩。

可以在下列網站去下載:

 https://www.dell.com/support/home/zh-tw/drivers/driversdetails?driverid=j75ny

When attempting to install ESXi 6.7 on a newly purchased DELL R740, the internal hard drive couldn't be detected.

I verified in IDRAC that a RAID5 virtual disk had been created, but during the ESXi installation, it remained inaccessible.

Afterwards, I searched online and discovered that DELL's official website offered an ESXi 6.7 installation file, which surprisingly resolved the issue. It was a bit troublesome, though.

You can download it from the following website:

https://www.dell.com/support/home/zh-tw/drivers/driversdetails?driverid=j75ny

把vmware上的虛擬機硬碟縮小

 在vmware上，要把虛擬機的硬碟放大很簡單，但如果要縮小，就有些難度了，剛好看到一篇文章有仔細的介紹，分享一下。

http://woshub.com/shrinking-vmdk-virtual-disk-vmware-esxi/

ESXI 5.5 megaraid 設定問題

 在esxi5.5上裝好megaraid的程式後，雖然可以從vsphere client上看到raid卡跟硬碟的資訊，但還是無法做一些設定上的調整。

要調整的話，一個是重開機從webios裡去調。另一個就是需要用gui的megaraid。

gui的megaraid沒辦法直接弄在vsphere client上，這時就需要在esxi上，找一台windows的虛擬機，在上面安裝gui的megaraid程式，裝好後，megaraid要記得設定"display all the system....."。

然後還要在這台windows的hosts檔案上加一筆esxi的host跟ip對應。

然後esxi上的cim server服務也要啟動，做完這些動作就沒問題了。

如果hosts上沒有加ip跟hostname的對應紀錄，就會有"unable to connect to cimom server"的錯誤。

ESXI主機監控RAID

 一般windows主機的伺服器，都可以裝RAID程式直接做監控或調整設定，但esxi就沒辦法直接這樣用，但還是有其他辦法，就是有裝在esxi上的程式，裝好後，在用其他windows上的raid管理程式連到esxi監控就行了，可以參考下例的網址，懶的打自己的安裝過程了。

http://kbwangtw.blogspot.com/2018/09/vm-esx-65-megaraid-driver-vmware.html

X3650 M3 安裝esxi 6.0 6.5 6.7 失敗 boot from cd/dvd rom failed

 拿了一台老舊的X3650 M3要安裝esxi 6.0 /6.5/ 6.7 ，都會失敗，一開始就讀不到安裝光碟，都會顯示failed。

上網查了一下是有人在這個型號上安裝6.0成功，所以就覺得應該要可以才對，但後來換了一片5.5的來裝，就成功了，看來只能裝比較低的版本，在來升級試式。

VMWARE ESXI上看到的硬碟空間與LINUX虛擬機上看到的硬碟空間不同

 假如在esxi上切了幾顆硬碟要來裝linux虛擬機，會發現裝完後，在linux上用fdisk所列出來的容量跟esxi管理介面上看到的不同，還差蠻多的。

原來是因為在esxi上b->->k->m->g的容量換算都是1024，但在linux上是1000。所以在linux上看到的容量都會比在esxi上看到的還大，硬碟切愈大，差愈多。

vmware ha切換

 vmware授權版，有ha的機制，如果第一台實台機異常當掉，上面的虛擬機當然就移轉到第二台運作。

今天在做關機維護時，卻發生一件事，在關機前，用正常的方式關閉虛擬機，然後在把第一台實台機給關了，因為上面虛擬機先關了，所以也沒設成維護模式。

後來實體機開機後，也從vcenter上把虛擬機也都正常啟動，以為都沒問題後，卻發現，所有虛擬機都是在第二台實體機上，並沒有在第一台，傻眼啊。

難道是我關機前沒設成維護模式的關係嗎，只好在找時間做移轉了。

VMWARE虛擬機無法編輯 "you cannot use the vsphere client to edit the settings of virtual machies of version 10 or higher"

在vsphere client 5.5上面要編輯一台虛擬機的設定時，會跳出這個錯誤，無法編輯，這也不像訊息裡寫的有什麼web介面可以來設定。
原來vsphere client 5.5還有分版本，自己用的比較舊，在去找新一點的來登入，就可以編輯虛擬機的設定了。

VMWARE OVF匯入失敗 "Failed to deploy ovf package invalid configuration for device ‘6’"

為了調整硬體資源，要把一台虛擬機從A實體機移到B，匯出成OVF的時後都ok，但要在另一台匯入時就出現錯誤＂
VMware – Failed to deploy ovf package invalid configuration for device ‘6’＂
解法就是先在虛擬機的設定上，移除光碟機這個裝置，然後在重新匯出一份，再來做匯入就行了。

VMWARE 移轉到 XEN Server

要安裝虛擬機，除了HyperV & VMWARE，還有一個Citrix出的Xen Server可以用。
Xen Server有什麼好咧，除了有免費版以外，免費版提供了HA的功能(舊版)，這就是VMWARE免費版沒有的東西。
要把VMWARE上的虛擬機轉到Xen Server上的話，Citrix官網會教你先在VMWARE上把虛擬機關閉，匯出成OVF，然後在用Xen Convert來做匯入到Xen Server，結果就是失敗，做了好多次都是失敗。
原來不用這麼麻煩，Xen Server有一個管理工具叫Xen Center，就像vsphere client一樣，除了管理Xen Server，它也可以直接用來把VMWARE匯出的OVF直接匯入到Xen Server，匯完什麼都不用改就可以開機使用了。
原廠的教學實在多此一舉。

VMWARE 虛擬機設定手動MAC Address : 無法開啟虛擬機器 它與VMWARE保留的MAC衝突

最近在測試虛擬機的備份跟還原，將備份的虛擬機，要還原到另一台測試的ESXI裡面，虛擬機的MAC要保持相同。
原本的虛擬機在建置時，是設定自動產生MAC，所以MAC是00:0C:29開頭。
還原到其他台ESXI之後，要將虛擬機的MAC設定改成手動，然後輸入還本的MAC時，就跳出"無法開啟虛擬機器的電源，乙太網路位址不允許。它與VWMARE保留的MAC衝突 "。
原是因當你把MAC設定調成手動時，MAC的開頭不能是"00:0C:29"，因為這段MAC通通都只能讓ESXI自動產生，所以就算你設定好了，開機就會產生錯誤無法啟動。





這時只要用ssh連上ESXI，切換到 "vmfs/volumes/虛擬機所在的datastore/虛擬機名字"，然後用vi去編輯裡面有一個.vmx的檔案。
找到你的網卡，通常就叫ethernet0.addressType = "generated"，在它上面自己加一行ethernet0.checkMACAddress = “false”，然後在把addressType改成ethernet0.addressType = "static"就行了。
MAC Address的部份可直接在圖形介面上設定即可。

VMWARE virtual machine manual MAC Address configuration: Unable to power on the virtual machine due to MAC conflict with VMWARE's reserved MAC.

Recently, I was testing the backup and restore of virtual machines. I needed to restore a backup of a virtual machine to another ESXi server for testing purposes while keeping the MAC address of the virtual machine the same.

The original virtual machine was set to automatically generate a MAC address, starting with "00:0C:29." After restoring it to another ESXi server, I had to manually configure the MAC address of the virtual machine. However, when I entered the original MAC address, an error message appeared stating, "Cannot power on virtual machine. The Ethernet address is not allowed. It conflicts with the MAC address reserved by VMWARE."

The issue arises when you switch the MAC address configuration to manual, and the MAC address starts with "00:0C:29." This range of MAC addresses is reserved for automatic generation by ESXi, so even if you configure it correctly, an error occurs when trying to power on the virtual machine.

To resolve this, you can SSH into the ESXi server and navigate to "vmfs/volumes/datastore_name/virtual_machine_name." Then, use the vi editor to modify the .vmx file within that directory.

Locate the network adapter section, which is typically named ethernet0.addressType = "generated." Add a new line above it with the following entry: ethernet0.checkMACAddress = "false". Then, change the addressType to ethernet0.addressType = "static".

For configuring the MAC address, you can do that directly in the graphical interface.