Virtualbox For M1 Mac

Virtualbox For Macbook Pro M1
Virtualbox Mac M1 Download
Virtualbox Alternative For M1 Mac
Virtualbox For M1 Mac Download

I’m old enough to remember when Mac used propriety chips in their computers. They were called “PowerPC” or PPC. Proprietary chips mean proprietary code to run them. . Such as it was with the old OS X operating systems. Right around 2005 Apple announced it would transition to Intel chips which most of the rest of the world was running on already. It opened up a new world of software and hardware to the Mac.

People found they could run OS X on Intel PC’s (aka Hackintosh).

Now here we are again 16 years later and Mac has gone their own route and selected another proprietary chip, the M1 which is ARM based and not X86. When you think ARM, think Raspberry Pi.

Virtualbox will not work on an ARM host computer. My quick Google-fu seems to say that the M1 is an ARM-based CPU, so no-go on Vitualbox; keep that old Mac running, or get a refurbished x86 when your war chest builds up again. 64-bit VMs work just fine on typical x86 non-ARM Intel & AMD PCs and Intel Macs. Hi guys, hope y'all doing great! I was wondering if anyone is using (or at least tried) Linux through VM on MacBooks with M1. I'm interested in switching from my 12' MacBook 2015 to the new MacBook Air with M1, but I need to know if it can run Linux through VM and if it really runs smoothly, because in my current one it doesn't run that smooth.

The advantages to doing this are MANY. Apple controls the hardware build and can write tight code for that specific hardware. The chips are FAST.

VirtualBox is an x86 virtualization hypervisor. It only runs on an x86 platform. See While Rosetta 2 will run many x86 apps very well on an M1 Mac, virtualization products are not supported per this Apple document. Jan 25, 2021 3 thoughts on “ Macs with the New M1 Chip – Be Advised ” David Damico January 30, 2021 at 12:45 am. Love your commentary on the M1. Like you, I was running a 2012 Mac Mini prior to the M1 version. I’m now using a Mac Mini M1 at home.

THE DOWNSIDE HERE IS THAT YOU LOSE LEGACY COMPATIBILITY. That old hardware you have connected to USB may not work anymore. That old hunk of software you love may not work anymore. Or the software you love may have to run on top of something called “Rosetta 2” which allows Intel apps to run on ARM OS’s. So there could be hiccups with that as well.

So lets get to my experience:

I built a man cave hobby room that has 3D printers, a vinyl sign cutter and a laser cutter. Most everything in the room was controlled by a Mac mini (Late 2012) which no longer has support for the latest operating system. It has reached the end of its life. Realistically it will still be supported for 2 years or so but old John won’t be. Old John is retiring and has to buy this crap while he still has a check. So I got me a shiny new M1 Mac mini.

So I unbox it and hook it up to my HP monitor which is fairly old and has a DVI input (which I have a DVI to HDMI adapter on).

Boot and then…….nada. Nothing. A couple of flashes and my heart sinks. I think my new Mac mini must have taken a jolt in shipping or something. A quick internet search reveals about 42,612 very angry people that their DVI monitors don’t work.

So just for fun I go grab a new 32″ TV I have and hook it to the HDMI and it boots right up and the display is great. Basically Dr. Google says that you need a USB-C to DVI adapter and things will work fine. Just for fun I actually have a

HDMI Adapter

Okay, I want you to visualize something. The back of the Mac mini has an HDMI port. When I hook an HDMI cable from the Mac to the adapter on the back of the TV……. IT DOES NOT WORK.

When I plug this adapter into a USB-C port on the back of the Mac and hook an HDMI cable to the adapter and the other end to the TV……….IT WORKS!

How in the tap dancing hell does that make sense?

That adapter costs $70 new and I use it for a lot of other stuff. I need it elsewhere. Not only that it ties up one of those fast Thunderbolt (USB-C) ports that I think I’m going to need.

But, lets not lose sight of the fact that my ancient monitor DOES INDEED work now. At any rate, with a new Mac mini with an M1 chip you’re probably going to have to factor in that you need a newer hardware monitor than I have or you will need an adapter. Virtualbox vm for mac os. You can find really cheap HDMI to DVI adapters BUT NOT ALL OF THEM WORK. It’s a mess. And it seems to be an OS software mess. Not a hardware problem.

Next issue I stumbled into is that as much as I hate to admit it…………I run Windows in Virtualbox on my Mac mini. That is until I got an M1 because Virtualbox doesn’t work on an M1. Currently the only way to run Windows is by using a Tech Preview of Parallels and a beta version of Windows 10 for ARM processors.

Serial numbers for photoshop cs6 mac. If you think Windows is an unstable OS try running it on a beta Parallels with a beta non Intel version. It WILL NOT install legacy x86 drivers. I have a Roland GX-24 vinyl sign cutter and it works under software which has its own drivers such as CoCut Pro or EasyCut Studio but the Roland Windows 10 drivers WILL NOT INSTALL. Fortunately for me EasyCut Studio Mac version works fine on the M1 and I can do 99% of what I want to do on it. My heavy lifting software, CoCut 2017 (Windows only) does in fact install on bastardized Windows 10 ARM and it does work so I’m set.

My laser etcher uses a program called LaserGRBL which is Windows only and it also installs. I do find that when I run the program in Parallels it’s a little goofy getting the USB connected laser machine accessible to the virtualized Windows and I even found I might have to reboot MacOS to get it back visible to Mac. 99.9% to 100% of what I do with the laser machine can be done in a Mac program called “Lightburn” which works fine on the M1.

My 3D printer software (PrusaSlicer) works fine under MacOS on the M1.

Finally I have a Police Scanner in the other room which has 3rd party, Windows only software called ProScan which allows me to listen to the scanner on my local network. It took me quite some time to get it working and the issues were with Parallels and the Windows sound devices. Right at this moment I’m not sure what I did right but it is working right now. I’m scared to reboot the Windows session!

Make no mistake though, Parallels Tech Preview running Windows 10 ARM is a turd of epic proportions. It crashes FREQUENTLY and almost never connects to the internet first time causing me to have to run the troubleshooter. Running the troubleshooter resets the ethernet adapter which connects it to the internet but I’m running on Wifi through Parallels and not using ethernet so who knows what the hell is going on?

Safari 5 for mac download. PROS AND CONS

PROS

Probably the biggest advantage is that the chip architecture between the iPhone and iPad and these new M1 chips is very similar. You can run iPhone and iPad apps on your M1 app. That may or may not seem useful at the moment but what it means is that the Mac ecosystem can get way tighter and way better. Stand by for great things from the ecosystem.
Mac M1 is lightning fast. Even lightning says “Phew” when it sees the Mac M1 operate.
Specific Code tied to specific hardware is always best. When you have something like an Intel platform and 4 million people make devices and drivers for it there are going to be problems.
Not as expensive as most Macs
Rosetta 2 seems to run all of my Intel Mac programs that I use and I’m pretty damn diverse. I have a lot of junk.
Lots of ports and 3rd party vendors make external hard drive adapters that have lots more ports. It is best to buy the cheap 256 GB Mac and get a hard drive caddy with extra ports. It will save a ton of money over buying a Mac with a 1 TB drive. A. Lot. Of. Money.

CONS

Big issues with legacy hardware with x86 drivers
Big issues with running virtualization software
Big issues with HDMI to DVI
Using an adapter to hook up a DVI monitor makes you lose one of your high speed Thunderbolt ports.
Lots of users claim horrific Bluetooth issues (no problems for me).

Conclusions

If you are a Mac only dude living in a lonely world (sorry that song was just on the radio) then an M1 is your Huckleberry. It’s super fast and will run your Mac ecosystem with aplomb. (Sorry, I just wanted to say aplomb somewhere).

If you have a roomful of old USB devices that you need Windows software and legacy x86 drivers to operate then maybe you better just get a Windows computer.

If you need to run other OS’s in virtualization software get another laptop and slap Ubuntu Linux on it because you ain’t gonna virtualize on this Mac M1, at least not yet.

Hi All,
While it will be macOS 11 (it was released as a developer beta as 10.16), macOS Big Sur seems to have some Kernel extension changes that i think will require Virtualbox fixes. Here is the error I get trying to launch my Ubuntu VM on 6.1.10.
Failed to open a session for the virtual machine Ubuntu Server.
The virtual machine 'Ubuntu Server' has terminated unexpectedly during startup with exit code 1 (0x1).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
And
VERR_VM_DRIVER_OPEN_ERROR (rc=-1911)
Make sure the kernel module has been loaded successfully.
where: suplibOsInit what: 3 VERR_VM_DRIVER_OPEN_ERROR (-1911) - Was not able to open the support driver. Generic open error used when none of the other ones fit.
From the macOS 11 Big Sur Release Notes:
Kernel
New Features
The kern.argmax limit has been increased, allowing programs to receive longer argument lists. (48661669)
Darwin kevent now allows non-parent processes to register for NOTE_EXITSTATUS, which delivers the same values as the wait() family of functions in the event data. Refer to the wait4() man page for more information. This event is subject to the following security checks:
The requesting process is allowed to send signals by sandbox restrictions.
The requesting process and the target process are running as the same user or the requesting process has root privileges. (58134463)
Known Issues
Installing a new kernel extension requires signing in as an Admin user. During kernel extension development, every time a kernel extension is changed, it must be signed and notarized. In both cases, your Mac must be restarted to load the extension. (55068348)
Remote panic dumps aren't currently available. (57915324)
New in macOS Big Sur 11 beta, the system ships with a built-in dynamic linker cache of all system-provided libraries. As part of this change, copies of dynamic libraries are no longer present on the filesystem. Code that attempts to check for dynamic library presence by looking for a file at a path or enumerating a directory will fail. Instead, check for library presence by attempting to dlopen() the path, which will correctly check for the library in the cache. (62986286)
kmutil install might fail to build a development kextcache. (63772702)
Workaround: Copy the release .elides to the locations of the development .elides:
sudo cp /path/to/livemount/System/Library/KernelCollections/BootKernelExtensions.kc.elides /path/to/livemount/System/Library/KernelCollections/BootKernelExtensions.kc.development.elides
sudo cp /path/to/livemount/System/Library/KernelCollections/BootKernelExtensions.kc.elides /path/to/livemount/System/Library/KernelCollections/BootKernelExtensions.kc.kasan.elides
sudo cp /path/to/livemount/System/Library/KernelCollections/BootKernelExtensions.kc.elides /path/to/livemount/System/Library/KernelCollections/BootKernelExtensions.kc.debug.elides
sudo cp /path/to/livemount/System/Library/KernelCollections/SystemKernelExtensions.kc.elides /path/to/livemount/System/Library/KernelCollections/SystemKernelExtensions.kc.development.elides

sudo cp /path/to/livemount/System/Library/KernelCollections/SystemKernelExtensions.kc.elides /path/to/livemount/System/Library/KernelCollections/SystemKernelExtensions.kc.kasan.elides

Virtualbox For Macbook Pro M1

sudo cp /path/to/livemount/System/Library/KernelCollections/SystemKernelExtensions.kc.elides /path/to/livemount/System/Library/KernelCollections/SystemKernelExtensions.kc.debug.elides
Use only absolute paths with the --volume-root option of kmutil, and don't use a trailing /. (63773848)
After removing a DriverKit extension, restart your Mac to complete uninstallation. (63995046)
Adhoc signed kernel extensions are displayed with a developer name of unknown in update dialogs and in Security preferences. (64215260)
Symbols exported by both xnu and Apple kernel extensions will change. Recompile your kernel extension with each update to macOS Big Sur 11 beta to ensure compatibility. (64262563)
Moving a kernel extension bundle out of /Library/Extensions might not completely uninstall it. (64331929)
Workaround:
Remove the extension from /Library/Extensions.
Boot to macOS Recovery.
Run Terminal.
Enter the command kmutil invoke-panic-medic.
Restart your Mac.
Follow the prompt to open System Preferences and navigate to Security & Privacy.
Follow the prompt to restart.

Virtualbox Mac M1 Download

An unexpected System Extension Updated alert for third-party kernel extensions which are included in macOS might appear. These include: Accusys, Inc., ATTO Technology, Inc., Areca Technology Corporation, CalDigit, Inc., HighPoint Technologies, Inc., Promise Technology Mobile Apps, and Other World Computing. (64337113)

Virtualbox Alternative For M1 Mac

Deprecations