{"id":208,"date":"2023-01-09T18:11:33","date_gmt":"2023-01-10T00:11:33","guid":{"rendered":"https:\/\/blog.mctechnologies.net\/?p=208"},"modified":"2023-01-09T18:14:47","modified_gmt":"2023-01-10T00:14:47","slug":"update-to-vmware-esxi-8-0-with-unsupported-cpus","status":"publish","type":"post","link":"https:\/\/blog.mctechnologies.net\/?p=208","title":{"rendered":"Update to VMWare ESXi 8.0 with Unsupported CPUs"},"content":{"rendered":"\n<p>Obligatory: DON&#8217;T DO THIS IN A PRODUCTION ENVIRONMENT, YOU SHOULDN&#8217;T REALLY DO THIS AT ALL<\/p>\n\n\n\n<p>I use two Atom C2550 servers in my homelab so I can have a little redundancy and can offload some low priority, low CPU intensive servers off my main server, but the new ESXi 8.0 doesn&#8217;t support them any longer.  Here are the steps I used to rectify the situation.  It works with both VCenter Images and command line updates.  <\/p>\n\n\n\n<p>Step 1:  Edit \/bootbank\/boot.cfg &amp; \/altbootbank\/boot.cfg and and add&nbsp;&#8220;allowLegacyCPU=true&#8221; (no quotes, a space between options) on the&nbsp;&#8220;kernelopt&#8221; line, then reboot. Example:<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"656\" height=\"421\" src=\"https:\/\/blog.mctechnologies.net\/wp-content\/uploads\/2023\/01\/image.png\" alt=\"\" class=\"wp-image-209\" srcset=\"https:\/\/blog.mctechnologies.net\/wp-content\/uploads\/2023\/01\/image.png 656w, https:\/\/blog.mctechnologies.net\/wp-content\/uploads\/2023\/01\/image-300x193.png 300w, https:\/\/blog.mctechnologies.net\/wp-content\/uploads\/2023\/01\/image-80x51.png 80w\" sizes=\"auto, (max-width: 656px) 100vw, 656px\" \/><\/figure>\n\n\n\n<p>Step 2: (Skip below for command line) You can now use the Image Update built into VSphere to update the unsupported CPU.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"660\" src=\"https:\/\/blog.mctechnologies.net\/wp-content\/uploads\/2023\/01\/image-1-1024x660.png\" alt=\"\" class=\"wp-image-212\" srcset=\"https:\/\/blog.mctechnologies.net\/wp-content\/uploads\/2023\/01\/image-1-1024x660.png 1024w, https:\/\/blog.mctechnologies.net\/wp-content\/uploads\/2023\/01\/image-1-300x193.png 300w, https:\/\/blog.mctechnologies.net\/wp-content\/uploads\/2023\/01\/image-1-768x495.png 768w, https:\/\/blog.mctechnologies.net\/wp-content\/uploads\/2023\/01\/image-1-80x52.png 80w, https:\/\/blog.mctechnologies.net\/wp-content\/uploads\/2023\/01\/image-1.png 1303w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p>Alternative Step 2: I use this website to get the command line to update to a specific version: <a href=\"https:\/\/esxi-patches.v-front.de\/\">esxi-patches.v-front.de<\/a>  add &#8220;&#8211;no-hardware-warning&#8221; (no quotes) to the update command.  Run the command (it took a few minutes of not doing anything) then reboot. <br>My example command:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>esxcli network firewall ruleset set -e true -r httpClient\nesxcli software profile update  -p ESXi-8.0a-20842819-standard -d https:\/\/hostupdate.vmware.com\/software\/VUM\/PRODUCTION\/main\/vmw-depot-index.xml  --no-hardware-warning\nesxcli network firewall ruleset set -e false -r httpClient<\/code><\/pre>\n\n\n\n<p>Result:<\/p>\n\n\n\n<figure class=\"wp-block-image size-full is-resized\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/blog.mctechnologies.net\/wp-content\/uploads\/2023\/01\/image-2.png\" alt=\"\" class=\"wp-image-214\" width=\"816\" height=\"562\" srcset=\"https:\/\/blog.mctechnologies.net\/wp-content\/uploads\/2023\/01\/image-2.png 816w, https:\/\/blog.mctechnologies.net\/wp-content\/uploads\/2023\/01\/image-2-300x207.png 300w, https:\/\/blog.mctechnologies.net\/wp-content\/uploads\/2023\/01\/image-2-768x529.png 768w, https:\/\/blog.mctechnologies.net\/wp-content\/uploads\/2023\/01\/image-2-80x55.png 80w\" sizes=\"auto, (max-width: 816px) 100vw, 816px\" \/><\/figure>\n","protected":false},"excerpt":{"rendered":"<p>Obligatory: DON&#8217;T DO THIS IN A PRODUCTION ENVIRONMENT, YOU SHOULDN&#8217;T REALLY DO THIS AT ALL I use two Atom C2550 servers in my homelab so I can have a little redundancy and can offload some low priority, low&#8230; <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-208","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/blog.mctechnologies.net\/index.php?rest_route=\/wp\/v2\/posts\/208","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.mctechnologies.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.mctechnologies.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.mctechnologies.net\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.mctechnologies.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=208"}],"version-history":[{"count":8,"href":"https:\/\/blog.mctechnologies.net\/index.php?rest_route=\/wp\/v2\/posts\/208\/revisions"}],"predecessor-version":[{"id":219,"href":"https:\/\/blog.mctechnologies.net\/index.php?rest_route=\/wp\/v2\/posts\/208\/revisions\/219"}],"wp:attachment":[{"href":"https:\/\/blog.mctechnologies.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=208"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.mctechnologies.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=208"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.mctechnologies.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=208"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}