Jump to content
Sign in to follow this  
Followers 0
br0adband

Catatalina Beta 10.15 - Anyone got it booting yet?

11 posts in this topic

Recommended Posts

So...

 

Here we go again with a new version of macOS and so far I haven't been able to get it booted in VMware Workstation, just curious if anyone else has either. Same old instructions to create a working bootable ISO function (same as Mojave but change the name of the installer app obviously). It won't boot past the Apple logo, can't boot into safe mode, or recovery either. Made several attempts so far to upgrade a clean Mojave VM using the Catalina installer app, still no joy on the reboot, it just hangs on the Apple logo with zero activity (no hard drive, network, nothing at all).

 

Of course Apple has made some changes, so now begins the troubleshooting and scoping out what's changed and how to work around it and get this thing up and running for some mucking around.

 

I suppose this would be a good thread to discuss all this in so, we'll see what happens. ;)

Share this post


Link to post
Share on other sites
Advertisement

That thread has nothing to do with running Catalina in a virtual machine, this one does and is specific to that purpose.

Share this post


Link to post
Share on other sites

Hm, here is working method to install Catalina in unlocked VMware Workstation:

First, you need working virtual machine with previous version of macOS. I used 10.13.6. Install macOSDeveloperBetaAccessUtility.dmg. Then download Catalina installer from AppStore, then run it. After preparing computer will be rebooted. And can't booted, you will see only apple logo, no disk activity, no processor activity. It's kernel panic. Just shutdown virtual machine, change type to Windows 10 x64 and start it again. Installation will continue. After next reboot virtual machine can not boot. Ok, shutdown it, change it type to macOS 10.14 back and start machine again. Installation will continue. That's all.

Share this post


Link to post
Share on other sites

I stuck on the Apple boot logo. When I switch the type to Windows X64 I only see error messages

Share this post


Link to post
Share on other sites

So I gave several attempts to this process as explained above by serezha and had no luck, even when I alter the machine type to Windows 10 x64 there's no activity once that kernel panic happens, no way apparently to get past it. I suppose we'll figure it out at some point, ain't in that much of a major hurry to get it working.

Share this post


Link to post
Share on other sites

VMware will likely need to fix something or it's an issue with the beta. I wouldn't expect proper support until Catalina is released which is usually when VMware release a new version of Fusion/Workstation. September timeframe.

Share this post


Link to post
Share on other sites
Posted (edited)

I managed to get Catalina 10.15 DB1 working in VMware Workstation 12 on a Windows 7 host :).

 

Spoiler

 

    

1611092860_CatalinaonVMware9.thumb.png.88d03d68b9a5a911093b4c1977df295b.png

 

 

 

 

As others have mentioned above, the VM will kernel panic for the second phase install (after "macOS Install Data" is written to the apfs target partition and the system reboots).

 

To bypass this problem, I added a 3GB HFS+ booter partition to which I restored Catalina's Base System.dmg (this 3GB partition comes after the apfs target partition), replaced the Packages symlink with a real Packages folder containing OSInstall.mpkg (extracted from InstallESD.dmg).

 

For the second phase install, temporarily change Guest OS Type to Windows 10 X64, and go into VMware BIOS (with F2 key) to boot macOS Base System\System\Library\CoreServices\boot.efi.  At the completion of the second phase, the system will attempt to reboot ---> shut down the VM and change Guest OS Type back to macOS.
 

Spoiler

 

1265266113_CatalinaonVMware1.thumb.png.59dcb3bb9b7d35174fcbd32b0bbe097e.png

1633914852_CatalinaonVMware2.thumb.png.ac00f44dac5255dd7b05a0c8757f6d51.png

 

347694735_CatalinaonVMware3.thumb.png.18c5770e93e1e4e272c970ab9b125b50.png

 

226517072_CatalinaonVMware4.thumb.png.9c3407af2b03b34204b0bfb0b838024a.png

 

243050409_CatalinaonVMware5.png.276992946290626595c19c581617b02d.png

 

 

The final boot after all the system files are laid down proceeds normally ---> see macOS Install Assistant, set region, setup new user, install VMware tools etc.  I booted into the final phase using Clover...

 

Spoiler

535118599_CatalinaonVMware6.thumb.png.b7f820b72fa0d6658e135adf95e8baad.png1854745388_CatalinaonVMware7.thumb.png.7e4dd9d28ea0c09242c715c8226d6c17.png1711787764_CatalinaonVMware8.thumb.png.f9351a697b5d8ed1489a83d8eb4bbc4d.png

 

 

 

 

EDIT1

7 hours ago, serezha said:

You do not need boot partition or clover. You need vmware 15 (or may be 14) to boot up from APFS partition.

If you have any problems with first reboot: use compatible host hardware (intel's ivy bridge and higher), use vmware workstation 15, use virtual hardware version 15, try to upgrade from high sierra (I do not tried to upgrade from Mojave, may not works), try to uninstall vmware tools before upgrade.

 

Yes, VMware 15 supports apfs but not VMware 12. 

 

Unfortunately, I can’t install ver 15 on my desktop GA-P55aUD3/i5-750 (VMware15 dropped support for Lynnfield and older CPUs) so I need Clover to boot into apfs partitions using VMware 12.

 

I did a clean install of Catalina DP1 using a full installer iso, created utilising createintallmedia script: macOS_iso_cim.tool.zip

 

Spoiler

 

Usage:  Assuming script in your ~/Downloads folder and Catalina full installer app in /Applications


cd ~/Downloads 
chmod +x ./macOS_iso_cim.tool 
sudo ./macOS_iso_cim.tool

Script will generate a macOS.iso installer on your desktop ---> attach this to your Catalina VM as a virtual CD/DVD ROM.

 

 

 

Funnily enough, there is no kernel panic and no need to change the OS type to Windows 10 X64 if you replace the pre-linked kernel of the installer/BaseSystem with a pre-linked kernel from the fully installed system...prelinkedkernel.zip

eg below, I replaced the prelinkedkernel in /macOS Install Data/Locked Files/Boot Files ---> successful phase 2 on next reboot...

 

Spoiler

1046255582_swapprelinkedkernelinmacOSInstallData.thumb.png.d43003bed79a0c5fa688519c58e5a61c.png1164569693_phase2boot.thumb.png.d9cca52edeabb6acbfa242bd9cad8042.png

 

 

 

EDIT2

5 hours ago, serezha said:

Is Catalina work good with first generation of Core i processors? Is Ivy Bridge only marketing restriction or support of old processors will be dropped in next betas?


Did you try monitor.allowLegacyCPU = "true" option for VMware 14/15? Vmware workstation 14/15 only need EPT, all core i processors have EPT support. Unrestricted guest is optional requirement.

 

No problems here.  AFAIK restriction applies only to CPU older than Sandy Bridge and is purely a marketing restriction eg MacPro5,1 with Nehalem CPU more than capable of running 10.15, esp if a metal capable graphics card is installed.

 

Obviously you have to ask Apple if there will be additional requirements in future...

 

The VMware installer automatically checks CPU of host so it won't allow installation of ver 15 on my desktop no 2 in the first place.  As I explained above, ver 12 is quite capable of running 10.15 with Clover to provide additional apfs support.

Edited by fusion71au
Extra info for @serezha

Share this post


Link to post
Share on other sites

Just updated another virtual machine to Catalina without any problems. I am use unlocked Vmware workstation 15.1 on windows 7 x64 host. I started update with 10.13.6, virtual hardware version 15, guest OS type is macOS 10.13. First I removed vmware tools. It is only precausion, but vmware tools may contain incompatible kexts. I installed beta profile, then downloaded Catalina installer from AppStore. The I started installation. After first reboot was kernel panic (apple logo without any disk and processor activity). I shutdowned virtual machine, change it type to Windows 10 x64 and started it again. Installation was continued automatically. After next reboot virtual machine can not boot, I saw boot manager from EFI. I shutdowned it, changed type to macOS 10.14 and started it again. Installation was continued and finished without any problems.

You do not need boot partition or clover. You need vmware 15 (or may be 14) to boot up from APFS partition.

If you have any problems with first reboot: use compatible host hardware (intel's ivy bridge and higher), use vmware workstation 15, use virtual hardware version 15, try to upgrade from high sierra (I do not tried to upgrade from Mojave, may not works), try to uninstall vmware tools before upgrade.

Share this post


Link to post
Share on other sites
17 hours ago, fusion71au said:

I can’t install ver 15 on my desktop GA-P55aUD3/i5-750

Is Catalina work good with first generation of Core i processors? Is Ivy Bridge only marketing restriction or support of old processors will be dropped in next betas?


Did you try monitor.allowLegacyCPU = "true" option for VMware 14/15? Vmware workstation 14/15 only need EPT, all core i processors have EPT support. Unrestricted guest is optional requirement.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By fantomas1
      First beta... macOS Catalina 10.15 beta (19A471t)  Release Notes!!!
       
      Useful information:
       
      macOSDeveloperBetaAccessUtility.dmg.zip (thanks to gengik84)
      Clover r4945 (thanks to Cyberdevs)
      Lilu_plugins (thanks to gengik84)
      Port Limit Patch (thanks to daliansky)
      older non metal nVidia and Intel cards (thanks to fusion71au))
    • By fusion71au
      Patch Catalina or Mojave macOS Installer App for Unsupported Machines
       
      Often for economic reasons, Apple prevents the Installer.app for its latest macOS from installing on older machines perfectly capable of running it eg macOS 10.14 Mojave on Unsupported Macs Thread.
       

       
      In Mojave 10.14, @ASentientBot posted a method to patch the distribution file in OSInstall.mpkg to enable the Mojave installer to install on unsupported machines (with or without graphics card metal support). 
       
      In Catalina 10.15beta, the above method no longer works since Apple is checking OSInstall.mpkg for its file signature and the mandatory requirement in Catalina to install to 2 separate apfs volumes necessitates using the original Catalina macOS Base System Installer.  Fortunately, it is still possible to substitute High Sierra’s Apple Signed OSInstall.mpkg inside the Catalina or Mojave InstallESD.dmg by making it R/W.
       
      The procedure below will allow Macs or Hacks able to install High Sierra to also install Catalina or Mojave (eg SMBIOS MacPro5,1, iMac11,3, MacBook Pro7,1 which have been unsupported in macOS 10.14.x and 10.15beta) -credit to @ASentientBot's post.
       
      Prerequisites
      1. Mac or Hack capable of and running High Sierra 10.13.x
      2. An original, untouched copy of OSInstall.mpkg from High Serra InstallESD.dmg - attached OSInstall_10.13.6.mpkg.zip save to your ~/Downloads folder
      3. macOS Installer App eg for Catalina beta or Mojave downloaded to /Applications
      4. Add NVRAM boot arg (or Clover config.plist boot arg on a hack) -no_compat_check to enable system to boot to final completed Mojave or Catalina install.
       
      Procedure
      1. Open Terminal and type the following
       
      open /Applications/Install*/Contents/SharedSupport/InstallESD.dmg (assuming the Catalina or Mojave Installer App is in /Applications)  
      2. Open Disk Utility, click File|New Image|Image from ‘InstallESD”
      3. Save as read/write image, no encryption in /Applications
      4. Unmount InstallESD in DU by clicking the "eject" icon next to it
       
       
      5. Open the R/W InstallSD.dmg in /Applications and replace Catalina’s/Mojave's OSInstall.mpkg with High Sierra’s version by typing in terminal
       
      open /Applications/InstallESD.dmg cp ~/Downloads/OSInstall_10.13.6.mpkg /Volumes/InstallESD/Packages/OSInstall.mpkg  
      6. Unmount InstallESD in DU by clicking the "eject" icon next to it
      7. Replace original Catalina/Mojave InstallESD.dmg with our patched one, making a backup of the original.  In terminal, type
       
      sudo mv /Applications/Install*/Contents/SharedSupport/InstallESD.dmg /Applications/InstallESD_orig.dmg sudo mv /Applications/InstallESD.dmg /Applications/Install*/Contents/SharedSupport/  
      8.  Test the newly patched installer!…

×