Jump to content

[pre-release] macOS Big Sur in VMWare

gengik84
 Share
1,188 posts in this topic

Recommended Posts

aben
aben
Posted
Posted
21 minutes ago, Mad Audi Scientist said:

Anyone who is getting the OS to run is doing image installs Or installing on external drive on a real Mac just to try out the OS. I guess it’s cool an all, but what’s the fun in that if you can’t boot in to a clean install. Anyhow will keep waiting for the boot loader masters to do their magic till one can do a clean install via external media directly to a hack. “Sergey pamagi nam pajalusta” :help:

Honestly it’s way more fun having to work your way through beta season, learning new stuff along, finding hints clues, workarounds, giving us the challenge rather than the usual tapping of the update button, doing nothing but watch the loading bar move. And yes these are clean clean installs from the macOS Beta app, it’s just the longer way out using tools like Intel VT-x tech which also happens to be super fun and cool too. 

  • Like 2
Link to comment
Share on other sites
ameenjuz
ameenjuz
Posted
Posted
7 minutes ago, aben said:

Honestly it’s way more fun having to work your way through beta season, learning new stuff along, finding hints clues, workarounds, giving us the challenge rather than the usual tapping of the update button, doing nothing but watch the loading bar move. And yes these are clean clean installs from the macOS Beta app, it’s just the longer way out using tools like Intel VT-x tech which also happens to be super fun and cool too. 

how to do this clean installs from the macOS Beta app

provide us detail

Link to comment
Share on other sites
Andres ZeroCross
Andres ZeroCross
Posted
Posted
29 minutes ago, black.dragon74 said:

You have to run these commands from the macOS recovery mode. Not the normal booted mode.


AFAIK, we can't enter recovery of Big Sur yet with current Bootloader. Just get black screen after press enter in macOS Recovery 10.16 with latest commit OpenCore

Link to comment
Share on other sites
Pavo
Pavo
Posted
Posted

Figured out how to resize the drive using the img method 

To resize the physical disk of BigSur when using the img dd method
*Identify the physical disk you dd the img to X is example
diskutil list
*repair the physical disk partition
sudo diskutil repairDisk diskX
*Resize the physical disk container volume
sudo diskutil apfs resizeContainer diskXs2 0

This can be done inside normal BigSur.

  • Like 3
  • Thanks 1
Link to comment
Share on other sites
Balamut
Balamut
Posted
Posted
2 minutes ago, fabiosun said:

@Balamut

_ml_init_max_cpus:

is not present in this kernel....

maybe now is it possible to have more than 64 cores?

Or Apple changed its name for cores limit...

 

If they do then 64 Core Threadripper or Dual Xeon Platinums will bury any MacPro.

  • Like 1
Link to comment
Share on other sites
Fordski
Fordski
Posted
Posted
59 minutes ago, Pavo said:

Figured out how to resize the drive using the img method 


To resize the physical disk of BigSur when using the img dd method
*Identify the physical disk you dd the img to X is example
diskutil list
*repair the physical disk partition
sudo diskutil repairDisk diskX
*Resize the physical disk container volume
sudo diskutil apfs resizeContainer diskXs2 0

This can be done inside normal BigSur.

Thanks for discovering and sharing this. I spent the good part of an afternoon trying to figure this out so I can migrate my Catalina files over.

Link to comment
Share on other sites
ludufre
ludufre
Posted
Posted

To whom it may concern.

 

I updated my guide to install Big Sur by creating your own installation using a virtual machine as installer. (With pictures)

 

So you don't have to use ready-made DMG/DD.

 

If you already have your Catalina working perfectly with OpenCore, it will theoretically work...

 

 

 

  • Like 7
  • Thanks 3
Link to comment
Share on other sites
Dragster27
Dragster27
Posted
Posted
On 6/27/2020 at 12:07 AM, Rocky12 said:

Here is the proof all the credit goes to jackluke over macrumors

 

Thanks for the info. I've latest clover, kexts , etc and a working catalina setup... in a haswell/hd4600 laptop

 

I've tried to boot Big Sur from USB installer using the modified com.apple.Boot.plist as shown above to no avail... 

 

has anyone been able to get the USB installer to boot with this method? 

 

Cheers,

D.

  • Like 1
Link to comment
Share on other sites
Max.1974
Max.1974
Posted
Posted (edited)
3 hours ago, chris1111 said:

amfi_get_out_of_my_way=1

Is not get out of my way :hysterical::hysterical:

 

Works for you @chris1111 ?

Im try this but im not sure, need change in partition install (Russian restored) too?

Thanks for all effort of the guys on this Community, you all the best!!!

 

 

Edited by Max.1974
Link to comment
Share on other sites
chris1111
chris1111
Posted
Posted
1 minute ago, Max.1974 said:

 

Works for you @chris1111 ?

Im try this but im not sure, need change in partition install (Russian restored)?

Thanks for all effort of the guys on this Community, you all the best!!!

Apple is s#"?:;^%s but you are gentleman ....

Im thinking if Chinese people will creat a ARM fake processor or something for us....:D ...

No not work 

  • Thanks 1
Link to comment
Share on other sites
ITzTravelInTime
ITzTravelInTime
Posted
Posted
2 hours ago, Dragster27 said:

 

Thanks for the info. I've latest clover, kexts , etc and a working catalina setup... in a haswell/hd4600 laptop

 

I've tried to boot Big Sur from USB installer using the modified com.apple.Boot.plist as shown above to no avail... 

 

has anyone been able to get the USB installer to boot with this method? 

 

Cheers,

D.

 

I have to try it, but I think the problem if with clover itself, it needs quite a lot of work to support this os

Link to comment
Share on other sites
Zhen-zen
Zhen-zen
Posted
Posted (edited)

Managed to find a way to install without VM / real mac (and also without USB stick since I'm lazy). Hope if it can relief the tension bought by preinstalled dmg.

 

Update: thanks to @tunglamvghy1210 @Anonym323, I added a missing point. Please check step 4 for updated instruction and step 5 on a fix for broken Safari.app.

1. Have a (fresh installed) Catalina container

While it also works in the same container with currently installed system, there might be issues when removing the volume. My friends with real Mac says you can only use Big Sur Recovery to remove the volume.

For a cleaner(?) install, you can stop after the boot entry changed from "macOS installer" to volume name and leave the initial configuration to Big Sur first boot.
2. Make sure you are ready to boot even without kexts

Necessary but it may depends on your configuration. For example:

Switching to a 1080p monitor instead of 4K ones. Btw enable-hdmi20 is unusable since user space patching is disabled. Also there's no binary at /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay

Get a USB keyboard and a mouse just in case.

Check your config.plist for things like -disablegfxfirmware and https://github.com/acidanthera/OpenCorePkg/commit/dea60c2a1e2ff83e3b871425d6f3b4adbcc4ef9b

Set a MaxKernel such as 19.6.0 for SMCBattery.kext and get https://github.com/RehabMan/OS-X-ACPI-Keyboard with MinKernel 20.0.0

Temporary set MaxKernel 19.6.0 for VoodooI2CHID.kext (Don't know why it may cause kp at stage 3 when creating kernel cache, but works well afterwards)

I'm not sure about the USB port limit patch, because I use a pure SSDT approach that disable unnecessary ports using _UPC.

3. Install Big Sur from Installer

I ran it from another Catalina and the minimum disk space required is ~51G (Big Sur) + ~15G (installed Catalina)

I left 66G for the new container, but the space's still not enough. Then I found VM volume takes 2G and then mount it to delete the 2G sleepimage inside.
4. Stage 1 (first reboot) with file extracted

The installer will prompt things like 29 mins remaining and stop at 17 or so. Sometimes the installer will abort just at the beginning, please reboot into the installer again.

After reboot to another Catalina system, you may find that the log in a new volume called Update. Please ensure that you have that volume and/or "macOS Install Data" (hidden folder) is gone in the data volume.

By the way, ramrod (or patchd) also left a log there after stage 2 if you use VM or real Mac.

5. Mount the preboot volume

Open folder named by Big Sur UUID (check timestamp) 

sudo cp ./com.apple.installer/boot.efi ./System/Library/CoreServices/
sudo cp -r ./System/Library/PrelinkedKernels.Staged ./System/Library/PrelinkedKernels

(com.apple.installer is hidden)

Now you can also move /System/Library/Templates/Data/Applications/Safari.app from the system volume to /Application/ at the data volume to manually update Safari. It's not possible to do that in Big Sur.
6. Reboot and choose the entry with new volume name. (Almost finished!)
7. Go to disk utility and get a first aid. (?)

8. Personal tips

The macOS installer entry is still there, however you can override it like OC's AllowSetDefault. Maybe deleting the com.apple.installer folder and edit nvram can remove it.

Since the recovery entry is not usable(or just me?), I repurposed this entry by editing com.apple.installer/com.apple.Boot.plist

Copy the BaseSystem.dmg with chunklist from Recovery to some place in the data volume.

Change the path in boot arg from ramdisk to that dmg.

It seems that those volumes (preboot, VM) can not be mounted in Big Sur, you may need to edit them in Catalina or earlier. However Recovery volume can still be mounted.


Hypothesis:
In stage 2 you will boot into a ramdisk that do stuffs like converting the apfs volume into new format and seal it. But real hardware will failed for issues with SMC watchdog (ramrod quit after disable_watchdog failed).
And if you try to boot from that partition directly without Catalina installed first, you will get apfs errors since firmlink to data partition are not established. So when upgrading from Catalina, these errors can be avoided. But there may be some risks using old apfs format. For example, new system partition has a "Sealed: yes" attribute and snapshot feature. First aid may do some work but still unclear.

Edited by Zhen-zen
  • Like 3
  • Thanks 1
Link to comment
Share on other sites
BigSir
BigSir
Posted
Posted

Has anyone managed to boot into a USB installer in OpenCore yet? All i get is a looping set of text and it wont go further. Something about com.apple.security cannot be found. I have a hunch its SIP related but I have no idea how to get into the recovery partition to turn it off. I was reading @Zhen-zen's guide but I think thats only for people who can begin the install within Catalina if i'm not mistaken. 

Link to comment
Share on other sites
zisqo
zisqo
Posted
Posted

Spoiler

1.thumb.jpg.9a3c582f3cf58a97979ded0db6c87050.jpg

well successed with X299 System.. it's not on VMware screen. also changing all device properties on ssdts will working fine.
i was basic-refer that KGP's ssdt but something was different.

 

btw it's working even if somebody said "it's not working yet"

Spoiler

1961239494_ScreenShot2020-06-27at1_27_51PM.thumb.png.dbe4c4de36ef17286b0c782a06ed97ef.png


 

ASUS X299 TUF Mark 1 / i7-7800X

 

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...