virtualization yet not supported on M1
Its now annoying months still none of the virtualisation technology are support on M1.
Tried,
- Oracle VirtualBox
- Vmware fusion
- Parallels
- Even Docker not working ..
Any solution !!
MacBook Pro 13″, macOS 11.0
You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
Its now annoying months still none of the virtualisation technology are support on M1.
Tried,
Any solution !!
MacBook Pro 13″, macOS 11.0
shirishshukla wrote:
• Its now annoying months still none of the virtualisation technology are support on M1.
Tried,
Oracle VirtualBox
• Vmware fusion
• Parallels
• Even Docker not working ..
Any solution !!
Not yet.
shirishshukla wrote:
• Its now annoying months still none of the virtualisation technology are support on M1.
Tried,
Oracle VirtualBox
• Vmware fusion
• Parallels
• Even Docker not working ..
Any solution !!
Whats your point here...(?)
There may well be a beta available if you contact the developer:
New Parallels Desktop
We switched Parallels Desktop to universal binary and optimized its virtualization code; and the version that we are eager to try on these new MacBook Air, Mac mini and MacBook Pro 13" new M1 SoC
Parallels Desktop for Apple Silicon Mac
https://www.parallels.com/blogs/parallels-desktop-apple-silicon-mac/
by Nick Dobrovolskiy
shirishshukla wrote:
yep.. we should drop mail to almost all vendors and opensource etc.. to make their product compatible for M1.. apple responsibilities is over after sell.
Apple can not and will not modify third party apps. Apple does not have
access to third party app developers' proprietary code. It is 100% the
responsibility of third party app developers to make their apps
compatible with new operating systems. Is it GM and Ford's
responsibility to make sure their cars work with third party aftermarket
products?
microsoft or apple their own apps are not sufficient to do daily work, they have to ensure if they are making major changes all 3rd party s/w vendors to be informed in advanced (so they have enough time)
and am sure GM or Ford ll never launch cars which run "avgas" unless there's enough stations.
shirishshukla wrote:
microsoft or apple their own apps are not sufficient to do daily work, they have to ensure if they are making major changes all 3rd party s/w vendors to be informed in advanced (so they have enough time)
and am sure GM or Ford ll never launch cars which run "avgas" unless there's enough stations.
FWIW, your "avgas" reference is not the same as GM or Ford only selling cars that run some third party gizmo. If a muffler company decided to only make mufflers that could only attach to a 12" exhaust pipe I'm certain that GM and Ford would not make cars that had 12" exhaust pipes. Same if a third party app developer decided to only make 32 bit apps, Apple would not produce hardware and operating system that could accommodate 32 bit apps. Is the dog wagging the tail or is the tail wagging the dog?
Apple gave at least 12 years warning that they were transitioning to 64 bit. They gave several years warning that the M1 chip was coming. If third party developers chose to disregard the warnings, and the changing technology, that is not Apple's fault or responsibility.
Yes it is annoying. You should let the makers of these products know that you are disappointed in their inability to upgrade their products.
yep.. we should drop mail to almost all vendors and opensource etc.. to make their product compatible for M1.. apple responsibilities is over after sell.
FWIW, I would shy away from Parallels M1 beta unless I had two M1 Macs.
virtualization yet not supported on M1