Thanks for confirming. Hopefully fixed in Beta 2 next week.Same Issue here with an ix500.
MBP M1 Pro
Thanks for confirming. Hopefully fixed in Beta 2 next week.Same Issue here with an ix500.
MBP M1 Pro
It doesn't work for somesweet so virtualization doesn't work![]()
Can you be less cryptic ?? What should I do to make parallels working ?It doesn't work for someAnd for those that have the issue there a specific tool to be run, available on the developers website.
View attachment 2486364
Do you have a link to this page?It doesn't work for someAnd for those that have the issue there a specific tool to be run, available on the developers website.
View attachment 2486364
Do you have a link to this page?
Yes i did it... starting any virtualization environment causes kernel panic and hard crash.Well I’m a developer, I’m using a silicon MacBook Pro. And I’m on the beta. Both docker and parallels work just fine for me. And as I’ve linked for when it doesn’t work there is a package to download.
Are you a signed up developer and have tried to download the package and fix your issues?
so no virtualisation, not working apple inteligence in many cases, and sleep. that must be the worse beta i have ever seen in macos.So it seems like one of the earlier Sequioa beta bugs is back. MBA 15 M3- when it sleeps and display locks automatically, I'm unable to unlock/log back in. I have to do a hard restart every time.
Not good...🙁
LOL That is why it’s a Betaso no virtualisation, not working apple inteligence in many cases, and sleep. that must be the worse beta i have ever seen in macos.
This didnt help me at all. This seems to be for running macOS virtualized, not using a Mac TO virtualize. This problem seems isolated to M4 series, I have M4 Max.It doesn't work for someAnd for those that have the issue there a specific tool to be run, available on the developers website.
View attachment 2486364
what Mac do you have?so no virtualisation, not working apple inteligence in many cases, and sleep. that must be the worse beta i have ever seen in macos.
Exactly! I'm not patient enough, especially when apple is screwing with people like thatThis didnt help me at all. This seems to be for running macOS virtualized, not using a Mac TO virtualize. This problem seems isolated to M4 series, I have M4 Max.
no it's a final solutionis that even a workaround?![]()
It's even in the Known Issues section of the release notes now, I was really hoping for a reissued beta with a fix for thisExactly! I'm not patient enough, especially when apple is screwing with people like thatIt seems issue was there in developer beta and they just decided not to hold of with public beta and release this major bug with it.
on top of everything mirroring also doesn't work..
no it's a final solution
This was added afterwards people found it, it did not come orginaly.It's even in the Known Issues section of the release notes now, I was really hoping for a reissued beta with a fix for this
Virtual Machines
Known Issues
- Upon update to macOS 15.4 beta 1, M4 Macs will be unable to launch virtual machines and attempts will result in a system restart. (145309647) (FB16542958)
Workaround: Do not launch virtual machines. If virtual machine applications launch upon login, boot to Safe Mode and disable in system settings.
Don't think so, probably it will be weeks before i can run docker on my m4 again ... I refuse to downgrade knowing how many issues it may cause.Here is hoping we see a beta 2 today......
Correct, hence the "now" in my comment. I agree, I scanned before installing and it was not there.This was added afterwards people found it, it did not come orginaly.
Indeed. I scanned as well, and it was already identified here on MacRumors that it was the M4 only, hence I rolled the dice and applied it to my M1 MAX 👍Correct, hence the "now" in my comment. I agree, I scanned before installing and it was not there.