Opened 14 months ago
Last modified 3 months ago
#21542 new defect
macOS 13 Ventura installation doesn't complete
Reported by: | Rainer Orth | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox-7.0.6 |
Keywords: | Cc: | ||
Guest type: | OSX Server | Host type: | Mac OS X |
Description
So far, I've been completely unable to complete the installlation of macOS 13 Ventura on macOS hosts.
I've now asked two colleagues to repeat the process on their systems:
- MacBookPro14,3 running macOS 12.6.3
- MacBookPro16,1 running macOS 13.2.1
Both guests (configured as single-cpu Mac OS X (64-bit) with USB 3.0) sucessfully start the installation off of a macOS 13.2.1 ISO image and runs successfully for a long time. Only a the very end, at the last (?) reboot, /usr/lib/libSystem.B.dylib isn't found.
The same procedure works successfully up to and including macOS 12 Monterey, but somehow breaks down on macOS 13.
I really wonder if macOS 13 works as guest in VirtualBox at all: while there a couple of reports, most seem to be on non-Apple hosts or, even worse, feel like the authors have just run search-and-replace on previous descriptions without actually checking if the procedure still works.
To be able to investigate what's going on, I've run a screen capture during the installation. I'm attaching both VBox.log and a screenshot of the failure situation (launchd not starting for lack of libSystem.B.dylib).
Attachments (2)
Change History (4)
by , 14 months ago
by , 14 months ago
Attachment: | vlcsnap-2023-03-09-14h00m31s790.png added |
---|
Screenshot of launchd start failure
comment:1 by , 4 months ago
This issue also/still occurs when installing macOS 14.2.1 (Sonoma) guest on a 2020 MacBook Pro host running macOS 14.2.1 and VirtualBox 7.0.12. [I assume the issue is the same because the boot messages match (e.g. "Library not loaded: /usr/lib/libSystem.B.dylib")]
comment:2 by , 3 months ago
I've debugged this a bit and the problem is the failure of Virtualbox to pass through certain Intel CPU features to the guest. As a result, the guest CPU is not considered to be Haswell architecture or newer. See #15471 for the missing features.
VBox.log of the installation attempt