Jump to content
Sign in to follow this  
Followers 0
br0adband

Catatalina Beta 10.15 - Anyone got it booting yet?

12 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 crazybirdy
      Patched OSInstaller.framework to allow macOS 10.15 installation on MBR HFS+ partition.
       
      Please read Readme-10.15.pdf first.
       
      How to finish the Catalina installation.
      1. Use EasyMBR-Installer1015 to make USB Catalina Installer.
      2. Boot to USB Catalina Installer, open Utilities -> Disk Utility, format as MBR HFS+. 
          Install Catalina to blank MBR HFS+ "Target" partition.
      3. Boot to USB Catalina Installer, open Utilities -> Terminal, run the script command:
          copytempdata
      4. Boot to "Target" MBR HFS+ partition on single user mode (-s), run the script command:
          hfsupdatecache
      5. Reboot to "Target" MBR HFS+ partition, setup user name and login, finish the installation.
       
      Also, you need to setup Clover as BooterConfig=0x28, CsrActiveConfig=0x67
       
      ----------------------------------------------------------------------------------------------
      List of known issues:
      1. iCloud Drive need APFS to work.
      2. Some app-pkg-installers can't install to HFS+, but install to APFS fine.
      ----------------------------------------------------------------------------------------------
       
      What is this patched OSInstaller doing?
      1. Pass the MBR check, allow macOS 10.15 installation on MBR partition.
      2. Pass the Firmware check, bypass the error of "An error occurred while verifying firmware".
      3. Pass auto-convert to APFS , "ConvertToAPFS=false" is no longer worked with 10.15.
      4. This MBR-Manual-Method will never convert to APFS, and will always install as HFS+ partition.
      5. This MBR-Manual-Method works with both MBR HFS+ and GPT HFS+ partition (GPT+recovery).
      No longer need to set new SMbiosversion, FirmwareFeatures, and FirmwareFeaturesMask with this MBR-patch.
       
      What's the difference between createinstallmedia method, MBR-Manual-Method, and MBR-Automatic-Method?
      As the following....
      1. createinstallmedia method,
          needs stage 1, stage 2 installation process, which is worked with GUID partition only, always convert to APFS format.
      2. MBR-Manual-Method (same as 10.12),
          install via stage 2 manually, which is worked with both MBR HFS+ and GUID HFS+, will never convert the partition format.
          We can manually format as MBR HFS+ or GPT HFS+ on installation screen like as 10.12.
          We can manually select MBR HFS+ partition to install 10.13, 10.14, 10.15 on installation screen now.
          Needn't to update the MBR-Manual-Method files, it will still work on 10.13, 10.14, 10.15 future versions, I think so.
          It can be installed as Fresh installation on formated blank partition only, but can't be installed as update from previous version.
      3. MBR-Automatic-Method (new for 10.13+),
          End of MBR and HFS+, there is no more MBR HFS+ patch available for 10.15 native OSInstaller.

      How to make 10.15 installer for MBR (MBR-Manual-Method)?
      Just use EasyMBR-Installer1015 to make installer, it works with both MBR and GPT.
      Read HowTo inside the dmg first, same as 10.12.
      Read HowTo Q/A Q4. How to patch to work with CPU SSE4.1 only for Mojave, Catalina?
      Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
       
      And, need a SMBIOS supported with /System/Library/CoreServices/PlatformSupport.plist.
       

       
      Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      A6. Some people download installer app from App Store, and get only 18 MB size, not the complete installer app (5.68 GB). You should boot to 10.12, or 10.13 to download it again from App Store, or use script Q6-DownloadFullApp/installScript_fullapp to download the full installer app via swscan.apple.com.
       

       
    • By PippoX0
      Working in Progress
       
      I want  that my Catalina  runs smooth
       
      I run Catalina beta on MBr HFS+ (only one partition)
       
      So what we can do ?
       
      0. I have gained my Intel HD3000 QE/CI working
         - i have used Intel HD3000 High Sierra Kexts
          Done
       
      1. Reduce size
        -  I have used monolingual and I have deleted all unwanted languages
        - i have deleted unwanted Speech voices
        - i have delete unwanted Fonts ( Japanese , Chinese, Emoji ...) 
        - i have delete unwanted Templates ( again speech voices)
        My Cat OS have been shrinked  from 16 Gb to 9,96 Gb
        Done
       
      2. Disable all unwanted Deamons and Agents
        -  I'm looking for disable all Debug deamons or Agents running which are slowing my Os
         Still seeking ....
       
      What's else ?
       
       
       
       
    • By fusion71au
      This is a brief guide on how to create a vanilla El Capitan (also same process for Sierra) OS X Installer USB with an updated prelinked kernel containing FakeSMC.

      It is tailored for those users who want to understand the “nuts and bolts” of how to create an installer and also to help brush up on their terminal skills (rather than have one made for them with the numerous automated “tools” available or even Apple’s createinstallmedia) :
       
       
      Specifically, it is also a “Proof of Concept” which shows that installation is possible without even having to rely on boot loader kext injection.

      Prerequisites
      Existing Yosemite installation (or Mavericks - see post#4 for steps 7,8) “Install OS X El Capitan.app" downloaded to the Applications folder Pacifist FakeSMC.kext - Slice or Kozlek branch Bootloader - Clover or Chameleon 8GB or larger USB drive (16GB recommended), formatted HFS+ (MBR or GUID) named “Installer”  
      Procedure
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Open OS X terminal and type the following lines, followed by <Enter> after each line.
          The image restore and file copying may take a while to complete, and at the end of the process, the Installer volume is renamed to “OS X Base System"....
       
      sudo -s hdiutil attach /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/SharedSupport/InstallESD.dmg asr restore -source /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg  -target /Volumes/Installer -erase -format HFS+ -noprompt -noverify rm /Volumes/OS\ X\ Base\ System/System/Installation/Packages cp -av /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System/System/Installation cp -av /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg /Volumes/OS\ X\ Install\ ESD/BaseSystem.chunklist /Volumes/OS\ X\ Base\ System diskutil unmount /Volumes/OS\ X\ Install\ ESD exit 3.  Right click on the “OS X Base System” Volume and click “Get Info”
       

      4.  Click on the lock icon and untick “Ignore ownership on this volume”
       

      5.  Extract/Copy the El Capitan Kernels folder into /System/Library/ of the USB with Pacifist.  NB It is found in the "Essentials.pkg" in /System/Installation/Packages
       

      6.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel —> OG.prelinkedkernel
       

      7.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of the installer USB using Finder.
       

      8.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel…..
       
      sudo -s chmod -R 755 /Volumes/OS\ X\ Base\ System/Library/Extensions chown -R 0:0 /Volumes/OS\ X\ Base\ System/Library/Extensions touch /Volumes/OS\ X\ Base\ System/System/Library/Extensions kextcache -u /Volumes/OS\ X\ Base\ System exit Any errors should be noted but the output below is normal e.g.


      9. Install your Bootloader targeting the OS X Base System volume
       
       
       
       
      10.  Boot your system with the USB without injected kexts into the OS X Installer GUI....
       
       
       
       
       
      Post Install
      The original prelinked kernel in a fresh install of El Capitan will also lack FakeSMC ie it will only be linked to Apple signed kexts.  In order to boot into El Capitan the first time around without boot loader kext injection, the PLK needs to be rebuilt for the El Capitan volume like we did for the installer:
       
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel for the El Capitan volume —> OG.prelinkedkernel
      3.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of El Capitan using Finder
      4.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel.  In this example, the El Capitan volume is named "El_Capitan" - change if you have named it something else...
      sudo -s chmod -R 755 /Volumes/El_Capitan/Library/Extensions chown -R 0:0 /Volumes/El_Capitan/Library/Extensions touch /Volumes/El_Capitan/System/Library/Extensions kextcache -u /Volumes/El_Capitan exit 5. Install your Bootloader targeting the El Capitan volume.  This step is only necessary if you are installing El Capitan on a new drive without existing boot loader (not required if installing on a disk with existing boot loader beside Yosemite).
      6. Reboot your system without injected kexts into El Capitan!
       
       
      Other links
      The All-In-One Guide to Vanilla OS X for beginners
       
      Updates for Sierra and High Sierra   Custom Prelinkedkernel Generator Tool I have made a custom prelinkedkernel generator "PLK.tool" for Sierra + El Capitan.  Instructions:   1.  Download and extract the attached BaseSystem_PLK.tool.zip into your ~/Downloads folder.   2.  Copy any extra kexts necessary for booting your hack to ~/Downloads/BaseSystem/ExtraKexts (e.g. FakeSMC, VoodooPS2Controller), making sure SIP is disabled. 3.  Copy BaseSystem.dmg to ~/Downloads/BaseSystem  4.  Open terminal and run the following commands... cd ~/Downloads/BaseSystem chmod +x PLK.tool ./PLK.tool ---> supply your admin password ---> will place your new custom prelinkedkernel on the desktop.       macOS High Sierra bypass Firmware and MBR checks in post#13.
      BaseSystem_PLK.tool_ElCap.zip
      BaseSystem_PLK.tool_Sierra.zip
      BaseSystem_PLK.tool_Mojave.zip (need to run in Mojave to avoid dependency errors)
      BaseSystem_PLK.tool_Catalina.zip
       
    • By ThatsMatt
      Salve, sono nuovo nel forum e mi serviva una mano nell'installazione dell' ultima versione di MacOs sul mio notebook HP Pavilion 15-ak112nl.
      Specifiche Tecniche: 
      CPU: Intel Core i7-6700HQ (2.60 / 3.50 GHz, 4 core, 6 MB CACHE L3). 
      Scheda Grafica: Intel HD Graphics 530 + NVIDIA GeForce GTX 950M 4 GB DDR3.
      Hard Disk: 1 TB SATA 5400 rpm.
      Ram: 8 GB DDR3L-1600.
      Audio: altoparlanti stereo Bang & Olufsen PLAY. 
      Rete: LAN 10/100, WLAN 802.11b/g/n, bluetooth 4.0 (Miracast).
      Grazie in Anticipo a chi mi risponderà
    • 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)
      MBR installation on macOS Catalina (thanks to crazybirdy) - workaround!!!
×