remaker
Contributor
Contributor

Catalina (15.0.16) Beta in a VM - Hung at "Apple" boot screen in VMWare Fusion

Jump to solution

The latest Apple macOS Catalina Beta is hanging at the "APPLE" screen during the install process.

Whether I boot directly from the installer or upgrade a working Mojave 10.14 installation, the result is the same.

I have run the installed with the  Machine type to macOS 10.14.

I tried setting machine type to "Windows 10 x64" and "Other 64 bit" to no avail.

It looks like it has attached a second VMDK ("Temporary Installation Source Disk") that is a Temporary Installer and it can't boot to that.

VMWare Fusion Professional Version 11.1.0 (13668589)

I can see fs2: from the EFI command prompt. The boot.efi file is there, but it hangs at the Apple logo...

1 Solution

Accepted Solutions
remaker
Contributor
Contributor

I'm pleased to report that once I upgraded to VMWare Fusion Pro 11.5, my dead, unbootable VMs have leaped to life after a hard restart and are finishing the Catalina installs as I sit here and type this message.

Hats off to Mikero​ for his prompt responsiveness on and off this forum.

Of course, it's a little late to test the Beta Versions of Catalina at this point, but it looks like the released MacOS Catalina 10.15 upgrade to Mojave 10.14 is installing just fine as a guest.

And, of course, the MacOS 10.15 is listed as a supported machine type, woohoo!

While I understand that the upgrade from 10.14 to 10.15 inside a guest is officially "not supported," it seems to have worked for me.

So, time for everyone to upgrade!

View solution in original post

0 Kudos
13 Replies
remaker
Contributor
Contributor

The lead up to the crash.

2019-07-02T16:57:22.671-08:00| svga| I125: SVGA enabling SVGA

2019-07-02T16:57:22.779-08:00| svga| I125: SVGA-ScreenMgr: Screen type changed to RegisterMode

2019-07-02T16:57:22.780-08:00| mks| I125: SWBWindow: Number of MKSWindows changed: 1 rendering MKSWindow(s) of total 1.

2019-07-02T16:57:22.780-08:00| windowThread-49| I125: VTHREAD 123145518579712 "windowThread-49" tid 25966397

2019-07-02T16:57:22.780-08:00| mks| I125: MKS-HWinMux: Started MacOS presentation backend

2019-07-02T16:57:22.847-08:00| mks| I125: SWBWindow: Number of MKSWindows changed: 2 rendering MKSWindow(s) of total 2.

2019-07-02T16:57:24.550-08:00| vcpu-0| I125: AHCI-VMM:HBA reset issued on sata0.

2019-07-02T16:57:24.550-08:00| vcpu-0| I125: AHCI-VMM: sata0:0: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.550-08:00| vcpu-0| I125: AHCI-VMM: sata0:1: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.550-08:00| vcpu-0| I125: AHCI-VMM: sata0:2: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.550-08:00| vcpu-0| I125: AHCI-VMM: sata0:3: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.550-08:00| vcpu-0| I125: AHCI-VMM: sata0:4: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.550-08:00| vcpu-0| I125: AHCI-VMM: sata0:5: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.550-08:00| vcpu-0| I125: AHCI-VMM: sata0:6: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.551-08:00| vcpu-0| I125: AHCI-VMM: sata0:7: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.551-08:00| vcpu-0| I125: AHCI-VMM: sata0:8: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.551-08:00| vcpu-0| I125: AHCI-VMM: sata0:9: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.551-08:00| vcpu-0| I125: AHCI-VMM: sata0:10: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.551-08:00| vcpu-0| I125: AHCI-VMM: sata0:11: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.551-08:00| vcpu-0| I125: AHCI-VMM: sata0:12: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.551-08:00| vcpu-0| I125: AHCI-VMM: sata0:13: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.551-08:00| vcpu-0| I125: AHCI-VMM: sata0:14: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.551-08:00| vcpu-0| I125: AHCI-VMM: sata0:15: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.551-08:00| vcpu-0| I125: AHCI-VMM: sata0:16: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.551-08:00| vcpu-0| I125: AHCI-VMM: sata0:17: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.551-08:00| vcpu-0| I125: AHCI-VMM: sata0:18: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.551-08:00| vcpu-0| I125: AHCI-VMM: sata0:19: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.551-08:00| vcpu-0| I125: AHCI-VMM: sata0:20: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.551-08:00| vcpu-0| I125: AHCI-VMM: sata0:21: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.551-08:00| vcpu-0| I125: AHCI-VMM: sata0:22: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.551-08:00| vcpu-0| I125: AHCI-VMM: sata0:23: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.551-08:00| vcpu-0| I125: AHCI-VMM: sata0:24: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.551-08:00| vcpu-0| I125: AHCI-VMM: sata0:25: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.551-08:00| vcpu-0| I125: AHCI-VMM: sata0:26: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.551-08:00| vcpu-0| I125: AHCI-VMM: sata0:27: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.551-08:00| vcpu-0| I125: AHCI-VMM: sata0:28: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.551-08:00| vcpu-0| I125: AHCI-VMM: sata0:29: PxSCTL.DET already 0. Ignoring write 0.

2019-07-02T16:57:24.675-08:00| vcpu-0| I125: SCSI0: RESET BUS

2019-07-02T16:57:24.675-08:00| vcpu-0| I125: SCSI0: RESET BUS

2019-07-02T16:57:24.890-08:00| vcpu-0| I125: Guest: About to do EFI boot: EFI VMware Virtual SATA Hard Drive (0.0)

2019-07-02T16:57:26.708-08:00| vcpu-0| I125: Guest: KextInjectHandlePrelinkedKernelXHCI: Unable to find target.

2019-07-02T16:57:26.713-08:00| vcpu-0| I125: Guest: KextInjectHandlePrelinkedKernelXHCI: Unable to find target.

2019-07-02T16:57:26.718-08:00| vcpu-0| I125: Guest: KextInjectHandlePrelinkedKernelXHCI: Unable to find target.

2019-07-02T16:57:26.723-08:00| vcpu-0| I125: Guest: KextInjectHandlePrelinkedKernelXHCI: Unable to find target.

2019-07-02T16:57:26.735-08:00| vcpu-0| I125: UHCI: HCReset

2019-07-02T16:57:26.766-08:00| vcpu-1| I125: CPU reset: soft (mode 0)

2019-07-02T16:57:26.766-08:00| vcpu-0| I125: Guest: Firmware has transitioned to runtime.

2019-07-02T16:57:26.830-08:00| vcpu-0| I125: APIC THERMLVT write: 0xdc

2019-07-02T16:57:26.831-08:00| vcpu-0| I125: APIC CMCI LVT write: 0xd9

2019-07-02T16:57:29.629-08:00| vmx| I125: VNET: MACVNetLinkStateTimerHandler: 'ethernet0' state from 1 to 5.

2019-07-02T16:57:47.330-08:00| vcpu-0| I125: Tools: Tools heartbeat timeout.

2019-07-02T16:57:47.330-08:00| vcpu-0| I125: Tools: Running status rpc handler: 1 => 0.

2019-07-02T16:57:47.330-08:00| vcpu-0| I125: Tools: Changing running status: 1 => 0.

2019-07-02T16:57:47.330-08:00| vcpu-0| I125: Tools: [RunningStatus] Last heartbeat value 3 (last received 20s ago)

0 Kudos
remaker
Contributor
Contributor

And the verbose boot reports

panic(cpu 0 caller (elided)): "Unable to find driver for this platform: \"ACPI\"./n"@\BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6110.0.0.121.5/iokit/Kernel/IIPlatformExpert.cpp:1994

Is the " improperly escaped?

Anyway. There we are.

0 Kudos
remaker
Contributor
Contributor

The instructions at https://planetvm.net/blog/?p=64552 helped.

But it wasn't totally clear.

In my case, I set the machine type to Windows 10 x64, and the boot failed (took a few minutes to time out) but then the EFI Bue menu appeared.

I selected the item from the EFI boot menu with a number "2" in it (second disk, the installer).

And now, I am at the installer. Weirdness. Will continue to report.

0 Kudos
remaker
Contributor
Contributor

So, for the step to create ine installer, it needs to be in macOS 10.14 mode,

For all of the steps running the INSTALLER VMDK (initial boot and config, second boot "About x minutes remaining), the mode needs to be in Windows 10 x64.

For the boot of the completely installed system, it should be switched back to macOS 10.14.

Seems like a correctly set up macOS 10.5 profile, when created, might fix this.

0 Kudos
wila
Immortal
Immortal

Hi,

Happy to hear that the blog post helped.

Apple still appears to change things in the install process.

Also ran the installer 2 times while writing that article and the second time the steps were slightly different from the first time.

Which is really weird to see.

Thanks for your comments here and at the planetvm site.

Don't have the time atm to rerun the installer and update the article, but that time will come again soon.

After all, I gotta get Vimalin ready for Catalina as well.

--

Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
remaker
Contributor
Contributor

I ran the Beta 2 software update, and I am stuck at the White-apple-on-black-screen again.,

So the workaround works for a fresh, new install, but fails hard and unrecoverably on an update.

For a workaround, I will extract the installer and do another fresh install, but this is a problem that needs to be addressed in Fusion.

0 Kudos
gilby101
Enthusiast
Enthusiast

Like remaker, I have tried the PB2 update (approx same as DB3?) from a PB1 VM.

Verbose mode shows same issue as in a new build, but workarounds not helping (for me).

Screen Shot 2019-07-04 at 12.04.29 pm.png

remaker
Contributor
Contributor

I just had a quick email discussion with the VMWare Fusion PM who kindly replied to me. In summary:

  1. A future release of VMWare Fusion will be required for full support of Catalina guests, since Catalina has more major internal changes than any recent macOS releases.
  2. macOS/OS X in-place upgrades have never been officially supported by VMWare Fusion in guests; therefore a full install is the only official supported "upgrade" path for guests.
  3. VMWare has not announced any intention for public beta of VMWare Fusion to support Catalina Hosts or Guests.

Developers at VMWare are diligently working on the issues and he anticipates full support in VMWare Fusion for Catalina once it is actually released as macOS 10.15.

0 Kudos
IjustWantToRepo
Contributor
Contributor
  1. A future release of VMWare Fusion will be required for full support of Catalina guests, since Catalina has more major internal changes than any recent macOS releases.

Damnit. I just purchased v11 for the purpose of testing Catalina. I had no need for the new version otherwise. So I kind of wasted that money, it seems.

0 Kudos
wila
Immortal
Immortal

Hi,

I'm not convinced that that particular quote is true.

Reason being that the support life cycle says that support on Fusion 11 ends at 2020/03/24 and not September 2019.

See:

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/support/product-lifecycle-matrix.p...

Perhaps Mikero​ can provide us with more details?

--

Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
0 Kudos
Mikero
Community Manager
Community Manager

Those are indeed my words Smiley Wink

We do have the ability to modify our own support matrix if we so choose.

-
Michael Roy - PM/PMM: Fusion & Workstation
Mikero
Community Manager
Community Manager

You’re assuming I was referring to a paid upgrade. I just mean that there needs to be a supported build, not whether or not it would be a paid upgrade to get it. Hold fast, friend Smiley Happy

-
Michael Roy - PM/PMM: Fusion & Workstation
remaker
Contributor
Contributor

I'm pleased to report that once I upgraded to VMWare Fusion Pro 11.5, my dead, unbootable VMs have leaped to life after a hard restart and are finishing the Catalina installs as I sit here and type this message.

Hats off to Mikero​ for his prompt responsiveness on and off this forum.

Of course, it's a little late to test the Beta Versions of Catalina at this point, but it looks like the released MacOS Catalina 10.15 upgrade to Mojave 10.14 is installing just fine as a guest.

And, of course, the MacOS 10.15 is listed as a supported machine type, woohoo!

While I understand that the upgrade from 10.14 to 10.15 inside a guest is officially "not supported," it seems to have worked for me.

So, time for everyone to upgrade!

0 Kudos