Broken Private Relay and Black Screen Issues with 26.6.2 and 27.0 Virtual Machines

There have been 2 serious regressions in the hypervisor framework since developer beta 6 of macOS 27 that have continued into the final release, and the first beta of 27.2

The first is that since developer beta 6 of macOS 27, virtual machines that have an Apple ID with iCloud+ signed in fail to route traffic in Safari through iCloud Private Relay despite it being on. Parallels, UTM, VirtualBuddy have all been tested and the issue applies to all of them, exposing the host machine's IP address. I have reported the issue since I discovered it and there hasn't been any communication that Apple even knows its an issue to my open report in Feedback Assistant.

The second issue is a newer one, and it affects macOS 26.6.2 and earlier virtual machines. Attempting to install 26.7 through the built-in software update causes the virtual machine to black screen upon reboot during the installation. Forcing the machine off and back on causes the virtual machine to revert back to macOS 26.6.2. There has been no available IPSW file to test if a clean install of 26.7 in a virtual machine is a viable workaround, or to see if there is a bug in the updating mechanism or bug in the 26.7 release itself in virtual machines.

The Parallels Desktop forum is beginning to get reports from users of that software of the same black screen issue trying to update their own 26.6.2 VMs to 26.7.

These issues have also not been corrected in either 27.2 Beta 1 nor 26.7.1

Has anyone found a workaround to either of these 2 issues, or submitted similar reports and got any kind of response from Apple?

The feedback reports about these issues are FB24828992 and FB24791716

iCloud Private Relay continues not to function in today's release of macOS 27.2 Beta 2 within virtual machines.

The black screen issue continues to affect macOS Tahoe virtual machines, as today's 26.7.1 RC2 continues to have the black screen upon update reboot.

Broken Private Relay and Black Screen Issues with 26.6.2 and 27.0 Virtual Machines
 
 
Q