driverose.blogg.se - Boot camp assistant m1

I do not think it will be the dual system version (apps execute directly from the dock etc) but more the old select before boot / at boot time environment with shared disk areas. Gut feel - if the Qualcomm deal is real and comes to an end soon (something the Pi users are crying out for) then yes Windows will come to the Mac BUT it will not be the full Intel version for awhile but a strange hybrid of the ARM / M1 / Intel cross compile. They also warn that you must have a VHDX or ISO of an ARM OS - no Intel translation is possible. Parallels 18 is still supporting Windows the best it can - over 200K apps are now running they claim and Windows can be loaded direct from Microsoft as a VM install option. So you have hardware that can boot and run multiple operating systems but limited specifically for hypervisor support for an operating system that users want but has zero signs of being available on any other chipset bar one!ĭebian under Parallels is solid (assuming you use their RISC versions - Intel versions are a bit hit and miss) but shows it's a VM rather than native still as it needs the hypervisor code to launch as the app launches rather than being 'pre-loaded' when Mac OS starts.

It is heavily rumoured that Microsoft are tied into an agreement that Windows on Arm is limited to Qualcomm chips only as they helped MS develop the underlying hardware interfaces.

Apple did not discuss this at first but the team working on Asahi found you could (possibly had to) set this up from the Mac OS rather than the boot code.

There is nothing in the boot code that stops another operating system from booting.

I only hope the hardware developers have early access to the Pro test machines.

Rosetta will not handle kernel extensions - a bit of an issue for the Mac Pro guys with 'odd' hardware that has dedicated interfaces (esp video and sound cards).

No solid idea why but I think its to force the maximisation of the M1 abilities rather than a quick 'bodge'.

Rosetta will not translate VM hypervisor code hence the delays getting a good selection of VM hypervisors - they are having to go back to basics rather than cross-compile or translate.

It does not handle some of the newer commands introduced with the Sandy Bridge and Haswell processors and this will be a limit till v3 comes out.

One of the reasons Rosetta 2 is so good is that the M1 chip set was designed to emulate core Intel opcodes in the RISC chips at hardware level rather than full software translation.Interesting things that may point to the future: