M4 Pro Max Linux VM

Parallels Version: 20.1.1 (55740)
Operating System Sequoia: 15.1
Hardware: Apple M4 Max
VM: Debian 12 (Bookworm)
There appears to be an issue with mounting external volumes, specifically the Linuz packages that are required to mount them.
The issue is reported in the Debian VM as:

*** stack smashing detected ***: terminated
Aborted

I can reproduce it on new VMs was follows:
sudo apt -y install nfs-common (this process hangs at around 52%)
resetting dpkg with:
sudo dpkg --configure -a results in the smishing error.

To test further, I attempted to build a VM from a Debian ISO, which failed early on with the error 'An Installation step failed. You can try to run the item again from the menu or skip it and choose something else. The failing step is: Detect and mount installation media."

This error is the same when using ieither netinst or full ISO media.

 

When I create a new VM with "Free Systems" -> "Download Debian GNU/Linux" and try to update with apt update; apt upgrade I also get an "stack smashing detected" when the initial ramdisk is built.

Installing a new VM from a vanilla Debian image does not work for me, neither.

Please forward this error also for further investigation as it seems to be related.

 

I'm hitting a similar problem with apt upgrade in Debian on an M4 Mac mini. I've also seen this with large compilations (like the Linux kernel), though it's intermittent. I wonder whether it depends on which CPU the VM thread is running on, the P or E one. If I kick off the compilation again, it succeeds, presumably the VM thread migrated to the performance CPU (or maybe there's just a bug in the migration code). I need to figure out how to limit parallels to run on specific CPUs only (there's a "taskpolicy" tool, maybe it does the trick).

 

FWIW, I managed to run dpkg successfully (mkinitramfs was failing previously for me) by allocating the VM a single CPU. Chromium still fails though with the same stack smashing error.

 

I'm getting the same problem with Parallels Pro 20.1.2 (55742). Running on a MacBook with M4 Pro with a Debian 12 (Bookworm) VM. I eventually get a segmentation fault .....

 

I know this isn't going to help any but this is the last I heard from support ....

Thank you for providing the technical reports.

Indeed, it appears that this issue requires deeper investigation and has been escalated to the Development Team.

Once there is an update, a fix, a request for additional information or a workaround, we will immediately inform you.

At this point, we need to mark this ticket as 'Resolved'. Don't worry, it doesn't mean the issue itself was resolved, and we forgot about you, no. This way, we avoid ticket duplication, which may increase the time required for a fix. Yet, we will do our best to find a solution as soon as possible.

To check on the issue status, you can request an update on the issue, by replying to this e-mail, and the ticket automatically reopens.

Thank you very much for your patience and understanding. We will get back to you as soon as we have an update from the Development Team.

 

See this thread - https://forum.parallels.com/threads...ers-with-apple-silicon-m4-chips.365676/page-7