{"id":506,"date":"2025-03-05T11:12:04","date_gmt":"2025-03-05T10:12:04","guid":{"rendered":"https:\/\/vmoller.dk\/?p=506"},"modified":"2025-03-05T13:20:19","modified_gmt":"2025-03-05T12:20:19","slug":"lenovo-vx-nodes-and-iavmd-downgrade-in-vlcm","status":"publish","type":"post","link":"https:\/\/vmoller.dk\/index.php\/2025\/03\/05\/lenovo-vx-nodes-and-iavmd-downgrade-in-vlcm\/","title":{"rendered":"Lenovo VX nodes and iavmd downgrade in vLCM"},"content":{"rendered":"<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"198\" src=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2025\/03\/iavmd-error2-1024x198.jpg\" alt=\"\" class=\"wp-image-513\" srcset=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2025\/03\/iavmd-error2-1024x198.jpg 1024w, https:\/\/vmoller.dk\/wp-content\/uploads\/2025\/03\/iavmd-error2-300x58.jpg 300w, https:\/\/vmoller.dk\/wp-content\/uploads\/2025\/03\/iavmd-error2-768x148.jpg 768w, https:\/\/vmoller.dk\/wp-content\/uploads\/2025\/03\/iavmd-error2.jpg 1072w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n<\/div>\n\n<div class=\"wp-block-image\">\n<figure class=\"aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"324\" height=\"226\" src=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2025\/03\/image.png\" alt=\"\" class=\"wp-image-511\" srcset=\"https:\/\/vmoller.dk\/wp-content\/uploads\/2025\/03\/image.png 324w, https:\/\/vmoller.dk\/wp-content\/uploads\/2025\/03\/image-300x209.png 300w\" sizes=\"auto, (max-width: 324px) 100vw, 324px\" \/><\/figure>\n<\/div>\n\n\n<p><\/p>\n\n\n\n<p>I have recently encountered the following error on several Lenovo VX systems, which prevents vLCM from initiating the upgrade from ESXi 7 to ESXi 8:<\/p>\n\n\n\n<p><em>Error: Version iavmd-3.0.0.1038 of the manually added Component Intel VMD driver with VROC support is an unsupported downgrade from version iavmd-3.5.1.1002 on the host.<br>Replace the Component in the image with one of the same or higher version.<\/em><\/p>\n\n\n\n<!--more-->\n\n\n\n<p>It appears that an earlier Lenovo VX recipe included &#8220;iavmd-3.5.1.1002,&#8221; but in version 8 of the recipe, the required version is lower (&#8220;iavmd-3.0.0.1038&#8221;). The simplest solution to resolve this issue is to remove the &#8220;iavmd&#8221; (Intel VMD driver) just before performing the upgrade. This can be done using either ESXCLI (via SSH) or PowerCLI with the following commands:<\/p>\n\n\n\n<p>With ESXCLI (remember to put the host in maintenance mode, first!):<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>esxcli software vib remove -n iavmd -f<\/code><\/pre>\n\n\n\n<p>With PowerCli (remember to put the host in maintenance mode, first!)<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>$esxcli = Get-EsxCli -VMHost &lt;insert hostname>\n$esxcli.software.vib.remove($false,$true,$false,$true,\"iavmd\")<\/code><\/pre>\n\n\n\n<p>The expected output should be this:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">Message : The update completed successfully, but the system needs to be rebooted for the changes to be effective.<br><br>RebootRequired : true<br>VIBsInstalled :<br>VIBsRemoved : {INT_bootbank_iavmd_3.5.1.1002-1OEM.700.1.0.15843807}<br>VIBsSkipped :<\/pre>\n\n\n\n<p>After the reboot, click &#8220;Check Compliance&#8221; in vLCM again, and then you should be able to resume the upgrade!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I have recently encountered the following error on several Lenovo VX systems, which prevents vLCM from initiating the upgrade from ESXi 7 to ESXi 8: Error: Version iavmd-3.0.0.1038 of the manually added Component Intel VMD driver with VROC support is an unsupported downgrade from version iavmd-3.5.1.1002 on the host.Replace the Component in the image with [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[48,20,25,57,8,7],"tags":[23,27,17,21,16,24,56,26,4],"class_list":["post-506","post","type-post","status-publish","format-standard","hentry","category-esxcli","category-esxi","category-powercli","category-vlcm","category-vsan","category-vsphere","tag-esxi","tag-lenovo","tag-patching","tag-powercli","tag-updating","tag-vcenter","tag-vlcm","tag-vsan","tag-vsphere"],"_links":{"self":[{"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/posts\/506","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/comments?post=506"}],"version-history":[{"count":21,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/posts\/506\/revisions"}],"predecessor-version":[{"id":533,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/posts\/506\/revisions\/533"}],"wp:attachment":[{"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/media?parent=506"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/categories?post=506"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vmoller.dk\/index.php\/wp-json\/wp\/v2\/tags?post=506"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}