Freezing issue when running macOS VM on Parallels

Wiktorl said:
Hi, I have similar problem. MacBook Pro Apple M1 Pro, Mac OS X Sonoma 14.3.1, guest Windows 11. When I run Parallels Desktop Mac freezes randomly (every few minutes) for few seconds- mouse cursor change into waiting. When I write on keyboard and have some key pressed when it happens the key is repeated several dozens times.
Click to expand...
I have exact same issue on Sonoma 14.4.1
 
ParallelsU842 said:
I have exact same issue on Sonoma 14.4.1
Click to expand...
Hello!
In order to proceed with further investigation, kindly provide us with the below information:
1. Reproduce the issue.
2. Collect a technical report (right-click Parallels icon in Dock > Help > Send technical data > check "Attach screenshots..." > press Send Report) and send the report's 9-digit ID in a reply.
Thank you!
 
I also have this issue, Ticket #4866575, Technical Report #466526291. Using a Macbook Air M3 with Parallels 19.4.1. It occurs regardless of guest/host combination on both macOS Sonoma 14.6 and macOS Sequoia 15 Public Beta (24A5298h).

Increasing the resources of the virtual machine also has no effect. It continues to be associated with whenever I use the scrolling on the trackpad of my Macbook.
 
A quick update, the issue is still occurring on the newly released macOS 15 Public Beta (24A5309e). Support suggested I remove DisplayLink Manager, to no effect.
 
After dumping sysdiagnose and report from both the guest and host, my case is now with Parallels Engineering. Very frustrating that there's no resolution for this issue yet.
 
This issue is still continuing and makes my day-to-day work in the guest extraordinarily difficult. I've emailed for an update to ask on Engineering triage times--because if the turnaround is slow I will have to find an alternative solution.
 
As I mentioned in my last post, I asked support about even the vaguest ETA on when engineering would be able to look at the issue and got the following response:

> "Hello,
> Thank you for your response.
> Unfortunately, the Development Team doesn't provide us with any ETA required for the investigation.
> While we understand your concerns, we currently have nothing to share with you on this matter - we hope it won't take a while.
> Rest assured, as soon as we get an update, fix, or any news regarding the case, we will let you know.
> We regret the inconvenience caused."

This is pretty frustrating, surely there's no reason that engineering can't at least share even the vaguest timeline for looking at the issue? Are we talking weeks? months? years? I'm not asking for an SLA here--just something so I can sort out my own arrangements to get my work done.
 
Another update, the issue is still occurring on the newly released macOS 15 Public Beta (24A5320a).

I am rapidly losing faith in Parallels given in fact there are no developers who use the product they work on or even browse the forums. Every day of working in the guest is painful for me.

How can any product owner stand by while there is absolutely no communication and transparency on the triage process of customer issues to the development team? For shame.
 
Yet another update, and the issue is still occurring on the newly released macOS 15 Public Beta (24A5327a). I am alone in the Parallels trenches, here, there is only dead product littering the ground--and the faint smell of money.
 
This has finally gotten so bad I signed up for the forum! Is there anything from Parallels about a way forward? Is is time to find another VM solution? I'm using VS code in a MacOS VM and almost every time I try to use the trackpad on the MBP or separately it freezes for a few seconds and them comes back to life; rinse/repeat.
 
I think the issue has lessened somewhat in the last beta (24A5327a), and the newly released macOS 15 Public Beta (24A5331b). The most relevant change I could from from the Apple change log was for Radar 84639494: https://developer.apple.com/documen...Silicon based,the legacy behavior. (84639494)

> On Apple Silicon based devices with M3 or later, and A16 Bionic or later, the values returned by reading the CNTFRQ_EL0 and CNTVCT_EL0 registers have been updated to 1 GHz, instead of the prior value of 24 MHz. It is still recommended for apps to use libsystem APIs like mach_absolute_time() for timekeeping. Your app will not be impacted by this change if it uses Apple's timekeeping APIs. For compatibility purposes, this change will only be visible when using the SDK associated with this release or later. On macOS, applications running inside a Virtualization.framework VM will continue to receive the legacy behavior. (84639494)

While the occurrence of the issue has lessened, it still happens from time to time. Hoping that this will soon be entirely resolved.
 
This is just a feeling -- but I think this may have something to do with graphics related functionality. It routinely appears in applications that use a hardware accelerated browser context, such as Chrome and VS Code.
 
SravanV said:
Try using macOS 15 RC, and see if the issue repeats.
macOS 15 RC got released on September 9, 2024, which is latest version.
Click to expand...

I just got tired of posting every time a new version was released. But yes, I did try that. It did not resolve the issue.

I have resolved the issue by obtaining Parallels 20 Build 55653 by guessing the download URL, and this bug is fixed in that new version. Ridiculous that the fix is not back-ported, but you gotta make money somehow I suppose.
 
I would also like to point out--it's likely that simply adding me to the Technical Preview/Beta programme for Parallels 20 would have probably resolved my issue weeks ago. But fat chance, when the developers never interact with the forum, or empower their support team.
 
My instance has also started freezing, the vm just becomes unusable doesn't respond only way to get it back is to hard shutdown and reboot, it then works for 30 secs ad hangs again, I am on version Version 20.0.1 (55659) on Mac pro m3 pro with 18gb ram os Sonoma 14.6.1 (23G93)
 
I guess I'm going to post another "me too" post. I have a MacBook Pro, M1 Max, 64GB RAM. Running Parallels Version 20.0.1 (55659). Host and VM are both Sequoia 15.0. The MacOS VM is useless. I can get one scroll with the trackpad if I go slow, but the next one will freezes for several seconds.
 
This is just another 'me too' post. Using MacOS 15.1.1 on the host machine and on the VM. Freezes for anything between 2 and 10 seconds. Does seem to be triggered more often than not when scrolling. Especially bad in VSCode and its forks.

Honestly if this isn't fixed in a few weeks now I'm just going to have to cancel my subscription and look for an alternative VM solution.
 
You must log in or register to reply here.
Back
Top