WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud
  • Tanzu
    • Application Modernization
    • Tanzu services
    • Tanzu Community Edition
    • Tanzu Kubernetes Grid
    • vSphere with Tanzu
  • Home Lab
  • Nested Virtualization
  • Apple
You are here: Home / Apple / Heads Up - Apple Mac Pro 6,1 fails to boot after upgrading to ESXi 6.7 Update 1

Heads Up - Apple Mac Pro 6,1 fails to boot after upgrading to ESXi 6.7 Update 1

11.16.2018 by William Lam // 13 Comments

We had a number of customers report that after upgrading their Apple Mac Pro 6,1 to the latest ESXi 6.7 Update 1 release, the system failed to boot and the following error was seen on the console:

Shutting down firmware services...
Mutiboot buffer is too small.
Unrecoverable error

A few customers made the observation that this was in result of a newer version of the Apple Firmware that was included in the Mac Pro 6,1 systems which seemed to have cause this problem. In addition, this also impacts brand new installations of ESXi 6.7 Update 1 on new Mac Pro 6,1 that includes a newer version of the Firmware. At this time, is it NOT recommended to upgrade to ESXi 6.7 Update 1 if you are running the Mac Pro 6,1. A request has already been made to the VMware HCL team to remove Mac Pro 6,1 for ESXi 6.7 Update 1 and hopefully should be reflected by later this evening.

UPDATE 04/11/19 - This issue has been resolved in vSphere 6.7 Update 2

Note: This issue can also affect the Apple Mac Mini, which is not an officially supported platform for ESXi.

In the mean time, VMware has published KB 59660 which provides a workaround that may help customers who have upgraded their Mac Pro 6,1 to ESXi 6.7 Update 1 to rollback to the previously installed version of ESXi. Please refer to the KB for more details and you can subscribe to the article for future updates regarding this issue.

More from my site

  • vSphere 8 on Apple Mac Hardware
  • vSphere ESXi 7.x will be last version to officially support Apple macOS Virtualization
  • Aquantia/Marvell AQtion (Atlantic) driver now inbox in ESXi 7.0 Update 2
  • Apple NVMe driver for ESXi using new Community NVMe Driver for ESXi Fling 
  • GPU passthrough with ESXi on the Apple 2019 Mac Pro 7,1

Categories // Apple, ESXi Tags // apple, ESXi 6.7 Update 1, vSphere 6.7 Update 1

Comments

  1. Eric Garrison says

    11/16/2018 at 9:59 am

    I did run into this several times and also recommended sticking to 6.7 GA.

    Reply
  2. specter345 says

    11/16/2018 at 12:48 pm

    When installing ESXi 6.7 U1 on a Mac Pro with the latest firmware, using 'preferVmklinux=true' method seems to result in a successful install.

    Reply
  3. Tim S. says

    11/19/2018 at 7:58 am

    Ugghh ESXi on Laptop?!?

    I'll stick with VMware Fusion 10 for the Mac!

    Reply
  4. hjlinde says

    11/27/2018 at 3:20 am

    Was just re-installing my two mac minis with 6.7U1 and ran into the same issue. However after doing a PRAM reset and shutting down the mac it all started to work. On the other mac mini though I had to reboot a few times and eventually it fixed itself again. One thing to note... When it works correctly it says the following:

    "Shutting down firmware services...
    Using 'simple offset' UEFI RTS mapping policy
    Relocating modules and startup the kernel..."

    After finishing the fresh installation. I havent had any issues as yet when rebooting. Seems to start up fine every time now.

    Reply
    • Mart says

      02/18/2019 at 5:22 am

      Confirmed.
      Tested the PRAM reset (3 additional startup chimes) + shutdown on a MacMini5,3 after it got stuck when I applied the 6.7U1 update. At the next boot, it proceeded past the point where the error messages appeared before. It made one additional reboot (maybe to complete version upgrade), but has booted stable afterwards. ESXi build is now at 8169922. The Mac firmware has not been upgraded since it ran OSX 10.10.

      Reply
  5. paul says

    01/31/2019 at 11:48 am

    FWIW, I tried resetting the PRAM and SMC on a MacPro6,1 and installing update 1 again with no difference in result.

    Reply
  6. Gokalp says

    04/01/2019 at 3:35 pm

    I was able to boot with a brand new install on the MacPro6,1 to 6.7 U1. I updated the bootrom to 129.0.0.0.0 by installing Mojave 10.14.2 to the local SSD and updated to 10.14.4 to get the latest bootrom. https://www.dropbox.com/s/9wlb4sefcmlyzao/BOOT%20ROM%20AFTER%2010.14.4.png?dl=0

    Reply
    • Gokalp says

      04/01/2019 at 4:04 pm

      Removed Serial Number from image: https://www.dropbox.com/s/g8f6lxydvc858bm/BOOT%20ROM%20AFTER%2010.14.4%20-%20open.png?dl=0

      Reply
  7. Gokalp says

    04/01/2019 at 4:14 pm

    Can we get 6.7 u1 added back to the HCL since it now works with latest bootrom bundled with 10.14.4 of MacOs Mojave?

    Reply
    • William Lam says

      04/02/2019 at 10:18 am

      Hi Gokalp,

      Thanks for sharing the update regarding the latest bootrom from Apple. At this time, the fix that's been put in place will be included in the upcoming vSphere 6.7 Update 2 release (which was just announced today, see https://blogs.vmware.com/vsphere/2019/04/announcing-vsphere-6-7-update-2-vsphere-platinum-updates-and-vsphere-robo-enterprise.html) and will be available at a later time. Once ESXi 6.7 Update 2 is released, the HCL will be updated to add support for the Mac Pro 6,1 and there is no plan to update that for 6.7 Update 1 at this time

      Reply
  8. Steve says

    04/07/2019 at 12:32 pm

    Just hold down the alt key to force the mac boot device Selektion. Then press and hold down STRG while klicking on the Boot drive icon (the arrow should turn into an Cycle Arrow). After this ESXi is Booting Fine every Time.

    Reply
  9. SHYAM GOPAL says

    06/11/2020 at 4:21 pm

    Any idea if its normal for the Macpro 6,1 running esxi 6.7 u3, to go to sleep (running but not responding to ping) after the display is disconnected ? Reconnecting the display does not bring it back.

    Reply
    • SHYAM says

      06/12/2020 at 11:18 am

      Update: The Macpro is not asleep. It continues to function correctly after the display is removed, however as soon as I plug in the thunderbolt it crashes immediately. This seems to point to a driver issue. Not sure how to figure this out, but if I do I will post it here.

      Reply

Thanks for the comment! Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Author

William Lam is a Senior Staff Solution Architect working in the VMware Cloud team within the Cloud Infrastructure Business Group (CIBG) at VMware. He focuses on Cloud Native technologies, Automation, Integration and Operation for the VMware Cloud based Software Defined Datacenters (SDDC)

Connect

  • Email
  • GitHub
  • LinkedIn
  • RSS
  • Twitter
  • Vimeo

Recent

  • ESXi configstorecli enhancement in vSphere 8.0 Update 1 03/28/2023
  • ESXi on Intel NUC 13 Pro (Arena Canyon) 03/27/2023
  • Quick Tip - Enabling ESXi Coredumps to be stored on USB 03/26/2023
  • How to disable the Efficiency Cores (E-cores) on an Intel NUC? 03/24/2023
  • Changing the default HTTP(s) Reverse Proxy Ports on ESXi 8.0 03/22/2023

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2023